Retention is everyone's priority and nobody's job.
Every leader agreed that existing customers protect the revenue line. Almost none said their organisation resourced it that way.
One head of CS described renewals as having "no clear owner". Sales and partnerships get the focus, while retention is an afterthought. Their team only began building basic renewal tracking in the last nine months: knowing when renewals fall, then triaging which healthy accounts to leave alone and which at-risk accounts to engage early.
A post-sale advisor put it more bluntly, arguing that post-sale should run with the same structure, inspection and rigour as pre-sale, just not run by salespeople. They see chief revenue officers as the natural owners: they carry the whole revenue number yet have no equivalent controls for the post-sale half of it. A fractional CS leader agreed the message is finally landing with founders and investors, because "they have to".
"Our dirty little secret in SaaS is that our business model is all about net retention… and we put barely any resource to it."
The perception gap compounds the resourcing gap. CS work is often reactive firefighting of problems inherited from the sale, without the visible "big win" moments that new-logo teams enjoy. Several interviewees linked this directly to fatigue across their teams.
Private SaaS data points the same way: among companies above $1M ARR, those with NRR of 110% or more grew faster than the 24% median, while those below 100% grew slower.³
Retention needs a named owner, a calendar and a pipeline view, just like new business does.
Our free retention health check scores your ownership, data and billing visibility. No integrations required.
Check your health score →Accountability without authority was the clearest gap between what CS leaders are responsible for and what they control.
A payments CSM described how even a small issue can involve product, engineering, support, a payment provider and the customer's own technical team. "The customer sees one company," so the CSM ends up as the bridge. They believe CSMs should own the customer outcome, but not every task required to achieve it. Another CSM described the same mismatch: engineering optimises for technical stability while CS feels the immediate human impact, and getting progress updates is a manual, chase-heavy process.
In early-stage companies the constraint is capacity. A leader combining business development and CS said there simply is not enough engineering time to serve existing clients and new business at once, and missed deadlines put renewals at risk. Meanwhile, the role keeps expanding. One advisor said CS too often drifts into support, into "shadow professional services, which is really expensive", or into sales, "which can erode trust".
Experienced people "get pulled the most into everything… and that doesn't scale."
Burnt-out employees are nearly three times more likely to plan to leave within a year,¹¹ and every CSM who leaves takes account context with them.
Give CS shared visibility across teams so coordination happens in a system, not in a CSM's inbox.
A CS operations lead sees companies moving towards "skeleton crew" CS teams that trust their process to multiply output. They described CSM roles as a 40-hour job attached to a book that demands 80, and their goal as enabling one person to do what used to take four. Their test for any process: would a five-year-old understand it? The wider service market is moving the same way: over 80% of customer service organisations expect to reduce agent headcount in the next 18 months.¹³