Strategy Deep-Dive · 9 min
Land and Expand Strategy: How Snowflake, Datadog, and Atlassian Scale Inside Enterprises
Deep-dive into land-and-expand — the strategy of selling small initial deployments that grow organically into enterprise-wide commitments. Implementation, metrics, examples.
Quick Answer
Land-and-expand is the strategy of selling small initial deployments that grow organically into enterprise-wide commitments. Snowflake, Datadog, MongoDB Atlas, and Atlassian are canonical practitioners. The model works because procurement is easier for small deals; once value is proven, expansion follows usage. The math: companies with 130%+ net dollar retention (NDR) can grow revenue without acquiring new customers. Modern usage-based pricing amplifies the model.
Key Takeaways
- ·Land-and-expand decouples customer acquisition from revenue growth.
- ·NDR is the canonical expansion metric; 130%+ indicates strong expansion economics.
- ·Snowflake's consumption-pricing model produces 150%+ NDR consistently.
- ·Datadog's multi-product expansion is canonical product-breadth strategy.
- ·Design for land-and-expand from inception (pricing, packaging, telemetry).
- ·Customer success investment is proportional to expansion opportunity.
- ·Modern B2B SaaS investors evaluate go-to-market through expansion metrics.
Why It Matters
Land-and-expand decouples customer acquisition from revenue growth. Companies that excel at expansion can grow 30%+ annually without proportional sales investment in new logos. The model rewards product quality, usage telemetry, and customer success investment over outbound sales velocity. For BD operators and revenue leaders, understanding the structural drivers of land-and-expand is required for designing modern enterprise SaaS go-to-market.
Land-and-expand emerged as a structural pattern in cloud-era B2B software. Pre-cloud enterprise sales required large upfront commitments — million-dollar perpetual licenses, multi-year contracts negotiated at the CIO level. Cloud delivery enabled small initial deployments that scaled with usage. Companies that designed for expansion (consumption pricing, product-led growth signals, customer success teams) outperformed companies with traditional enterprise GTM by structural margins.
Companies Using This Strategy
Snowflake
Canonical modern consumption-pricing example. Customers start with departmental usage; expand to enterprise-wide data warehouse. NDR consistently 150%+.
Datadog
Started with single-product monitoring; expanded to multi-product observability platform. Customer typically uses 4+ Datadog products at maturity.
MongoDB Atlas
Atlas (managed MongoDB) lands with development workloads; expands to production database for enterprise applications.
Atlassian
Jira lands with engineering teams; expands to product, design, IT, business teams. Bitbucket, Confluence, Trello extend further.
Notion
Lands with individual user or small team; expands to entire organization via collaboration network effects.
Read case study →Why land-and-expand works structurally
Land-and-expand exploits structural advantages of cloud delivery and modern procurement: (1) **Small deals bypass procurement friction**: $5K-$50K deployments avoid CIO-level review, legal negotiation, security audits. Department managers can approve with corporate cards or simple POs. (2) **Usage validates value**: customers who have used the product for 6+ months have ground-truth data on whether it works. Expansion conversations are evidence-based. (3) **Switching costs accumulate**: data, integrations, and team training create real switching costs once the product is operational. (4) **Consumption pricing aligns vendor and customer**: when revenue grows with customer usage, vendor incentives align with customer success. (5) **Internal champions emerge**: product users become internal advocates who drive expansion within their organizations. The model fails when the initial deployment doesn't provide enough value to justify expansion conversations. The land deal must produce demonstrable wins.
Net Dollar Retention (NDR) and the math of expansion
NDR is the canonical land-and-expand metric. NDR = (Starting ARR + Expansion - Churn - Contraction) / Starting ARR. NDR of 100% means existing customers exactly replace churned revenue. NDR of 130%+ means existing customers generate 30%+ growth without new logo acquisition. NDR of 150%+ (Snowflake territory) means existing customers drive most of the growth. The math has compounding implications. A company with $100M ARR and 150% NDR will reach $225M from existing customers alone after 2 years (excluding new acquisitions). With moderate new logo growth, total revenue compounds rapidly. The metric is reported by public SaaS companies and tracked closely by investors. NDR is the canonical 'quality of revenue' signal for B2B SaaS — high NDR means low churn and strong expansion economics.
The Snowflake consumption-pricing model
Snowflake's pricing is purely consumption-based — customers pay per compute-second and per terabyte-stored. There are no seat licenses or feature gates. The pricing structurally enables land-and-expand because customers can start with minimal usage and grow without renegotiating contracts. The Snowflake model has multiple structural advantages: (1) **No procurement re-friction**: customers don't need to renegotiate as usage grows. Expansion is automatic. (2) **Aligned incentives**: Snowflake's revenue grows with customer success. Customer success investment has direct ROI. (3) **Usage telemetry**: Snowflake knows exactly which customers are growing usage. Account teams can engage proactively. (4) **Cohort economics**: Snowflake cohorts (customers acquired in a given quarter) typically grow revenue 2-3x over 3-4 years. The model has costs. Consumption pricing produces revenue volatility (customers can reduce usage). Forecasting is structurally harder than seat-based subscription. But the upside — Snowflake's >150% NDR — has more than compensated.
The Datadog multi-product expansion pattern
Datadog's expansion follows a different pattern. Customers land with a single product (typically Infrastructure Monitoring or APM) and expand to multiple Datadog products over time. As of 2024, customers using 4+ Datadog products generate disproportionate revenue. The pattern requires careful product investment: (1) **Product breadth**: Datadog has expanded into Logs, RUM, Synthetics, Security, Cloud Cost Management, and many other adjacencies. (2) **Integration quality**: each new product integrates with the others. A customer using APM + Logs + RUM gets correlated visibility that single-product alternatives can't match. (3) **Pricing simplicity**: most Datadog products are usage-priced with consistent metering. Customers can adopt incrementally. (4) **Account team coordination**: dedicated account teams identify expansion opportunities and orchestrate cross-product adoption. The Datadog multi-product pattern is replicable but requires substantial product investment. Most companies cannot build 10+ adjacent products simultaneously. Datadog's specific timing (entering observability before most categories were defined) was structurally advantageous.
Designing for land-and-expand from day one
Companies designing for land-and-expand from inception have advantages over companies retrofitting: (1) **Pricing structure**: usage-based or per-seat pricing that grows organically beats annual-contract pricing for expansion. (2) **Product packaging**: avoiding feature-gated tiers that require contract renegotiation for expansion. Modern packaging emphasizes capacity rather than feature differentiation. (3) **Onboarding for solo users**: products that work for individual users land before expanding to teams. PLG patterns emphasize solo-user value. (4) **Internal virality features**: collaboration, sharing, and team-invite features make expansion organic. (5) **Usage telemetry from day one**: companies that instrument usage from inception can identify expansion opportunities proactively. Retrofitting telemetry is harder. For founders building B2B SaaS in 2026, designing for land-and-expand is default expectation. Investors evaluate go-to-market plans through expansion metrics. The pattern has shifted from differentiator to baseline expectation.
When It Works
- ·Product provides clear value in small initial deployment (single team, single use case)
- ·Pricing structure supports organic growth without contract renegotiation
- ·Product naturally expands across teams or use cases (collaboration, multi-product breadth)
- ·Customer success investment is proportional to expansion opportunity
- ·Usage telemetry identifies expansion opportunities proactively
When It Fails
- ·Initial deployment doesn't provide demonstrable value (no expansion conversation)
- ·Pricing structure requires contract renegotiation for expansion (procurement re-friction)
- ·Product doesn't naturally expand (single-team single-use-case applications)
- ·Customer success investment is inadequate for expansion identification
- ·Competitive products at similar prices commoditize expansion
How to Implement
- 01Design pricing for organic growth: consumption pricing or per-seat with clear marginal cost.
- 02Build product packaging that emphasizes capacity over feature differentiation.
- 03Instrument usage telemetry from inception to identify expansion opportunities.
- 04Invest in customer success teams proportional to NDR opportunity.
- 05Design product features for internal virality (sharing, collaboration, team invites).
- 06Build account-team coordination processes for expansion conversations.
- 07Set NDR targets and report them publicly to align incentives across organization.
Common Pitfalls
- 01Over-investing in new logo acquisition at expense of expansion infrastructure.
- 02Pricing structures that create procurement re-friction for expansion.
- 03Customer success teams sized for retention rather than expansion.
- 04Product packaging that gates expansion behind contract renegotiation.
- 05Inadequate usage telemetry making expansion conversations reactive rather than proactive.
Sources
Frequently Asked Questions
Companies That Pioneered This Pattern
Operational Playbooks
Playbook
How to Build a Strategic Partnership Program From Scratch
An operator playbook for designing, launching, and scaling a strategic partnership program — from first hire to a measurable revenue contribution.
Playbook
The Enterprise Tech Partnership Playbook
How tech companies should structure strategic partnerships with enterprise customers and platforms — moving beyond logo deals to real co-engineering, co-selling, and joint roadmaps.
Playbook
The VC Portfolio BD Playbook: Building Real Partnership Value at Scale
How venture firms should structure portfolio business development to actually move partner-sourced revenue across their companies — not just facilitate intros.
Related Rankings
List
Best Cold Email Tools of 2026: Apollo, Lemlist, Smartlead, and the Outbound Stack
Ranked list of the top cold email and outbound sales tools — Apollo, Lemlist, Smartlead, Instantly, and the leading platforms for B2B outbound prospecting.
List
Best CRM Platforms of 2026: Salesforce, HubSpot, and the Modern Customer Relationship Stack
Ranked list of the top CRM platforms for B2B sales teams — Salesforce, HubSpot, Pipedrive, Microsoft Dynamics, Zoho, and modern alternatives.
List
Best Customer Data Platforms (CDPs) of 2026: Segment, mParticle, RudderStack, and the Modern Data Stack for Customer Data
Ranked list of the top customer data platforms — Segment, mParticle, RudderStack, Hightouch. The platforms unifying customer data for analytics and activation.
Other Strategy Deep-Dives
Strategy
AI-Native Product Strategy: How Cursor, Perplexity, and Ramp Build Products That Compound With Models
Deep-dive into AI-native product strategy — building products where AI is foundational, not a feature add-on. Examples, mechanics, and implementation patterns.
Strategy
API-First Distribution Strategy: How Stripe, Twilio, and Plaid Won Through Developer Experience
Deep-dive into the API-first distribution strategy — what it requires, which categories it fits, and how the canonical API-first companies executed.
Strategy
Blitzscaling Strategy: When Reid Hoffman's Speed-Over-Efficiency Playbook Works
Deep-dive into blitzscaling — prioritizing speed over efficiency to capture winner-take-most markets. Reid Hoffman's framework, canonical examples, and when it fails.
Strategy
Category Creation Strategy: How Gong, Salesforce, and HubSpot Defined Their Markets
Deep-dive into category creation — defining a new market category before competitors arrive. What it requires, when it works, and how the canonical category creators executed.
Explore Further
Hub
Tools
Free calculators and interactive utilities
Hub
Resources
Ideas, checklists, glossaries, and statistics
Hub
Playbooks
Strategic playbooks for partnerships and BD
Hub
Case Studies
Strategic breakdowns of leading companies and projects
Hub
Lists
Curated rankings of the best companies, tools, and programs
Hub
Profiles
Founders, investors, and operators shaping tech
Hub
Postmortems
Why FTX, WeWork, Theranos and other major failures collapsed
Hub
Roles
Business development and partnership roles defined
Hub
Salaries
Compensation data by role and city
Hub
Compare
Side-by-side comparisons of roles and strategies
About the Author
David Shadrake
David Shadrake works on strategic business development and tech partnerships, with focus areas across AI, fintech, venture capital, growth, sales, SEO, blockchain, and broader tech innovation. Read more of his perspective on partnerships, market dynamics, and emerging technology at davidshadrake.com.