"RevOps" has become a job title, a department, an agency promise - and often a rebranded synonym for "Sales Ops". Amplee presents itself as a Salesforce & RevOps firm; so we had better say precisely what we mean by the word, by confronting the definitions in circulation with what actually happens in an org.
01Definition: from product to cash collection
Salesforce defines Revenue Operations as a strategic framework that brings together all revenue-related activities - marketing, sales, customer service and finance. The distinction it draws with Sales Ops is the most useful one we know: sales operations only step in in the middle of the cycle; RevOps covers the entire revenue journey, from product to collection - leads, opportunities, quotes, orders, invoicing, payment, cash collection.
Specialist firms give a tighter version - the strategic alignment of sales, marketing and customer success for predictable growth - and add an idea we fully share: RevOps is run like a product, with a roadmap, sprints and an owner. Not like a project you deliver once.
Sales Ops optimizes a team. RevOps optimizes a flow - the one that runs from first contact to money in the bank.
02What RevOps is not
- Not a rename of Sales Ops. If the scope stops at signature, it is Sales Ops. RevOps begins when invoicing, renewal and customer success enter the same loop.
- Not the go-to-market strategy. GTM defines how you sell: target, message, channels, process. RevOps aligns and equips the teams that execute. The two feed each other, but confusing them amounts to tooling a process nobody has decided on.
- Not a stack of tools. Adding a forecasting tool on top of pipeline definitions nobody shares produces a more precise forecast… of something nobody understands.
03The four pillars - and the fifth one people forget
- Process - a single lead-to-cash flow, with stage definitions shared between marketing, sales, service and finance (see Lead, MQL, SQL: getting the definitions straight).
- Data - one source of truth for the customer, the contract and the revenue; a CRM and an ERP that talk to each other, rather than exporting to each other at every month-end.
- Stack - rationalized and native wherever possible. Our reading: every tool "next to" the CRM is a reconciliation waiting to happen.
- Measurement - analytics and forecasting on stages whose definition does not change from one quarter to the next.
- People - the pillar the diagrams forget: service-level agreements between marketing and sales, a written definition of what a qualified lead is, and training. A process the teams work around does not exist.
04The KPIs that matter
The lists converge from one source to the next. The ones we track systematically, by level of the flow:
- Acquisition: customer acquisition cost (CAC), sales cycle length, win rate.
- Revenue: annual recurring revenue (ARR), contract value, customer lifetime value (LTV/CLV), average revenue per user.
- Retention: churn, renewal rate, net revenue retention (NRR) - the ultimate judge of a recurring model.
- Cash: days sales outstanding (DSO), revenue backlog. This is where RevOps differs from Sales Ops: it looks all the way to the money.
05What it changes in Salesforce, concretely
- A single lead-to-cash data model. Lead → opportunity → quote → contract → order → asset → invoice: Salesforce covers the chain with standard objects, from Sales Cloud to Revenue Cloud. The question is not "which tool", but "where are the breaks" - the quote in a spreadsheet, the invoice in the ERP with no link back.
- Stages defined once. Lead statuses, opportunity stages with their probabilities and forecast categories, campaign member statuses: these are configuration objects, not verbal conventions. One status = one observable criterion.
- Forecasting as a by-product. If the stages are maintained, the forecast is reliable; otherwise no AI tool will save it.
- Finance inside the org. Revenue Cloud carries contracts, orders, renewals and invoicing - but depending on the edition (contracts and orchestration in Advanced, invoicing under the Billing license). The RevOps scope is also drawn at the time of the license quote.
- A product rhythm. Our method - assess, build, support - delivers in short sprints on real cases; RevOps is not decreed in a committee, it shows up in conversion rates.
06Where to start
With an honest diagnosis of the flow: where the lead gets lost, where the quote leaves Salesforce, where the invoice does not come back. That is exactly the purpose of our Health Check. To go further downstream: Quote-to-Cash: the 7 steps. To scope: our Sales Cloud & RevOps expertise or a 30-minute conversation.