Concept · Growth

Land and expand

A small deployment opens a path only when the next use case, buyer and economics make sense.

A small start can grow as value is demonstrated across an account.

A team begins using a tool and likes it. The supplier now wants the whole company to buy. The gap between those events is the central problem of land and expand. Local adoption can reveal value and produce a champion, but a broader deployment can introduce a new budget owner, security obligations, implementation work and users with a different task. The next sale must solve those requirements as well as preserve the first team’s benefit.

In one sentence

Land and expand is a growth motion in which a limited initial customer deployment creates a path to additional users, workloads or products within the account.

Define both ends of the motion. A land might be a paid team, a department, a site or an initial workload. Expansion might add seats, another workflow or a complementary product. If an organization is counted by separately billed business unit, several customer records can belong to one corporate parent. The commercial unit must be stable enough to distinguish an existing-account expansion from a newly counted account. Slack’s disclosed Paid Customer required at least three paid users in an organization. [Metric definition](https://www.sec.gov/Archives/edgar/data/1764925/000162828019004786/slacks-1.htm).

Slack’s 2019 S-1 describes a combination of self-service adoption and direct selling. Its disclosure is a useful documented example, with an important limit: it includes acquisition of large customers as well as expansion. The claim that every large deployment began with a small free team would go beyond the passage. [Go-to-market model](https://www.sec.gov/Archives/edgar/data/1764925/000162828019004786/slacks-1.htm).

Three routes, three next decisions

Use the customer’s next task to choose the expansion route. More spend is an outcome, not a task.

More users

Expand a common workflow to another team only when coordination creates value. The new users may need different permissions, training or support; count those needs before multiplying seats.

More workloads

Add a new workload when the customer has a recurring problem the platform can solve. Consumption growth can vary with demand or optimization, so usage should not be treated as a guaranteed minimum.

More capabilities

Sell a complementary capability when it addresses a distinct need and fits the existing work. A bundle can increase billed value without the customer receiving an incremental benefit; check actual use.

A continuum, not a switch

Expansion becomes defensible when the next customer task, buying authority, product readiness and cost are established. Wider adoption is not automatically better than a bounded successful use.

LowUnproven footprintHighUseful, economical expansion

“A successful pilot earns another decision; it does not authorize the rollout.”

Why it matters

The mechanism begins with reduced initial commitment. A limited deployment can allow someone to try a real workflow before seeking a larger budget. The subsequent mechanism is different: evidence must travel from the user to the people who control a wider purchase. A team’s enthusiasm is useful testimony; it is not evidence that access controls, support, migration and total cost are ready for everyone.

Create a stopping rule before expanding a hypothetical pilot. Specify the recurring task, the expected useful behavior, the neighboring workflow and the approval conditions. If the task is not repeated, investigate why. If the team succeeds but the neighbor has different needs, keep the limited deployment rather than treating the expansion target as entitlement. These are proposed operating choices, not an empirical claim that one pilot protocol works in every business.

Separate account growth from customer growth. A threshold count answers how many organizations are above a spending level at a date. Net dollar retention asks what happened to a previously paid cohort’s recurring revenue. Neither answers what it cost to support the expansion. A financially useful rollout still requires service cost, gross margin and payback at the relevant account boundary.

Real-world examples

The same concept shows up in different ways across industries.

SlackAccount scale and cohort growth tell different stories

→

Slack reported 575 paid organizations above $100,000 ARR in January 2019 and 143% net dollar retention. The first is a snapshot; the second compares recurring revenue of a prior paid cohort, excluding new paid customers. Their definitions are the lesson, not a universal expansion benchmark. [Key Business Metrics](https://www.sec.gov/Archives/edgar/data/1764925/000162828019004786/slacks-1.htm). [Read the case](/en/breakdowns/slack-land-expand).

When it breaks

The cleanest counterexample is a product useful to one specialist team with no valuable adjacent workflow. The initial sale can be sound and expansion still be a poor idea. A supplier that adds a generic product merely to increase account value risks distracting the user and paying new implementation cost for little benefit.

Aggregate retention can hide concentrated growth. A few growing accounts can offset contraction and attrition in others. A rate above 100% therefore does not mean all customers are satisfied, all logos remained or the median account grew. In the Slack case, the disclosed retention rate fell while the threshold customer count increased; those measures have different populations and can both be accurate.

A low-friction land can also be expensive. Bespoke onboarding, high support demand or weak follow-through may make the small deployment uneconomic. Slack’s risk disclosure recognizes investment in direct selling and uncertain corresponding revenue. Treat product-led entry and enterprise selling as complementary costs when the wider buying decision needs both.

Key takeaways

01
Specify the initial account boundary, the next use case and the person who can approve it. Preserve the distinction between a user, team and corporate parent.
02
Track the same cohort through expansion, contraction and departure. Show account-count retention alongside recurring-revenue change and delivery cost when those data are available.
03
Stop an expansion that fails to create additional customer value. Use the linked Slack case to distinguish evidence of scale from evidence of a repeatable small-to-large path.

Sources

Slack 2019 S-1: go-to-market model · Slack / SEC. MD&A, Our Go-to-Market Model, Self-service adoption and marketing / Direct sales and marketing, printed pp. 65–66; Business, corresponding headings pp. 104–105
Slack 2019 S-1: key business metrics · Slack / SEC. Key Business Metrics, printed pp. 68–70: January 31, 2017–2019 table; Paid Customers definition; Paid Customers >$100,000 definition; Net Dollar Retention Rate definition
Slack 2019 S-1: investment and conversion risk · Slack / SEC. Risk Factors, “Failure to effectively develop and expand our direct sales capabilities could harm our ability to increase the number of organizations on Slack and achieve broader market acceptance of Slack”, printed p. 27, paragraphs 1–3; Factors Affecting our Performance, Conversion of organizations on our free version to paid customers, printed pp. 66–67; Continued investment for growth, p. 68