Google ELTS: pay or I stop the work - and CIQ eats the disputed 150k out of the existing discount to remove the excuse

July 29, 2026 at 9:06 PMstrategycritical

Situation

In the 7/28 CIQ ELTS payment discussion with Google (Madhu, Alyssa, Arun, Katur and Kelly Hall), Peter went in deliberately hot and said so. Madhu was trying to hold Kelly to account for who made a technical decision back in February, with the implication that if CIQ made it Google would not pay for work since then. Peter refused the premise - these are technical decisions, they get made by the team, they get recorded by your people as the decisions of the consolidated team, and then we move forward - and then removed the money as an obstacle by offering to absorb it against an existing concession: I gave you a 250,000 dollar discount over here, so you are bitching about 150,000. I will shake your hand right now that that is on us. That 250,000 discount just turned into a 100,000 discount. With the excuse gone he put the actual question: are we getting paid or are we not getting paid, and if we are not getting paid I am taking my toys and going home. Madhus boss and others stopped the meeting and committed to closing it out by the next day. The call also ended abruptly, which Peter read as someone telling Madhu to stand down.

Reasoning

Peter treated the 150k as the pretext rather than the dispute, so he bought it off cheaply to expose whether Google intends to pay at all. His stated read: 150,000 dollars matters to us, it does not matter to Google one bit, that is a rounding error - and they are getting an operating system from it to run their sovereign cloud. Therefore if they let us walk for this, there is something we dont know, and we were never going to get paid no matter what - CIQ was the backup plan. Conceding the money converts an unresolvable he-said-she-said about February into a single binary he can act on. He also refused the retroactive-attribution frame on principle, because accepting it would mean every future engineering discussion has to be paired with a does this impact our contract discussion, which he told Kelly would strip engineers of the flexibility to pick the right solutions going forward. He priced the downside honestly and accepted it - Bjorn will be upset, it is a time suck and a big logo loss - and staked the call on his own read: I am a betting man.

Additional Context

Follows the 7/21 decision to hold the Google 6.18 image as contract leverage, the 7/24 release of the 6.18 build while holding the line on future deliverables, and the 7/24 slow-roll of Googles kernel-build documentation request. Kelly Hall had documented the contract language and emails and noted Madhu was also trying to a la carte 8.6 and renegotiate terms agreed years ago, on roughly 300k. Peter told Nathan on 7/29 that LTS support payments are behind and they have promised a resolution today, so I will know more in 24 hours. Alyssa confirmed by 7/28 evening that Google was working on issuing the ELTS PO, and Peter asked Kelly to pass on a thank-you for her rationality through all of this.

Observed Evidence

Peters own first-person account of the call in a recorded 1:1 the following day, with the pre-call reasoning captured verbatim in the Kelly Hall DM, the Nathan DM confirming the 24-hour resolution commitment, Alyssas written confirmation that the ELTS PO is being issued, and the calendar record of the meeting and attendees.

Matching Patterns

70%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(1 keyword match (contract), involves Kelly Hall and Bjorn Hovland, same category (strategy), refuses the presented frame and substitutes a single actionable criterion)
40%
Small Circle for Sensitive Operations(1 keyword match (leverage), same category (strategy))

Confidence Breakdown

33/35
Evidence
24/30
Pattern
20/20
Source
15/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering decisions made by the consolidated team are final and are not retroactively reopened as commercial liabilities. Also - CIQ will pay real money to convert an ambiguous dispute into a clean yes-or-no.
Who Affected:Kelly Hall, who was the one being held to account and is now backed publicly; Nathan Blackham and the kernel team, whose future deliverables are the thing being withheld; Bjorn, who Peter expects to be upset about the logo loss; and every engineer who would otherwise have to run a contract-impact check before choosing a technical approach.
Precedent:Establishes that CIQ will buy off a pretext to force the real question, and that walking away from a marquee logo is an acceptable outcome when the relationship is not paying. Also sets that retroactive decision-attribution is refused on principle, not negotiated.
Consequences:Real on both sides. The 150k concession is a genuine handshake offer, and the stop-work threat is genuine - Peter said explicitly he is fine either way and accepted the logo loss.
Timing:Now because payments were already behind and Madhu had escalated to relitigating February - waiting would have let the retroactive-attribution frame become the accepted basis for the whole engagement.

Source

reflection

AI Confidence

92%

Related Context

🎥
Baek 1:1, 7/29 - Peter recounting the Google call

fathom

Homie not playing this. We are not getting paid. So are we getting paid, Google, or are we not getting paid? And if we are not getting paid, I am taking my toys and going home... Kelly, these are technical decisions. They get made by the team. They get recorded by your people as the decisions of the consolidated team. And then we move forward. And I gave you a 250,000 dollar discount over here. So you are bitching about 150,000. I will shake your hand right now that that is on us. And CIQ will eat that 150,000... That 250,000 discount just turned into a 100,000 discount. So what are we doing? ... Unless you are bitching about something that is bigger than 250,000, can you pay us? And if you dont pay us, I am done doing work. ... other people in the meeting, including her boss, stopped the meeting. They were like, we hear you. We understand. We will close this out by tomorrow.

🎥
Baek 1:1, 7/29 - Peters read on why

fathom

we are talking about 150,000 dollars, which matters to us. It does not matter to Google one bit. That is a rounding error. And they are getting an operating system from it to run their sovereign cloud. There is, in my mind, if they let us walk for this, there is something we dont know... And we were never going to get paid no matter what. (Baek: We were their backup plan) Correct. We are never getting paid. So, I am fine either way.

💬
DM with Kelly Hall, pre-call

slack

I am so done with that woman. Does she not realize that if she were to prevail here: a) it would not get them more money b) it would mean that going forward, ALL engineering discussions would have to be paired with a does this impact our contract discussion... engineers would not have the flexibility to pick the right solutions going forward. It is just so stupid.

💬
DM with Nathan Blackham, 7/29

slack

good on the extension of work. LTS support payments are behind and they have promised a resolution on that today. So I will know more in 24 hours.

📅
CIQ ELTS payment discussion, 7/28 12:00 PDT

calendar

Attendees: mdewaikar@google.com, alyssap@google.com, katur@google.com, ymadhu@google.com, khall@ciq.com, pnelson@ciq.com, arunpnair@google.com

Outcome

Agreement closed Jul 30. The relationship then expanded rather than cooled - Google came back Aug 10 with a paid live-kernel-patching quote request on top of the existing contract.

Rating: 5/5

Decision ID: 2250827b-ae98-4225-a199-7caadfe38698