Who should own expansion: sales, customer success, or a dedicated team?
Split it by how hard the sale is. Simple expansions that follow naturally from usage (more seats, the next tier) should sit with CS, because they are already in the conversation and adding a salesperson just slows it down. New products, new departments and anything with a fresh buying committee should sit with sales, because that is a real deal with real procurement. The mistake is choosing one owner for everything. The second mistake is giving CS expansion targets without giving them the training, the pricing authority or the compensation to go with it, which produces resentment rather than revenue.
Go deeper
5 resources, 1 India-specific, 5 link-checked.
📄 Article
✓ Link checkedFreeIntermediate
The Gainsight CEO on why CS should own an NDR number rather than just a churn number, including the idea of giving every CSM their own book of MRR to grow from 100 to 115.
Concrete splits (70/30 or 80/20 base to variable) and the key design warning: pay on gross retention as well as NRR, or CSMs will chase expansion while the base leaks.
Lays out the three real ways to organise a CS team (by segment, by lifecycle stage, by engagement model) and what each one costs you, which is the actual decision a first-time CS leader faces.
Names three scalable structures: embedded digital experience team, centralised content with distributed strategy, and community hub with program satellites.
Forrester's read is that most CS organisations struggle for lack of a clear charter and a segmentation framework.
Tie each program to NRR, gross retention, time to value, renewal forecast accuracy, and health score accuracy.
Kellogg's argument that churn has too many definitions to be trustworthy, and that private companies should measure NDR the way public ones do. The slides are the reference deck for this debate.
Two minutes on the exact ownership question, answered by Indian SaaS operators who have run it all three ways. Useful as the short opinionated take before you commit an org chart to it.