The word covers a wide range, from genuinely independent advice to a sales process wearing a different name. It is worth knowing what the useful version looks like.
The work itself
Understanding what actually happens
Most of the value is here, and it looks like the least technical part.
Every business has a documented process and a real one. The real one includes the customer invoiced differently, the check somebody does from experience, the spreadsheet that reconciles two systems every Friday, and the step that exists because a system could not do something in 2018.
Finding those requires sitting with the people doing the work rather than interviewing the person who manages them. It is unglamorous and it is where the useful findings come from.
Assessing what you have
What systems exist, what they cost, what they do, what they were bought for, who uses them, and what depends on what.
This regularly produces immediate findings that pay for the engagement: licences for people who left, subscriptions to products nobody uses, two systems doing the same job, a support contract nobody has called in three years.
Identifying what should change, and in what order
The list is usually long. The sequence is what matters, because dependencies exist — you cannot build useful reporting on data nobody trusts, and you cannot automate a process nobody has agreed.
A good recommendation set is ordered, with the reasoning for the order stated.
Saying what should be left alone
The part that distinguishes advice from selling.
Plenty of systems are old, unglamorous and entirely adequate. A consultant recommending replacement of everything is not assessing; they are selling. The willingness to say "this is fine, leave it" is the clearest signal you are receiving advice.
The most useful thing a consultant says is frequently "do not do that yet". Advice includes what not to spend money on.
How to tell advice from selling
Ask directly: what do you earn from what you recommend?
Commission, reseller margin and implementation work are not automatically wrong. Plenty of good suppliers advise and then implement. What matters is that the position is disclosed so you can weigh the recommendation appropriately.
A consultant who answers plainly — "we resell that product and would earn margin, here is why I am recommending it anyway, and here are the alternatives" — is being straight with you. One who becomes vague has answered the question.
Other signals worth reading:
Do they ask about the business before the systems? Anyone who leads with technology has a solution looking for a problem.
Do they disagree with you? A consultant who agrees with everything is not adding anything.
Do they recommend doing nothing anywhere? If every area needs investment, be suspicious.
Can you take the output elsewhere? Advice you can only act on through them is not advice.
What you should receive
Documents you could hand to a different supplier and get a comparable quote:
- A written description of your current position — systems, costs, how the work actually happens
- Findings, including the awkward ones
- Prioritised recommendations with indicative costs and the reasoning
- A sequence, with dependencies explained
- What to leave alone, and why
- The risks, stated plainly
Not a presentation. Documents you own and can use.
When it is worth paying for
Before a large decision. A system replacement, a move to different premises, a significant change in how the business operates. The cost of advice is small relative to the cost of getting it wrong.
When nobody internally has the time. Most small businesses have somebody capable of working it out and nobody with the weeks to do it.
When there is a disagreement about direction. An independent assessment settles arguments that would otherwise be resolved by whoever is most persistent.
When you are being asked questions you cannot answer. A customer's security questionnaire, an insurer's requirements, an accreditation.
When something is clearly wrong and nobody can say what. Costs rising, staff complaining, work being lost, and no obvious single cause.
When it is not
If you already know what needs doing and need it done, you need a supplier rather than a consultant. Paying for advice you already have is a common and avoidable expense.
If the problem is genuinely narrow — one integration, one migration, one system to choose — a scoping conversation with a competent supplier is usually enough, as covered in what a technical discovery involves.
Getting value from an engagement
Be honest about the budget. Recommendations that ignore what you can afford are not recommendations.
Give access to the people doing the work, not only to managers. This is where the findings come from.
Share the awkward things. The system nobody uses, the supplier relationship that has gone wrong, the process everyone works around. Consultants find these anyway, and finding them late wastes the engagement.
Agree what you will receive, in writing, before starting.
Decide who will act on it. Advice with no owner internally becomes a document in a folder.
Our consultancy team works with UK businesses on this basis, with the outputs yours to take anywhere — including to another supplier. Start a conversation.
