Fractional RevOps means buying senior operations expertise part-time; a first ops hire means owning it full-time in-house. Below roughly £5M ARR the fractional route usually wins on cost and speed-to-value; past that, an in-house owner starts to earn their seat. Here’s the honest split.
At some point between roughly £2M and £20M ARR, every B2B SaaS company has the same conversation: the ops pain is now weekly, someone senior is spending Friday afternoons fixing the CRM, and the question lands on the table — do we hire a revenue operations person, or bring in fractional help?
Full disclosure before anything else: I sell fractional RevOps support. Read everything below with that in mind. I’ve also been the in-house hire — twice, building the function from scratch — so I’ve sat on both sides of this table, and the honest answer is that each option wins in different situations. Here’s the comparison I’d want if I were the buyer.
The real costs, side by side
The full-time hire. A capable mid-senior RevOps manager in the UK runs roughly £60–90K base, call it £75–110K fully loaded. Add three to six months of hiring time, then onboarding before full productivity. Total first-year commitment: comfortably six figures and nine-plus months before the machine is meaningfully better — if the hire is right.
That last clause is the hidden cost. Hiring your first ops person is genuinely hard, because the person who’d be great at it is exactly the person your team can’t yet evaluate — there’s no in-house ops expertise to interview against. Mis-hires at this seniority cost a year.
Fractional. Market rates run roughly £3–6K/month for one to two days a week of senior time (mine sit in that band), typically with a diagnostic up front. First-year cost: £36–70K, starting within weeks, no employment risk, cancellable. You’re buying someone who has built the function before — the pattern-matching from prior builds is most of what you’re paying for.
On pure price the fractional route is cheaper in year one. But price isn’t the axis that should decide this.
The axis that should decide it: volume of work vs. difficulty of work
Ops workload splits into two kinds. Difficult, infrequent decisions: designing the lifecycle, rebuilding scoring, fixing the integration architecture, setting the SLA structure. Frequent, straightforward execution: list pulls, campaign ops, report requests, day-to-day admin, being in the room when things break.
Fractional is built for the first kind. A senior operator at one day a week can carry all the design decisions of a company at this stage — those decisions are hard, but they aren’t forty hours a week of hard. What fractional cannot do is absorb high execution volume or be present at 4pm on a Tuesday when the sync breaks.
So the honest heuristic: count your execution volume. If day-to-day ops requests would fill three-plus days every week, you need a hire (and probably a mid-level one, not a senior one). If the pain is mostly wrong-by-design systems and unmade decisions, seniority-on-tap beats headcount.
The sequencing most companies get backwards
The most expensive common path: hire first, design later. The new hire inherits an undiagnosed mess, spends six months underwater in reactive tickets, and never gets to the structural work — through no fault of theirs. The design debt compounds into their tenure.
The cheaper sequence, whoever you eventually employ:
1. Diagnose — know exactly what’s broken and what it’s costing before committing a six-figure salary to fixing it.
1. Design and fix the structural layer — fractional or project-based, weeks not quarters.
1. Then hire into a working system — and now the job spec writes itself from the roadmap, you know whether you need senior design skills or solid execution skills, and your fractional person can help you interview (the evaluation gap, solved).
Frequently the right long-term answer is a full-time hire — around £10M+ ARR with real execution volume, it almost always is. The fractional stage isn’t a substitute for that; it’s what makes the hire land well.
The contrast plays out predictably. The team that hires a first ops person straight into a broken system spends that person’s first year on archaeology — untangling definitions, routing, and reporting they didn’t build and can’t easily question — and burns out a good hire on cleanup instead of the work they were sold. The team that sequences it — diagnose the system, fix the foundations, then hire — hands its first ops person a working machine to run and improve, and keeps them. Same role, same salary; the difference is whether the hire inherits a diagnosis or has to perform their own while also doing the job.
The questions to ask any fractional provider (including me)
Have you built this function in-house, not just advised on it? What happens when you’re not available mid-week? What does the handover to an eventual hire look like — and will you help recruit them? Is there a diagnostic before the retainer, priced separately? A provider who plans for their own replacement is planning for your success; one who doesn’t is planning for a very long retainer.
—
My version of the sequence: the Pipeline Leak Audit (£3,000 fixed) is step one, and everything after it — fix sprint, fractional, or a roadmap you execute yourself — is optional by design. Start with a free 30-minute health check or send an enquiry.