The Revenue Operations Gap
Most SaaS companies hit a growth ceiling not because they lack demand, but because their revenue infrastructure cannot handle scale. Pipeline exists. The sales team is capable. Marketing is generating leads. But something between these functions is leaking — and leadership cannot see where.
This is the RevOps problem. And it is almost always invisible until it becomes expensive.
What Revenue Operations Actually Is
Revenue Operations is not a department. It is an operating model that aligns sales, marketing, and customer success around shared data, shared processes, and shared accountability for revenue outcomes.
In practical terms, RevOps is responsible for:
- Designing and maintaining the revenue tech stack
- Defining and enforcing CRM hygiene standards
- Building the dashboards that give leadership visibility into the revenue system
- Optimising the handoffs between marketing, sales, and customer success
- Running attribution analysis to understand what actually drives revenue
The distinction that matters: RevOps is not support for sales. It is the infrastructure that makes the entire revenue motion more predictable and more efficient.
The KPI Framework That Actually Works
The most common RevOps failure is measuring the wrong things. Vanity metrics (MQLs, call volume, activity metrics) create the illusion of progress without revealing the health of the revenue system.
The metrics that matter for a scaling SaaS company:
Pipeline Metrics
- Pipeline coverage ratio — pipeline / quota (target: 3–4x)
- Pipeline velocity — (number of opportunities × win rate × average deal size) / sales cycle length
- Pipeline creation by source — which channels are generating qualified pipeline
Conversion Metrics
- Lead-to-opportunity conversion rate
- Opportunity-to-close conversion rate (by stage, by rep, by segment)
- Average sales cycle length (by deal size, by channel, by ICP segment)
Revenue Metrics
- Net Revenue Retention (NRR) — the single most important SaaS metric for growth stage
- Customer Acquisition Cost (CAC) by channel
- CAC payback period
- Expansion revenue as a percentage of new ARR
Efficiency Metrics
- Revenue per full-time employee
- Magic Number — (new ARR / previous quarter S&M spend) × 4
The Tech Stack for Scale
The RevOps tech stack is not about buying the most tools. It is about buying the right tools and integrating them properly so that data flows without friction.
A well-structured RevOps stack for a scaling B2B SaaS company typically includes:
CRM layer — Salesforce or HubSpot. The choice depends on deal complexity and team size. HubSpot for velocity sales; Salesforce for complex enterprise.
Marketing automation — HubSpot, Marketo, or Apollo for email sequences and lead nurturing.
Outbound tooling — Apollo.io, Lemlist, or Outreach for structured outbound sequences.
Conversation intelligence — Gong or Chorus for call recording, coaching, and deal intelligence.
Business intelligence — Tableau, Looker, or a well-structured HubSpot dashboard for revenue reporting.
Customer success — Gainsight or ChurnZero for tracking health scores and reducing churn.
The integration between these tools is more important than any individual tool. A disconnected tech stack creates data silos that make attribution impossible and forecasting unreliable.
Sales-Marketing Alignment: The Structural Fix
The misalignment between sales and marketing is not a personality problem — it is a structural one. It persists because the two functions optimise for different metrics and report to different leaders.
The fix is structural:
1. Shared pipeline targets — marketing is accountable for pipeline created, not leads generated
2. Shared ICP definition — reviewed and updated quarterly with both functions in the room
3. SLA on lead follow-up — sales commits to contacting MQLs within a defined window; marketing commits to quality standards
4. Shared attribution model — agreed rules for how revenue is attributed to marketing and sales activity
5. Joint weekly review — pipeline review with both functions present, focused on quality, not quantity
Building RevOps Without a RevOps Head
Most scaling SaaS companies cannot yet afford a dedicated VP of RevOps. The alternative is to assign RevOps responsibilities explicitly — even if distributed across existing roles — and to standardise the operating rhythm:
- Weekly: Pipeline review, forecast update, deal inspection
- Monthly: Channel performance review, CAC/LTV analysis, tech stack audit
- Quarterly: ICP review, GTM strategy update, OKR review
The operating rhythm is the scaffolding. It forces the conversations that prevent revenue leakage from compounding.
Interested in building a more predictable revenue system? Read our Services page or get in touch to discuss your specific situation.
Want to discuss this topic?
Contact us