Consulting Diagnoses. Advisory Stays for the Fix.

Every advisory firm says the same thing in the first meeting. We are not consultants. Nobody ever explains what that is supposed to mean. So here it is, specifically, because the difference is not marketing language. It changes who owns the outcome.

Consulting Diagnoses the Problem and Hands You the Answer.

A consulting engagement has a defined deliverable, and the deliverable is a recommendation. Someone studies your business, builds a deck or a report, and presents a conclusion. The engagement is considered a success the moment that conclusion is delivered and accepted.

What happens after the deck is someone else's problem. Usually yours.

Advisory Stays Until the Recommendation Actually Works.

An advisory engagement has a different finish line. The work is not done when a recommendation is delivered. It is done when that recommendation is running inside the business, producing the result it was supposed to produce.

That distinction sounds small. It is not. It is the difference between being paid to be right and being paid for something to actually work.

Recommendation Risk, Defined

Recommendation risk is the chance that a correct recommendation fails once it meets the actual systems, people, and politics required to execute it. A plan can be analytically sound and still die on contact with your org chart, your CRM, or the manager who was never told the plan existed.

Consulting transfers recommendation risk to the client at the moment of handoff. Advisory keeps it, because the advisor does not get to call the engagement finished until the risk is retired, not transferred.

Why This Distinction Actually Matters at a $20M to $200M Company.

Debsan's whole thesis is that what built the company is rarely what scales the company. A recommendation does not rebuild an operating model. Implementation does. If an engagement ends at the recommendation, it has diagnosed the gap between what built you and what scales you, and then left you to close that gap alone, with the same team and the same bandwidth that produced the gap in the first place.

That is not a criticism of consulting as a category. Some problems genuinely are diagnosis problems, and a sharp outside read is worth real money on its own. But most mid-market operational problems are not diagnosis problems. Leadership usually already knows, roughly, what is wrong. What they are missing is the capacity to actually fix it while running the business at the same time.

A Concrete Picture of Recommendation Risk in Action

Picture a $40 million manufacturer whose sales process has outgrown the three people who built it from memory. A consulting engagement studies the pipeline, correctly concludes that stages are modeled on the wrong sale, and recommends a redesigned pipeline with clear stage definitions and owners. The deck is excellent. Leadership agrees with every slide.

Six months later the pipeline in the CRM has not changed, because nobody owned translating the recommendation into the actual system, retraining the sales team on it, and holding anyone accountable to using it. The recommendation was never wrong. It just never survived contact with the business that was supposed to run it.

An advisory engagement treats that gap, between the deck and the daily operating system, as part of the job rather than someone else's follow-through. The pipeline gets rebuilt inside the CRM itself, the team gets trained on the new stage definitions in the context of real deals, and someone checks back in thirty, sixty, and ninety days to see whether the new pipeline is actually how deals move now, or just how a slide once said they should.

The Handoff Is Where Most Transformations Die.

Here is the pattern, if you have lived it: the consultant presents a smart recommendation to a packed room. Everyone nods. Three weeks later the recommendation is a PDF in a shared drive, and the person who was supposed to own its implementation is back to firefighting the thing the recommendation was meant to fix.

Nobody decided to ignore it. Nobody had the bandwidth to own it. The recommendation was correct and irrelevant at the same time, because correctness was never the constraint.

This is not a people problem, and it is not a motivation problem. It is a structural one. A consulting engagement's incentives end at delivery. Nobody on that team is still accountable for the result six months later, because nobody on that team is still in the building.

What Advisory Actually Looks Like.

At Debsan, advisory means staying inside the actual systems long enough for the recommendation to become the new default, not an exception someone has to remember to follow. That looks like building the process into the CRM instead of writing it in a memo, training the manager who now owns the decision instead of just naming them in a slide, and checking back in thirty, sixty, and ninety days to see whether the thing that was supposed to change actually changed.

It also means a project can run longer and look less clean on a timeline. Retiring recommendation risk takes as long as it takes. That is a feature, not scope creep, and it is the entire reason to hire Debsan instead of a slide deck.

How to Tell Which One You Are Actually Buying.

Three questions cut through the label on the invoice. What is the actual deliverable: a document, or a working system someone can point to and use today? How is the engagement paid: a fixed project fee that ends at delivery, or a structure tied to the thing actually running in production? And who is accountable if the recommendation does not take: the firm that wrote it, or just you, six months after they have moved on to the next client?

If the honest answer to all three points at a document, a fixed fee, and you alone holding the risk, you bought consulting. There is nothing wrong with that, as long as you know it going in and you have the internal capacity to carry recommendation risk yourself. The failure mode is not hiring a consultant. The failure mode is hiring a consultant for a problem that needed someone to stay.

CEOs Usually Ask These Four Questions

Is a consultant just an advisor with a different title? No. The title is not the distinction. The distinction is whether the engagement's success is defined by delivering a recommendation or by that recommendation actually working, and who is on the hook for the gap between those two things.

If the recommendation is correct, does it matter who delivered it? Yes, because correctness is rarely the constraint. Most recommendations that fail were not wrong. They failed because nobody retired the recommendation risk between the deck and the daily operating system.

How do I know if my current advisor is actually consulting? Check the finish line they are working toward. If the engagement is scoped to end at a presentation rather than at an adopted result, you are paying for consulting under an advisory name.

Should every company skip consulting and only hire advisory? No. A narrow, well-defined diagnostic question is sometimes exactly what a sharp consulting engagement is built for. The mistake is hiring a consulting engagement to solve a problem that was never a diagnosis problem to begin with.

Call it whatever you want on the invoice. What matters is who is still accountable for the result after the deck is closed.