Google Contract Engineering Justification

March 30, 2026 at 10:49 PMstrategyhigh

Situation

Directed Nathan Blackham to provide engineering cost breakdown for GDC work, and Kelly Hall to provide revenue numbers, building justification for higher pricing in Google contract renewal/expansion. Nathan confirmed ~$800K/yr cost for 1-2 engineers on GDC with zero profit, and CIQ actually spends more on GDC than GCE.

Reasoning

Financial runway is tight (per AMA context), and the Google contract is one of the critical deals. Peter confirmed through Nathan that CIQ is underwater on GDC — spending ~$800K with zero profit. Commercial discussion is tomorrow (Mar 31), so this is deliberate last-minute preparation. Directed team to target 'midpoint of the chart' — defensible numbers without being unreasonable. Multi-year document covers future plans too.

Additional Context

Kelly Hall initiated group DM thread saying 'need to align on engineering justification in advance of commercial discussion tomorrow. Will need to align tonight.' Peter brought Nathan in for cost data and directed the narrative framing.

Observed Evidence

Peter asked Nathan: 'how much more would we need to charge them so we were getting paid appropriately for the work we are doing.' Nathan said ~$800K cost, zero profit. Peter directed: 'Make the numbers add up to about the midpoint of the chart' and 'I need some sort of breakdown that semi-justifies those numbers.'

Matching Patterns

40%
Protect Engineering Capacity(keyword match on resources, same category strategy)

Confidence Breakdown

33/35
Evidence
18/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:Peter personally driving contract prep signals this deal's critical importance to company financial health
Who Affected:Entire engineering org — per AMA, landing one major deal unclenches hiring freeze
Precedent:Sets baseline for how CIQ prices future engineering partnerships with hyperscalers
Consequences:If pricing is too aggressive, risk losing the deal. Too conservative, remain underwater. Midpoint is deliberate.
Timing:Commercial discussion tomorrow Mar 31 — last-minute but deliberate information gathering

Source

reflection

AI Confidence

82%

Related Context

💬
Group DM - Nathan/Kelly/Max/Peter

slack

Starting this new thread for us to align on engineering justification in advance of commercial discussion tomorrow

Outcome

No outcome recorded yet.

Decision ID: 3abe851e-92f1-4f18-91e7-6ae897663086