Protect the inked Core42 deal - no Stratum and no new commitments until we have done discovery with the end customer

September 25, 2026 at 8:10 PMstrategyhigh

Situation

Bjorn wanted CIQ positioned to deploy Stratum (CIQ Kubernetes) on the first Core42 cluster after Core42 mentioned installing Kubernetes post-handoff. Peter walked him back: the question is not whether Stratum can be deployed (it can) but whether it meets the end customer need, which is unknowable until CIQ talks to that customer. Stratum is a child of RKE, not Rancher, and has never been deployed outside Wolford environment. Aggressive promising belongs in the sales motion; once a deal is inked, do not add commitments that could risk it. In the Core42 pre-deployment call Peter told Core42 CIQ has a Kubernetes offering but wants to understand exactly what the customer wants before recommending anything, and on Friday listed the discovery questions: what applications, why Kubernetes, how they interface with it, and what distribution experience their people have.

Reasoning

The first Core42 cluster is a whale-landing deployment - Peter said winning it is enough to make everyone rich by itself, and Core42 loving CIQ wins the rest of the data center. A new Kubernetes platform pushed into a customer with Rancher expectations would be an unforced error that could cost the relationship. The risk is not trust in Wolford or engineering ability; it is fit to an unknown use case. Discovery resolves it cheaply, and a later Rancher-to-Stratum migration path remains an option.

Additional Context

Bjorn agreed after the Stratum convo and committed not to do anything that would blow up the deal; Adam Jackson tasked with getting CIQ in front of the end customer. Wolford noted using Stratum would require the whole PIC team to harden it through late October.

Observed Evidence

Stratum convo: The question is not can we deploy Stratum, it is does Stratum meet the customer need, and that we cannot know until we talk to the customer. Ryan 1:1: I think I have walked him away from that. Pre-deploy call: deferred any Kubernetes recommendation pending use-case discovery. Friday Slack: explicit discovery question list.

Matching Patterns

45%
Promise Only What Is Inside CIQ Control(customer commitment, deal risk)
30%
Decide on the Precedent, Not the Case(general rule: sales motion vs post-signature)

Confidence Breakdown

33/35
Evidence
20/30
Pattern
19/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering will not let product enthusiasm add scope to a signed deal; post-signature, protecting the win outranks expanding it.
Who Affected:Wolford and the PIC team (spared a hardening crunch), Ryan delivery team, Adam Jackson who owns getting the customer meeting, Bjorn GTM plans for Stratum.
Precedent:General rule: promise aggressively while selling, stop adding commitments once inked. Consistent with the 8/24 call to declare SOW1 won and forbid reopening anything that does not need reopening.
Consequences:Stratum stays off the first cluster unless discovery shows fit; a later migration path (Ubuntu to Rocky, Rancher to Stratum) is the fallback for getting CIQ products in.
Timing:Core42 mentioned Kubernetes days before the build-out; the window to add scope was open and Bjorn was moving on it.

Source

reflection

AI Confidence

86%

Related Context

🎥
Stratum Convo (9/24)

fathom

I am super comfortable with, during a sales motion, balls to the wall... This is different for me because we have inked a deal. And I do not want to lose it.

🎥
Ryan <> Peter 1:1 (9/24)

fathom

I want to make sure we win the win in front of us and bank that... So I want to be really careful about adding anything new to our commitments.

🎥
Core42 & CIQ Pre-Deployment Meeting (9/24)

fathom

we have a Kubernetes offering, but I would like to understand exactly what the customer wants to do with it before we would make a suggestion one way or another.

💬
Group DM with Bjorn, Wolford, Anderson, Jackson

slack

I want to know what applications they want to run, why they want k8, how they interface with it, why they think they need to interface with it...

Outcome

No outcome recorded yet.

Decision ID: 9cad23b7-50b2-4f6e-b11f-87bafe3e3ad7