The Land and Expand Motion: Starting Small on Purpose

Before you sign the first contract, decide what the expansion trigger will be: a seat count, a usage tier, a second team or department, or a feature currently gated behind a higher plan. Structure the initial deal so that trigger is visible and likely to be hit within the first two quarters, not buried in a plan the buyer will not reach for a year. Say a buyer signs for a five seat starter plan: if their team is already twelve people, you have not landed a deal built to expand, you have landed a deal built to be renegotiated at renewal instead of expanded along the way.

Most onboarding is built around getting the buyer to first value on the use case they bought for. That is necessary, but it leaves expansion to chance. Build a second onboarding checkpoint, thirty to sixty days in, that specifically introduces the adjacent use case or team you eventually want to land: if a single team bought for one workflow, that checkpoint might show them the reporting view a manager would want, or the integration a second department already uses elsewhere. Without that deliberate second touch, expansion depends on the buyer discovering it themselves, which happens far less often than product teams assume.

A land and expand motion moves fast when the expansion conversation happens, and stalls when legal and procurement become the bottleneck. Standardize your order form addendum for seat and tier changes so an expansion does not require a full new contract cycle, and use an e-signature tool like Foxit eSign so a champion can approve an upgrade between meetings instead of waiting on a scheduling call. A pre-signature checklist in a tool like Process Street, covering the handful of approval steps most expansions need, keeps a willing buyer from cooling off while paperwork catches up with their decision.

New logo pipeline gets a stage by stage view in most CRMs. Expansion opportunities inside existing accounts usually do not, which is why they get missed. Give expansion the same structure: a signal that the account is ready (hit the usage trigger, added headcount, asked about a locked feature), a defined next step, and an owner, whether that is the original seller, a CSM, or both working the account together. Average win rates on new logo deals sit around 19 percent¹, and expansion deals inside a live, referenceable account routinely close at much better odds, which is the entire economic case for building this motion deliberately instead of leaving it informal.

Give every expansion opportunity these elements:

• A stage-by-stage view of expansion opportunities, kept alongside your new logo pipeline.
• A readiness signal, such as hitting the usage trigger, adding headcount or asking about a locked feature.
• A defined next step recorded on the account.
• A named owner, whether the original seller, a CSM or both working the account together.

Founders often expect expansion within the first quarter, then get discouraged when accounts stay flat and abandon the whole motion. A more realistic view is a first meaningful expansion signal by the end of the second quarter for most B2B products, once onboarding is complete and the account has had time to hit real usage. If an account has not shown any expansion signal by month six, that is worth a direct conversation about whether the use case landed at all, rather than waiting quietly for a renewal that might not come.

For example, say an account landed in January on a starter plan and finished onboarding in February. By the end of the second quarter the team has hit the usage tier you set as the trigger, but nobody has told the seller. Because expansion readiness is tracked like pipeline, the account shows a signal and an owner, so the CSM books a conversation about the second team instead of waiting for the renewal notice. If the same account had shown no signal by month six, the useful move is the direct conversation about whether the use case landed at all, and what would need to change for it to expand.