Design-Partner Program

The structured motion that turns a modeled engine into a measured one — and a pipeline into proof.

Confidential · June 2026 · For discussion with prospective investors and partners. Illustrative figures throughout. Connectors are built but have not yet run against a live system; this program funds the first live connection.

The gap this closes

Aperture is built and tested on synthetic data. The "$121k / 22% shadow-AI" readout is the real engine running on a synthetic PRNG seed — a modeled result, not a customer outcome. The honest gap in our story is demand-side proof: no enterprise has yet pointed the engine at one of their own systems. The Design-Partner Program is how we close that gap by structuring the motion, not by overstating what exists today.

What we are looking for

One or two regulated enterprises — health plans, insurers, financial institutions, or property-tech operators handling sensitive estates — willing to point Aperture at a single real administrative or billing API. We are not asking for a platform commitment or a broad rollout. We are asking for one connector, one scoped API, and the access to produce a measured readout. Regulated environments are the right starting point because their governance pressure is real and their data boundaries are exactly what the independence firewall is designed to respect.

What a design partner gets

• Early access to Aperture before general availability, with direct working sessions alongside the engineering team.
• Influence over the standard — design partners shape the measurement definitions, control mappings, and reporting format that become govrn's reference baseline.
• A fixed-scope governance baseline for the connected estate: a defined, repeatable assessment rather than an open-ended engagement.
• Their own first measured shadow-AI figure — the actual cost-and-exposure readout for their estate, replacing industry estimates with a number measured against their data.
• Preferred licensing terms locked at the design-partner stage, ahead of standard commercial pricing.

What we get

• The modeled-to-measured proof — the moment a real readout replaces the synthetic one.
• The first live connector, hardened against a production API rather than a test harness.
• A reference account that converts the rest of the pipeline.

The proof-of-concept structure

The PoC is deliberately narrow. Scope one connector against one real administrative or billing API. Produce a measured cost-and-shadow readout in weeks, not quarters. Hold the independence firewall throughout — the body that builds against the partner's estate is structured to be separate from the body that attests to the result. As a pre-entity, five-person company, that separation is intended structure, not a current operating fact; the design-partner engagement is where we begin operating it in practice rather than only describing it.

This PoC maps directly to the dated connector milestone in the Roadmap — the first live connection is the milestone, and this program is how it gets booked.

Honest status of the pipeline

Two leads are in motion: a major Midwest Blue Cross Blue Shield plan and Grace Hill. Both are genuine, and both are currently held pending Solutions work before they can convert to a scoped live engagement. We are not representing either as a signed design partner today. The raise funds exactly this: the engineering capacity to stand up the first live connector and run it against a real API, turning one of these leads — or a comparable regulated enterprise — into the first measured estate.

This document is the offer. It is what converts a pipeline of conversations into the first connected, measured, referenceable account.