Most revenue operators can tell you their MQL conversion rate, their pipeline coverage ratio, and the number of records they cleaned last quarter. What fewer can tell you is how any of those activities connect to the value of the business they work for. That gap — between the work RevOps does and the outcomes executives care about — is one of the most persistent positioning problems in the discipline.
In a recent RevOps Co-op webinar, Matthew Volm, CEO and Founder of RevOps Co-op, sat down with Steve Busby, CEO and Founder of Revenue Operations Associates, to walk through the math behind revenue growth. The session drew on content from the Revenue Operations Certification that RevOps Co-op and Revenue Operations Associates developed together — specifically the module covering how RevOps activities connect to enterprise value. The goal was straightforward: help revenue operators stop talking in activities and start talking in outcomes.
The framing Busby established at the outset matters for everything that follows. Business leaders — boards, CEOs, private equity owners — care about one thing above all others: enterprise value. And enterprise value is a function of cash flow: how much a business generates, how predictably it generates it, and how sustainable that generation is.
"What RevOps is doing is directly tied to that, and I think there's a positioning and communications gap — RevOps tends to talk in activities as opposed to outcomes. The single most important thing we want to do today is give you a sense of what you do and how it relates to those outcomes, particularly the ultimate outcome." — Steve Busby
Enterprise value is determined by revenues minus expenses, which produces net income, which converts to cash flow. Earnings before interest, taxes, depreciation, and amortization (EBITDA) is the most commonly used proxy for that cash flow figure. Apply a multiple to EBITDA — which varies by industry and growth profile — and you have an enterprise value. For the hypothetical "Acme Company" Busby used as an example during the session: $50 million in revenue, $5 million in EBITDA at a 10% margin, and a 10x multiple yields an enterprise value of $50 million.
The practical implication for RevOps teams is significant. Every activity you do ultimately flows into one of two buckets: driving more revenue or driving more earnings. As Volm put it during the session, "If you are interacting or speaking with your CEO, someone on the executive team, the board — ultimately they want you to tell them how you are helping to accomplish one of two things: driving revenue or driving income." The field update in Salesforce, the comp plan revision, the new onboarding workflow — all of it should trace back to one of those two things, and the data management principles that make RevOps work are only valuable insofar as they connect to that chain.
One of the session's most direct challenges to conventional RevOps thinking came in Busby's breakdown of the revenue growth equation. Revenue growth is not just a function of new business acquisition. It is the result of four variables:
Most pipeline reporting, most vendor tooling, and most conference content focuses almost exclusively on the first variable. The other three often receive a fraction of the attention proportional to their actual impact on net revenue growth.
"Don't just report them, understand them. And I think most people are shocked once they realize that, geesh, for the four things in our revenue equation, there's so much focus on new that expansion, churn, and contraction could be 30, 40, 50% of revenue growth — but does that get 30, 40, 50% of your time and resource allocation as a business? Usually it gets less than what it merits." — Steve Busby
Busby illustrated the point with three hypothetical companies, all growing new customer revenue at 10%. Company A had significant churn eating away at that growth — a leaky bucket scenario. Company B was both growing new customers and expanding with existing ones, resulting in 15% net growth and the kind of profile that commands a high valuation multiple. Company C was treading water: moderate new growth offset by moderate losses. The session's second poll asked attendees which company they'd want to acquire; the answer was overwhelmingly Company B. The point is obvious in hindsight, but the practical implication is that most RevOps teams are spending their days optimizing for Company A's metrics.
The sports analogy Busby used here is worth sitting with: "Most companies, it's all about the offense — it's sexy, touchdown passes, quarterback. That's the new revenue. But defense wins championships. And same thing, your CS and account management function can score huge points, and ultimately they win or lose games more often than just a sexy offense."
This connects directly to how ideal customer profiles (ICPs) are constructed. Busby's challenge to teams: start with the retention and expansion ICP — who stays longest, spends most, and is cheapest to serve — and then ask marketing to go find more of those people. Too often, ICP is built backward from quota attainment rather than from long-term customer economics.
Net revenue retention (NRR) is the metric that captures all four variables of the revenue equation in a single number. An NRR of 100% means a business is flat with its existing customer base — it's growing as fast as it's losing. Below 100%, the existing customer base is shrinking, and new customer acquisition is simply filling a hole. Above 100%, the business is growing even before it adds a single new logo.
Busby described NRR above 100% as the conditions under which both revenue engines fire simultaneously — and the combination of strong new business acquisition and strong NRR is what creates the highest enterprise values.
"The holy nirvana is we're growing with our existing customers, and we're finding new customers. And those are the companies that have huge enterprise values." — Steve Busby
For RevOps teams, the practical question is: what is your company's NRR, and what are the specific operational drivers moving it in either direction? Overselling, poor onboarding, inadequate account management, and pricing structure mismatches are all factors that pull NRR down — and all of them are areas where RevOps has direct influence. The discipline of building a better funnel for growth and success teams is directly connected to NRR outcomes, even if that connection rarely gets articulated in those terms.
Busby described customer lifetime value (CLV) as his favorite metric in the entire revenue lexicon — and spent more time on it than any other topic in the session. The reason is structural: CLV is one of the only metrics that forces marketing, sales, customer success, account management, and finance to share a common scorecard.
The calculation is a mini profit-and-loss statement for an individual customer: total revenue earned over the life of that customer, minus the cost to acquire (customer acquisition cost, or CAC), minus the cost to serve. The result is the profit that customer generates over their lifetime — and the economics compound dramatically when customers stay for multiple years, because CAC is incurred once while revenue and (ideally) margin continue.
"Your ability to say, 'Hey, boss, I'm seeing this and 6, 12, 24 months out, we don't fix this, we're gonna have a real issue, and here's three things I think we should be doing' — and you're prepared and you've done the math. That's how you elevate." — Steve Busby
There are four levers that directly move CLV: average revenue per unit (ARPU) or average selling price, retention rate (which determines customer lifespan), CAC, and cost to serve. RevOps has a hand in all four. Busby's practical advice on CAC: start simple. Don't over-engineer the calculation out of the gate. Take sales plus marketing expense for a period, divide by the number of customers acquired in that period, and use that as your baseline. Compensation can be layered in as the model matures.
Volm added a critical note on churn rate calculation that deserves emphasis: the denominator matters. One divided by churn rate gives you the estimated customer lifespan — but the churn rate must be measured on a term that matches the actual contract structure. If customers are on month-to-month contracts but churn is measured annually, the calculation will produce a misleading lifespan estimate. Annual contracts, quarterly contracts, and consumption-based models all create different measurement requirements. Getting the data right before drawing conclusions is as important as knowing which formula to use.
Busby organized the session's content around five primary levers that RevOps teams can pull to move enterprise value:
1. New customer acquisition. The familiar territory — pipeline, conversion, sales velocity. Critical, but over-indexed relative to its share of the full revenue equation.
2. Net expansion. Growing revenue from existing customers through upsells, cross-sells, and price increases. Often underweighted in revenue planning and resource allocation.
3. Pricing. Busby was direct about this: pricing is one of the highest-leverage levers available, and RevOps teams are often well-positioned to surface insights about where pricing power exists or where pricing structure could be modified to capture more value. Incremental revenue from a price increase flows to the bottom line at a higher rate than incremental revenue from new customer acquisition, because cost of goods sold and CAC are already accounted for.
4. Productivity and efficiency. Marketing return on investment (MROI), sales efficiency, revenue per employee — these are the operational metrics that reflect how well a business converts resources into revenue. AI is beginning to show up here, but as Busby noted, the proof is in whether revenue per employee is actually improving. If it isn't, the productivity benefit isn't yet materializing in the economics.
5. Cash conversion. Less squarely in RevOps' lane, but worth understanding. As Volm illustrated with the example of shifting from upfront seat-based pricing to consumption-based models: the timing of cash flows matters enormously to finance, and RevOps decisions about pricing structure, contract terms, and compensation design all have cash flow consequences. Being able to speak that language with the CFO is a meaningful differentiator — particularly as usage-based pricing models become more common.
The most memorable moment of the session was the Acme Company example — a worked calculation showing how specific RevOps initiatives translate into enterprise value impact.
Starting point: a company with $50 million in revenue, $5 million in EBITDA, a 10% profit margin, and a 10x valuation multiple, yielding an enterprise value of $50 million.
RevOps initiatives modeled:
- $2 million in incremental revenue from better targeting, improved conversion, and pipeline velocity improvements (4% revenue growth)
- $1 million in churn reduction from improved onboarding, account management, and customer health monitoring
- $500,000 in operating cost reduction from process efficiency improvements
- After adjusting for gross margin on the incremental revenue, the combined EBITDA impact was approximately $2 million
At a 10x multiple, $2 million in EBITDA translates to $20 million in incremental enterprise value — a 40% increase in the value of a $50 million company.
"It sort of really is that simple: if you can quantify and substantiate, 'I had $100,000 EBITDA impact,' and you know your business trades at 10 times EBITDA, so that $100,000 is worth $1 million — if you did that, they'll say, 'Great, you added a million. We know exactly what we're paying you.'" — Steve Busby
The session made clear that this math doesn't require a giant intervention to be meaningful. Even $100,000 in EBITDA impact, at a 10x multiple, is $1 million in enterprise value. The business case for RevOps investment essentially writes itself — once the math is done and the connection is articulated.
Busby closed with a framework for the metrics RevOps professionals should be fluent in across the full revenue cycle — from the left side of the bowtie (awareness and demand generation) through the middle (pipeline and sales) to the right side (customer success, retention, and expansion).
Outside the funnel entirely: total addressable market (TAM), serviceable addressable market (SAM), and serviceable obtainable market (SOM). These define the ceiling and focus for revenue planning, and understanding whether a market is growing or contracting informs where RevOps resources should be concentrated.
Within the funnel and revenue cycle, the key metric buckets:
The point isn't to know all of these in equal depth. It's to understand which of these your company's leadership team uses to measure progress, and to be able to connect your work to those numbers. As Busby put it: "Shift from activity reporting towards outcome reporting."
For RevOps professionals looking to elevate their strategic impact, this is the mechanism. Not doing more work, but connecting the work that's already being done to the outcomes that leadership actually tracks — and being able to make that case credibly, with math behind it.
The conversation Busby and Volm outlined is ultimately about positioning — helping RevOps teams communicate their work in the terms that matter most to the people who fund, promote, and extend the influence of that work. The math behind revenue growth is not complicated. Connecting it to what you do every day is closer than most operators realize.
Learn more about how Revenue Operations Associates helps companies build and execute the RevOps function in a way that connects directly to enterprise value — and check out the Revenue Operations Certification available through RevOps Co-op for a deeper dive into the metrics and frameworks covered in this session.
Check out our blog, join our community and subscribe to our YouTube Channel for more insights.
