GDC new ask after landing Anthropic - write down what we believe, parrot it back, give an ETA assuming funded, and use it to win the added 300K without slowing the base contract

Situation

On 10/29-10/30 Tissa came back with a larger ask after Google landed a big opportunity (Anthropic). Peter directed Nathan and Justin: before spending any time, write down what CIQ believes is true and send it to Tissa to validate - (1) what is delivered Monday, (2) the additional ask parroted back to confirm version and build, (3) when CIQ could have it assuming it is funded. Tissa is working to get CIQ about 300K more, taking GDC toward 1M plus royalties next year, and this must not slow signature of the existing contract. Peter relayed Tissa request that CIQ engineers stop saying that is not in the contract and say we will talk to Pete instead. On 10/30 he asked for the CIQ ETA column filled, including future releases, to talk through any gap between desire and capability.

Reasoning

After a week of version confusion, a written playback is the cheapest way to avoid building the wrong thing. Assume-funded separates engineering feasibility from the commercial question so the gap becomes a priced add-on Peter and Kelly sell. Routing no to Peter keeps engineer-to-engineer relations clean. The base contract is about to close, so the new ask is an upsell, never a reason to reopen.

Additional Context

Confirmed by Peter without changes. Follows the same-day decision on the full kernel IBT ask.

Observed Evidence

1). What are we delivering on Monday 2). parrot back this additional ask 3). When do we think we could have it by (assume it is funded). He has asked that we stop saying in meetings with his engineers that is not in the contract and instead just say we will talk to Pete. / let us be super clear with him in writing about what we are giving them.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis