Skip to content
Revenue Operations

Land and Expand

2026-06-12 9 min read

Land and expand is a go-to-market strategy that closes a small initial deal with a customer (the land), then grows the account through cross-sells, additional seats, or new product modules (the expand). It is the dominant model for product-led and bottom-up B2B SaaS — Slack, Snowflake, Figma, and Datadog all built billion-dollar businesses on land-and-expand. The strategy depends on strong NRR (typically 120%+) to justify the lower initial deal size.

TL;DR

Land and expand is a B2B SaaS go-to-market strategy that closes a small initial deal, then grows the account through seat expansion, cross-sell, and module upsell. Dominant model for product-led companies — Slack, Snowflake, Figma, and Datadog built billion-dollar businesses on it. Depends on 120%+ NRR to justify the lower initial ACV.

What is land and expand?

Land and expand is a sales motion where the initial sale (the land) is intentionally small — a single team, a single workspace, a starter tier — and the customer's revenue contribution grows over time as usage, seat count, and module adoption expand (the expand). The model trades higher first-deal friction for lower LTV in exchange for higher win rate, faster sales cycles, and dramatically higher net revenue retention.

It is the canonical strategy for product-led growth companies and for any B2B SaaS where the product can demonstrate value to a single team before being adopted org-wide. Slack landed in engineering, expanded to every department. Snowflake landed as a single warehouse, expanded to every analytical workload. Figma landed with designers, expanded to product, engineering, and marketing.

The contrast is enterprise top-down selling — a $250K+ annual contract negotiated with a CIO or CFO, sold against a 9-month evaluation cycle, with the buying decision concentrated in a single executive. Land-and-expand inverts that: the buyer is the practitioner, the first contract is $5–50K, and the expansion is driven by demonstrated value, not procurement.

Why land and expand matters

For a company with strong product-market fit, land-and-expand produces dramatically better unit economics than top-down enterprise selling. Initial CAC is lower because the deal is smaller and the cycle is shorter; CAC payback compresses because the customer can self-onboard; NRR compounds because every expansion is high-margin revenue against a sunk acquisition cost.

Snowflake's S-1 disclosed 158% NRR — meaning the average customer's spend grew 58% per year inside the contract. Datadog disclosed 130%+. Figma, before its acquisition, was running 150%+. Those numbers are what makes land-and-expand work: a $10K first deal that becomes $40K in year two and $120K in year four is materially more valuable than a $50K first deal that stays flat for three years.

For operators, the strategic implication is that ICP fit at the team level matters more than first-deal size. A small deal with the right team in the right account compounds; a large deal with the wrong sponsor stagnates. RevOps teams should track expansion velocity (months from land to first expansion) and expansion depth (final-year ARR / first-year ARR) as primary metrics, not first-year ACV.

How land and expand works in practice

  • Land — small, fast, low-friction. Self-serve sign-up or a $5–25K team deal. Buyer is the practitioner, not procurement. Sales cycle 14–45 days. Goal: get to first value within the first 14 days.
  • Adopt — measured by usage, not by paid seats. The first 60–90 days are about activation: are people logging in daily, completing workflows, integrating with their tools? This is where customer health score starts mattering.
  • Expand internally — seat count and adjacent teams. Months 3–9. The original team adds seats; an adjacent team (engineering → design, sales → CS, marketing → analytics) starts a parallel workspace.
  • Expand by module — new product surfaces. Months 9–18. The customer adopts additional products in the suite. Snowflake adds data sharing; Slack adds Slack Connect; Figma adds FigJam.
  • Consolidate — convert to enterprise. Year 2+. Multiple workspaces consolidate into a single contract, often with SSO, security review, and a procurement-led negotiation. Expansion ACV typically 3–10× first-year ACV.

Example: $15K land → $180K in year 3

A SaaS analytics company sells to a 5-person product team at a 200-employee company for $15K ARR. Year 1 activity: the team uses the product daily, health score reads green, two analysts ask for additional seats. End of year 1: $28K ARR.

Year 2: product team's lead recommends the tool to engineering, who buys a 12-seat workspace. Marketing analytics team is brought in via an exec QBR. The company expands from 1 to 3 workspaces. End of year 2: $85K ARR.

Year 3: SSO and SOC 2 push the company toward a consolidated enterprise contract. Three workspaces merge into one master agreement; a new module (advanced governance) is added. End of year 3: $180K ARR. The original $15K deal produced $180K in year 3 — a 12× expansion — and the customer is now a strategic account.

Benchmarks

