Most Customer-Led Growth initiatives struggle with budget season. Though the economics are typically strong, the issue is that the people asking for budget speak CS, and CFOs speak finance. If you’ve ever walked out of a planning meeting with a vague commitment to “revisit this next quarter,” this is probably what happened.
The mistake is building the business case around the motion rather than the return. Proposals focused on headcount, tooling, and better onboarding sequences land in the CFO’s pile of “cost requests dressed up as strategy.” What lands as investment is a proposal with a clear return, a credible model, and an honest answer to what happens if the company does nothing.
This post is about how to build that case. The illustrative numbers below use a $50M ARR base. Your actual figures will differ, and the model is designed to be calibrated to your situation.
What CFOs actually evaluate
Before drafting the business case, it helps to understand the four questions every CFO works through when evaluating a growth investment:
- What does this cost?
- What does it return, and when?
- How confident are you in that projection?
- What is the cost of not doing this?
Most CLG presentations answer question one thoroughly, gesture at question two, and skip three and four entirely. That’s a problem, because three and four are where most investment decisions actually get made. A return projection without a confidence argument reads as a guess. A case with no cost-of-inaction analysis makes doing nothing look free, which it isn’t.
The financial frame
CLG economics are genuinely CFO-friendly once you translate them out of CS language. But the numbers below only hold if you’re catching the underlying signals early enough to act on them. A signal-based revenue system is what turns “NRR went up” from a lagging report into something you can actually plan and budget around.
Net Revenue Retention as a revenue line
NRR is often presented as a CS performance metric: how well the team retained and grew the base. That framing is part of the problem. NRR makes a poor north star on its own precisely because it’s a lagging indicator, not a lever you can pull directly. For the business case, reframe it as a revenue line instead. On a $50M ARR base, a 10-point NRR improvement from 105% to 115% generates $5M in incremental annual revenue. That revenue costs far less to produce than new logo acquisition, because the customer acquisition cost is already sunk. The incremental sales motion is shorter, the relationship is established, and the conversion rate is structurally higher.
The CFO’s comparison isn’t “should we fund CS better?” The comparison is “where does this $5M come from most efficiently?” When framed that way, expanding the existing base often wins.
CAC versus expansion cost
New customer acquisition costs significantly more than expanding an existing account. The spread varies by industry and sales model, but it’s routinely in the 5x to 7x range. That ratio matters for the business case because it gives you a denominator for the return comparison. If your average new logo CAC is $50K and your average expansion CAC for a similar revenue increment is $8K to $10K, CLG investment compounds that efficiency advantage across every account in the base.
Gross churn as a burn rate
Gross churn is easier for CFOs to grasp when presented as a burn rate rather than a percentage. On a $50M base, each point of gross churn represents $500K in annual recurring revenue that has to be replaced at full acquisition cost. If you’re running 6% gross churn, that’s $3M a year going out the door before you generate a dollar of growth. Reducing it by two percentage points recovers $1M in revenue that would otherwise require $5M to $7M in acquisition spend to replace.
That is a compelling ratio. Present it that way. It’s also worth being explicit that churn reduction and expansion are not the same motion. Retention protects revenue; growth creates it, and the business case is stronger when it treats them as two separate levers with two separate owners, rather than bundling them as one generic “CS investment.”
Experience Yield: the return on CS investment
Most CS organizations track inputs (headcount, tooling spend, QBRs delivered) and outputs (NPS, CSAT, renewal rate). What they rarely track is the return on each dollar of CS investment in terms of retained and expanded revenue. Experience Yield is that ratio: revenue retained and grown per dollar invested in the post-sale motion.
The concept will feel familiar to a CFO, because it’s ROI applied to a function that historically hasn’t been expected to account for it that way. Introducing it does two things. It anchors the CLG business case to a trackable metric. And it signals that you’re not asking for budget on faith: you’re proposing a ratio you intend to measure and improve over time.
If you’re starting from scratch and don’t have a baseline, acknowledge it. Propose a measurement framework as part of the investment. A CFO who sees you’ve thought about accountability will be more willing to approve a first-year cost than one who suspects the return will never be measured.
The worked example
The model embedded in this post uses a $50M ARR base, but the structure applies at any scale. The three inputs that drive the case are: NRR improvement, gross churn reduction, and CLG investment cost.
A representative scenario for a mid-market SaaS company at this scale might look like this:
Current NRR of 105%, with a realistic improvement to 110% over 18 months through better expansion signals, more deliberate QBR structure, and a CLG Council that brings CS and revenue leadership into alignment. That 5-point NRR improvement translates to $2.5M in incremental expansion revenue annually. This is where signal-based expansion does the real work: the NRR number doesn’t move on its own, it moves because someone built the infrastructure to spot expansion-ready accounts before they ask.
Gross churn reduction of 2 percentage points, from 6% to 4%, through earlier risk identification and more proactive intervention. That’s $1M in retained revenue that would otherwise require $5M to $7M in new logo spend to replace.
Total annual revenue impact: $3.5M.
Annual CLG investment — incremental headcount, enablement, tooling, and program infrastructure: $1.5M.
Net return in year one: $2M.
Experience Yield: $2.33 in revenue impact for every dollar invested.
Cost of inaction: $3.5M in revenue left exposed annually, with no path to improving the ratio.
These numbers are illustrative. A company running 110% NRR already will have different headroom than one at 95%. A company with low gross churn has a different cost-of-inaction argument than one losing 10% of the base each year. Use the sliders in the model above to calibrate the scenario to your actual situation before walking into the CFO conversation.
The confidence argument
Even a compelling model will hit resistance if you can’t answer question three: how confident are you in that projection?
The honest answer is that CLG return projections carry more uncertainty than, say, a new sales territory investment, because the motion is less linear. But there are two things you can do to make the case credible.
First, anchor it to the baseline. Show the NRR variance across your current account base. Almost every company has a segment of accounts with meaningfully better NRR than the average, and a segment performing well below it. If you can identify what separates the two groups, you have the beginning of a hypothesis about what drives the return. That’s more credible than a projection built on benchmarks from analyst reports.
Second, stage the investment. A CFO is more likely to approve a structured pilot with defined success criteria than a full program with uncertain returns. Propose a 90-day measurement phase tied to a cohort of accounts, with clear metrics and a decision gate before the broader rollout. It reduces the perceived risk without reducing the ambition.
If your organization is still relying on dashboards and satisfaction scores to make this case, it’s worth being honest about why the projection feels shaky. That gap is usually a measurement maturity problem, not a CLG problem. Most companies are stuck at the stage where they can describe account health but can’t yet connect it to a forward revenue number. Naming that gap explicitly, and proposing to close it, is itself part of the confidence argument.
A word on org design
Before you finalize the business case, be specific about what CS actually owns in your organization.
In some companies, expansion into new buying centers sits with Sales. In others, it’s split, with CS owning vertical expansion and Sales owning new departments or divisions. That distinction matters enormously for how you frame the return.
If your CLG business case implicitly claims expansion revenue that your Sales organization considers its territory, you’ll spend the CFO conversation relitigating an org design question neither of you wants to resolve in that room. Build the case around the revenue motion CS clearly owns, and let the numbers stand on their own. If the expansion/CS boundary is genuinely blurry, address it before the meeting, not during it.
The CLG argument doesn’t require CS to own everything. It requires CS to own something measurable and to demonstrate a return on that ownership.
What not to lead with
A few things that tend to undermine CLG business cases before they get traction:
Leading with NPS or CSAT. These are satisfaction metrics, not revenue metrics. A CFO looking at a business case grounded in satisfaction scores will reframe the conversation as a cost question. Start with revenue outcomes.
Framing CLG as “investing in the customer experience.” That’s a brand positioning argument, not a financial argument. CFOs fund returns. The customer experience is the mechanism, not the case.
Asking for budget without a measurement framework. If you can’t describe how you’ll track Experience Yield or NRR improvement at the cohort level, the business case looks like a cost request with optimistic assumptions attached. Come in with a measurement plan, even a rough one.
The cost of doing nothing
This is the most underused element of the CLG business case, and it’s the one that tends to land hardest in the room.
The cost of not investing in CLG is not zero. It’s the CAC you’ll spend to replace churned revenue that a better post-sale motion would have retained. It’s the expansion revenue that stays unrealized because no one built the signals and plays to capture it. It’s the compounding disadvantage of a competitor that builds a stronger CLG motion in your installed base before you do.
On a $50M base running at current industry-average NRR and churn figures, the cost of inaction runs in the millions annually. Put that number in the conversation explicitly. Make the CFO compare “invest $1.5M and return $3.5M” against “invest nothing and leave $3.5M exposed.” Framed that way, the question isn’t whether CLG investment makes sense. The question is why it hasn’t happened sooner.
One more thing
The strongest CLG business cases aren’t the ones with the most sophisticated financial models. They’re the ones where the CS leader clearly understands the revenue mechanics of their business. A CFO who sees that will trust the projection more than one who gets a polished deck built on analyst benchmarks.
Know your NRR by cohort. Know your gross churn rate and what’s driving it. Know your expansion rate by segment and where the variance is highest. Build the case from that data, not from industry averages. That’s what makes the difference between a budget conversation and a strategic alignment conversation.