Gate Rakuten 8.6 / RT-kernel support work on a signed 1.6 to 1.8M expansion that funds dedicated headcount

July 6, 2026 at 11:29 PMstrategymedium

Situation

Decided that the risky, currently unsupportable Rakuten 8.6 / RT-kernel support work will either not be done at all or only be delivered tied to a signed contract expansion in the 1.6 to 1.8M range that funds dedicated Rakuten headcount on CIQ side. The bar is enough to cover roughly two dedicated engineers, not an arbitrary large number. Peter forwarded the engineering teams infrastructure objections to Bjorn to arm the customer conversation.

Reasoning

CIQ tore down the 8.6 infrastructure when support expired and would have to rebuild it and hire specific engineers to support the RT kernel, which is a completely different codebase. Peter refuses to absorb that cost speculatively: the work only happens if the deal economics justify it and fund the dedicated headcount. This is the same deal-must-fund-the-engineering-investment posture he applied to Everfox and the Rakuten margin line, made concrete with a specific dollar floor and a headcount rationale.

Additional Context

Confirmed by Peter. Bjorn owns the customer conversation; Peter set the internal engineering-investment gate. Engineer Jonathan Maple flagged the nonexistent infrastructure and oversubscription, which Peter forwarded to Bjorn.

Observed Evidence

7/3 Nathan DM: we are looking at a 1.6 to 1.8M expansion, we will not be doing the work without that; dedicated Rakuten headcount on our side; enough to cover two heads, not 2M. 7/2 Maple DM: either not going to do this or it will be tied to a signed expansion; the RT kernel is a completely different codebase.

Matching Patterns

62%
Route Non-Differentiating FTE Classes to Partners(scope/headcount gating tied to who pays for the investment)
50%
Protect Engineering Capacity(refuse to absorb unfunded engineering scope, headcount)

Confidence Breakdown

30/35
Evidence
18/30
Pattern
19/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering does not take on rebuild-and-support cost speculatively; a deal must fund the dedicated headcount it requires before the work starts.
Who Affected:Bjorn/Ramesh (customer negotiation), Nathan (would staff it), Jonathan Maple (raised the infra objection).
Precedent:Same deal-funds-the-investment posture as Everfox (6/30) and the Rakuten margin line (6/18); here made concrete with a dollar floor.
Consequences:Real: the work is conditional on a signed expansion; Peter will walk otherwise.
Timing:Rakuten pushing for the support ahead of Bjorn customer conversation; Peter set the floor before that talk.

Source

reflection

AI Confidence

80%

Related Context

💬
DM with Nathan (7/3)

slack

We are looking at a 1.6 to 1.8M expansion. We will not be doing the work without that. It would come with dedicated Rakuten headcount on our side. Enough to cover two heads though, not 2M.

💬
DM with Jonathan Maple (7/2)

slack

We are either not going to do this, or it will be tied to a signed expansion. I hear you clearly on the nonexistent infrastructure.

Outcome

No outcome recorded yet.

Decision ID: 5e0de103-e53c-462e-b3e4-79a625c9a015