Consulting ends at the deck. Advisory stays through implementation. Why the distinction should shape how you hire for outside help.
Most clients use consulting and advisory as synonyms. Most firms are happy to let them. The language is soft, the scope is flexible, and the billing is easier when nobody has to defend what exactly was delivered. This is, in our view, the single biggest reason external engagements go sideways in month three.
The distinction is not pedantic. It changes what the engagement is for, who should be in the room, what is considered a success, and when the work is actually done. Getting it wrong wastes a quarter. Getting it right sets the tone for everything that follows.
A consulting engagement is a diagnostic and a recommendation. You hire a consultant because you have a question, and you want a rigorous, outside answer. The deliverable is a document, a set of options, a ranked path forward, and a handover. Good consulting is disciplined, fast, and honest. It tells you what you should do and why, and then it leaves.
This is genuinely useful work. A well-run consulting engagement can save a company a year of wrong turns. What it does not do is execute. The consultant was not hired for that, was not priced for that, and in most cases is not structurally set up to do that. The engagement ends when the recommendation lands.
The problem is what happens next. The deck goes into a drawer. The recommendation gets partially implemented by a team that was not in the room when it was written. Priorities shift. Three quarters later, the client wonders why nothing moved. The honest answer is that nothing was supposed to. Consulting does not move things. People do, and nobody hired the people.
Advisory is what you hire when you need someone in the room while the decisions are being made, not just before. It is structurally different work. The advisor is not delivering a document. They are part of a decision loop. They sit in leadership meetings, review specific choices as they come up, disagree in real time, and are accountable for the weekly calls, not just the quarterly review.
The question is not what do I think you should do. It is what are we going to do this week, given what just happened.
Advisory is slower to show results on paper. It is also far harder to fake. A consultant who has never run the kind of business they are advising can still write a good deck. An advisor who has never run that kind of business will be found out in the second meeting. That is one of the reasons good advisory relationships are so much rarer than good consulting engagements.
If you have a specific, bounded question, hire a consultant. Scope it tightly, insist on a short timeline, and make sure the deliverable is the decision, not the deck. Do not let the scope expand into implementation unless you have renegotiated the engagement, the team, and the fee, because you now want advisory and you should pay for it honestly.
If you need someone to help you make weekly decisions for the next year, hire an advisor. Hire one who has run the kind of business you are running, not one who has only studied it. Pay them for their judgment, not for their hours. And write a contract that actually lets you end the relationship at 90 days if the chemistry is wrong, because chemistry matters more in advisory than it does in almost any other professional relationship.
The firms that do both tend to be clearer about which one they are doing in any given engagement, and charge accordingly. We are one of those firms. We think the distinction is the first conversation worth having, not the last.