The remit, concretely
- System ownership — the CRM and its connected stack, including who can change what.
- Data model and definitions — what an MQL is, when lifecycle stage advances, how revenue is recognised in reporting.
- Process design across handoffs — marketing to sales, sales to onboarding, onboarding to success.
- Automation and enablement — routing, scoring, sequences, the plumbing reps never see.
- Reporting and forecasting — one dashboard leadership actually uses.
- Commercial tooling spend — licences, seats, add-ons, and whether they earn their cost.
RevOps vs sales ops vs marketing ops
Small companies do not need three functions. They need one person who owns the system end to end — which is why fractional RevOps became a category.
| Function | Optimises | Typical first hire at |
|---|---|---|
| Marketing ops | Campaign delivery, attribution, martech stack | Marketing team of 5+ |
| Sales ops | Rep productivity, territories, comp, CRM hygiene | Sales team of 8+ |
| RevOps | The handoffs and the shared definitions between all three | 20–50 employees, or after a CRM migration |
Signals you need RevOps now
- Marketing reports 400 leads, sales says they got 90, and both are looking at the same CRM.
- Forecast accuracy is a running joke.
- The person who understands the CRM is a marketer doing it in evenings.
- You've bought tools to fix problems the previous tool was bought to fix.
- Board reporting is assembled in a spreadsheet every month.
What RevOps looks like in the AI era
AI has changed the job less than the noise suggests, but it has changed the stakes. Breeze agents, AI forecasting and AI summaries all consume CRM data — so the value of clean, consistently-populated properties has gone up, not down. A RevOps function that keeps definitions tight is now also the function that makes AI output trustworthy.
The other shift is in what gets automated: routine list-building, note-taking and first-draft outreach are increasingly machine work, which frees RevOps capacity for the architectural decisions that were always the real job.
Full-time, fractional or agency?
A full-time RevOps lead makes sense once the systems change weekly and someone must be in the room for every commercial decision. Below that, fractional gets you senior judgement without the salary — typically a few days a month covering architecture, reporting and the change backlog.
Common mistakes
- Hiring a RevOps lead and giving them no authority to change process.
- Treating RevOps as CRM admin — the admin work is the smallest part of the remit.
- Defining MQL in a workflow instead of in a document everyone signed off.
- Buying a new tool before fixing the definitions the old one was reporting on.
- Expecting AI features to compensate for a broken data model.