Bottoms-up vs top-down GTM
Bottoms-up is not a sales category. It is a buyer behavior: end users adopting a product on their own and pulling it into the organization. If your product cannot be tried in five minutes by an individual user without IT, procurement, or security involvement, you do not have a bottoms-up motion no matter what your pitch deck says. Top-down sells to executives with budget; the playbooks don’t transfer.
What it actually means
Bottoms-up means an end user (a developer, a designer, a salesperson) adopts your product without their employer’s involvement, finds it useful, and over time it spreads through the organization until someone in finance asks “what is this charge on the credit card?” Top-down means you sell to an executive who decides their team will use it, then deploys it through procurement and IT. The two motions look completely different from inside the company building them.
Bottoms-up requires self-serve activation, low friction signup, and value within the first session. The product has to be useful to one person before it is useful to a team. Slack, Figma, Notion, GitHub, and Linear all started this way. The common pattern is a product that solves a real problem for one user, that user invites colleagues, and the company eventually has hundreds of users before anyone in finance gets billed. The time from first user to first dollar is often months or years.
Top-down requires a buyer with budget authority who can make decisions for their organization, a sales motion that engages procurement and security, and a contracting process that handles MSAs and DPAs. Salesforce, Workday, and most enterprise SaaS sell this way. The deal cycle is months to a year, the deal sizes are large, and a single signed contract can be worth more than a year of bottoms-up usage. The cost of acquiring an enterprise customer is high, but so is the per-customer revenue.
The two motions also have different defensibility. Bottoms-up creates organic moats: once a team is on Figma, switching is painful because everyone has files and workflows in it. Top-down creates contractual moats: multi-year deals, integrated workflows, and switching costs that are intentional. Both work, but they fail differently. Bottoms-up companies fail when the product stops being useful to an individual; top-down companies fail when the executive sponsor leaves and the contract is up for review.
The most common confusion is companies claiming bottoms-up when they are actually running a top-down motion with a free trial. A free trial that requires IT to provision, security review to approve, and a sales call to activate is just top-down with a less convenient signup. The test is simple: can a single user, on their own, get value from your product in their first session without anyone else helping? If yes, you have a bottoms-up motion. If no, you do not, and pretending you do will lead you to underinvest in the sales motion you actually need.
How to know if yours is broken
Can a single end user activate your product in five minutes without involving IT, procurement, or security?
If you removed your sales team tomorrow, would new users still find, sign up, and activate the product?
Does the value of your product compound when more users in the same organization adopt it, or stay flat?
When you look at your closed deals, did most of them start with one user trying it, or with an executive deciding for their team?
Common misconceptions
“Bottoms-up is the future and top-down is dead.”
Top-down still moves enormous deals in enterprise. Workday, ServiceNow, and Salesforce are all top-down and still growing. Bottoms-up is the better fit for some products and buyers, not a universal upgrade. Pick the motion that matches your buyer.
“A freemium tier means you have a bottoms-up motion.”
Freemium is a pricing tactic. Bottoms-up is a buyer behavior. You can have freemium without bottoms-up (if the free tier still requires sales contact to upgrade) and bottoms-up without freemium (if the paid product is cheap enough that an end user can expense it without approval).
“Bottoms-up companies don’t need a sales team.”
They eventually do. The pattern is bottoms-up adoption to land in the account, then sales to expand to enterprise contracts once usage crosses a threshold. Companies that refuse to add sales when bottoms-up adoption matures leave significant revenue on the table.
Related concepts
Or browse the full glossary.