--- title: "How to buy consulting so that it has to work" url: "https://vucale.com/blog/how-to-buy-consulting-so-that-it-has-to-work" description: "Most consulting contracts are structured so that the supplier is paid the same whether anything changes. Five things to put in the scope instead." --- # How to buy consulting so that it has to work July 7, 2026·2 min read·VUCALE The reason so many consulting engagements end without anything changing is not usually incompetence. It is that the contract did not require anything to change. Deliverables were documents, the documents were delivered, and everybody performed exactly as agreed. This is fixable at the point of buying, which is the only point where the client has leverage. ## Define the outcome, not the deliverable A deliverable is a document. An outcome is something being different afterwards, stated so that both sides can tell whether it happened. Not a target operating model. Something like: quotes go out the same day rather than in three days, or the month-end close takes five days rather than nine. Specific enough that in six months nobody has to argue about whether it worked. If a supplier resists writing the outcome down, that is information. They may have good reasons — outcomes depend on the client too — which is a conversation worth having before signing rather than after. ## Buy in short increments Long engagements accumulate momentum that survives their own usefulness. Nobody wants to stop a programme in month seven, so it continues. Short, fixed-scope increments with an explicit decision point at the end of each make stopping a normal event rather than an admission of failure. The supplier has to earn the next one, which is the incentive you actually want. ## Make knowledge transfer a deliverable Not a handover session at the end, which is where budget goes to die. Documentation written during the work, configuration in your repositories from day one, and your people in the room while things are being built rather than reading a summary afterwards. Write it in the scope. A supplier who treats knowledge transfer as optional will deprioritise it whenever the schedule tightens, which is always. ## Write the exit at the start What gets handed over, in what format, within how long, at what cost. Agreed when you have leverage, not when you have already announced you are leaving. On a consulting engagement the handover includes the reasoning: not just what was built but why, what was tried and rejected, and what the supplier would do differently. That is the part that is usually lost and the part that is worth most. ## Beware the shape of the fee **Time and materials** pays for hours, so hours accumulate. It works with a supplier you trust and a tight scope, and badly otherwise. **Fixed price on a vague scope** produces a supplier defending the scope boundary rather than solving your problem. The change requests start in week three. **Outcome-linked** sounds ideal and is difficult to write, because outcomes depend on the client doing their part. It works when the outcome is narrow and measurable, and turns into an argument when it is not. **Fixed scope, short increments** is the least bad general answer. Small enough to price honestly, short enough to stop, specific enough to evaluate. ## The one question to ask At the end of this engagement, what will be different, and how will we know? If the supplier answers with a list of deliverables, they have not answered. If they answer with something measurable and then explain which parts depend on you, that is a supplier who has thought about whether their work lands — and that is most of what you are buying. - contracts - scoping - incentives - buying advice ## Keep reading - [The constraint is change capacity, not strategy](https://vucale.com/blog/the-constraint-is-change-capacity) - [A consultancy that resells cannot advise you](https://vucale.com/blog/a-consultancy-that-resells-cannot-advise-you)