Playbook · Expansion
Plan to grow expansion revenue in a SaaS business
Expansion revenue is usually the cheapest growth lever in SaaS, and the most neglected.
- 8 ranked moves
- 4-week sequence
- For SaaS with $1M+ ARR and an existing CS function
Plan to grow expansion revenue in a SaaS business: what should you actually do?
Expansion revenue (upsells, cross-sells, seat growth) is usually cheaper to grow than new logo acquisition but gets far less attention. Start by mapping which accounts are under-using paid features, build a usage-based upgrade trigger, and give customer success a specific expansion quota rather than treating expansion as a side effect of retention work.
Last updated 3 August 2026
| Play | Effort | Cost |
|---|---|---|
| Map usage against plan limits for every account | 2-3 days to build the first report | $0-$500/month for a BI tool if not already in use |
| Build an automatic in-app upgrade trigger at the usage limit | 3-5 days of engineering | $0-$300/month for Appcues if not already using an in-app messaging tool |
| Give customer success or account management a formal expansion quota | 1 week to design and roll out | $0 beyond any commission structure changes |
| Identify accounts with growing headcount or usage patterns externally | 1 day to set up alerts | $0-$100/month for Sales Navigator |
| Package a mid-tier add-on for the most commonly requested feature | 2-4 weeks depending on the feature | Engineering time for the add-on build |
| Run a proactive account review at renewal minus 90 days | Ongoing, built into the CS process | $0 |
| Test a multi-year or annual upgrade offer at renewal | 1 day to set up the offer | Cost of the discount itself |
| Report expansion revenue as its own line item to the leadership team | Half a day | $0 |
Most SaaS companies spend far more effort on new logo acquisition than on expansion revenue, even though expanding an existing account is usually 3-5x cheaper than acquiring a new one. The reason is structural: acquisition has a dedicated team with a number, while expansion often falls to whoever happens to notice an account is ready to upgrade, with no formal process or quota behind it.
This plan is for a SaaS company with at least $1M in ARR and an existing customer success or account management function, where net revenue retention is under about 110% and there's reason to believe accounts are under-using the product relative to what they'd get value from.
- — A SaaS company with at least $1M ARR and existing paying customers using the product for 3+ months
- — A customer success or account management team, even a small one
- — Product usage data that can be tied to individual accounts
- — Pricing that has a genuine upgrade path (more seats, higher tier, add-on modules)
If your net revenue retention is already above 120% and expansion is already a well-oiled process, this plan won't add much — focus instead on new logo acquisition or retention of at-risk accounts.
The moves
Ranked, highest return first.
Work down the list. Each one names the first step so there's nothing to plan.
- 01
Map usage against plan limits for every account
Accounts bumping up against a plan's usage limits — seats, API calls, storage — are your clearest expansion candidates, and most companies don't have this list built and reviewed regularly.
First step: Pull a report of every account's current usage as a percentage of their plan limit, sorted highest to lowest, and flag anyone above 80%.
- Tools
- Your product database, a BI tool like Metabase or Looker
- Effort
- 2-3 days to build the first report
- Cost
- $0-$500/month for a BI tool if not already in use
- 02
Build an automatic in-app upgrade trigger at the usage limit
Waiting for a customer success manager to manually notice usage creeping up is slow and inconsistent. An automatic in-app prompt when someone hits 80-90% of their limit catches every account, not just the ones a human happened to review.
First step: Add an in-app banner or modal that triggers at 80% of plan usage, offering a clear one-click path to upgrade.
- Tools
- Your product's front end, or a tool like Appcues
- Effort
- 3-5 days of engineering
- Cost
- $0-$300/month for Appcues if not already using an in-app messaging tool
- 03
Give customer success or account management a formal expansion quota
Without a specific number attached to expansion, it becomes secondary to churn prevention and support work, both of which feel more urgent day-to-day.
First step: Set a specific quarterly expansion revenue target per CSM or account manager, separate from their retention or churn targets.
- Tools
- Your CRM, a compensation plan update
- Effort
- 1 week to design and roll out
- Cost
- $0 beyond any commission structure changes
- 04
Identify accounts with growing headcount or usage patterns externally
A customer whose team is visibly growing (new job postings, LinkedIn headcount growth, funding news) is a strong signal they'll need more seats soon, even before usage data shows it internally.
First step: Set up alerts for headcount growth or funding news on your top 50 accounts using a tool like Crunchbase or LinkedIn Sales Navigator, and flag them for a proactive CSM check-in.
- Tools
- LinkedIn Sales Navigator, Crunchbase, Vitally or Gainsight for account health tracking
- Effort
- 1 day to set up alerts
- Cost
- $0-$100/month for Sales Navigator
- 05
Package a mid-tier add-on for the most commonly requested feature
If support tickets or sales conversations regularly reveal customers wanting a feature that's currently only in a higher tier or not offered at all, packaging it as an add-on captures revenue you're currently leaving on the table.
First step: Pull the last 6 months of feature requests and support tickets, find the single most common ask that isn't yet in the customer's current plan, and scope a paid add-on around it.
- Tools
- Your support tool (Zendesk, Intercom), product roadmap
- Effort
- 2-4 weeks depending on the feature
- Cost
- Engineering time for the add-on build
- 06
Run a proactive account review at renewal minus 90 days
Renewal conversations that only happen at renewal minus 30 days are usually about retention, not expansion. Starting 90 days out gives room to have a genuine growth conversation instead of a defensive one.
First step: Build a renewal calendar that flags accounts 90 days out, and have CSMs prepare a usage review and expansion recommendation ahead of that call rather than a generic check-in.
- Tools
- Your CRM's renewal tracking, a QBR template
- Effort
- Ongoing, built into the CS process
- Cost
- $0
- 07
Test a multi-year or annual upgrade offer at renewal
Moving a monthly account to annual, or an annual account to multi-year, at a modest discount locks in expansion revenue and improves cash flow, and many customers will take it if the discount is real.
First step: Offer a specific discount (e.g. 10% off for moving from monthly to annual) to the next 20 accounts up for renewal and track the acceptance rate.
- Tools
- Your billing system (Stripe, Chargebee)
- Effort
- 1 day to set up the offer
- Cost
- Cost of the discount itself
- 08
Report expansion revenue as its own line item to the leadership team
If expansion is buried inside overall revenue growth, it's easy for it to quietly stay flat while new logo growth gets all the credit and attention.
First step: Add expansion revenue (upsell, cross-sell, seat growth) as its own tracked line in the monthly or quarterly revenue report, separate from new logo revenue.
- Tools
- Your revenue reporting tool or spreadsheet
- Effort
- Half a day
- Cost
- $0
Sequence
What to do first, week by week.
Map usage and set targets
Build the usage-against-plan-limit report, flag high-usage accounts, and set a formal expansion quota for CS or account management.
Ship the automatic trigger
Build the in-app usage-limit prompt and set up external growth signal alerts (headcount, funding) for top accounts.
Package the add-on and test annual upgrades
Scope the most-requested feature as a paid add-on and launch the annual/multi-year upgrade offer to the next batch of renewals.
Build the renewal-minus-90 process
Roll out the 90-day-out account review process for CSMs and add expansion revenue as its own tracked line in reporting.
Avoid
Where this usually goes wrong.
Treating expansion as a side effect of retention work
Without a specific quota and process, expansion gets deprioritized behind day-to-day support and churn-prevention work, which always feels more urgent in the moment.
Only having renewal conversations at renewal minus 30 days
A conversation that close to the renewal date is almost always defensive, focused on keeping the account rather than growing it. Starting 90 days out allows a genuine expansion discussion.
Relying on CSMs to manually notice usage growth
Manual noticing is inconsistent and misses accounts that don't happen to come up in conversation. An automatic usage-based trigger catches every account against the same rule.
Questions
Common questions.
What counts as expansion revenue in SaaS?
Expansion revenue includes upsells to a higher plan tier, cross-sells of add-on modules, and seat or usage growth within an existing account — any revenue increase from a customer who was already paying, as opposed to a brand-new logo.
What net revenue retention rate signals a real expansion problem?
Net revenue retention under roughly 100-110% typically means expansion isn't offsetting churn and downgrades. Above 120% is often considered strong, though the right benchmark varies by segment and average contract value.
Should expansion be a customer success responsibility or a sales responsibility?
Either can work, but whichever team owns it needs a specific, separate quota for it — expansion handled as an informal side task of a retention-focused CSM role tends to get deprioritized.
How do we find accounts that are ready to expand?
Usage data against plan limits is the most reliable internal signal — accounts above roughly 80% of a usage cap are strong candidates. External signals like headcount or funding growth on the customer's side add a second layer of evidence.
Is a discount for moving to annual billing worth it?
Often yes — a modest discount (around 10%) to move a monthly account to annual, or annual to multi-year, improves cash flow and locks in the revenue, and take rates are usually meaningful if the discount is genuine.
More playbooks
Other plans worth reading.
Marketing plan for expanding into a new country
ReadPlaybook · RebrandPlan for launching a company rebrand
ReadPlaybook · Solo founderGrowth plan for a solo, bootstrapped founder
ReadPlaybook · B2B SaaSGrowth plan for a pre-revenue B2B SaaS
ReadPlaybook · EcommerceGrowth plan for an ecommerce store's first 100 orders
ReadPlaybook · LocalGrowth plan for a local service business
ReadElsewhere on gtm.help
Keep exploring.
Tool guides
What to use, what it costs, when it earns its keep.
BrowseTool comparisons
Head-to-head picks for the calls people get stuck on.
BrowseMarketing checklists
Task lists by business type and competitive situation.
BrowseStraight answers
The growth questions founders ask, answered with numbers.
BrowseGet started
Get this ranked for your business.
Paste your URL and you'll have a plan built from your site and competitors in about a minute.