The first engagement, scoped
Drafted from the founder working session, 12 June 2026. The engagement design below reflects the embedded partner’s ground truth and the founding team’s sequencing intent. Items still open are listed at the end.
What the first-play entity looks like from the inside
The pattern is familiar from the founding team’s prior embedded work in billion-dollar infrastructure businesses: organisations with heavy obligations and genuinely low digital maturity, because technology is not what they do. These are construction and utility organisations at heart. They carry plenty of hard, hardware-based technology, which brings its own software problems, but the corporate digital layer is thin: no real internal team, most capability outsourced, applications bought piecemeal that don’t mesh, no architecture or strategy holding it together, and procurement capability that is weak precisely where their regulatory exposure makes procurement matter most.
That last point is the live opening. The embedded founder is currently supporting the entity through a system procurement (governance/risk/compliance class), built the entity’s budget in his current engagement, and has developed a proof-of-concept tool on his own initiative. The entity hasn’t seen the tool yet — that demonstration is a card the founding team holds, to be played when the first bounded engagement is framed.
The delivery thesis this engagement must prove
A regulated utility cannot let its engineering team, let alone its finance function, build mission systems with AI directly, no matter how capable the models get. The accountability does not exist: when something fails, the organisation needs a counterparty, support, and a throat to choke, and the frontier AI companies are not providing that layer. The venture’s position is that the AI does the production work, but what the client buys is a supported product with a responsible party behind it. Engagement one exists to prove that position holds in regulated reality.
The architecture follows from the same logic. This cohort already self-manages data centres because regulation demands it, so delivery is designed local-first: a tiered model stack — on-prem/local models for the regulated core and routine volume, open-weight models via API, and frontier models reserved for the hardest judgment-grade calls — with routing deciding what runs where. That design does triple duty: it holds compute cost down (section 8), it keeps sensitive data inside the client’s own environment, and the local tier is the portability hedge behind our sovereignty position — if a frontier model is recalled or restricted (as one was, worldwide, in June 2026), the regulated core keeps running. This is not theoretical: one of the founders already runs exactly this hybrid — a locally-deployed open model alongside a frontier model — in a live, regulated-grade quant system.
Scope and entry
- Entry: the live procurement, not a cold pitch. The work the entity already trusts the partner with extends naturally into the first bounded deliverable; the productised readiness assessment (section 9) remains the repeatable wedge for entities two onward.
- Bounded first, function later: one deliverable with a defined edge, instrumented from day one (senior hours consumed, correction rates), not “be the digital function” from day zero.
Sequencing — settled in principle
Two of the three founders proceed now and prove the model; the third remains entirely outside the venture until a clean exit from current employment, then joins. Nothing runs through the employed founder in the interim. This is deliberately a trust-based structure: if the founding relationships cannot carry that arrangement, the venture was never going to work. (Subject to legal review before any client contract is signed.)
What success looks like — the 90-day bar
One signed, paying, retained client within 90 days of launch. That is the whole threshold. The benchmark that sets it: new tier-two-and-below consulting firms routinely take far longer than a quarter to land their first client, and some fail without ever landing one — so a signed and retained client inside 90 days, entered warm, would put this venture meaningfully ahead of the reference class. Everything else is instrumentation rather than success criteria: senior hours consumed per month and correction rates (the quality-ceiling evidence), and whether the engagement generates a referral conversation (the GTM evidence). A second and third client then prove the revenue model repeats, and that proof is the scaling story: demonstrated reliable revenue in a regulated cohort, ready to run across the REZ pipeline.
Still open
- Who inside the entity sponsors the first contracted engagement, and at what budget line
- Where the boundary sits between the partner’s current personal contracting and the venture’s first contract — and what the legal review says about the transition