Expansion revenue playbook: how to measure and build expansion

Key takeaways

• Company-defined retention metrics differ: Snowflake reported 126% net revenue retention for Q2 FY2027, Twilio reported 116% dollar-based net expansion for Q2 2026, and Datadog described trailing-twelve-month NRR in the low 120s in August 2026
• Three expansion motions drive this: seat expansion (collaborative products), usage-based growth (consumption pricing), and feature upsell or cross-sell (tiered plans); best companies layer all three
• Expansion should be signal-driven rather than calendar-driven; strong buying signals include nearing plan limits, new use case adoption, admin activity spikes, API usage growth, and repeated premium feature gate hits
• Treat expansion as a product motion, not a sales motion, and score product usage signals to trigger the right outreach at the right time

Expansion can use an established relationship, but its economics depend on support, sales effort, discounts and product usage. Compare contribution margin and payback for new-logo and expansion motions using the same accounting.

Public companies illustrate why definitions and dates matter. Snowflake reported 126% net revenue retention for the quarter ended 31 July 2026 (Q2 FY2027 earnings release). Twilio reported 116% dollar-based net expansion for Q2 2026 (earnings release). Datadog described trailing-twelve-month NRR in the low 120s on 6 August 2026 (Q2 2026 transcript). These company-defined metrics have different denominators and are not a universal benchmark. Datadog also attributed 30% of year-over-year revenue growth to new customers; that is not the same as new ARR share.

This playbook breaks down how expansion revenue works, the three core motions that drive it, and how to build a repeatable system for growing revenue from your installed base.

What expansion revenue is and why it matters

Expansion revenue is any incremental revenue generated from existing customers after their initial purchase. It includes upgrades, add-ons, seat increases, and usage growth beyond the original contract value.

The reason expansion revenue is so important comes down to unit economics. Expanding an existing customer requires:

• No new acquisition cost -- the customer already trusts your product
• Shorter sales cycles -- they understand your value proposition
• Comparable conversion -- define eligible expansion and new-logo opportunities, then compare conversion and sales effort over the same window
• Lower churn risk -- deeper product adoption creates switching costs

When expansion revenue outpaces gross churn, your net revenue retention (NRR) exceeds 100%. That means your existing customer base grows on its own, compounding revenue over time without incremental acquisition spend.

Three core expansion motions

Every expansion revenue strategy relies on one or more of these three motions. The best companies layer all three together.

1. Seat expansion

Seat expansion is the most straightforward motion. A team signs up with 10 seats, then grows to 50 as adoption spreads across departments.

When it works best:

• Collaborative tools where value increases with more users (Slack, Figma, Notion)
• Products with network effects inside an organization
• Platforms where individual usage is visible to non-users, creating organic demand

How to drive it:

• Track team size vs. active seat count -- if a 500-person company has 20 seats, there is room to grow
• Build features that require cross-team collaboration (shared workspaces, @mentions, approval flows)
• Create "viewer" or "guest" tiers that expose non-paying users to the product
• Trigger outreach when invite rates spike or when users hit seat limits

2. Usage-based growth

Usage growth happens when customers consume more of what they already pay for. This is the engine behind companies with consumption-based pricing like Snowflake, Twilio, and AWS.

When it works best:

• Products where usage scales with the customer's business growth
• APIs, infrastructure, and data products
• Any product where value delivered correlates directly with volume

How to drive it:

• Build usage dashboards that show customers their consumption trends
• Set up alerts that notify customers (and your team) when usage approaches tier thresholds
• Invest in features that open new use cases -- each new use case multiplies consumption
• Make it easy for customers to increase limits without a sales conversation

3. Feature upsell and cross-sell

Feature upsell involves moving customers to higher-tier plans or selling them additional products. This is the primary motion for companies with tiered pricing.

When it works best:

• Products with clear capability differentiation between tiers
• Multi-product platforms (HubSpot adding Marketing Hub to a CRM customer)
• Products where advanced features serve specific roles (admin, analytics, security)

How to drive it:

• Gate high-value features behind premium tiers and show usage attempts against those gates
• Use product usage signals to identify which premium features a customer would benefit from
• Bundle features that solve adjacent problems rather than arbitrary feature groupings
• Offer time-limited trials of premium features so customers experience the value before buying

How product usage signals predict expansion readiness

Treating expansion as a sales motion instead of a product motion is the biggest mistake in expansion revenue. The best expansion programs are signal-driven, not calendar-driven.

Here are the product signals that indicate a customer is ready for expansion:

Strong buying signals:

• Usage approaching limits -- customers hitting 80%+ of their plan limits
• New use case adoption -- customer starts using features in a previously unused product area
• Admin activity spikes -- someone is configuring new integrations, adding team members, or adjusting permissions
• API usage growth -- programmatic usage often precedes significant expansion
• Feature gate hits -- repeated attempts to access premium features

