In short
- RevOps (revenue operations) is the systems, data and processes behind marketing, sales and customer success: the CRM, the pipeline stages, the handoffs and the reports.
- It makes the funnel measurable, so you can see where deals come from and where they get stuck.
- At the early stage it can start small: one CRM, clear stages, and one definition of a lead that everyone uses.
- RevOps measures the message; it can't fix it. The segment and the positioning decide what's worth tracking.
A founder asks a simple question: where do our best deals come from? Marketing has one answer, sales has another, and the CRM has a third, half filled in.
Three answers to one question usually means the systems behind the funnel were never set up to agree.
What RevOps is
Revenue operations is the layer of systems, data and processes behind everyone who brings in revenue: marketing, sales and customer success. It covers the CRM, the pipeline stages, the lead routing, the handoffs between teams, the automations and the reports.
Its job is to make the funnel visible and reliable. When it works, you can see how many leads came in, where they came from, how many became meetings and deals, and where they got stuck.
What it looks like at the early stage
An early-stage startup doesn't need a RevOps team. It needs a few basics done well:
- One CRM everyone actually uses, like HubSpot.
- Clear pipeline stages with a definition for each, so "qualified" means the same thing to everyone.
- Source tracking, so every lead carries where it came from.
- A clean handoff from marketing to sales, and from sales to customer success.
- A short weekly report the founders read.
Settle the definition of a lead first. Ask marketing, sales and the founders what a lead is, and you may get three answers again. Write it from your segment and your ICP: someone at a company that fits, who did something that shows real interest, like asking for a demo or replying to outreach. Everyone else can stay on your email list without being counted in the pipeline.
In the startups where I built the marketing function, I built the RevOps hands-on too, including the RevOps behind an ABM program, and it came after the positioning, the foundation everything else was built on.
RevOps and positioning
RevOps measures the message, and it can't fix it. If the positioning is open, the CRM fills up with leads from five segments, and the reports can't tell you which one to focus on.
The positioning tells RevOps what's worth tracking. Once you've chosen a target segment and an ICP, every lead can be tagged against them, and the reports start answering the questions the founders care about: are we winning the buyers we chose, and how fast?
So put the leads that fit next to the total in the weekly report. After a positioning change, the total can drop while the leads that fit go up, and a report that shows only the total can hide that the change is working. The repositioning page has more on judging a new positioning.
RevOps and the GTM team
Marketing, sales and customer success work best as one GTM team. RevOps is what makes that real in practice: one set of definitions, one source of data, one view of the pipeline. Without it, each team reports its own numbers and the meetings turn into arguments about whose number is right.
RevOps with AI tools
AI tools now sit on top of the CRM: summarizing calls, enriching leads, drafting follow-ups, scoring accounts. They're only as good as the data and the context under them. Clean stages give them reliable data, and your marketing brain gives them the positioning to write from.
Where it fits
RevOps comes after the decisions it measures. Lock the positioning first, then set up the system that tracks whether it's working. The positioning sprint covers the first part in 3 weeks.
How does your own homepage score? Get a free homepage audit: your homepage scored on the same 7 dimensions of positioning, with a line from your own page behind each score. Free, private, never published.