How is business advisory different from consulting?

The structural difference

Consulting is project-shaped. Somebody comes in to solve a defined problem — assess the operation, build the model, evaluate the market, train the team — and the engagement has a start, a deliverable and a finish. They leave. What happens next depends entirely on what you do with the output.

Advisory is relationship-shaped. The same person works with the business over time, and what they accumulate is not deliverables but understanding. That is why the value does not arrive all at once: it builds.

Neither is better. They answer different questions.

What consulting does well

It is the right shape when the problem is bounded, the expertise needed is specialised, and the output is something you can act on alone afterwards.

You need three markets evaluated and a recommendation. You need a model built for an application. You need an operational assessment before you scale. Those have a defined end and a natural stopping point, and paying for a relationship you do not need would be wasteful.

What advisory does differently

The questions advisory deals with are not bounded, and they do not resolve. Whether to hire becomes who to hire, which becomes whether the hire is working, which becomes what has to change now that it is. Somebody who watched that whole sequence gives different advice from somebody assessing it as a snapshot.

It also covers the things that are not problems yet. An advisor who knows your revenue pattern and your cost structure notices that the margin has been compressing for three quarters before you do. They flag what the contract you are about to sign will actually do in its third year. They mention that the way you are taking money out is building something you will have to unpick.

None of that is a deliverable anybody would commission. It is a by-product of continuous attention.

Context is the whole of it

What accumulates is context, and it is specific rather than general.

Context about you: what you tend to underestimate, where you tend to overspend, which kinds of decisions you make well on your own and which ones need a second look. Context about the business: what the year actually looks like month by month, which months lie. Context about the people: who has grown into the job, who is a constraint on growth, what the place can absorb.

A project engagement cannot develop that, however good the person is. It is a function of time rather than skill.

The thing an advisor accumulates that a consultant cannot is context.

Which one you actually need

If the problem is specific, bounded and ends in a document you can use — that is consulting.

If what you want is somebody who knows the business, who will push back on your thinking, and who is reachable when a decision arrives rather than when a project is scheduled — that is advisory.

Plenty of businesses want both at different moments. PSC provides the advisory relationship, and will say plainly when a question sits outside what advisory covers rather than taking it on anyway.

What to settle either way

The same four things, whichever shape you are buying, and all four belong in writing before money moves.

What the scope actually is, and what happens when something outside it comes up. What the number is, agreed before anything starts, with changes raised when they happen rather than at the end. Who does the work — a name, not a department. And how it ends: how long it runs, how much notice stops it, what is owed if you stop part-way, and whether it renews on its own unless you say otherwise.

If a figure ever surprises you, say so on the spot. That is the point of having one person to say it to.