Moderate signals:

• Increased login frequency across the team
• Dashboard or reporting usage up -- indicates the product is becoming a source of truth
• Support tickets about advanced features -- they are thinking about capabilities they do not have yet

Weak signals (use with caution):

• Contract renewal approaching (this is calendar-driven, not signal-driven)
• Company funding announcement (external, not product data)
• Headcount growth on LinkedIn (lagging indicator)

The goal is to build a scoring model that weights these signals and triggers the right expansion motion at the right time. Tools like Skene can help surface these product signals automatically by analyzing how users move through your product.

Building expansion triggers from product data

A trigger is a specific event or threshold that initiates an expansion workflow. Here is how to build them:

Step 1: Define your expansion events. Map the product actions that historically precede expansion. Look at your last 20-30 expansion deals and identify what customers did in the product in the 30 days before upgrading.

Step 2: Set thresholds. Not every signal is equal. Determine the frequency, recency, and combination of signals that indicate true readiness. For example: "3+ feature gate hits in 7 days AND usage above 70% of plan limit."

Step 3: Route to the right action. Not every expansion opportunity needs a sales call:

• Self-serve upgrade path -- for seat additions and usage increases under a certain dollar amount
• Automated email -- for mid-tier upsell opportunities with a clear value message
• Sales outreach -- for enterprise cross-sell or large contract expansions
• CSM conversation -- for strategic accounts where expansion is part of a broader success plan

Step 4: Measure conversion by trigger type. Track which triggers lead to actual expansion and which are noise. Prune low-converting triggers and double down on what works.

Pricing as an expansion lever

Your pricing model is the most powerful expansion lever, and most companies underutilize it.

Usage-based pricing can create expansion when a billable unit grows with customer value. More usage can also reflect inefficiency, seasonality or abuse, so validate the relationship and customer economics instead of assuming it.

Tier thresholds should be set so that growing teams naturally hit the next tier. If your pricing tiers are at 10, 50, and 200 seats, and most teams grow from 15 to 40 users, you have created a dead zone where expansion does not trigger an upgrade. Set tiers where natural growth patterns create upgrade conversations.

Feature-gated tiers should gate features that become important as companies mature. Security features, SSO, audit logs, and advanced analytics are natural enterprise-tier gates because growing companies eventually require them.

The land-and-expand model works best when the initial price point is low enough to avoid procurement friction, and the expansion path is smooth enough that growing spend feels like a natural extension of adoption, not a new buying decision.

Compare NRR consistently

No universal stage band makes unlike definitions comparable. Start with a consistent cohort and formula:

Key observations:

• Segment by customer size and contract model because mix can move NRR independently of product changes
• NRR above 100% means expansion exceeded contraction and churn in the measured starting cohort
• Use dated peer disclosures only when definitions and denominators are comparable
• NRR is one outcome measure, not proof of profitability or causal product quality

If NRR is below 100%, decompose gross retention, contraction and expansion before choosing the next investment. Expansion work and churn reduction can have different causes and economics.

Common mistakes in expansion revenue programs

Pushing expansion before activation

If a customer has not fully activated on their current plan, upselling them creates resentment, not revenue. Before any expansion conversation, verify the customer has reached their core activation milestones and is seeing value from what they already pay for.

Misaligned pricing tiers

When the jump between tiers is too large, customers stay on lower plans longer than they should. When the jump is too small, expansion revenue per account is trivial. Analyze your actual upgrade patterns and price accordingly.

Treating expansion as a quarterly push

The worst expansion programs are quota-driven campaigns where reps blast upgrade offers at the end of the quarter. Expansion should be a continuous, signal-driven process. When a customer is ready, the offer should be there. When they are not, leave them alone.

Ignoring the self-serve path

Many expansion opportunities -- especially seat additions and usage increases -- do not need a human in the loop. Requiring a sales call to upgrade creates friction and kills small, frequent expansions. Build self-serve upgrade flows for the straightforward cases. Save sales time for the strategic upsells.

Not closing the feedback loop

When a customer declines an expansion offer, capture why. The reasons (not enough budget, not the right time, feature does not fit our use case) are critical inputs for product, pricing, and go-to-market strategy.

Getting started

1. Audit your current NRR. Break it down by customer segment, cohort, and plan tier.
2. Map your expansion events. Identify the product signals that preceded each historical upgrade.
3. Build 3-5 triggers. Start with the highest-signal events and create automated workflows.
4. Instrument self-serve upgrades. Make it possible for customers to add seats and upgrade plans without talking to anyone.
5. Create an expansion dashboard. Track expansion MRR, trigger conversion rates, and NRR trends.
6. Review monthly. Expansion systems degrade if not maintained.

Expansion revenue isn't a once-a-quarter tactic. It's a growth engine, and it compounds. Start with one motion, instrument it properly, and expand from there.