Grace Hill — Reference
A warm thread, a strong first design-partner candidate, and the kind of account the first proof-of-concept exists to prove.
Confidential · June 2026. This is a pipeline reference note, not an executed agreement. No proposal has been signed. The relationship is held pending Solutions readiness. Any figures referenced elsewhere are illustrative.
What this is
This is a candidate note, written honestly. Grace Hill is not a customer, not a signed design partner, and not a closed deal. It is a warm thread with a CTO-level relationship attached, and it is the single most useful kind of account to point the first proof-of-concept at. We are documenting it because the shape of the opportunity teaches the thesis better than an abstract example would: the Aperture engine is built and tested but pre-MVP on live data, and Grace Hill is the type of account that converts "modeled" into "measured."
Why it qualifies as a first design partner
A good first design partner is not the biggest logo. It is the account where the forcing function is real, the leadership is willing, and the workflows are exactly the ones the engine was built to see. Grace Hill scores on all three.
| Signal | What we see | Why it matters |
|---|---|---|
| Real forcing function | A regulated, compliance-sensitive domain | Governance is not optional posture — there is an external reason to measure and attest |
| AI in the workflow | Generative AI applied inside compliance-sensitive workflows | This is precisely the surface the standard reviews — the AI a company uses, and adjacent to the AI it ships |
| AI-forward leadership | A CTO who is leaning in, not resisting | Design partnerships die without an internal champion; this one has one |
| Warm entry | An existing thread, not a cold start | Lowers the cost and risk of the first conversation |
Each of these is a reason the first proof-of-concept becomes tractable here rather than theoretical. A regulated domain supplies the why now. Generative AI inside the workflow supplies the what to measure. AI-forward leadership supplies the who says yes. The warm thread supplies the how we start.
What a proof here would prove
The product is honest about its stage. The Aperture engine is deterministic, runs with no model in the measurement path, and moves pointers rather than payloads — built and tested, with a passing suite. What it has not yet done is run against a live API. The demonstration figures shown elsewhere come from the real engine on synthetic seed data; they are modeled, not a customer result.
That is exactly the gap a first design partner closes. A proof-of-concept at an account like Grace Hill is where the connectors meet a live API for the first time, where "modeled" becomes "measured," and where the govrn standard demonstrates the full arc on a real workflow: See it, prove it, run it. It is also where independent attestation earns its keep — the body that builds is never the body that attests, and a regulated customer is the one most likely to value that separation.
Status and what gates it
The relationship is warm and the candidate is strong. It is held pending Solutions readiness — deliberately. We are pursuing the entity-first strategy: stand up the company before pressing any design-partner conversation forward. The next build also matters here: multi-tenant isolation, auth, RBAC, and audit are not yet in place, and a live design partner is the right reason to ship them.
So this note carries no claim beyond the facts. A warm thread. A CTO who is leaning in. A regulated domain with a real reason to govern AI in its own workflows. That combination is what makes Grace Hill a credible first proof-gate — the account where the first proof-of-concept proves the arc the rest of the pipeline is built to repeat.