The best sign an engagement worked is that the client no longer needs the firm. Dependency is not a model, it is failure in disguise: you recognise it by knowledge that never transfers, undocumented processes, and an engagement with no defined end. A good handover is designed at the opening, not at the closing, because by the end the knowledge already sits with the consultant.
The best sign that an engagement has worked is that the client no longer needs us. That sentence should be obvious. Yet a large part of the consulting industry is built on the exact opposite: maintaining dependency, extending contracts, keeping knowledge illegible in order to stay indispensable.
We think that is a fault, professional as much as moral, and that it shows in results long before it shows in the relationship.
Dependency is not a model, it is failure in disguise
A firm that stays because the client cannot do without it has not delivered value: it has delivered a bottleneck. The signals are easy to recognise.
- Knowledge never transfers. Deliverables are opaque, decisions stay in the consultant’s head, and the trade-offs are justified nowhere.
- Processes are not documented. Everything rests on presence, nothing on the system. The day the consultant leaves, the organisation reverts within weeks.
- The engagement has no defined end. Amendments follow one another and nobody ever talks about the exit, and the question becomes steadily more uncomfortable to raise.
That can make good revenue in the short term. It never makes a good reputation, and in a market where executives talk to each other, reputation is the one acquisition channel you cannot buy.
The handover is prepared from day one
The classic mistake is thinking about transfer at the end. Too late: by then the knowledge is already concentrated in the consultant, and the transfer becomes retroactive documentation producing a binder nobody will open.
A good handover is designed when the engagement opens, not when it closes. Concretely, that means three things.
- Build with the team, not instead of it. Every structuring decision is taken in pairs, never alone in a room. It is slower at the time, and it is the only way for the decision to survive the departure of whoever carried it.
- Document as you go. The playbook, the definitions, the trade-offs: written during, not reconstructed afterwards. A trade-off documented as it is made keeps the context that explains it, and that context is what allows it to be revised later.
- Name internal owners. Every block of the go-to-market system has someone accountable on the client side, from the start. Whatever belongs to nobody degrades within months, however well it was built.
Our job is not to do it for you. It is to make sure you know how to do it.
Exit criteria, written at framing
This is what makes the rest credible, and what almost no firm sets out.
Useful exit criteria are observable: which team runs which ritual without us, which indicators are produced without our involvement, which decisions are taken without outside validation. “When you are autonomous” is not a criterion, it is a phrase that guarantees an engagement that stretches.
Written at framing, those criteria change the nature of the relationship: they give the client a way to measure our work other than by impression, and they force us to organise the transfer rather than promise it.
What the client keeps after we leave
A well-run engagement leaves tangible things behind, not an invoice and a vague memory.
A formalised and adopted ICP the team uses to disqualify. A prospecting playbook the sales team runs alone, written in their words. A data foundation that drives decisions instead of decorating them, the subject of building your revenue operations foundation. A pricing grid held by internal teams, with the arguments that go with it.
Assets that live without us. The real deliverable of a consulting firm is not the report: it is the client’s autonomy.
What it costs us, and why we do it anyway
It is worth saying plainly: this model shortens engagements. An engagement that ends because the criteria are met earns less than one that extends.
What it produces instead is a client who refers you, and who comes back on their own at the next stage with a new problem. In a consulting market where referral makes up most of the pipeline, that is the most profitable trade-off over the medium term. It simply requires accepting less predictable revenue in the short term, which is a business choice before it is a posture.
The Arkimoz method
From the framing stage, we set the exit criteria with you: how will we recognise that the engagement is over and that your teams have the wheel. We work in continuous transfer, not in isolated delivery, and every ninety-day motion plans what has to remain behind it.
And we commit to leaving when those criteria are met, rather than inventing the next reason to stay. That is what gives meaning to the distinction between strategy and execution we develop in strategy vs execution: staying long enough for the gesture to become a reflex, and not a day longer.
A good firm does not measure success by how long it stays. It measures it by how solid what remains is once it is gone.
Frequently asked questions
- How do you recognise an engagement that creates dependency?
- By three signs. Knowledge never transfers: deliverables are opaque and decisions stay in the consultant's head. Processes are not documented, everything rests on presence. And the engagement has no defined end, amendments follow one another and nobody talks about the exit.
- When should the handover be prepared?
- At the framing stage, never at the end. By the closing, knowledge already sits with the consultant and the transfer becomes retroactive documentation, producing a binder nobody opens. Prepared at the start, transfer is a way of working rather than a step.
- What should remain after a firm leaves?
- Assets that live without them: a formalised and adopted ICP, a playbook the team runs alone, a data foundation that drives decisions, a pricing grid held internally. The real deliverable of a consulting firm is not the report, it is the client's autonomy.
- How do you set exit criteria?
- At framing, in writing, in observable terms: which team runs which ritual alone, which indicators are produced without us, which decisions are taken without outside validation. Vague criteria of the 'when you are autonomous' kind guarantee an engagement that stretches.