Bottom-up adoption
BOT-um up uh-DOP-shun
A growth pattern where individual practitioners adopt a product first, and organizational purchasing follows after usage spreads.
Bottom-up adoption is when individual users adopt a product before the company makes a formal purchasing decision. A developer tries a tool on a side project. They bring it to their team. The team brings it to other teams. Eventually the company buys an enterprise license.
This is the growth pattern that defines developer tools. Developers do not wait for procurement to approve a tool. They sign up, try it, and adopt it if it works. By the time the company is ready to buy, the product is already embedded in the workflow. This is the foundation of product-led growth.
Bottom-up adoption requires a product that individuals can start using without IT approval: free tiers, self-serve signup, no mandatory SSO, and quick time to value. The product must prove itself to the individual user before the organization gets involved.
Examples
A developer adopts a database on a personal project.
The developer uses Supabase for a side project. They like it. When their team starts a new service at work, they suggest Supabase. The team adopts it. After three teams are using it, the VP of Engineering signs an enterprise agreement.
Slack spreads through an organization bottom-up.
One team starts using Slack's free tier for internal communication. Other teams notice and create their own workspaces. Within months, half the company is on Slack. IT consolidates everyone into one paid workspace.
A company detects bottom-up adoption signals.
The growth team monitors signup domains. They notice 15 users from the same company signing up individually over two months. A sales rep reaches out to the company's engineering lead to discuss an enterprise plan.
In practice
Read more on the blog
Frequently asked questions
How do you convert bottom-up adoption into enterprise revenue?
Monitor usage signals (multiple users from the same company, high usage volumes, team invitations). When signals are strong, have a sales rep reach out to discuss enterprise features (SSO, admin controls, compliance) that the organization needs.
What products are best suited for bottom-up adoption?
Products that individual practitioners can sign up for and use immediately without IT approval. Developer tools, design tools, project management tools, and communication tools all lend themselves to bottom-up adoption.
Related terms
A sales approach that targets executive decision-makers first, who then mandate adoption across the organization.
A go-to-market strategy where the product itself drives acquisition, conversion, and expansion through self-serve usage.
A sales strategy where you start with a small deal or team and grow revenue within the account over time through expansion.
A go-to-market strategy that targets developers as the primary audience, relying on them to adopt and champion the product within organizations.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.