Expansion Revenue in PLG: A 10-Step System to Grow Net Revenue Retention
How product-led companies build expansion revenue that lifts net revenue retention: the five triggers that predict upgrades, proactive vs. reactive expansion, how to route accounts by size, the NRR maths, and a ten-step system with metrics and mistakes to avoid.
By Alexandre Contador, Fractional CGO & GTM Advisor

New-logo growth gets the attention; expansion gets the margin. Every customer you already have is the cheapest source of next quarter's revenue — if your product and your go-to-market notice the right moment and make the next step easy.
In product-led companies, expansion should happen earlier, faster and with less human involvement than in sales-led ones, because usage data tells you a customer is ready before they've decided. This guide lays out the signals, the motion and a ten-step system, plus how to measure it with net revenue retention (NRR).
Why expansion works differently in PLG
In sales-led companies, expansion is mostly a customer-success and account-executive function: renewals, upsells and cross-sells are commercial conversations led by people. In PLG, the product itself generates the evidence.
| Sales-led expansion | PLG expansion | |
|---|---|---|
| Signal source | Account reviews, relationship, renewal date | Product usage and team behaviour |
| Timing | At renewal or quarterly review | When the signal appears (any day) |
| Channel | Human conversation | In-product prompts, email, then human where warranted |
| Cost | High per account | Low per account, scaled by automation |
| Risk | Upsell feels disconnected from value | Prompt feels pushy if poorly timed |
The core difference is reactive vs. proactive.
- Reactive: the customer hits a limit, gets frustrated and eventually upgrades — or churns.
- Proactive: the system detects the signal two weeks before the limit and starts a contextual conversation while the customer is still enjoying the value.

