by Vladi Semenov
Head of Sales
4/3/26
Key Takeaways
More companies are asking Customer Success to own a number.
That shift makes sense. Expansion revenue is too important, too efficient, and too visible to leave unmanaged.
But many leadership teams are making the same mistake: they assign CS a renewal or expansion target before they build the system required to hit it.
That is not a compensation issue. It is not a talent issue. It is an operating model issue.
According to Bain & Company's 2024 Technology Report, net revenue retention declined at 75% of software companies even as nearly 60% of those same companies increased their customer success investment. More spend did not automatically produce better outcomes. That should be a warning to any CRO, CFO, or CCO: adding budget to CS is not the same as building a revenue engine.
The opportunity is real. Existing customers now generate 40% of new ARR across B2B SaaS — and over 50% for companies above $50M ARR, according to 2026 data from wearefounders.uk. And expansion revenue is more efficient than net-new by a significant margin: Benchmarkit's 2025 SaaS Performance Metrics report puts the Expansion CAC Ratio at $1.00 versus $2.00 for new customer acquisition. The installed base is simply the more efficient growth vehicle. For finance and revenue leaders, the conclusion is straightforward: if a larger share of growth is expected to come from the installed base, then the installed base needs the same operating discipline applied to pipeline creation in sales.
That is where most companies break down.
Sales usually runs with infrastructure. Signal capture. Prioritization. Workflow. Forecast visibility. Inspection. Accountability.
CS often does not.
Instead, many teams are still operating with static health scores, manual renewal tracking, disconnected product and support data, and reactive outreach. That may be enough for managing relationships. It is not enough for managing a revenue number.
Once CS carries revenue accountability, leadership expectations change. The question is no longer whether the team is engaged or customer-centric. The question is whether the motion is measurable, repeatable, and forecastable.
Can the CCO identify which accounts are most likely to expand and trigger the right motion at the right time? Can leadership see what is working, what is stalled, and what is at risk before the quarter closes?
If the answer is no, then the problem is not headcount.
More CSMs chasing fragmented signals do not create a scalable growth motion. They create a larger cost base against the same weak system. That is how companies increase CS spend without materially improving retention or expansion performance.
This is why "give CS a number" is the wrong first move.
The right first move is to build the revenue system underneath the number.
That means connecting the customer data stack so product usage, support history, CRM context, and success workflows can actually work together. It means moving from static scoring to live signal detection. It means replacing manual follow-up with orchestrated motions. And it means giving leadership visibility into performance early enough to intervene.
That is exactly what Magnify is built for. Magnify connects the systems your CS team already lives in — Salesforce, Gainsight, Zendesk, Pendo, Gong, and 40+ others — and turns that combined signal into automated, measurable expansion motions. Not in quarters. In weeks. The result is a post-sales team that can identify the right accounts, run the right plays, and report on outcomes with the same rigor your sales team applies to pipeline. You wouldn’t send sales into the wild without a marketing system like Marketo providing coverage, why expect anything different from post-sales?
The companies that will win here will not be the ones that simply ask more from CS. They will be the ones that equip CS to operate like a revenue function.
So before you assign a renewal or expansion target, ask a simpler question:
Have we built a revenue system for post-sales, or are we just assigning a revenue number to a service organization?
Because if sales would never be asked to carry a target without pipeline visibility, workflow infrastructure, and forecast inspection, CS should not be either.
👉 Book a Demo to see how Magnify gives your CS team the operating infrastructure to turn expansion targets into predictable, measurable outcomes.
If you’d like to learn more on this topic checkout our CCO’s Growth Automation Playbook
Discover how Magnify helps revenue teams identify risk earlier, uncover expansion opportunities, and turn customer signals into coordinated action.
Book a Demo