Most consulting sends you to a call before you learn anything about price. We publish what we can commit to in writing, and we are honest about the part that only the assessment can answer.
The first step is two to five days on site: shadowing how the work actually happens, then building something real against your own data. The price and the scope are agreed in writing before we start, not discovered afterwards.
We haven't published a number here yet. Ask when you get in touch and you will have the figure before you agree to anything.
Every stage below happens inside those two to five days, at the price agreed before we start.
Day zero, before we arrive
Credentials, a systems inventory and a stakeholder map.
The first days on site
A record of how the work actually happens, taken from the people doing it, not the people describing it.
Running alongside the shadowing
A gap map: how the business runs against how it says it runs, with every line tied to a name or a file.
Every engagement, at every length, including two days
A working system, built against your real data, not a mockup of one.
The last day
A ranked list of what else is worth building, and a written decision on whether to continue.
If the answer is yes, the embed runs for roughly twelve weeks, with three dated guardrails: the first integration working inside 14 days, production inside 90, and handover in week twelve. Disengagement is scheduled at kickoff, not negotiated at the end.
Each integration is its own scope line. More systems, more price.
Data that needs cleaning before anything can be built against it adds time the assessment already priced separately.
One team learning one new step costs less than a rollout across several.
A regulated release path adds review time a straightforward one does not.
We have not published a range for the embed. A number with nothing behind it would be a guess dressed up as a fact, and the four factors above genuinely move it. You get a written price for it once the assessment has told us which of them apply to you, before you agree to anything.
We do not record hours spent on your engagement. No hours-spent field, no utilisation figure, no billable ratio, anywhere. The moment that number exists, someone attaches a target to it, and an engineer optimising for hours is a consultant, whatever the title says.
Handover is included in the price you already agreed, not billed once we are inside.
Does the best opportunity we found clear the cost of the embed? If it does not, we say so.
The principal who was not on your engagement reviews the decision and writes their own sentence, not a signature. The two people who spent days inside your business, and are proud of what they built, are the worst placed to judge whether to leave. Walking away is an expected outcome, not a failed one: the assessment was paid for, something ran on your data, and you were told something true.