What Does an Operations Consultant Actually Do? (And When to Hire One)

At some point, most growing businesses hit the same wall. Orders are coming in, the team is busy, revenue looks healthy, and yet everything feels harder than it should. Tasks fall through gaps. Nobody is quite sure who owns what. You spend your evenings fixing problems that a decent process would have prevented.

That's usually when someone suggests bringing in an operations consultant. It's also when most owners hesitate, because the job title tells you almost nothing. "Consultant" covers everyone from a former corporate director charging £1,500 a day to someone who read a book about lean manufacturing last month.

So here's a plain explanation of what the work actually involves, when hiring a consultant genuinely pays, and how to avoid the engagements that end in a thick report and no change.

The Day-to-Day Work

Strip away the job title and the work breaks down into five activities.

Most engagements start with process mapping. The consultant sits with the people doing the work and documents how orders, enquiries, refunds and reports actually move through the business, including the workaround someone built in a spreadsheet two years ago that the whole fulfilment process now quietly depends on. That map is usually the first time anyone has seen the entire operation in one place, and it almost always surprises the owner.

From there, the job is finding bottlenecks. Once the flow is visible, the queues become obvious, and they're rarely where people assumed. A common one in smaller businesses: every approval routes through the owner, so the constraint on the whole operation is one person's inbox. Another: two systems that don't talk to each other, with a person in the middle retyping data and introducing errors as they go.

Then comes designing better workflows. Removing steps that only exist for historical reasons, reordering work so it stops bouncing between people, defining who owns each handoff, and deciding which parts should be automated and which genuinely need a human. Good consultants are specific here. "Improve communication" is not a workflow. "Refund requests land in one queue, get approved automatically under £50, and escalate to a named person above that" is.

Technology selection sits alongside this. If you're weighing up inventory systems, warehouse platforms or automation tools, a consultant who has seen a dozen implementations can tell you which options suit a business your size and which ones you'll regret by March. Independent advice is worth most just before you sign a contract, not after.

Finally, implementation planning. Turning everything above into a sequence: what changes first, who does it, what gets tested before going live, and what can safely wait six months. Without this part, the rest is theory.

Advice and Projects, Not Running Things

The line between consulting and managed services confuses a lot of buyers, and it matters because they solve different problems.

An operations consultant advises and delivers projects. They map, diagnose, design and plan, and often help build, but your team still runs the operation day to day. When the engagement ends, you own an improved machine. Managed operations services are the opposite arrangement: a provider takes over running defined parts of your operation on an ongoing basis and owns the outcomes. Consulting changes how your business works. Managed services change who does the work. Plenty of businesses use both at different stages, but you should know which you're buying.

Business coaching is different again. A coach works on you: goals, habits, leadership, accountability. That has its place, but the deliverables are conversations. An operations consultant works on the machinery of the business, and the deliverables are concrete: process maps, redesigned workflows, a shortlist of systems with costs attached, a rollout plan. If you can't point at what you received afterwards, you bought coaching at consulting rates.

When Hiring One Actually Pays

Not every business needs one, but four situations come up again and again.

The first is scaling pain. The processes that worked at £300K start creaking somewhere past £1M. Orders take longer to get out, errors creep in, and adding staff doesn't seem to add capacity because new people inherit the same tangled workflows. That's a process problem wearing a hiring costume.

The second is systems chaos. The business runs on nine different tools plus a layer of spreadsheets only one person understands. Data gets retyped between platforms, reports never quite agree with each other, and nobody trusts the numbers enough to make decisions from them.

The third is a big platform decision. If you're about to commit serious money to an ERP, a warehouse management system or a 3PL, a few days of independent advice is cheap insurance. The consultant has no commission riding on the outcome, which is more than can be said for the software vendor's sales team.

The fourth is preparing to delegate. If the whole operation lives in your head, you can't hire an operations manager, sell the business or take a holiday longer than a weekend. A consultant extracts what you know, documents it, and helps define the role you actually need to hire.

What a Good Engagement Looks Like

Some wariness about consultants is fair, because the stereotype exists for a reason. Everyone knows a business that paid for a 60-page strategy deck that nobody opened twice.

A good engagement follows a simpler arc: audit, roadmap, implementation support. The audit is a short, structured look at how your operation actually runs, usually a week or two of interviews, observation and data. The roadmap is the output, and it should be short, prioritised and sequenced, with rough effort and cost against each item. Not everything you could fix. The five things worth fixing first, in order, with reasons.

Then comes the part that separates useful consultants from expensive ones: they stay around while the changes happen. Maybe hands-on, maybe a few hours a month reviewing progress and unblocking decisions. Plans meet reality within weeks, and someone needs to be there when they do. If a consultant's involvement ends the day the document is delivered, that document will gather dust.

The Cost, Set Against the Alternative

Rates vary enormously. UK independents and small firms typically charge daily rates in the hundreds to low thousands, and a diagnostic project for an SMB often lands somewhere in the low thousands overall. That's real money for a small business, so be clear about what it's competing with.

It's competing with the cost of getting it wrong on your own. A poorly chosen platform means licence fees, a painful migration, and months of team time spent fighting the tool. A mis-hire made because the role was never properly defined costs far more than the recruitment fee. And a year of the owner spending every evening on admin has a price too, even if it never shows up on an invoice. You're not really paying for a report. You're paying to avoid an expensive wrong turn.

Questions to Ask Before You Hire

A short conversation filters out most of the wrong choices. Ask these before you sign anything:

Vague answers to the first two are the warning sign. The last one is a character test: a consultant who can describe the client they'd turn away will give you straight answers later.

Where to Start

If any of this sounds like your situation, start with a simple exercise: write down the ten tasks that eat most of your week and mark which ones exist because a process is broken rather than because the work is genuinely necessary. That list is the beginning of an audit, whoever ends up doing it.

And if you'd like an outside eye, this is one of the things Fulcrum Three does for UK SMBs. Our operations consultancy covers process audits, workflow design, technology selection and implementation support, and we'll tell you plainly if consulting isn't what you need.