Know your scoreboard: NRR and GRR
Net revenue retention (NRR) = (starting recurring revenue + expansion − contraction − churn) ÷ starting recurring revenue, measured on a fixed cohort. Gross revenue retention (GRR) excludes expansion, so it can't exceed 100% and shows how much of the base you keep.
You need both: NRR tells you whether growth from the base is working; GRR tells you whether the base is leaking.
SaaS Capital's benchmark research for private B2B SaaS finds that higher net retention correlates with higher ACVs, that companies with NRR of at least 110% grew faster than the population median and those below 100% grew slower, and that for the $25K–$50K ACV band:
Source: SaaS Capital
Two cautions. Benchmarks differ by contract size, billing model and whether the base is self-serve or sales-led, so compare against a similar cohort. And the very high NRR headlines come from large public companies with enterprise contracts; a self-serve SMB base typically sits lower.
The maths of small improvements
An illustrative example (our own arithmetic, not a benchmark): a PLG company has 500 accounts at an average €3,600 ARR, or €1.8M ARR, and a starting NRR of 95%. Better expansion triggers add €1,000 of ARR to eight accounts. Whether that matters depends on whether it happens once or every month:
| Scenario | Annual expansion | NRR effect |
|---|---|---|
| Baseline | — | 95.0% |
| 8 accounts expand by €1,000 ARR each, once | €8,000 | +0.4 pts → 95.4% |
| 8 accounts expand by €1,000 ARR every month for 12 months (96 expansions) | €96,000 | +5.3 pts → 100.3% |
The takeaway: a modest, repeatable expansion motion — a handful of accounts a month — is enough to move NRR across the 100% line. Use the SaaS growth rate calculator to model your own numbers and the CAC payback calculator to compare expansion revenue against the cost of acquiring new logos.
The five expansion triggers
Trigger 1: Usage-limit approach (not hit)
Most systems alert when a customer hits a limit. Better: alert at 80%. At 80% they're experiencing value, and the message is "you're getting a lot out of this — here's a smooth path to more." At 100% the conversation is damage control.
Trigger 2: Team growth
A customer that adds two or more users in 30 days is spreading the product internally. That's organic growth; follow with outreach about team plans and the economics of expanding.
Trigger 3: Power-feature adoption
Compare feature adoption between your highest- and lowest-ACV cohorts. Features far more common in high-ACV accounts are your expansion indicators. When a user finds and uses one independently, they've self-identified as expansion-ready.
Trigger 4: Tenure milestone
Customers active for six or more months have shown retention and are the highest-probability expansion targets — and often underserved by motions focused on new activations. A milestone touchpoint that celebrates progress and shows the next level can be one of the most effective moments.
Trigger 5: Collaboration threshold
When multiple users edit shared work, review each other's output or build on shared resources, the product has become organisational infrastructure, with high switching costs. That's the moment to move from small-team pricing to a company-level agreement.
Choose the motion by account size
| Segment | Motion | How it works |
|---|---|---|
| High-ACV accounts (product-led sales) | Consultative | A product signal triggers a CS or sales conversation; the rep has usage, limit and team context: "based on how your team uses it, here's the next level" |
| Mid-market (hybrid) | Automated first, human second | A signal triggers a clear expansion email; if no action within about 72 hours, a human follows up |
| Self-serve / SMB | Fully automated | In-product prompts at trigger points, automated sequences, frictionless upgrade flows; no human unless account size warrants |
The 10-step expansion system
1. Set the baseline. Calculate NRR and GRR for the last four quarters, split by segment and plan. Find where expansion and contraction concentrate.
2. Segment accounts. Define tiers (self-serve, mid-market, high-ACV) by ACV, seats or ICP fit, and assign a motion to each.
3. Identify your expansion indicators. Compare usage between high- and low-ACV cohorts; list the behaviours that predict upgrades. Ask Claude Code to query your product database and rank them by lift.
4. Instrument the triggers. Make each of the five triggers an event or computed property (percentage of limit used, new users in 30 days, power-feature use, months active, collaborative actions) in your analytics and CRM.
5. Set thresholds. Start with 80% of a plan limit, two or more new users in 30 days, and six months' tenure. Tune against real upgrades.
6. Write the plays. For each trigger: the signal, the offer (what you're asking them to upgrade to or add), the channel and a message under about 80 words that references what they did. Avoid generic "just checking in" notes.
7. Build the automation. A weekly "expansion radar" lists accounts with usage above 80% of plan, three or more new users in 30 days, or a new department active, and drafts a short note from the account owner for review.
8. Equip champions. Send a monthly usage report showing the value delivered (hours saved, tasks completed). It gives champions evidence to defend renewal and expansion internally.
9. Protect the base. Add churn-risk alerts triggered by 14 days without logins, a drop in a key action, support complaints or billing failures; route to success or send an automatic rescue email.
10. Review and learn monthly. Track conversion by trigger, revenue per play, false-positive rate and customer sentiment; retire plays that annoy customers and double down on those that convert.
For the automation side, see agentic GTM workflows and the workflows inside the free PLG Workflows and Automations pack.
A QBR that surfaces expansion naturally
For accounts above your high-touch threshold, a quarterly business review (QBR) is a natural place to talk expansion without it feeling like a sales call. Structure it as:
- Value delivered: usage, outcomes and goals achieved since the last review.
- Where they're headed: upcoming initiatives and the teams or use cases that might benefit.
- What's in the way: limits, missing capabilities, seats or integrations.
- Next level: only then, how an upgrade or add-on supports their goals.
Three questions that open the conversation: "Which team would benefit from this next?", "What would you do if you had no limits on X?" and "What would make this a no-brainer to expand?"
Metrics to track
| Metric | What it shows |
|---|---|
| NRR and GRR (by cohort and segment) | Overall retention health |
| Expansion MRR per month | Revenue from existing customers |
| Trigger-to-upgrade conversion | Which signals work |
| Time from signal to action | Responsiveness |
| Seat and usage growth per account | Organic spread |
| Contraction and downgrade rate | Hidden leakage |
| At-risk accounts flagged and saved | Effectiveness of alerts |
Subscription-analytics tools such as ChartMogul or Baremetrics, connected to Stripe, calculate MRR movements, churn and cohort retention automatically; product analytics such as PostHog supplies the usage signals behind each trigger.
Common mistakes
- Waiting until the limit is hit. Alert at 80%.
- Treating all accounts the same. A fully automated flow is wrong for a high-ACV customer, and a human is wasted on a $20/month plan.
- Upselling before value. Trigger on outcomes the customer has already experienced.
- Ignoring contraction. A downgrade is a signal, not noise.
- No frequency cap. A customer should never get three upgrade prompts in a day.
- Measuring revenue only. Track sentiment and complaints too.
- Skipping the activation foundation. Expansion depends on early value; start with activation and consider the try-it path for the top of the funnel.
Where to go next
- Download the free PLG Workflows and Automations and the PLG OS.
- Read the foundations: Ultimate guide to PLG for B2B SaaS.
- Tie it to the tech stack that supports it.
- Browse the PLG topic hub.
Frequently asked questions
NRR measures the revenue you keep and grow from an existing cohort of customers over a period, including expansion, contraction and churn. A figure above 100% means the cohort grew even without new customers; below 100% means losses outweighed expansion.
It varies by contract size and segment. SaaS Capital's retention benchmarks for private B2B companies show higher NRR correlates with higher ACV; for companies with $25K–$50K ACV, the median is 102% with a top quartile of 111% and a bottom quartile of 97%. Compare yourself to a cohort like yours, not to public-company headlines.
Reactive expansion happens when a customer hits a limit, gets frustrated and then upgrades or churns. Proactive expansion detects the signal earlier — for example at 80% of a plan limit — and starts a helpful conversation while the customer is still experiencing value.
Both, by account size. Fully automated flows suit self-serve and SMB accounts; an automated email followed by human follow-up suits mid-market; high-ACV accounts warrant a consultative conversation with full usage context.
Trigger on value, not on calendar dates; reference what they actually did; make the next step optional and easy; cap how often any account can be contacted; and give customers an obvious way to dismiss prompts.
Free resources & related work
Want a second opinion on your GTM?
30 minutes, no pitch — just a direct conversation.
Next in Product-Led Growth
The Try-It Path: How to Let Buyers Try Before They Talk (PLG for Sales-Led SaaS)
Most B2B websites have one door: "Request a demo". This guide shows how to add a try-it path — Find, Try, Prove, Buy — that lets buyers experience your product on their own, with a 20-check audit, five fixes to start with and ways to adapt it for sales-led, complex and AI-agent-assisted buying.
Keep reading
All Product-Led Growth guides →
The Try-It Path: How to Let Buyers Try Before They Talk (PLG for Sales-Led SaaS)
Most B2B websites have one door: "Request a demo". This guide shows how to add a try-it path — Find, Try, Prove, Buy — that lets buyers experience your product on their own, with a 20-check audit, five fixes to start with and ways to adapt it for sales-led, complex and AI-agent-assisted buying.

PLG Activation Guide: 16 Nudges That Move Users to Value, and How to Define a PQL
How to define activation, build the 16 in-product nudges that move new users to their first win, score product-qualified leads (PQLs) with a simple point model, and automate alerts and handoffs — with rollout order, metrics and common mistakes.
The Ultimate Guide to Product-Led Growth for B2B SaaS
A complete guide to product-led growth for B2B SaaS — what it actually requires, how it's different from sales-led motions, and how to diagnose where your activation funnel is broken.