Expansion and upsell should be owned by whoever can see the signal first and keep the customer relationship intact, with a clear rule for when the deal moves to someone else. For most B2B teams, that means customer success owns spotting and qualifying expansion inside the existing footprint, sales or account management owns the commercial close for larger or net-new deals, and both work from one shared account record. The org chart matters less than the handoff rules and how credit is split.
Quivly, the AI workforce for post-sales teams, supports that split without making either team rebuild the account story. Each customer’s health, usage, revenue, support, calls, and Slack sit on one profile, and CRM deals appear in Opportunities next to that context. An expansion Agent or Play can surface accounts ready to grow and draft the outreach, then wait for the right owner to review it before anything goes out.
Key Takeaways
- The sales-versus-CS fight is usually about credit and customer experience, not about who is better at selling. Name both problems before choosing a model.
- Split ownership by expansion type: growth inside the current contract is different from a new product, a new team, or a large multi-year deal.
- Write down the handoff rule, the moment and the information that move a deal from one owner to the other.
- Agree on credit before the year starts, so neither team has a reason to reach around the other at renewal time.
- Both teams should work from the same account record, so the seller never walks into a call blind to open issues.
- Review the model every quarter using real deals, not opinions.
Why Do Sales and Customer Success Fight Over Expansion?
A post-sales leader we spoke with runs implementation, support, and success under one org. Planning for next year had turned into a standing argument with sales over who owns expansions and upsells. Sales gets nothing for renewals, so it wants upsell for quota credit. The post-sales team had seen what happens when that goes wrong: in the past, sellers re-engaged customers at renewal time, created friction, and left behind a list of new demands that the CS team then had to absorb.
That story has three separate problems tangled together:
- A credit problem. If one team gets no recognition for growth in the base, it will look for a way to get it, even if that means stepping into an account it doesn’t know.
- A context problem. A seller who joins late, without the history of tickets, calls, and promises, can make commitments the delivery team can’t keep.
- A timing problem. When expansion conversations bunch up at renewal, every pricing talk becomes a negotiation about the whole relationship.
Picking an owner fixes only the first problem. The handoff rules fix the other two. If you’re still sorting out how other post-sales roles split the work, this breakdown of who owns what across FDEs, solutions engineers, and CSMs covers the delivery side.
What Should Decide Who Owns Expansion? 6 Criteria
Use these criteria to pick a model, or to test the one you have today.
- Where the expansion signal shows up first. Seat growth, usage near a limit, and new teams asking for access usually appear in product and support data that CS watches every day. Whoever sees the signal first should at least own qualifying it. In Quivly, usage, health, and support sit on the same customer profile, so the signal is visible to both teams.
- The type of expansion. More seats or usage on the current product is close to account management. A new product line, a new business unit, or a multi-year commitment is closer to a new sale. Many teams split ownership along this line.
- How the motion is measured. If CS carries a retention or net revenue target, it has a reason to grow accounts. If only sales carries a growth number, expect sales to push for ownership. Align measures before you assign owners.
- Customer experience. The customer should not have to repeat their history to a new person. Whoever joins the account needs the full context before the first call.
- Capacity and skill. A CSM covering a large book may not have time to run a complex commercial cycle. A seller with a large new-business quota may not have time to nurture small upsells.
- A visible handoff. Everyone should be able to see who owns each open expansion deal and what stage it’s in. Quivly shows CRM deals as a board, list, or calendar, org-wide or on each customer, with saved views both teams can share.
| Ownership model | Works best when | Watch out for |
|---|---|---|
| CS owns expansion end to end | Expansion is mostly seats or usage on the current product, and CS carries a growth target | CSMs without commercial skills or time; growth treated as a side task |
| Sales or account management owns expansion | Expansion deals are large, new-product, or multi-year, and need a full sales cycle | Sellers joining late without context; friction at renewal |
| Split by expansion type | You can define the line clearly, for example current product versus new product | Gray-zone deals with no owner; rules nobody wrote down |
| CS sources, sales closes, shared credit | Both teams need a reason to cooperate on the same accounts | Unclear credit rules; double-counting in forecasts |
How to Set Expansion Ownership and Handoff Rules, Step by Step
These steps take you from a standing argument to a written model both teams can run. Each step shows how Quivly handles it.
- List the expansion types you actually sell. Pull recent expansion deals and group them: more seats, more usage, new product, new team, new region. Decide which types stay with CS and which go to sales. Write the line down. In Quivly, the Opportunities list view lets you filter and sort deals synced from your CRM, so the review starts from real deals.
- Agree on credit before you assign owners. Decide how credit works when CS sources a deal and sales closes it. Keep it simple enough that every rep can explain it. Quivly doesn’t set compensation; this is a leadership decision, and it removes the main reason for one team to reach around the other.
- Define the signals that open an expansion conversation. Agree on what counts: usage near a plan limit, new teams asking for access, a new stakeholder, a healthy account approaching renewal. This guide to spotting upsell-ready accounts from usage data covers the signals themselves. In Quivly, you can build an Agent from the Expansion spotter template, which runs on a schedule or when usage crosses a threshold, looks up usage and contacts, and drafts outreach for review.
- Route each signal to the agreed owner. Signals for in-footprint growth go to the CSM. Signals for larger deals go to the CSM and the named seller together. A Quivly Play can target a customer segment, send alerts to the account owner’s Slack DM or a channel, and email the owner plus named teammates. With Manual approval, the customer owner reviews proposed changes before anything runs.
- Write the handoff brief. When a deal moves to sales, the seller gets one brief: goals, current usage, open tickets, recent calls, commitments already made, and who the stakeholders are. In Quivly, a CSM can draft that brief in the customer’s notebook from connected data, and the seller can ask follow-up questions in Ask Quivly or in Slack without logging into five systems.
- Keep the seller and CSM on one record. After the handoff, both teams see the same deal and the same account. Quivly shows the customer’s deals on its Opportunities tab, and open pipeline feeds the customer’s revenue picture and health score context. The CRM stays the system of record, so deal stages still change there.
- Review the model each quarter. Look at which deals closed, which stalled, and which caused friction. Adjust the line between expansion types, then update the Agent or Play so routing follows the new rule.
The step most teams skip is the handoff brief. Without it, a seller enters the account cold, and the customer gets the experience the leader above described. Context should travel with the deal, the same way it should at the sales-to-CS handoff after the first close.
How to Choose: If You… Then…
- If most expansion is seats or usage on one product, then let CS own it and give CS a growth measure so the motion gets real attention.
- If expansion often means a new product or a new business unit, then split by type: CS qualifies, sales runs the commercial cycle, and the handoff brief is required.
- If sales gets no credit for the base and keeps reaching in at renewal, then fix credit first. A sourced-by-CS, closed-by-sales rule with shared credit removes the incentive to go around the CSM.
- If sellers keep making promises delivery can’t keep, then require them to read the account brief and check open tickets before the first expansion call.
- If nobody can say who owns an open expansion deal, then create one shared Opportunities view filtered to expansion deals and review it weekly with both teams.
- If expansion signals sit unnoticed, then automate the first step with a scheduled Agent or Play and compare it with the tools in this roundup of expansion playbook tools.
Buyer Considerations
If you’re evaluating tooling to support an expansion model, test it on a handful of accounts that grew last year. Check whether the signals that preceded each expansion were visible in one place, and whether a seller could get the full account story without asking the CSM for it. Ask how alerts are routed to different owners, whether outreach waits for review, and how the tool treats your CRM as the system of record. Confirm that deal views can be shared across teams so ownership is visible to everyone. For a wider look at how teams find growth in the base, see these tools for identifying revenue growth opportunities.
Conclusion
Who owns expansion is less important than whether the rules are written down. Split ownership by expansion type, agree on credit before the year starts, route signals to the agreed owner, and make the handoff brief mandatory. Quivly keeps both teams on one customer record, shows CRM deals next to health and usage, and can surface expansion-ready accounts with outreach drafted for the owner’s review.
If you’d like to see expansion signals and handoffs on your own account data, book a demo with Quivly.




