Land-and-Expand

How do you design a land-and-expand motion?#

1. Choose a whole initial use case#

The land should solve a complete job for a specific user and buyer — small enough to approve without a committee, large enough to demonstrate economic value. A half-job produces a customer who cannot tell whether the product worked.

2. Agree the proof before the sale closes#

Document the baseline, the success outcome, the data source, the measurement period, and the customer's own responsibilities. Product activity is only useful when it connects to a business or risk outcome the buyer already cares about. See Customer Success.

3. Map named expansion paths#

For every land, write down the specific next step: which unit grows, who the next buyer is, what triggers the conversation, what technical dependency must be cleared, and what the value case will be.

"The entire enterprise" is not an expansion plan. "The EMEA compliance team, once the US team's Q3 audit closes, contingent on SSO and regional data residency" is.

4. Measure retention correctly — both numbers, always#

GRR = (starting recurring revenue − churn − contraction) ÷ starting recurring revenue

NRR = (starting recurring revenue − churn − contraction + expansion) ÷ starting recurring revenue

expansion rate = expansion recurring revenue ÷ starting recurring revenue

GRR is capped at 100% and measures whether you keep what you had. NRR can exceed 100% and measures whether the cohort grows. Reporting NRR alone is the single most common way founders mislead themselves. Report logo retention and cohort maturity alongside both — a young cohort has not had time to churn.

5. Attach expansion economics#

expansion CAC = attributable expansion sales, success, solution, and incentive cost ÷ expanded accounts

expansion payback (months) = expansion investment ÷ monthly contribution from incremental recurring revenue

If expansion requires recurring custom service, that cost belongs in gross margin, not in acquisition cost. Booking recurring delivery labour as a one-time acquisition expense makes every expansion look profitable and is the reason some "efficient" expansion motions never reach the margin they projected.

6. Test concentration and saturation#

Report NRR excluding the largest one, three, and five customers. Report expansion by source unit. Report the share of accounts with a credible next use case — because mature accounts saturate, and a motion whose remaining runway is unmeasured is a forecast waiting to miss.

Worked example: reading a cohort honestly#

A fictional cohort begins the year with 100 customers and $1,000,000 of ARR. During the year: churn removes $80,000, contraction removes $40,000, and expansion adds $260,000.

The headline numbers#

GRR = ($1,000,000 − $80,000 − $40,000) ÷ $1,000,000 = 88%

NRR = ($1,000,000 − $80,000 − $40,000 + $260,000) ÷ $1,000,000 = 114%

expansion rate = $260,000 ÷ $1,000,000 = 26%

The cohort ends at $1,140,000. But 12% of starting ARR disappeared before expansion did anything. The founder must not present 114% NRR as "14% organic growth with almost no churn" — the correct sentence is "we lost 12% and bought it back with 26% expansion."

Expansion economics#

The company spends $65,000 on expansion sales, customer success, solution work, and incentives. At 80% contribution margin:

incremental annual contribution = $260,000 × 80% = $208,000

monthly incremental contribution = $208,000 ÷ 12 = $17,333

expansion payback = $65,000 ÷ $17,333 = 3.75 months

Caveat on this figure. It divides a full year's expansion investment by the monthly contribution of expansion that accrued across that year, not from day one. Treat 3.75 months as an order-of-magnitude comparison against new-logo payback, not as a cash-flow forecast. For a cash view, use the actual monthly bookings curve.

Now inspect concentration#

One customer produced $130,000 of the expansion — half of it. Excluding that account:

NRR = ($1,000,000 − $80,000 − $40,000 + $130,000) ÷ $1,000,000 = 101%

The strategy still works. But the difference between 114% and 101% is one relationship, and capacity planning, forecasting, and the investor narrative should all say so.

Now add the delivery cost#

Suppose the expanded product requires $4,000 of annual customer-specific service per expanded account, across 20 expanded accounts:

recurring service cost = 20 × $4,000 = $80,000

net incremental annual contribution = $208,000 − $80,000 = $128,000

monthly = $128,000 ÷ 12 = $10,667

expansion payback = $65,000 ÷ $10,667 = 6.1 months

Payback nearly doubles, from 3.75 to 6.1 months, and the 80% margin assumption is revealed as the load-bearing wall it always was. Expansion ARR without delivery cost is not economic expansion. See Gross Margin.

What are the common mistakes?#

• Landing too small to prove value. A token contract creates cost and no evidence. The customer cannot expand from a deployment that never demonstrated anything.
• Selling the expansion in the first contract. The customer should buy today's value. Pre-selling the roadmap converts a land into an obligation you have not yet earned.
• Using NRR without GRR. Expansion hides churn and contraction. Two companies at 114% NRR — one at 95% GRR, one at 88% — are not comparable businesses.
• Reporting price increases as adoption. Separate price, seats, usage, and cross-sell in the expansion bridge. If you cannot separate them, you cannot tell whether customers are getting more value or just paying more.
• Treating expansion capacity as free. Expansion competes with new-logo acquisition, onboarding, and escalations for the same customer success and solution engineering hours.

When does land-and-expand break?#

• The initial use case is disconnected from the economic buyer. A delighted team whose budget owner never saw the outcome cannot pull the account forward.
• Architecture cannot support organisation-wide governance. If permissions, data separation, admin visibility, or deployment options cannot handle a second business unit, expansion becomes a re-implementation.
• Adjacent products do not reuse the workflow or the trust. Cross-sell into a different job, a different user, and a different budget is new-logo acquisition with a familiar logo attached — price and staff it accordingly.
• Procurement blocks incremental purchases, or the first contract locks in a low price. Some enterprises make every addition a new cycle. Model expansion as a fresh buying process where that is true, and avoid multi-year terms that price the whole account at the wedge's value.
• Usage-based expansion reflects waste rather than value. Customers optimise consumption downward, or react badly to unpredictable bills. Pair consumption growth with realised outcomes, budget alignment, and transparent forecasts. See Usage-Based Pricing.
• Expansion is really lock-in. Revenue that persists because leaving is painful is not the same as revenue that persists because the product is valuable. The two look identical in NRR and behave very differently when a credible alternative appears. See Switching Costs.