What transformation actually means
Most companies already have ChatGPT licenses, a half-built bot, and a slide that says "AI strategy." None of that changes Tuesday. Transformation is the unglamorous work of deciding which workflows get an agent, which get an automation, which stay human, and in what order, then rebuilding the handoffs so the new system becomes the default way of working.
If you already know the one painful workflow, start with an agent or an automation. Transformation is for when the question is bigger than one pipeline: the org is under pressure to "do AI," tools sit unused, and nobody owns the sequence.
How we run it
- Map: the real operating model: where hours go, where judgment lives, which tools are load-bearing, which are theatre.
- Sequence: a short list of changes in the order they can actually land. First system proves value. Second rides the proof.
- Pilot: one cluster live. Agents and automations where they belong, with human control on material calls.
- Adopt: training for the people who have to use it, plus the Run layer so it doesn't quietly die.
Same Map → Pilot → Run spine as the rest of the firm. Transformation is the wider frame around it. Detail: How we work.
What you get
Operating-model map
Where AI belongs, where it doesn't, and the cost of leaving the current mess alone.
Change sequence
A short, ordered list of workflows to touch, sized so it actually gets funded.
First live cluster
The first systems running in real accounts, measured against the manual baseline.
Adoption plan
Who owns it, who gets trained, what "done" looks like in 30 and 90 days.
Fit / not a fit
Good fit
- Leadership pressure to "do something with AI" and no honest sequence
- Tools already bought that nobody uses
- A decision-maker who will change process, not just buy software
- Willingness to start with one cluster, not a company-wide fantasy
Not a fit
- You already know the one workflow, that's an agent or automation pilot
- You want a strategy deck with no build
- No access to how the work actually happens
- Transformation as a synonym for laying people off
Pricing signal
- Map: typically $4k–$12k for an operating-model diagnosis (higher than a single-workflow Map because the surface is wider).
- Pilot cluster: scoped after Map. Usually a bundle of the first agent/automation work plus the change sequence. You get one number before we build.
- Run: monitoring, iteration, and adoption follow-through after proof. Training can sit inside this or as its own engagement.
We do not sell open-ended transformation retainers before the work has a name. Detail: Services pricing · How we work.
FAQ
Is this a strategy workshop?
No. Map produces a sequence you can act on, and the next step is a live pilot in your accounts. If you only want slides, we are the wrong firm.
Do you replace our whole stack?
Almost never. We meet you in the tools you already use and change the operating model around them. New software only when the current stack is the actual blocker.
How is this different from buying agents and automations separately?
Those are the build. Transformation is the order, the operating model, and the adoption. You can buy a pilot without transformation. You should not buy transformation without a pilot attached.
Will our people lose their jobs?
We design for hours returned and judgment kept. Headcount theater is not the engagement. If that's the brief, say so up front so we can decline.
Under pressure to "do AI"?
Tell us what the board, the team, or the week actually looks like. We'll tell you whether this is a Map, a single pilot, or not a fit.