Book a discovery call
Home / Method
We discover before we recommend, prove the path before we commit, then assemble the solution from the right parts. And we come back, because the business you built it for keeps moving.
The problem as the business experiences it, before anyone has framed it.
The most expensive mistakes come from solving the wrong problem well.
The complaint is a symptom. We're after the constraint underneath it.
The cheapest way to kill a bad approach is to try it at low stakes.
Assembled for you, not pulled off a shelf. New technology where it earns its place.
A solution nobody can run without us isn't finished.
Working on handover day is a low bar. The question is whether it still earns its place a year in. Every other engagement ends at delivery. Ours returns on a set cadence to inspect what we built against how the business now runs, and revise it where it has drifted. That's the loop: inspection feeds back into Discovery, and the line runs again on what has changed.
Delivery is a moment. Usefulness is a moving target. Volumes grow, rules change, people join and leave, and a process that fit perfectly at handover starts to chafe. Adaptation is the standing commitment to change what we built so it keeps fitting — the workflow rewritten, the automation retuned, the governance updated. Every change documented and testable the same way the original was, so what you own stays defensible.
Most consulting frameworks are three alliterating words that sound designed rather than used. We had one of those, Assess / Assemble / Accelerate, and threw it out. "Assess" was a weaker synonym for the Discovery we were already doing, and "Accelerate" was an outcome dressed up as a step.
What replaced it isn't a cleverer set of words. It's the actual sequence work passes through, named after what happens there. Some stations are short. Intake can be a single conversation. Others take most of the engagement. Two of them, Discovery and Assembly, are load-bearing enough that we put them on the door.
The practical effect: you get a written findings document at the end of Discovery whether or not you build with us. If what you asked for isn't what you need, that's when we say so, before anyone has spent money on the wrong thing. And nothing moves to Assembly on a hunch. Station 03 exists so the expensive commitment is made against a tested prototype rather than a confident opinion.
The last station is the one that matters most and the one nobody sells you. Delivery is where most engagements end, which is exactly when the drift starts: volumes grow, rules change, the workaround creeps back in. Inspection is a standing return on an agreed cadence, and what it finds goes back into Discovery. The line is a loop, not an arrow.
The process held together by spreadsheets.
It works because one person knows how it works. When they're out, it stops. When they leave, it breaks.
Data nobody trusts.
Three systems, three answers, and a monthly meeting spent arguing about which number is right instead of what to do about it.
Software that makes you work its way.
You bought the tool, then rebuilt your process around its limitations. Now the workarounds are the job.
Work that takes three days and should take two hours.
Usually it's not the work. It's the six handoffs, the re-keying, and the waiting in between.
A pile of documents and no way through it.
Contracts, claims, records, intake forms. We spent two decades making sense of exactly this, at a scale most businesses never see.
"We should be using AI for this."
Maybe. We'll tell you where it actually helps, where it doesn't, and what has to be true before you trust it with real work.
The terminal on this site does a miniature version of phase one against whatever you type. It's a sketch, not an engagement, but it shows the shape of the thinking.