MetricBest-in-class PLGMedian PLGTop-down enterprise
First-year ACV$5–25K$15–50K$80K+
NRR (12 mo)130–160%110–125%100–115%
Time to first expansion60–120 days6–9 months12–18 months
Year-3 ARR / Year-1 ARR5–12×2–4×1.2–1.8×
Sales cycle (initial)14–45 days30–90 days90–270 days
Win rate (qualified)35–55%20–35%12–22%

Benchmarks compiled from OpenView 2025 PLG Benchmarks, Bessemer State of the Cloud 2025, and ProfitWell B2B SaaS retention study 2025.

Common mistakes

  • Treating expansion as opportunistic. Expansion is not a nice-to-have — it's the model. Build a dedicated expansion motion with a named owner (often Account Management or a Growth team), expansion playbooks, and quarterly expansion targets.
  • Over-discounting the land. A $1K land doesn't expand to $100K just because it's cheap. Discounting signals low value and attracts low-fit customers. Price the land for the practitioner persona at fair market value.
  • No activation metric. Without a clear definition of "activated" (e.g., 3 users, 5 active workflows, 1 integration), CS teams can't tell which lands will expand. Define activation per persona.
  • Letting expansion become reactive renewals. Expansion conversations should happen 6–9 months before renewal, when the customer is still in growth mode. Waiting until 90 days before renewal turns expansion into a defensive renewal play.
  • Wrong ICP for the model. Land-and-expand fails in markets where the buyer is the executive (highly regulated, compliance-driven, top-down procurement). Match motion to market.

Land-and-expand is measured through the retention metric stack: NRR is the headline outcome; expansion revenue and upsell revenue are the components; gross retention is the floor. Acquisition economics: CAC and CAC payback period. Account-level health: customer health score. Strategy context: product-led growth, the dominant motion that uses this strategy.

At a glance

Category
Revenue Operations
Related
5 terms

Frequently asked questions

What is a land-and-expand strategy?

Land-and-expand is a B2B SaaS go-to-market motion that closes a small initial deal (the land — typically $5–50K) and grows the account over time through seat expansion, cross-sell, and module upsell (the expand). It depends on 120%+ NRR to be economically superior to top-down enterprise selling.

Which companies use land-and-expand?

It is the dominant model for product-led growth companies — Slack, Snowflake, Figma, Datadog, Notion, Atlassian, Monday.com, and Asana all built billion-dollar businesses on land-and-expand. Snowflake disclosed 158% NRR at IPO; Datadog 130%+; Figma 150%+.

What's the difference between land-and-expand and enterprise selling?

Enterprise selling lands a $80K+ contract with an executive after a 6–12 month evaluation cycle. Land-and-expand lands a $5–50K contract with a practitioner in 14–45 days, then grows the account 3–10× over 24–36 months. The two motions need different sellers, marketing, pricing, and packaging — running both well requires segmenting GTM by ICP.

How do you measure land-and-expand success?

Primary metric is NRR (target 120%+). Secondary: time to first expansion (target 60–120 days for PLG), expansion-revenue mix (target 35–50% of new ARR), and year-3 / year-1 ARR ratio (target 5×+). First-year ACV is intentionally low and not a useful metric in isolation.

Does land-and-expand require product-led growth?

Not strictly — sales-led SaaS can run land-and-expand by landing with a single team and expanding via account management. But the highest-performing land-and-expand models pair the motion with PLG: self-serve onboarding compounds with sales-assisted expansion. Pure sales-led land-and-expand caps out at 110–120% NRR; PLG + land-and-expand routinely hits 130–160%.

Sources

  1. OpenView. 2025 Product-Led Growth Benchmarks, 2025. openviewpartners.com
  2. Bessemer Venture Partners. State of the Cloud 2025, 2025. bvp.com
  3. Snowflake S-1 filing. SEC, 2020. sec.gov
  4. ProfitWell. B2B SaaS Retention Benchmarks, 2025. profitwell.com

Fairview tracks expansion velocity, NRR contribution by team, and module attach rate inside customer accounts — see the operating intelligence overview for the broader category.

Definitions and benchmarks reviewed by Siddharth Gangal, Founder, Fairview.

See it in Fairview

Track Land and Expand automatically.

14-day free trial. No credit card. First data source connected in 5 minutes.

Know the number. Take the action.

Continue reading

More from this cluster

See land and expand in your data — book a 20-min demo

Editorial standards

Sources

Definitions and benchmarks reference primary sources from the Revenue Operations pillar. Verified at publication.

  1. 1 State of Revenue Operations 2025 — Forrester / SiriusDecisions, 2025. View source .
  2. 2 B2B Pipeline Coverage Benchmarks — Pavilion, 2025. View source .
  3. 3 LinkedIn State of Sales 2025 — LinkedIn, 2025. View source .

Fairview cites primary sources only — government data, academic research, industry benchmarks from named publishers, and official vendor documentation. See our editorial standards.