Seven steps, one page. You never buy the whole journey up front — each step tells you whether the next is worth it. Scroll to walk the full engagement, or jump straight to any step below.
An online self-assessment across your people, your organization, and your technology — a printable read of where you're strong and where you're behind. It's built to surprise: most companies are further behind on their people and organization than their technology, the opposite of where budgets go. No call, no email wall.
Four questions on readiness for change and four on need for change, scored independently and read together into one of four bands: Primed, Ready-unconvinced, Willing-but-unequipped, or Stuck.
Each area is scored 1–10 against published anchors, totaled out of 80. 56–80 reads Ready (O) or Production-ready (T); 33–55 reads Foundational work first; 8–32 reads Survival risk (O) or Not yet safe to widen (T).
The read is deliberately directional, not flattering. Most companies discover they've been funding the platform while the organization is the actual wall. The full scored instrument — the Readiness Score proper — comes in the Roadmap.
A conversation that opens with your diagnostic already in hand. We walk through what your weakest area means and what a first move looks like, and ask about your size and systems, enough to shape a first project before you've spent a dollar. This is where we explain what the paid steps cost.
We open already holding your read, so we spend the time helping you understand what your result means for you, and what a sensible first move looks like. No pitch deck, no pressure to decide on the call.
One person on our side gets a general sense of fit — a real organization, someone with the standing to sponsor a first project, and a gap worth exploring. It's a conversation, and it isn't the only look you'll get: the Roadmap is where fit gets tested for real. An honest "not quite yet" here costs you nothing.
You leave knowing roughly what a first step would cost and involve — enough to decide without pressure.
A structured read across all three dimensions and a plan: your destination, your full Readiness Score, and the shape of your journey — first project named, the waves after it roughed in.
We stand at the finished organization and work backward. The output is a signed Destination Architecture — your purpose, written plainly enough that an agent could tell what to build and what not to; your intelligence engine; and your organizational form, including how agent decisions stay chained to a named human.
Five conditions have to hold for that architecture to count as done: agent-first workflows, a system that improves from its own results, ownership of your own models and data, judgment built into every layer, and human flourishing as a hard requirement. Miss one, and this step isn't finished yet, however good the rest looks.
The Diagnostic's directional read becomes the real instrument: all sixteen areas, scored and banded. The honest number matters more than the flattering one — a high score with nothing deployed is the most expensive place to be in this framework.
A large organization resists a transplant; a small one doesn't. The Roadmap sets which mode fits: Direct Mode (50 or fewer — the whole company, in place, no twin needed), Light Edge Mode (50–500 — one Edge Twin around your highest-coordination workflow), Full Edge Mode (500+ — the twin built outside normal reporting lines, on CEO or board budget), or Mandatory Edge Mode (government/public sector — the only path, adapted for procurement and compliance).
The Roadmap gives you the shape. The deeper Blueprint, alongside the Pilot, draws the actual route.
We build your first project: the Intelligence Stack, stood up for one workflow. It runs alongside your existing way first — the new version proposes, your people still decide, and the gap between the two is the training signal. Proof is the override rate falling over time.
The Intelligence Stack runs the decision loop continuously — sense, interpret, decide, act, learn — with GOVERN/ASSURE running across all of it, never off.
No spec, no agent. Before it runs, each agent gets a written spec — what it's for, how much it can decide alone, what it can access, and who's accountable if it's wrong — so authority is always visible, never assumed.
The new workflow runs on the same real inputs as the old one. It proposes; your people still act. Where the two disagree is the most valuable signal in the whole engagement, captured along with the reason.
The rail matures in three stages — alert-only, escalation authority, kill-switch capability — each earned by the Four Pillars, never by the calendar. As the override rate falls, the workflow earns more authority, one tier at a time, with rollback always in place.
The deep version of the Roadmap — a full read of your people and technology, and the sequencing of every wave after it. Its signature move is reconciliation: where two parts of the business disagree about who controls what, that disagreement is the finding. Most clients run it alongside the Pilot, so the Pilot has real evidence to build on instead of a guess.
An organization's real advantage is mostly tacit — carried by whoever has done the work for years. The first agent any person meets is an interviewer, gathering how they actually work, and what comes out gets written into a one-page manifest per workflow: what it is, who says so, and what happens if it's wrong. If a reason can't be stated, the data doesn't move.
Every role touching the workflow gets broken into tasks, each scored 1–5 for agent-readiness. 4s and 5s go to agents now, 3s pilot in the parallel run, 1s and 2s stay human — and headcount reduction doesn't count as architecture until the absorption math is actually done.
Where the two reads of the same area disagree, that gap is the finding:
No single-surface consultant can produce that — it takes both reads to see the seam. Reconciliation is how the Blueprint turns two scores into one sequenced route.
Once the Pilot proves, we run the next workflows — easiest first, one or two at a time, each proven before the next begins. Continuous change becomes how you operate, not a project that ends.
Most transformation stories have one people-plan: reduce headcount. Ours is different — as agents take the volume, the question becomes whose judgment expands to fill the space that opens up. We map whose judgment grows, keep the human layer working the exceptions (their reasons are the highest-value signal the system produces), and make who-decided-what visible.
People who ran a process by hand become the ones who govern the system that now carries it. That's the rise, made concrete.
The old org chart — a latency map of how information waits — gets replaced with pod-based networks organized around capability. The framework, the sequenced route, and the discipline of proving-before-trusting are all yours now. Your people run the reviews. We step away.
The goal was never dependency on us. The mature state is a standing loop your people run: spot the next workflow ready to move, prove it in parallel, migrate it, repeat — self-disruption as a standing capability.
The governed core, the route, and the review discipline are yours, with no vendor lock. The moat is what a competitor can't buy: your way of operating and your people's judgment, fused into the engine.
GOVERN / ASSURE runs underneath every step, from Backcast through Rewire — never a phase you pass and leave behind. It logs every decision, holds the guardrails, and owns the kill switch. Four pillars make it concrete:
Authority granted per agent, task by task, and enforced by the system — so overreach simply isn't possible.
One agent can ask another for help — but cannot borrow its authority to do it. Overstep is caught at the boundary between roles.
Monitoring agents watch for violations in real time and surface to a human — never act alone, so the watch scales with the work.
Every consequential move is specified, logged, and defensible before it happens — chained to a named human owner.
Authority isn't granted up front — each stage is earned as the Four Pillars prove out inside the Pilot.
A deployment gate, not four features. Each pillar is scored 1 to 5, and the rail is capped at its lowest score — no new class of agent reaches production until every pillar clears 3. A strong score in one can't cover for a weak one elsewhere.
The Discovery Call's gut-check and the Roadmap's signed mandate are the human side of this; the rail is what they're judging once work begins.
From the Roadmap on, they're paid engagements — walked through on the Discovery Call before you commit to anything. We size the work with you, never off a price list.
The goal was never dependency on us. As the pilots prove and the waves migrate, the whole thing becomes yours: the governed operating core, the sequenced route, the discipline. Your people run their own reviews now, spending their time on judgment and creativity while agents carry the heavy lifting. We fade.
Anyone can buy the same engine now. The materials are available to anyone; what makes it yours is the structure you raise on your own foundation, and the people who govern it. Owning your intelligence is owning your differentiation. Renting it is renting your commoditization.
Five minutes, your scores, no email wall. The gap is rarely where the budget went.