Why your consulting engagement failed before it started.

The failure wasn't in the delivery. It was in the room before the contract was signed — in the brief that wasn't written, the outcome that wasn't named, and the decision-maker who was never in the call. Here's how that pattern plays out — and what to do instead.

The moment it breaks.

There is a specific moment in every failed consulting engagement where the outcome became inevitable. It is not the missed deadline, the off-target deliverable, or the founder who stops responding to Slack. Those are symptoms. The moment is earlier — usually in the first conversation, sometimes in the brief, always before the invoice is raised.

The failure looks different from each side of the table. For the operator who hired the consultant, it looks like money leaving the account while the work drifts. For the consultant taking the brief, it looks like realising halfway through a scoping call that the client has not yet decided what they want to be true in twelve weeks. Either way, the failure is baked in before the work starts.

The pattern is consistent enough to describe in four moves. Understanding them doesn't make you immune — but it makes the failure harder to miss.

Move one: hiring a type instead of an outcome.

The first move happens when a founder decides they need "a strategy consultant" or "a GTM advisor" or "a fractional CMO" before they have defined what problem those words are supposed to solve. The category is hired. The outcome is not.

This is more common in Singapore and Southeast Asia than it sounds. The ecosystem here runs on warm introductions and pattern-matching — someone hired a fractional CFO and it went well, so the next founder hires a fractional CFO. The consultant is credentialed, the references check out, the first meeting goes well. The engagement starts without anyone in the room having written down what success looks like in week ten.

The consultant then does consultant things. They diagnose, they framework, they produce. The founder receives work product and realises, slowly, that it is not the thing that was stuck. The consultant was solving the right problem for a different company. Nobody is lying. Nobody is lazy. The scope just wasn't written in a way that forced anyone to test the assumption.

Move two: the absent decision-maker.

The second move: the person who signs the invoice and the person who attends the working sessions are different people. This is almost always fatal.

A common version: the founder delegates the consulting relationship to a senior manager — usually for legitimate reasons: they are raising, they are managing a crisis, they trust the team. The working sessions happen. The diagnostics are thorough. The recommendations are solid. And then the founder reads the final memo and says "this isn't what I wanted" — not because the work was wrong, but because they were never in the room where the scope was set.

The correct posture: the decision-maker must be present for the first two sessions and the final review, at minimum. Not to approve every output — that micromanagement kills good operators — but to calibrate what "right" means early enough that it can still be course-corrected. An operator who can't get thirty minutes of the founder's calendar in week one cannot produce an outcome the founder will trust in week ten.

Move three: confusing delivery with work.

The third move is structural and almost invisible until it's too late. The consultant delivers a document. The founder accepts the document. The engagement ends. Nothing changes inside the company.

This is the consulting industry's oldest sleight of hand, and it works because documents feel like outcomes. A 60-page strategy deck, a market-entry report, a competitive analysis — these are real work. They take real time to produce. They look like value. But a document that lives on a SharePoint and is referenced in zero subsequent decisions is not an outcome. It is theatre performed in the past tense.

The test to apply to any engagement before it is scoped: what will be running in the client's systems at close-out? A live funnel. A hired operator. An automated workflow handling a specific job. If the answer is "a document," push back until you find the thing behind the document — because there is always a thing behind the document, and that thing is what the founder actually needs.

Move four: scope that drifts.

The fourth move happens after the engagement starts. The scope was clear at signing. Then the founder mentions a second problem in week three. Then a third. The consultant — who wants to be helpful, who is in the room and can see the problems — starts addressing them. The original outcome recedes. The engagement expands sideways. By week eight, everyone is working hard on things that were never in the brief.

The antidote is not rigidity — good operators adapt. It is explicit renegotiation. Every time the scope shifts materially, a new memo is written. A new outcome is agreed. The old one is either closed out or explicitly de-prioritised. This sounds bureaucratic. In practice it takes forty-five minutes and a short email, and it means that the final engagement review is never a surprise.

The practices and consultancies that do the best work over time are the ones that have normalised saying "that's outside the current scope — let's decide together whether to extend or address it in a follow-on." It is not a refusal to help. It is a commitment to finishing the thing they started.

The six things a good brief must contain.

• 01
  A measurable outcome. One sentence. Not "improve activation" — "lift activation from 22% to 38% on new cohorts within 10 weeks." If you cannot write the outcome in one sentence, you have not finished scoping the work.
• 02
  Calendar dates, not durations. "Eight weeks" becomes twelve. "Start: 5 May, close-out: 30 June" does not. Every milestone gets a calendar date. Drift is harder to ignore when it has a specific date attached.
• 03
  What the client provides. Data access, system credentials, a named decision-maker who attends the first two sessions, and an honest account of what has already been tried. A consultant who starts without this is navigating blind.
• 04
  What is shipped, and where. Not a document — a live artefact in the client's systems. A funnel that runs. A workflow that fires. A hire who has started. The output must outlive the engagement.
• 05
  A fixed price. Hourly billing rewards time spent, not outcomes reached. A fixed fee — paid in two tranches, no escalators — aligns both sides on getting to done. If the work is bigger than estimated, that cost belongs to the operator who underscoped it.
• 06
  Explicit exclusions. What the consultant will not do. This is the most important section because it prevents the scope from drifting into adjacent work that looks helpful but isn't what was agreed. "We will not run the all-hands. We will not represent the company externally. We will not write board materials."

Frequently asked questions.