Land in one team, then expand across the whole company

Land and expand means starting with a small deal in one team or department, proving value there, and then growing the account across the rest of the company. The first deal is easy to approve. The real revenue comes later, as other teams adopt the product. It fits B2B and SaaS products that solve a problem shared by many teams in the same company, with pricing that grows with seats, usage or departments.

Why it works

Large company-wide deals are slow and risky for buyers. They involve many stakeholders, long security reviews and big budgets. A small team purchase skips most of that and lets the customer test the product with little risk. Once it works, you have proof inside the company and a user who can vouch for you, which is far more persuasive than any case study from another company.

Expansion revenue also costs less to win. You already have a contract, security approval and a relationship, so each new team is a shorter sale than a new customer.

How to do it

1. Design an easy first purchase. Offer a team plan or starter package that a single manager can approve, ideally on a card or a simple order form.
2. Pick the right landing team. Look for a team with an urgent problem, a motivated leader and visibility across the company. A successful launch there is easy for others to see.
3. Get them to a clear result. Agree what success looks like and help them reach it quickly, with onboarding, training and regular check-ins.
4. Build a champion. Identify the most enthusiastic user or manager. Give them material to share, such as a results summary, and invite them to customer events.
5. Map the account. List other departments, regions and subsidiaries that face the same problem. Note who leads each one and how they buy.
6. Use internal referrals. Ask your champion for introductions to peers. Run lunch-and-learn sessions or internal demos the champion hosts.
7. Make expansion easy. Let new teams join the existing contract with simple add-on orders and the same security approvals.
8. Consolidate when ready. Once several teams use the product, propose an enterprise agreement with central billing, admin controls and volume pricing.

Example

A hypothetical contract management SaaS sells a team plan to the legal team at a mid-sized manufacturer. Within two months, the legal team cuts its contract turnaround time and the general counsel mentions it in a leadership meeting. The account manager asks the general counsel to introduce procurement and sales operations, who both handle many contracts. Each team joins on an add-on order under the same security review. A year later, with four departments using the product, the customer asks for a single company-wide agreement with central admin controls, and the account grows several times larger than the first deal.

Metrics to track

• Net revenue retention. Revenue from existing customers after expansion, contraction and churn. Land and expand should push this up.
• Expansion revenue share. The share of new annual recurring revenue that comes from existing customers.
• Teams or departments per account. Average number of teams using the product in each customer over time.
• Time from land to first expansion. How long it takes for a second team to join after the first deal.
• Landing team retention. If first teams do not renew, expansion will never happen.

When it backfires

• Landing too small. A pilot with a handful of users may never produce results anyone notices.
• Landing in the wrong team. A team with no influence or a weak use case produces no champion and no referrals.
• Pricing that punishes growth. If adding teams triggers sharp price jumps or new contracts, customers cap usage.
• Forgetting the first team. Chasing new departments while the original team’s needs go unmet risks losing the anchor.
• Siloed contracts. Letting each team buy separately with different terms creates admin pain and makes consolidation a negotiation against you.

Questions people ask

How small should the first deal be?

Small enough that one manager can approve it without a long procurement process, and large enough to prove the product works. The right size depends on your market and how purchasing works in your customers' companies.

When should we push for a company-wide contract?

Once several teams use the product and the customer is managing multiple purchases, a central agreement saves them effort. Wait until there is real usage across teams before asking procurement to consolidate.

Who should own expansion, account managers or new business reps?

Either works if the role is clear. Many teams have account managers own growth inside existing customers, with new business reps focused on landing new logos.