How Does a Land and Expand Motion Actually Work?

How does a land and expand motion actually work?

You design the first purchase so that succeeding at it creates the conditions for the second. Not a small deal that you upsell later, but a deliberate first use case whose success naturally produces the next one. If the first deal does not lead anywhere by design, you do not have land and expand, you have a small deal.

We sit next to a lot of B2B go to market teams, building the sites and systems their motion runs on. The gap between companies that talk about land and expand and companies that actually run it is almost always in the first purchase, not in the expansion effort.

Here is the framework, in five parts, and what each one requires you to actually build.

What does good land and expand look like at scale?

Revenue growing faster from existing customers than from new ones. Snowflake's own results for its fiscal 2026 fourth quarter, for the period ended 31 January 2026, reported a net revenue retention rate of 125 percent. That means the same set of customers spent a quarter more than they had the year before.

The same release reported 733 customers with trailing twelve month product revenue greater than 1 million dollars, up 27 percent year over year, and 790 Forbes Global 2000 customers, up 5 percent. Look at those two numbers together. The large customer count grew five times faster than the logo count.

That is the signature of the motion working. Growth is coming from accounts getting bigger, not from the sales team landing a proportionally larger number of new names. Consumption pricing makes it especially visible, but the shape applies to seat based businesses too.

Part one: what should the land actually be?

The smallest complete use case, not the smallest package. Those sound similar and behave completely differently. A complete use case delivers a real outcome for one team. A small package delivers a partial outcome for everyone, which delivers nothing.

Pick a use case with a natural adjacency. If team A succeeds with this, team B has an obvious reason to want it. That adjacency is the expansion path and it has to exist before the first contract is signed, not be discovered afterwards.

The test is whether you can name the second buyer during the first sale. If you cannot, the land is a dead end and expansion will require starting the whole sales process again from cold, inside an account that now has opinions about you.

Part two: what has to be true for the land to succeed?

The first team has to reach a measurable result inside the first contract period, and somebody has to notice. Both halves matter. A quiet success expands nothing because the internal case for spending more has no evidence behind it.

So define the success metric with the customer at the start, in their terms, and instrument it. Then report it back to them in a form they can forward to their own finance team. That report is the single most valuable artefact in the whole motion and most companies never build it.

Getting this right is also what separates expansion from renewal anxiety. An account with documented results renews without a conversation. Our piece on customer marketing and expansion covers the operational side of producing that evidence repeatedly.

Part three: how does the expansion trigger work?

It should come from usage, not from the calendar. Seats filling up, volume approaching a limit, a second team asking for access. These are observable events and they are the only honest basis for the next conversation.

Quarterly business reviews scheduled by your side are a weaker instrument, because they arrive when it suits your forecast rather than when something changed for them. They are not useless, they are just not the trigger.

Build the instrumentation before you build the playbook. A land and expand motion without usage visibility is a hope, and the account executive is left guessing which accounts are ready. That is a data problem masquerading as a sales problem.

Part four: who owns the expansion?

Whoever has the relationship with the person who would sponsor it, which is often not the person who signed the first deal. Expansion usually means a new budget holder, and a new budget holder means a new sale, however warm the logo is.

This is where organisational design bites. If your customer success team owns the relationship and cannot sell, and your sales team can sell and has no relationship, expansion falls into the gap between them. Deciding this explicitly is worth more than any playbook.

Our general view is that the person who owns expansion should also own the success metric from part two, because those are the same job seen from two angles. Splitting them creates a handoff at the exact moment credibility matters most.

Part five: how should pricing support the motion?

The next step up has to be obvious and small. If moving from the landed use case to the next one requires a fivefold price jump and a procurement cycle, expansion stops being a natural consequence and becomes a project.

Price transparency helps more than most B2B companies believe. Nielsen Norman Group's B2B usability research, published by Jakob Nielsen on 31 May 2006, found that when users ranked 28 types of B2B information, price came first, 29 percent above product availability in second place. That preference has not softened since.

You do not have to publish every number. You do have to make the shape of the next step legible to someone building an internal case without you in the room. Our article on pricing and packaging tiers goes into how to structure that.

When is land and expand the wrong motion?

When your product only delivers value at full deployment, or when the buying decision is genuinely made once at the top. Some categories work that way. Trying to land small in them produces a pilot that proves nothing and dies quietly.

It is also wrong when your smallest sellable unit still requires a six month implementation. At that point the land is not small, it is just cheaper, and you have taken on all the cost of a large deal with the revenue of a small one.

Be honest about which you are. Plenty of companies run a land and expand narrative over an enterprise motion because the former sounds more modern, and the mismatch shows up as a sales team that cannot hit either target.

What should the website do to support this?

Make the expansion path visible to people who never spoke to your sales team. A large share of internal expansion cases are built by someone who was not in the original process, using your public pages, at a moment when nobody from your company is involved.

That means the pages describing adjacent use cases have to stand alone, and the pricing structure has to be comprehensible without a call. This is the part we can speak to directly, because it is what we build, and it is consistently under invested relative to the acquisition pages.

The practical version is a use case page per adjacency, each answering what this is, who it is for, what it costs to add, and what changes operationally. Our piece on feature page design covers making those pages do real work.

What is the most common way this fails?

The land succeeds, nobody documents it, the champion changes jobs, and the expansion conversation starts from zero with someone who has no memory of the result. This happens constantly and it is entirely preventable.

The prevention is boring: write the result down, share it with more than one person in the account, and keep a version the customer can circulate without you. Institutional memory inside your customer is an asset you have to actively create.

The second most common failure is expanding into a use case your product serves badly, because the account was willing. That converts a happy customer into an unhappy one, and it is a worse outcome than not expanding at all.

What would we build first?

The success report from part two. Before the playbook, before the triggers, before the pricing redesign. One document per account, showing what the landed use case actually delivered, in the customer's own numbers.

It is the input to every other part of the framework. It proves the land worked, it gives the champion something to circulate, it justifies the price of the next step, and it tells you which accounts are actually ready.

If you want help making the expansion path legible on your site, or building the pages an internal champion needs when you are not in the room, we are happy to walk through it. Find us at phoenix.studio.