Own the Google GDC answer personally, commit nothing to Google, and require Hassan to put the ask in email

September 11, 2026 at 3:05 PMstrategyhigh

Situation

In the group DM with Greg Kurtzer, Bjorn Hovland and Brady Dibble, asked who owns a Google GDC question, Peter answered that the answer to the question specifically is Me, that CIQ can ask, but that CIQ cannot commit to Google. He then added a paper-trail condition: get Hassan to send the request to Peter in email, cc-ing Brady and Bjorn, because Peter will need that.

Reasoning

Peter separated three things the question had collapsed together - who owns the answer, whether CIQ can explore it, and whether CIQ can promise it. He claimed the first, granted the second, and refused the third. Requiring the request in email with Greg-level and Product-level people copied converts an informal partner ask into a record: it forces Hassan to state precisely what is being requested, gives Peter something to point at if the ask later grows, and makes the internal audience for the commitment explicit before any commitment exists.

Additional Context

The GDC Term Sheet Review with Bjorn, Nathan, Brady and Kelly Hall ran the same morning, and Bjorn had flagged in #leadership-roundtable that CIQ has been doing good faith work for quite some time and Google needs to get moving on closing the contract. So the refusal to commit is load-bearing - CIQ is being asked for more while the contract is still open.

Observed Evidence

Two direct quotes minutes apart claiming ownership, refusing the commitment, and setting the written-request condition, against the roundtable context that the Google contract is still unsigned.

Matching Patterns

50%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(names the owner of the lane explicitly - the answer is Me, separates asking from committing rather than answering the request as posed)
30%
Protect Engineering Capacity(refuses to let a partner ask become an engineering commitment before the contract exists)

Confidence Breakdown

34/35
Evidence
26/30
Pattern
20/20
Source
7/15
Corroboration

Reasoning Depth Analysis

Org Signal:Signals that partner asks reaching Engineering through informal channels get pulled onto Peter desk and onto the record before anything is promised, and that good faith work is not the same as a commitment.
Who Affected:Brady Dibble and Bjorn, who are now copied recipients and therefore accountable witnesses to the ask. Greg, who sees the CTO claim the lane. Hassan, who has to be explicit in writing.
Precedent:Sets the precedent that a verbal or Slack-relayed partner request gets converted to email with leadership cc-ed before Engineering engages - a cheap, repeatable gate against scope creep on an unsigned deal.
Consequences:Real: no commitment was given, and the ask is now blocked pending a written request.
Timing:Now rather than later because the Google contract is still unclosed while CIQ has already been doing unpaid good faith work, so the cost of an informal yes is at its highest.

Source

reflection

AI Confidence

87%

Related Context

💬
Group DM with Greg Kurtzer, Bjorn Hovland, Brady Dibble

slack

So two things... I think the answer to your question specifically is Me. And we can ask. We cannot commit to Google.

💬
Group DM with Greg Kurtzer, Bjorn Hovland, Brady Dibble

slack

Also - get Hassan to send me the request in email, cc-ing you and Bjorn.... I will need that...

💬
#leadership-roundtable

slack

Bjorn Hovland: google update. We have been doing good faith work for quite some time. They need to get moving on closing contract.

Outcome

Peter remains single owner of the Tissa conversation; second contract draft in hand

Rating: 4/5

Decision ID: 33031d87-b427-4c02-b0ba-8d4ae7ad07ac