Hold the finished Google 1.18.1 deliverable until the contract signs - release it the moment they sign

November 9, 2026 at 3:46 PMstrategyhigh

Situation

On Nov 5 Google GDC put its CIQ purchase order on hold for internal review of the CVE terms while still asking for new work. Peter had 1.18.1 finished and ready to ship. He told Kelly and Bjorn CIQ had NOT given Google the final deliverable and he would sit on it until he heard back from Tissa, and emailed Tissa that the 18.1 work was done but a pause on signing is a pause on payment for work done months ago, which is not a way he can run a company. On Nov 6, when Google confirmed the contract was moving, he told Nathan and Justin: We can give 1.18.1 to Google. They are signing.

Reasoning

Hypothesis (auto-logged, not yet reviewed): withholding something Google is desperate for is the one lever that converts goodwill into a signature without escalating to a threat or stopping work. The hold was tied to a single condition (signing) and released the moment it was met, so it reads as leverage rather than punishment. It also protects the team from being burned on weekends for free work, which Peter named in the leadership meeting.

Additional Context

Bjorn raised the PO hold in Weekly Department Leadership on Nov 5 and suggested Peter call Tissa, saying at some point he would say pencils down. In the Fathom transcript the lines about sitting on the deliverables are labeled Gregory Kurtzer but match Peter verbatim in Slack and email the same morning - treated as a speaker-label error. Longer term Peter told Tissa he is aligned on moving to an all-you-can-eat contract.

Observed Evidence

Slack 11/5: we have NOT given Google the final deliverable, I will sit on it till I hear from Tissa. Email to Tissa 11/5: our 18.1 work is done, a pause on signing means a pause on payment. Slack 11/6: we can give 1.18.1 to Google, they are signing.

Matching Patterns

45%
Promise Only What Is Inside CIQ Control(google contract, commercial boundary)

Confidence Breakdown

33/35
Evidence
20/30
Pattern
19/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering work for Google is commercial work that needs paper; delivery follows the contract.
Who Affected:Kelly (account owner) gets a concrete lever with Google procurement; Justin and Nathan learn their finished work is held, not lost.
Precedent:A finished deliverable can be held against an unsigned contract, and is released as soon as the condition is met.
Consequences:Real: the build was held about a day and released on signing.
Timing:Google paused the PO while escalating new asks and the team was working weekends.

Related Context

💬
Kelly/Bjorn/Peter group DM

slack

We have NOT given Google the final deliverable of the three we were working on. I am going to sit on it at least till I hear back from Tissa.

📧
Re: 1.18.1 Update and follow up

email

Google needs to understand that a pause on this signing means a pause on payment for work that happened months ago. I am not in a position to run a company that way.

💬
Peter/Nathan/Justin group DM

slack

We can give 1.18.1 to Google. They are signing.

🎥
Weekly Department Leadership 2026-11-05

fathom

I have deliverables for them today and tomorrow that they are desperate for. So I can sit on those.

Outcome

No outcome recorded yet.

Decision ID: 3710c91b-ec1a-458f-88b5-a8ff3d045897