Land and Expand

Selling business software used to mean winning a single contract. The whole company would use the thing, so the approval chain was long. Security reviewed it, legal read the contract, procurement pushed the price down. Six to eighteen months passed between the first conversation and a signature.

Asking about the status of a deal in a sales meeting produced the same answer every time. Security review, still, for the third month running. In month four, word arrives that the executive sponsor has moved on, so the explanation starts over from the beginning. Without a signature, every hour spent counts for nothing.

A different route opened once products showed up that a team could try for free and a manager could put on a company card. Shrinking the first contract shortens the approval chain: a ten-seat deal skips security review and procurement entirely and ends at a team lead's desk. And the fact that one team is genuinely using the product becomes the argument for the next contract. The raw material for persuasion moves from a slide deck to a usage record.

It starts with picking one team to enter through, and runs in six steps.

1. Pick the team. Not the group with the greatest theoretical need, but the one most inconvenienced by the problem right now. For a collaborative document tool, that's the team that has already had an incident from passing three versions of the same file around.
2. Size the first contract to fit inside the approval chain. Keep it under the amount a team lead can approve without escalating. Propose $460 a month to an organization whose discretionary limit is $400 and you buy three months of approval process for $60.
3. Confirm it stuck. Watch actual usage for the first 30 to 60 days after signing. Twelve seats sold with four people logging in weekly is not something you can expand on.
4. Wait for the expansion signal. When the first team starts inviting people from other teams into documents, or asks for more seats, that's the moment to widen.
5. Move to the neighboring team. The material here is the first team's record, not the product brochure. Numbers like review turnaround dropping from two days to half a day land as an internal case study from inside the same company.
6. Consolidate into a company-wide contract. Once scattered seats pass a threshold, the company usually asks for pricing terms first. The long security and procurement process you avoided at the start gets done here, and with several hundred people already using the product, the conclusion doesn't get overturned.

Expansion is normally handed off from the rep who closed the deal to whoever owns the account afterward. Because selling and embedding split between two people, steps 3 and 4 need an owner named in advance or the company ends up with nothing but first contracts.

The approach only works when one team alone gets value from the product. Collaborative document tools and design tools qualify: ten people is enough for the thing to be worth using. Payroll or enterprise resource planning software, where value appears only when the whole company moves at once, offers no small door to enter through.

Four conditions make it fit: seat-based pricing, usage that is visible to the people nearby, a market where team leads hold discretionary budget, and a light setup cost. Visibility does more work than it looks like. Sharing a document puts the product in front of whoever receives it, while an audit tool used alone by one accountant gives the neighboring team no way to know it exists.

In finance and the public sector, where a security review is the first gate rather than the last, a ten-seat contract triggers the same review as a thousand-seat one, and the advantage of entering small disappears. Products priced per transaction or per gigabyte don't produce a seat-growth story either.

The limit is that the money arrives late. Twelve seats puts the first year around $2,300, which takes close to a year just to repay what the account cost to win. If it never widens, it never repays at all. Companies running this approach therefore measure themselves on how many times the seat count multiplied after a year, not on how many first contracts they closed.

It pairs naturally with solution selling, which sells the resolution of a problem rather than a feature list. Picking the first team means naming the problem that team is living with, and that conversation is exactly the one solution selling is built for.

"Let's run this as land and expand. Marketing, ten seats, instead of the whole company."

A proposal to dodge the long approval chain by starting small and widening later.

"We landed but we can't expand. Six months in and it's still the same ten seats."

The first contract closed, but the footprint isn't growing, so no revenue follows.

"An account that was 20 seats a year ago came in at 180 this quarter."

Reporting a small entry that grew into a company-wide contract.

Pagedeck switched to this approach after one failed deal. Sofia proposed a company-wide rollout to a 500-person company, spent five months in security review alone, and watched it die when the sponsoring executive changed roles just as the review was wrapping up.

At the next company she started with twelve seats in the marketing team. Ninety days later, eleven of the twelve were logging in weekly and forty documents had been shared outside the team. The design team, having received some of those documents, reached out first — and Sofia brought the marketing team's record rather than a product pitch. Eight months on, the company moved to a 140-seat contract, and the security review attached to it finished in three weeks, because four departments were already using the product.

The most common mistake is reading "enter small" as "discount." Low barrier to entry sounds like a price cut. But what shrinks is the seat count, not the price per seat. Cut the unit price to get in and that number hardens into the account's baseline. At 180 seats the math still runs on the discounted rate, so seats multiply tenfold while expansion revenue — the revenue growth that comes from existing customers using more — arrives at half of what was expected. That growth is the entire point of the approach, and cutting the rate at the start cuts into it.

The second is assuming that once you're in, it spreads on its own. Stories about practitioners adopting something that then sweeps through an organization make it look that way. In practice the neighboring team is a separate unit with a separate budget and a separate approver. That the first team likes the product is a reference for them, not a decision. Left unaddressed, the account list fills up with entries stuck at ten seats for two years. Contract counts rise while revenue sits still, and waking those accounts back up costs about as much effort as finding new ones.