RevOps explained: revenue operations when you don't have a team
Most RevOps writing assumes a 500-person SaaS firm with a department. Here is what the same job looks like when it is one overloaded person and a shared sheet.
One deal, three departments, three different numbers — and the four break-points.
RevOps is not a tool, a dashboard or a job title you buy. It is a decision about who owns the revenue numbers.
The version almost every Indian mid-market business recognises: marketing says the month produced 300 leads. Sales says it got about 40 worth calling. Finance can see the invoices and nothing in between. Nobody is lying. The three teams are counting three different things and calling them the same word.
RevOps is the answer to that. It sits one level above the question of which attribution model you use — that post covers how credit gets assigned to channels, and this one covers who is allowed to decide what a conversion was in the first place.
What RevOps actually is, and the problem it solves
Revenue operations is a single owner for the plumbing that runs between marketing, sales and customer success: the data, the process, the tools and the reporting.
The term went mainstream after Gartner predicted in May 2021 that 75% of the world's highest-growth companies would deploy a RevOps model by 2025, naming "functional silos handing off clients from one function to the other" as the barrier it removes (Gartner, 17 May 2021). Treat that as a dated prediction about large companies, not a fact about yours.
The problem it exists to solve is specific. There are three handoffs in any revenue engine, and each one leaks:
- Marketing to sales. A lead is passed over with no agreed definition of what makes it worth calling, so sales ignores most of them and marketing concludes sales is lazy.
- Sales to customer success. The deal is closed on promises nobody wrote down, so onboarding starts from scratch and churn risk is built in on day one.
- Everyone to the board. Three teams pull three reports from three systems, and the review meeting is spent reconciling numbers instead of deciding anything.
Note what is not on that list: new software. These gaps are definitional, which is why buying another tool rarely closes them.
RevOps vs sales ops vs marketing ops
These three get used interchangeably and are not the same job. Marketing ops serves the marketing head, sales ops serves the sales head, and RevOps serves the revenue number both roll into.
| Marketing ops | Sales ops | RevOps | |
|---|---|---|---|
| Reports to | Marketing head or CMO | Sales head or CRO | Founder, COO or CRO — above both |
| Owns | Campaign systems, lead capture, automation workflows, source data | Pipeline stages, territories, quotas, forecast hygiene, rep enablement | All of the above plus the joins between them — shared definitions, the handoff, one reported number |
| Core question | Did the campaign work? | Can the team sell faster? | Is the whole engine working, and do our numbers agree? |
| Typical first hire | Automation or analytics admin | CRM administrator | Someone promoted out of one of the other two |
| Fails when | It optimises for leads nobody can sell | It optimises a pipeline fed by bad leads | It gets the title but not the authority to set definitions |
That last row decides whether RevOps works. Someone who can describe the mess but cannot rule on what counts as a qualified lead is a reporting clerk with a better title.
The four things RevOps owns in practice
Strip away the vocabulary and the job is four buckets. Read them as a checklist of work that is currently happening badly or not at all.
- Data. One record per company and per person, deduplicated, with an agreed source field. Most of the pain lives here. It leans on your first-party data discipline and clean conversion tracking.
- Process. The written rules for how something moves from enquiry to customer: the stages, who changes them, and within how long. HubSpot's default lifecycle stages run subscriber, lead, marketing qualified lead, sales qualified lead, opportunity, customer, evangelist — and are explicitly customisable (HubSpot Knowledge Base, last updated 17 July 2026). Most teams inherit those labels and never define them.
- Tooling. Not which tools to buy — our martech stack post covers selection. RevOps owns what the stack is allowed to do: which system is the master record, which fields are mandatory, what syncs where, and who gets admin rights.
- Reporting. One number per metric, one owner, one release calendar. If two people can both publish "leads last month", you do not have reporting, you have opinions.
Everything else labelled RevOps is usually one of these four wearing a costume.
What RevOps looks like at three scales
This is where most advice on this topic breaks down for Indian businesses. The honest answer depends on headcount, and at the small end it is "do not hire".
| Scale | What you actually have | What you genuinely need | What not to do |
|---|---|---|---|
| No RevOps function roughly under 25 people | One CRM used loosely, a shared sheet, the founder doing the monthly report | Written definitions and one agreed source for the pipeline number. A single afternoon of work, repeated quarterly. | Hire for it. There is not enough process to operate yet. |
| One shared owner roughly 25–150 people | A marketing or sales ops person quietly doing both, on top of their actual job | Explicit authority over definitions and the reporting calendar, plus protected time — about a day a week, ringfenced. | Give the mandate and still expect campaigns and month-end close. |
| Dedicated team roughly 150+ people | Two or more people, named systems owners, a real forecast process | A split between data and process on one side, tooling and enablement on the other. | Let it quietly become a dashboard-building desk with no authority. |
The middle row is the hardest. The work is real but does not justify a full salary, so it goes to whoever is most organised and then gets crushed by their day job. The fix is a mandate and a protected day, not a hire.
The one reconciliation problem worth solving first
If you do nothing else from this post, do this. Marketing's "leads", sales' "qualified" and finance's "revenue" never match, and there are four reasons why — none of them anyone's fault:
- Different objects. Marketing counts form submissions, which are people. Sales counts opportunities, which are companies. Three people from one company is three leads and one deal. Forrester's B2B Revenue Waterfall exists precisely because of this: it moves teams off single leads and MQLs and onto connected buying groups instead (Forrester, last modified 3 August 2026).
- Different dates. Analytics tools date a conversion to when it happened. Ad platforms often date it to the click. Finance dates it to the invoice. Same event, three months.
- Different attribution settings. Google Analytics offers three attribution models, and the attribution settings control how key event reports assign credit, including the lookback window (Google Analytics Help, accessed 13 October 2026). Change the setting, change the number.
- Different filters. Someone excludes spam, someone else does not. Someone counts resubmissions, someone else deduplicates.
You will not make these three numbers equal. That is not the goal. The goal is that each one is defined, repeatable and comparable to itself last month. A wrong-but-consistent number beats an accurate number nobody can reproduce.
Our own practice: the one-page definition exercise
In our own work on client accounts, this is the first thing we run before touching a campaign — because marketing reporting is unreadable until it exists. We get marketing and sales in one room and make them answer six questions in writing. It takes under two hours.
| Question | The answer we usually get first | A definition you can actually operate |
|---|---|---|
| What is a lead? | "Anyone who filled the form" | A contact with a named company and a stated requirement, from an approved source |
| What makes it qualified? | "When sales likes it" | A salesperson has spoken to them and confirmed need, authority and a timeframe |
| Who marks it qualified? | Nobody, or both teams | The assigned salesperson, in the CRM, within 48 hours of contact |
| What is one unit? | One form submission | One company — three people from the same firm is one |
| Which date counts? | Whichever the report defaults to | The date the stage changed, stated on every report |
| Who publishes the number? | Three people, three numbers | One named owner, one weekly report, one source system |
Two things we tell clients to expect, before the exercise rather than after.
Your lead count will drop. Deduplicating to companies and requiring a stated need removes a chunk of the old number. Your cost per lead rises on paper the same day. Nothing got worse — the previous number was just counting things that were never going to be called.
The first month is not comparable. You have changed the ruler. Say so, keep the old number alongside the new one for one cycle, then drop it. We do not promise a size for the shift — it depends on how loose the old definition was.
One honest limit. Digital Hangover is a digital marketing agency — we do not sell RevOps consulting, and we are not the people to redesign your sales compensation, territory model or CRM architecture. We own marketing's side of this problem: source data, tracking, the lead definitions we report against and the attribution logic behind them. The rest of the operating model is your sales leadership's job.
How to start without hiring anyone
Six steps, in order, none of which need budget or a new tool.
- Write the six definitions above and put them in one shared document with a date on it. This is the whole foundation.
- Name one owner of the number. One person publishes the weekly pipeline figure. Everyone else quotes them.
- Pick the master system. Usually the CRM. If you are still choosing one, our note on CRM selection for smaller businesses covers that decision properly.
- Make three fields mandatory at lead creation: company, source, and stated requirement. Nothing enters without them.
- Agree one handoff rule with a clock on it. Who contacts a new lead, within how many hours, and what they write back into the record. If you want to prioritise within that queue, lead scoring is the mechanism — but do not score before you define.
- Fix the report, not the dashboard. One page, same metrics, same definitions, every week. Our dashboard guide and the KPI selection post cover what belongs on it.
Review the document quarterly. Definitions drift as the business changes, and a stale definition is worse than none because people still trust it.
What you get when the numbers finally agree
The payoff is not a prettier dashboard. It is that decisions get faster and cheaper.
When one number is agreed, you can see which lead sources produce deals rather than form fills, and shift budget on evidence. You can calculate lifetime value against real acquisition cost instead of a guess. You can tell a retention problem apart from an acquisition problem, which are usually confused with each other. And your analytics stops being a monthly argument.
None of that needs a RevOps department. It needs somebody with the authority to say what a lead is, and a business that stops counting it four ways. Start with the definitions, map them onto the stages in your marketing funnel, and let the rest wait until your headcount earns it.
Frequently asked questions
What is RevOps in simple terms?
RevOps, or revenue operations, is one owner for the plumbing that runs between marketing, sales and customer success — the data, the written process, the tools and the reporting. It exists so the three teams stop producing three different numbers for the same month.
Is RevOps the same as sales ops?
No. Sales ops works for the sales head and improves how the sales team sells — stages, territories, quotas, forecast hygiene. RevOps sits above both sales and marketing and owns the definitions and handoffs between them. A sales ops person cannot rule on what marketing is allowed to call a lead; a RevOps person can.
Do we need a RevOps person at 40 employees?
Usually not a dedicated one. At that size the realistic model is one shared owner — an existing marketing or sales ops person given explicit authority over definitions and reporting, plus about a day a week of protected time. The mandate matters more than the headcount.
What does a RevOps person do day to day?
Mostly unglamorous maintenance: deduplicating records, enforcing mandatory fields, fixing broken syncs, auditing whether stages get changed on time, and publishing one weekly report everybody quotes. Strategy is a small slice of it.
Does Digital Hangover offer RevOps services?
No — we are a digital marketing agency, not a RevOps consultancy. We own marketing's side of the same problem: source data, conversion tracking, the lead definitions we report against and the attribution logic behind them. Sales compensation, territory design and CRM architecture sit outside what we do.
Reporting you can actually act on
We run paid media against defined leads and clean tracking, not form-fill counts.
Make Digital Hangover a preferred source
One tap tells Google to show more of our SEO and marketing coverage in your Top Stories.
