Land and expand is a two-phase B2B and SaaS growth motion. First the vendor lands a small, low-risk initial deal with a new customer (a limited seat count, a single team, or one use case), deliberately keeping the first purchase easy to approve. Then, once the product has proven itself inside the account, the vendor expands revenue from that same customer over time: adding seats and users, cross-selling additional products, upselling to higher tiers, or growing consumption on a usage-based plan. The appeal is economic. Landing small lowers the barrier to a first yes, and expanding within a proven account is usually cheaper and higher-converting than winning a brand-new logo.
The phrase is well-established, informally originated industry jargon rather than an academic or single-authored framework, and no one credible coiner or founding date is documented. Forbes was already describing it as a known sales approach in a November 2014 article by Josh Linkner, so the term predates that in common use. Chasm Group frames it as a modern relabeling of the older practice of account development and argues it has to be a company-wide strategy rather than a sales tactic. TSIA built a more granular four-stage framework, LAER (Land, Adopt, Expand, Renew), around the same idea, and Egnyte's leadership has described an internal three-stage variant, Land, Expand, Explode.
Today the motion is standard across sales, customer success, and RevOps teams in subscription software. Slack, whose free-tier teams convert and grow into paid company-wide plans, and Atlassian, which cross-sells across Jira, Confluence, and Bitbucket, are the examples that recur most often in secondary coverage. Net revenue retention is the metric most commonly used to judge whether the expand half is actually working.
How the land and expand phases work
The two phases are run differently and often by different teams. Landing is an acquisition problem: price and package the entry point so a single buyer can say yes without a large committee, a long procurement cycle, or a full rollout. That usually means a small seat count, a single department, a free or low-cost tier, or one narrow use case that delivers a visible win quickly.
Expanding is a retention-and-growth problem. Once the product is embedded and generating measurable value, the vendor grows revenue inside the same account through four common levers: adding seats as more users adopt the tool, upselling to higher-priced tiers with more capability, cross-selling adjacent products in the same suite, and growing consumption on usage-based pricing. Which lever dominates depends on the pricing model: a per-seat product expands mainly through seats and tiers, a consumption product through usage. In practice the expand motion is frequently owned by customer success or account management rather than the original closing rep, because it depends on adoption and renewed trust rather than a cold pitch.
Land and expand vs. net revenue retention
These two are easy to conflate because they describe the same phenomenon from opposite ends. Land and expand is the strategy: the deliberate choice to win small and grow within the account. Net revenue retention, also called net dollar retention, is the metric that measures whether that strategy is working. NRR compares recurring revenue from an existing set of customers at the end of a period against the start, counting expansion up and contraction and churn down.
A vendor can run a land-and-expand motion and still post weak NRR if churn or downgrades outpace expansion, which is exactly the signal that the expand half has stalled. Reading them together is the point: the strategy sets the intent, the metric grades the execution. This also distinguishes land and expand from its tactics. Upsell and cross-sell are the specific moves used to execute the expansion; product-led growth is a broader acquisition-and-adoption methodology that can feed the land phase but is not synonymous with expanding an already-won account.
Reading a competitor's shift toward land and expand
For a competitor-tracking team, land and expand is most useful as a lens for interpreting a rival's public signals rather than a term to define in the abstract. A vendor pivoting from new-logo acquisition toward expansion-led growth tends to leave trackable artifacts. Pricing and packaging pages start to add seat-based or usage-based tiers and new modules or add-ons clearly aimed at cross-selling an existing base. Job boards open Customer Success, Account Management, and explicitly named Expansion or Growth roles. New customer case studies emphasize account growth over time (started with one team, now company-wide), and review-site language begins to mention upsell pressure.
These are exactly the changes a competitive-monitoring workflow surfaces: pricing-page diffs, job-posting changes, new case-study pages, and shifts in review sentiment. Taken together they tell a sales or product team when a rival is reweighting toward expansion, which matters most in shared accounts where that competitor has already landed and is now trying to grow underneath you. That intelligence sharpens battlecards and displacement plays.
Common mistakes and limitations
The most common failure is treating land and expand as a sales tactic rather than a company-wide commitment. If the entry deal is landed but the product does not deliver a fast, visible win, there is nothing to expand into, and the small first contract simply becomes a small, churning contract. Chasm Group's argument is precisely this: expansion has to be designed into onboarding, product, and customer success, not bolted on by a quota-carrying rep after the fact.
A second trap is landing too small or in the wrong place: a foothold in a team with no path to the rest of the organization, or a discount so deep that expansion never recovers the economics. The strategy also assumes the account has room to grow; in a small customer with a single use case, there may be no expand phase to run. Finally, expansion revenue can mask underlying weakness: strong growth from a few accounts can hide broad churn, which is why NRR, cohort views, and logo retention should be read alongside the motion, not in place of it.