Google Scope Change - Hold the Line on Commercial Terms

January 12, 2026 at 4:23 AMstrategyhigh

Situation

Decided to personally join the Monday lunch meeting with Tissa to lead negotiation on Google scope change. Google was trying to bundle Rocky 8 and 9 into one version (reducing from 8 to 5 versions) and push release next format without updated commercial terms.

Reasoning

Google is using pressure tactics and needs executive pushback. The commercial implications are significant (~$300K/year in Extended LTS revenue at risk). Trust has eroded with Google using aggressive negotiation tactics. CTO presence signals this is a line CIQ will not cross. Need to protect commercial terms before giving away technical changes.

Additional Context

Google trying to get new release schedule without paying for it. Jamie was being pressured by Aditya on the technical call. Skip has done the scripting work for release next but has not deployed it - maintaining leverage.

People Involved

Kelly Hall, Jamie Brooks, Max Spevack, Tissa, Aditya

Source

reflection

AI Confidence

90%

Related Context

🎥
Google Scope Change Status

fathom

We almost gave away the new release schedule without commercial terms. So we were able to catch that and put pause... Peter is now not traveling on Monday, so hes going to join me for lunch with Tissa.

Follow-up Todos

Suggest follow-up todo

Follow up with Kelly on Tissa lunch outcome

Due: Jan 14

Check in with Kelly after the Monday Google meeting to understand how the Tissa lunch went and what the next steps are on the scope change negotiation. Key questions: Did we hold the line on commercial terms? What is the path forward for Extended LTS revenue protection?

Why: Peter was not invited to the Tissa lunch despite planning to join. Need to stay informed on this critical negotiation that protects ~$300K in Extended LTS revenue and sets precedent for how Google negotiates scope changes.

Outcome

★★★★☆(4/5)

Direction given to Kelly to meet with Google and hold the line on not doing free work. Execution delegated appropriately.

Recorded on January 12, 2026

Decision ID: 59b90ab9-acf1-4cca-b696-ec2ad6aad531