Fractional RevOps: When the Problem Is Your Data, Not Your Reps

A client told me their win rate was 40%. Their CRM said 40%. Their board deck said 40%.

The real number was 22%.

Nothing was falsified. Deals that went quiet were never marked lost, they just sat in the pipeline forever, so the denominator only ever counted deals someone had bothered to close out. Two years of decisions had been made on a number that was measuring the diligence of the reps rather than the health of the business.

They were about to hire two more salespeople to fix a conversion problem that was actually a definitions problem.

The short version

Fractional RevOps is worth buying when your pipeline numbers can't be trusted, not when your reps are underperforming. The tell is simple: if two people pull the same report and get different answers, or nobody can explain what moves a deal from one stage to the next, adding headcount amplifies the problem instead of solving it.

Symptoms that say data, not reps

• Two people pull the same report and get different numbers, and the disagreement is about definitions rather than dates.
• Nobody can say precisely what has to be true for a deal to move from stage two to stage three. Ask three reps, get three answers.
• Forecast accuracy is worse than a coin flip and nobody is surprised any more.
• Your best-performing rep has a personal spreadsheet. That spreadsheet is your actual CRM.
• Deals go quiet and are never closed out, so open pipeline only ever grows.
• Marketing and sales report different lead counts for the same month and have both stopped raising it.

Three or more of those and hiring another rep will make the reporting worse, because you've added another source of inconsistent input to a system nobody trusts.

Here's what most people get wrong

They think RevOps is a tooling job. It isn't. It's a definitions job with some tooling attached.

The instinct when the numbers are wrong is to buy something: a better CRM, an enrichment layer, a dashboard product. I've watched a company migrate from one CRM to another to fix data quality, which is a bit like moving house to deal with clutter. Same boxes, new address, and now half of them are unlabelled.

What actually fixes it is boring and mostly conversational. Someone decides what a qualified opportunity is, writes it down, gets the team to agree, and then enforces it. The software is downstream of that. Do it in the other order and you've bought a more expensive version of the same confusion.

What a fractional RevOps engagement actually does

The first two weeks: find out how bad it is

Audit the pipeline against reality. Pull the last two quarters of closed deals and reconstruct what actually happened versus what the CRM says happened. This is where the gap between the reported number and the real one shows up, and it's usually uncomfortable.

Weeks three to six: fix the definitions

Rewrite the stage definitions so each one has an observable exit criterion. Not "prospect is interested" but something you could verify from the outside: a named budget holder has been on a call, a proposal has been sent, a date has been agreed. Then clean the historical data enough that trend lines mean something.

Weeks seven to twelve: make it stick

Automate the hygiene so it doesn't rely on discipline. Deals that go untouched for thirty days flag themselves. Required fields are required at the point they matter, not at the point of creation where everyone fills them in with rubbish. Reporting gets rebuilt on the new definitions and old dashboards get deleted rather than left running alongside.

That last part is the one people skip. Two sets of numbers in circulation is worse than one wrong set, because now every meeting starts with an argument about which report is right.

When you don't need this

If you have fewer than about twenty deals a quarter, your data problem is a sample size problem and no amount of process will fix it. Spend the money on demand instead.

If your reps are hitting quota and your forecast is roughly accurate, leave it alone. Plenty of businesses run on slightly messy data perfectly well. RevOps becomes worth paying for at the point where decisions are being made on the numbers and the numbers are wrong.

And if the honest problem is that you don't have enough conversations happening at all, clean data won't create them. That's a targeting and volume problem, and it's a different purchase. We covered which purchase fixes which layer in fractional VP Sales versus AI SDR versus agency.

Why fractional rather than a hire

Because the heavy work is front-loaded. The audit, the definitions, the migration and the automation are maybe ninety days of concentrated effort, and then it drops to a few days a month of maintenance.

Hire a full-time RevOps person for that and you have someone brilliant with nothing to do by month five, who will start building dashboards nobody asked for to stay busy. Fractional matches the shape of the work, which is also why so much of this kind of role has moved to flexible and interim contracts in the UK.

Frequently asked questions

What does a fractional RevOps consultant do?

Audits pipeline data against reality, rewrites stage definitions so they're observable, cleans historical records, automates hygiene, and rebuilds reporting on the corrected basis. Usually a concentrated ninety-day engagement followed by light maintenance.

How do I know if I have a RevOps problem or a sales problem?

Ask two people to pull the same report. If the numbers differ and the disagreement is about what counts rather than when it was pulled, it's RevOps. If the numbers agree and they're bad, it's sales.

How long does a fractional RevOps engagement take?

Around twelve weeks for the core work: two weeks auditing, four fixing definitions and data, six automating and rebuilding reporting. Maintenance after that is typically two to four days a month.

Will new CRM software fix my data problem?

No. Migration moves the problem and adds a project. Fix the definitions first, then decide whether the tool is genuinely the constraint. It usually isn't.

What does fractional RevOps cost in the UK?

It sits in the same band as other fractional leadership, broadly £600 to £1,500 a day depending on seniority. We've written up the published ranges and why they should be read as indicative.

Should I fix my data before starting outbound?

Not necessarily. Outbound builds its own dataset and doesn't depend much on the state of your CRM history. If anything, running clean outbound gives you a trustworthy set of numbers to compare the old ones against. Our approach to that is in the signal-based outbound guide.

Who owns RevOps in a small company?

Usually nobody, which is the problem. Below about thirty people it tends to be the founder or a sales leader doing it badly in the gaps. That's fine until the numbers start driving decisions.

Next step

If you're not sure whether your pipeline number is real, that's the first thing we check on a GTM audit. Bring a report and we'll pressure-test it with you.