A Series B founder I worked with last quarter pulled up a slide that said "land and expand" three times. Then he showed me the data. 92% of new ARR came from new logos. Expansion was 8%. Net revenue retention sat at 96%.
That is not land and expand. That is land, ship the contract, and forget the customer until renewal panic three months before the date.
Most B2B SaaS teams talk about land and expand the way undergrads talk about networking. Everyone knows the words. Almost nobody runs the motion. The result is a growth model that needs to refill the bucket from scratch every year, because the bucket has holes and nobody is pouring more water in from the customers already inside it.
I've spent the last ten years building RevOps and GTM systems for B2B SaaS teams, currently as Founding GTM Engineer at Peec AI. Every land and expand audit I run finds the same five gaps. This post is the playbook I wish someone had handed that Series B founder before he signed his 2026 plan.
Net revenue retention at top-quartile private B2B SaaS in 2026. Median sits at 104%, and SMB-heavy books often slip under 100%. The gap is almost entirely an expansion problem, not a churn problem.
What land and expand actually means in 2026
Land and expand is a GTM motion where the first contract is intentionally smaller than the account's potential. You win on one team, one product, or one use case. Then you grow inside the account through three levers: more seats, more products, and more usage.
The "intentionally smaller" part is what most teams get wrong. They sell whatever the prospect will buy, then call expansion the responsibility of customer success, who get a budget of zero and a comp plan that says nothing about it.
A real land and expand motion needs four things working together:
- Pricing that lets a small first contract grow without a re-negotiation.
- A first contract scoped to a single team, product, or use case so adoption is fast.
- An expansion owner with a quota and a comp plan, not just a CS manager with a feeling.
- An expansion signal system that tells the owner when an account is ready to grow.
Skip any one and the motion breaks. I've seen teams nail pricing and signal and still get 102% NRR because no human owned expansion. I've seen teams hire account managers and still flatline because pricing made every expansion a six-week procurement fight.
The benchmarks that actually matter in 2026
Before you build the motion, anchor on the numbers. NRR is the headline. But the second number underneath it tells you whether the motion works.
A few things worth calling out from the 2026 data. Enterprise (ACV above $100K) hits a median of 118% NRR. Mid-market sits at 108%. SMB drops to 97%, meaning the median SMB SaaS shrinks every year before new logos are counted. Above $50M ARR, expansion is more than half of all new revenue at the median.
If you are below $20M ARR and expansion is under 20% of new ARR, you are running a hunter motion that calls itself land and expand. The fix is not a CS hire. The fix is upstream.
Why most land and expand motions stall
Five reasons, in order of how often I see them.
1. The first contract is too big
Sales reps are paid on first-year ACV. So they sell as much as they can on day one. The prospect signs a 5-team, 200-seat enterprise deal. Six months later, 40 seats are activated and the buyer is dodging renewal calls because they cannot defend the spend.
The "land" in land and expand has to land. That means a contract small enough that the buyer can prove value in 90 days without a politicking. If the first contract requires a board meeting, your land motion is broken.
2. Pricing is built for procurement, not for growth
Annual contracts with per-seat pricing, fixed at signing, paid up front. That is a procurement-friendly model and a growth-hostile one. Every seat add is a contract change request. Every usage spike is a phone call.
The data is clear: usage-based pricing delivers 34% faster expansion cycles and 18 to 23% higher NRR than flat-rate. 43% of SaaS companies now run usage-based pricing as of 2026, up 8 points from 2025. 61% run hybrid models with a seat base plus a consumption layer. If your contract has no expansion path that does not require legal review, expect a flat NRR.
3. CS owns expansion but has no quota
Pick one. Either CS owns expansion with a quota, a target, and a comp plan that pays on it. Or CS owns adoption and renewals, and a separate account manager or expansion AE owns growth.
The hybrid "CS owns relationship and feeds expansion to sales" model works at companies above $100M ARR with mature ops. Below that, it produces a queue of warm leads that nobody picks up, because CS does not get paid to qualify them and AEs do not get paid to chase them.
4. No signal system
Most expansion happens because a customer asks. That is not a motion. That is order taking. A real expansion system tracks product usage, account changes, and adjacent team adoption, and routes a signal to the owner when conditions are met. No system, no proactive expansion. Reactive expansion caps you at roughly 105% NRR forever.
5. The product does not have a second act
Sometimes land and expand fails because there is nothing to expand into. Single product, single user persona, no usage variable. In that case, no comp plan or signal system fixes the problem. You need a second product, a second persona, or a usage meter inside the existing one. Pricing and packaging is the real lever, not sales motion.
If your CS team owns expansion with no quota, your NRR is capped at 105%. Pick a model and pay it.
Hybrid ownership without comp alignment is the single biggest cause of stalled land and expand motions I see at Series A and B B2B SaaS.
The land and expand motion that works
Here is the four-stage motion I build with B2B SaaS teams when they want expansion to actually contribute 40% of new ARR by year-end.
Stage one: land small
The first contract should be the smallest commercial unit that delivers measurable value in 90 days. For a Series A SaaS product I worked with last year, that meant a single team license, no platform fee, three-month minimum, with a clear adoption gate to renew at 12 months.
We took the first contract size down from a $48K average to $18K. Win rate doubled. The 12-month renewed value across the same accounts averaged $34K. Year two value averaged $61K. Land smaller, grow further.
The sales comp plan has to reflect this. If reps get paid on first-year ACV only, they will not sell small. Build a 12 to 24 month vesting structure where expansion revenue inside year one accrues to the original closer, then transitions to the expansion owner. That keeps the rep honest about right-sizing the first deal.
Stage two: activate
CS has 60 to 90 days to get the customer to a defined activation milestone. Not "they logged in." A real adoption metric. For a CRM data tool: enrichment runs scheduled on at least 5,000 records. For an analytics product: three custom dashboards in active use. For an AI product: 70% of seats used the product in the last 14 days.
If activation fails, the expansion motion fails. There is no point in signaling expansion to an owner if the underlying account is not adopted. I see teams skip this gate constantly. They push expansion plays to accounts that are not even using the base product, and the owner burns the relationship.
Stage three: signal
This is where most teams fall apart, because it is the part that needs RevOps work, not just sales work.
The signals you want to track:
- Usage threshold crossed. Account hit 80% of seat limit, 90% of API quota, or 70% of the included usage tier.
- New team activity. A new team or department started using the product. Even one user from a new domain or department code.
- Champion role change. Your buyer got promoted or moved to a parent company. Both are expansion triggers.
- Adjacent product event. A relevant integration was set up. A feature was used that maps to your second product.
- Account growth. Headcount grew 20%, a new round was raised, a competitor was named in a recent earnings call.
You build this in HubSpot (or whatever CRM is the source of truth) with custom properties on the company object, fed from your product database via reverse ETL and from enrichment sources like Clay. If you want the depth on reverse ETL, see the reverse ETL playbook. For the enrichment side, the Clay waterfall guide covers the data layer.
The signal then routes to the expansion owner via HubSpot workflows or, for more complex orchestration, an n8n flow. The output is a task with the account, the signal, the suggested play, and a 5-day SLA. Not a Slack notification anyone can ignore. A task with a name on it.
Stage four: expand
The expansion play depends on the signal. Five plays cover 90% of motions:
- Seat expansion triggered by seat limit. Owner reaches out, references usage data, proposes the next tier. Close cycle: 2 to 3 weeks.
- Usage tier upgrade triggered by API or consumption threshold. Often automated with an in-product prompt, then human follow-up for negotiation.
- Team expansion triggered by adjacent team activity. Owner reaches out to the new team's leader, references the existing internal champion.
- Product expansion triggered by feature usage signaling fit for a second product. Owner schedules a discovery on the second product use case.
- Renewal uplift triggered by approaching renewal with healthy adoption. Owner pre-empts the renewal with a multi-year deal at a higher ARR.
Each play has a defined trigger, a script, and a target close cycle. Build them in HubSpot sequences or your sales engagement tool, but tie the play directly to the signal that fired it. Generic outreach to expansion accounts is the same as generic outbound: low reply, low close, burned relationships.
Comp plan that actually drives expansion
I will keep this section short because it is the most contentious part of the motion. The teams that get expansion right pay for it directly.
The single biggest shift I have seen is paying expansion AEs (or account managers, name is not the point) a full quota on net new expansion ARR. Same OTE as a new business AE, sometimes higher base because they own the customer relationship. The math works because expansion sales cycles are 40 to 60% shorter and win rates are roughly twice as high. So they hit quota with less ARR, but the ARR is cheaper to acquire.
For a deeper look at how to structure these comp plans without breaking the budget, the sales compensation playbook walks through the math.
The RevOps backbone
Land and expand is a RevOps problem dressed up as a sales motion. The data plumbing matters more than the script.
Here is the minimum stack:
- CRM with custom objects for account-level expansion tracking. HubSpot or Salesforce both work. If you are evaluating, the HubSpot vs Salesforce 2026 comparison covers the trade-offs.
- Product database synced into CRM via reverse ETL (Hightouch, Census, or a custom n8n flow). Usage data on the account record updates in real time.
- Enrichment layer for account context like headcount, funding, and tech changes. Clay is the standard.
- Signal routing in workflows. HubSpot workflows for simple cases, n8n for multi-step orchestration with external triggers.
- Reporting on expansion as its own pipeline. Separate from new business. Different stages, different velocity, different conversion model.
If you want the broader picture of how to assemble this without buying every tool on the market, see the minimal RevOps tech stack and our CRM and RevOps work.
Case: how a Series B team moved NRR from 96% to 119% in 14 months
Names changed, but the playbook is real. A Series B vertical SaaS company, $14M ARR, growing 60% YoY. NRR at 96%, all new ARR from new logos, an exhausted sales team chasing fresh hunting territory every quarter.
We did four things over 14 months:
- Repriced the first contract. Dropped the per-seat starting price by 22% and added a usage-based tier on top of the seat base. Average first deal dropped from $52K to $31K. Win rate moved from 18% to 27%.
- Hired one expansion AE. Quota on net new expansion ARR. OTE matched new business AEs.
- Built the signal system. Product usage data piped from Postgres into HubSpot custom properties via Hightouch. Six signals defined, routed as tasks to the expansion AE with a 5-day SLA.
- Aligned comp. New business AEs vested on year-two expansion at 30% of standard rate. CS bonus tied to a defined activation milestone, not a CSAT score.
Outcome at month 14: NRR 119%. Expansion ARR 38% of new ARR. The expansion AE hit 142% of quota. New business AE happiness went up, because the existing book was finally generating real expansion through proper hand-offs.
The total cost of the motion change was one hire and roughly 6 weeks of RevOps build time. The ARR impact in year one was about $2.1M of expansion revenue that previously did not exist.
Running a flat NRR despite a growing customer base?
Book a free 30-minute audit and we will map the three changes most likely to move your expansion number this quarter.
Book an audit →FAQ
What is a healthy NRR for B2B SaaS in 2026?
Median private SaaS NRR is around 104%. Top quartile is 118% or higher. Enterprise-heavy books should target 115%+, mid-market 108%, and SMB-heavy books 100% or better. Below 100% means your existing customer base is shrinking before new logos are counted.
Should the same AE who closed the deal own expansion?
It depends on company size. Below $10M ARR, yes, the same AE often owns expansion because there is not enough volume to justify a dedicated role. Between $10M and $50M ARR, separate the roles and pay both. Above $50M ARR, build a full account management function with named accounts and territory rules.
How small should the first contract be?
Small enough that the buyer can prove value in 90 days without a board meeting. As a rule, the first deal should be below the buyer's personal signing authority where possible. For most mid-market buyers that is $25K to $50K. For SMB, $5K to $15K. Land small, grow inside.
Is usage-based pricing required for land and expand?
No, but it makes the motion easier. Usage-based or hybrid models grow contracts without re-negotiation, which is the biggest friction point in seat-only expansion. Pure seat-based pricing can work if you have a clear team-to-team expansion story and a fast contract amendment process.
How do I build the signal system if I am not technical?
Start in the CRM. Define five signals on the company object as custom properties. Feed them manually from a weekly product usage export. Once the plays prove out, invest in reverse ETL to automate the data flow. Skip the big platform purchase until you have proven the signals actually drive closed expansion ARR. We cover the build pattern in our AI automation work.
What to do this week
Pull two numbers: NRR for the last four quarters, and the percentage of new ARR coming from expansion. If NRR is below 105% or expansion is below 25% of new ARR, the motion is broken. Pick one of the four stages above where the gap is biggest and fix that first. Do not try to rebuild all four at once. The teams that succeed pick the highest-impact stage and run it for 90 days before touching anything else.
If you want a second set of eyes on where your motion is leaking, reach out. We will walk through your numbers and tell you the one change that would move expansion ARR most in the next quarter.