Revenue operations, and who keeps the CRM honest

The symptom everyone recognises

The pipeline report says one number, the founder believes another, and both are guesses because half the deals have a close date in the past and a stage nobody has touched in five weeks. Sales leadership responds by asking reps to update the CRM, which works for eleven days.

This is not a discipline problem. It is an ownership problem. Revenue operations — RevOps — is the function that owns the machinery between marketing, sales and the numbers: the fields, the stages, the routing, the reports and the weekly check that they still mean what they claim.

What the role owns, concretely

Area	What that means weekly
Pipeline hygiene	Stale deals flagged, close dates challenged, duplicates merged — before the forecast call, not after
Reporting	One dashboard everyone trusts, with the definition of each metric written down
Lead routing	Inbound assigned in minutes by a rule, not by whoever notices
Stack maintenance	HubSpot or Salesforce plus the sequencer, the enrichment tool and the integrations that quietly break
Sales enablement ops	Templates, sequences and call recordings organised so a new rep ramps from something

None of this requires being in the room. All of it requires being awake when the forecast call happens, which is why this role transfers cleanly to the same time zone and badly to one twelve hours away.

When you need a person, and when you do not

You do not need a RevOps hire if you have fewer than roughly three reps and one product. At that size the founder can hold the pipeline in their head, and a part-time consultant to configure the CRM once is a better purchase than a full-time owner.

You do need one when there are two or more teams touching the same records, when the forecast has been wrong three quarters running, or when nobody can say how a lead gets from form fill to first call without drawing it on a whiteboard.

Be honest about the third case: sometimes the answer is not a person at all but a two-week cleanup and three automations. We will say that on the call. Where that is the answer, it is the automation work rather than a seat.

The cost, and what stays yours

A U.S. RevOps manager is a six-figure hire before benefits. A nearshore hire doing the same operational work is a fraction of that fully loaded — the comparison worth making is total employer cost both sides, laid out in what a U.S. hire really costs.

Everything the role builds lives in your instance: your fields, your workflows, your dashboards, your documentation. There is no vendor platform in the middle, which means no migration project if the engagement ends.

The first thirty days, in order

The sequence matters more than the tooling. Cleaning data before you have agreed what the fields mean produces a tidy version of the same argument.

Week	Work	Output you can check
Week 1	Write down the definitions: what each stage means, what makes a deal qualified, when a close date may move	One page everyone has read and nobody disputes
Week 2	Map the actual path from form fill or cold reply to first call, including the manual steps	A diagram with the gaps circled
Week 3	Cleanup: duplicates, stale deals, close dates in the past, owners who have left	A before-and-after count, kept
Week 4	The weekly routine and one dashboard, with the definition of each metric on it	A forecast call that argues about deals, not about the data

Week one is the one that gets skipped, and skipping it is why the second cleanup is always necessary. If two people define “qualified” differently, no amount of hygiene makes the pipeline report mean anything.

The four numbers worth watching weekly

Not a dashboard of thirty tiles. Four, reviewed in the same meeting every week, are enough to catch most problems while they are still small: the share of open deals with a close date in the past; the share with no activity in the last fourteen days; median time from lead created to first human contact; and stage-to-stage conversion on the two stages where deals actually die. Each one is a question about the machinery rather than about a rep, which is why the conversation stays useful.

What matters is that the definitions do not move. A metric quietly redefined mid-quarter is worse than no metric, because it produces confident comparisons between two different things.

Where RevOps and the sales team should not overlap

This role keeps the machinery honest; it does not carry a number and it does not manage reps. When RevOps starts being asked to chase reps for updates, two things happen: the data stops improving, because chasing is not a fix, and the role becomes unpleasant enough that whoever holds it leaves. The durable version is that the system makes the missing update visible and sales management owns the consequence.

The same boundary applies to reporting. RevOps owns how a metric is calculated and published; sales leadership owns what the number means for the quarter. Merging those two jobs into one person is how a forecast becomes a negotiation.

What to have ready before the first day

Admin access to the CRM, a list of the tools it connects to, read access to whatever billing or finance system defines revenue, and thirty minutes each with the two reps who use the CRM most and the person who builds the current report by hand. That last conversation is usually the most valuable one of the first week: a hand-built report is a written record of everything the CRM does not currently do.

Common questions