Short answer: Hire a full-time operations manager when you have continuous operational work — daily coordination, team management, ongoing delivery oversight. Use fractional or project-based support when the work is designing and building systems, which is finite and specialised. Many businesses need the build first and the manager afterwards, in that order.
The three options
Full-time operations manager. An employee running operations day to day. Coordinates delivery, manages the team, handles suppliers, keeps things moving. Continuous, embedded, generalist.
Fractional operations lead. An experienced operator working part-time across several businesses, typically a day or two a week. Brings senior capability at a fraction of the cost, without the continuity of an employee.
Project-based systems consulting. A defined engagement to design and build the operational infrastructure, then hand it over. Finite, specialised, deliverable-based.
These are frequently treated as substitutes. They're not — they address different problems, and choosing the wrong one is expensive.
The question that decides it
Is your problem running operations or designing them?
If work is being coordinated badly, deadlines slip, suppliers aren't managed and nobody owns delivery — that's a running problem. You need a person doing it continuously.
If work is being coordinated by heroic manual effort because the systems don't connect, data lives in five places, and there's no documentation — that's a design problem. Hiring a manager to run that is hiring someone to maintain a mess, and good candidates recognise it during the interview.
When full-time makes sense
- You have enough continuous operational work to fill a role — typically fifteen or more people, or high transaction volume.
- The work involves managing people, which is hard to do fractionally.
- Responsiveness matters daily.
- You can afford it properly. A capable operations manager in the UK is a significant salary line, and an underpaid one costs more.
When fractional makes sense
- You need senior capability but not full-time hours.
- You're between stages — too big for the founder to run operations, too small to fund a full role.
- You need someone who has seen more operations than you have, which is exactly what working across several businesses provides.
- You want the option to scale involvement up or down.
The limitation: a fractional lead is not present for daily fire-fighting, so the operation has to function without them for most of the week. That usually requires the systems to already be in reasonable shape — which is the sequencing point.
When project-based consulting makes sense
- The core problem is structural: disconnected tools, dirty data, undocumented process.
- You need a defined outcome by a defined date.
- The work is specialised — data migration, system architecture, automation build — rather than generalist coordination.
- You want to hand over documented systems your existing team can run.
The sequencing that works for most businesses: build the systems as a project, then decide whether running them needs a full-time person or a fractional one. Frequently the answer, post-build, is less than you assumed pre-build — because a substantial portion of the operations manager role in a small business is compensating for absent systems.
The cost comparison
Rough UK figures: a full-time operations manager is a five-figure annual commitment plus employer costs, ongoing. A fractional lead at a day a week is a fraction of that with no employment overhead. A systems build is a one-off in the four to five figure range with modest ongoing platform and maintenance costs.
The build is usually the cheapest per unit of problem solved — but only if the problem is structural. If it's genuinely a running problem, a system doesn't solve it and you've deferred the hire for nothing.
Frequently asked questions
Can one person do all three?
Rarely well. Building systems and running operations are different skills and different working modes.
What if we hire a manager and they build the systems?
It happens, and it can work. The risk is that operational firefighting consumes the time, and the build never finishes.
How do we know when we need full-time?
When the fractional or project support consistently identifies work that needs daily presence. That's the signal.
We build the system and hand it over — no lock-in, no dependency. See how we work.
