We land the first workflow.
Your firm lands the next six.
What the engineers arrive carrying
The substrate is not a deliverable on a joint statement of work. It exists before the engagement, which is why no plan is asked to fund its discovery and why a pursuit does not have to be priced around a six-week assessment to reach a workflow that runs.
- the foundation layer
Connectors onto the interfaces those systems already expose, a fail-closed PHI gate, hard tenant isolation, and a typed tool registry. Installed as it stands.
- the decision record
The hash-chained, bi-temporal determination record. It is the product of every run rather than a work package someone has to scope, staff and defend in a change board.
- the first workflow
Prior authorization, stood up on the systems the plan already runs. No modernization first — that is the condition the platform was built under, not a concession made to win a room.
- discovery
Not a line item and not a phase. What we already know about our own platform is not something a plan should be invoiced to be told.
What we deliberately do not staff
This is not a gap we intend to close later. The connector into the claims system, the change management through the operation, and the run-state after go-live each sit closer to the plan’s own operation than to the platform — and each keeps arriving long after our engineers have gone. Said plainly, because a delivery partner will work it out anyway: our revenue concentrates at the front of the engagement and is meant to fall away. A partner’s does the opposite. Those two shapes fit together, and that is the only durable reason to be in a room together.
We do not sell the replatform — which is the only reason anything else on this page is believable — and we are not the firm to own the systems roadmap either. One workflow lands with us. The next six are a delivery engagement someone has to staff, and it will not be us.
No logo wall. Deliberately.
No partner is named here, and none will be until there is something signed and delivered to point at. What is here instead is the boundary, written where both sides can read it before anyone builds a pursuit around a guess. If it fits the practice you already run, the next conversation is a short one.
Deeper: what actually gets installed · the first workflow · the economics of reuse