What does RevOps actually mean?
RevOps means treating the path from first enquiry to cleared payment as one process with one set of facts. The term is short for revenue operations. Most firms run that path as three or four separate relays: marketing hands leads to sales, sales hands a signed deal to delivery, delivery tells finance when to invoice, and finance chases the money. Each handover is a place where something can be dropped.
A RevOps approach does not add a department. It agrees who owns each step, puts the key records where everyone can see them, and checks the joins between teams on a regular schedule. You can find a one-line definition in the glossary.
Where did RevOps come from, and does it apply to a service firm?
The term is most associated with software companies that sell subscriptions, where sales, marketing and customer success all affect recurring revenue. Much of what is written about it assumes that model: large teams, a dedicated operations hire and a stack of specialist tools.
The idea applies just as well to an agency or consultancy, and the leaks are often worse. A service firm’s revenue depends on people remembering to raise invoices against milestones, retainers and change requests. A software company’s billing system charges the card every month whether anyone remembers or not. In a 20-person agency, nobody is employed to watch the gap between a won deal and its first invoice.
What does revenue leak look like in an agency?
Revenue leak is money you have earned, or could have earned, that never reaches the bank. In a service firm it tends to show up in the same few places:
- A deal is marked won in the CRM, but nobody sets up the billing schedule.
- A milestone is delivered and signed off, but the invoice is raised weeks later, or not at all.
- Extra work is agreed on a call and never makes it onto an invoice.
- An invoice goes overdue and nobody chases it, because everyone assumes someone else has.
- A good lead waits a week for a reply while the team works on whatever is loudest.
None of these is a failure of the CRM or the accounting system. Each tool records its own part correctly. The leak happens in the space between them.
What does a RevOps function do day to day?
A RevOps function makes sure every stage has an owner, a record and a regular check. The table below shows how that breaks down in a typical service firm.
| Stage | The question it answers | Usually owned by |
|---|---|---|
| Pipeline | Which deals are real, and what are they likely to be worth? | Sales lead |
| Handover | Has every won deal got a delivery owner and a billing plan? | Operations lead |
| Billing | Has every due milestone been invoiced? | Operations or finance |
| Collection | Which invoices are overdue, and who is chasing them? | Finance |
| Review | Where did work stall this month, and why? | Founder or managing director |
The review line matters most. Without a fixed moment where someone compares won work against invoices against cash, the other lines drift. For the pipeline stage, sales pipeline stages and the weighted pipeline covers how to put a sensible number on deals that are not yet won.
A worked example: where does the money go?
This example is illustrative, with invented figures. Take a 30-person agency with a sales lead, an operations lead, a part-time finance manager and a founder who still signs off every large deal.
In March the agency wins a £60,000 website project, billed as six milestones of £10,000. The deal is marked won in the CRM. The project manager assumes finance will set up the billing plan. Finance is waiting for the project manager to say the first milestone is done.
| Date | What happened | Unbilled won work |
|---|---|---|
| 1 March | Deal won, no billing plan set up | £60,000 |
| 28 March | Milestone 1 delivered, no invoice raised | £60,000 |
| 25 April | Milestone 2 delivered, still no invoice | £60,000 |
| 3 May | Founder compares won deals with invoices and spots the gap | £60,000 |
| 5 May | Two invoices raised, £20,000 | £40,000 |
| 4 July | Invoices paid, 30 days late | £40,000 |
Nothing went wrong in any single system. The CRM showed a won deal and the accounting system showed no invoices, and both were correct. The agency simply took more than five weeks to invoice work it had already delivered, and then waited a further month for payment because nobody chased on the due date. A monthly check comparing won work to invoiced work would have caught it in late March.
The example also shows why planned billing, issued invoices and cash received are different numbers. Planned, invoiced, collected explains why they should be reported separately.
Do you need to hire someone for RevOps?
Most firms of 10–75 people do not need a dedicated RevOps hire. What they need is a clear owner for each stage in the table above, and one person responsible for the review. In practice that is often the operations lead, with the founder attending once a month.
A hire starts to make sense when the review is taking more than a day a month, when you have several sales people and several delivery teams, or when the data needed for the review lives in so many places that pulling it together has become a job in itself.
How do you start RevOps without a new team?
You start by making the joins visible and giving each one an owner. A practical first month looks like this:
- List every won deal from the last six months and check each one has a billing plan. Anything without one is your first finding.
- Agree one owner per stage. Write the names down. “Sales and delivery” is not an owner.
- Set a fixed monthly review comparing won work, invoices raised and cash received, and keep it on the calendar even when it feels quiet.
- Agree your chasing process for overdue invoices, including who sends the first reminder and when. If you want the legal background, see late payment interest and credit control.
- Track accounts receivable weekly, split by how overdue each invoice is.
Only after that is working does it make sense to look at software. A tool will not choose owners for you, but it can stop the review from depending on one person’s spreadsheet.
Where OpsUPLOOP fits, and where it doesn’t
OpsUPLOOP is operations software for teams that sell and deliver. For RevOps, it connects your pipeline to what you bill: it shows won work next to its planned billing, and keeps planned billables, issued invoices and collected cash as separate numbers. It researches, scores and drafts, and a person decides. Each customer gets their own instance, configured to their firm’s stages, rules and owners. The OpsUPLOOP Billing page shows how that works.
It can be your CRM or sit on top of the one you have, but it is not a cash-flow forecast. It is also not a PSA: it does not do timesheets or resourcing. If your main problem is scheduling people across projects, a PSA is the better buy, and CRM, PSA or operations software? sets out how to choose.
Other questions
Is RevOps a job title or a function?
Both, depending on the size of the firm. Larger companies hire a Head of RevOps with a team. In a 10–75 person firm it is usually a set of responsibilities shared by the founder, the operations lead and whoever runs finance.
Is RevOps the same as sales operations?
No. Sales operations looks after the sales team's process, tools and reporting. RevOps covers the same ground and carries on past the signed deal into handover, billing and collection.
Does RevOps replace the finance team?
No. Finance still owns the ledger, VAT, payroll and the accounts. RevOps makes sure the right work reaches finance at the right time, so invoices go out when they should.
What should you measure first?
Start with the value of won work that has not yet been invoiced, and the value of invoices that are overdue. Both are usually visible within a week, and both point straight at money.