Notion, Figma, and Slack all started with individual users signing up for free. They all ended up with Fortune 500 enterprise contracts worth hundreds of thousands of dollars per year. The path from one to the other is not accidental — it is a structured expansion motion that starts with individual adoption, builds through team-level value, and culminates in organizational commitment. This article explains the three phases of the bottom-up enterprise expansion model and what you need to run it.
Why freemium is an enterprise strategy, not just a pricing model
The conventional view of freemium is that it is a conversion tactic: give users enough value for free that they eventually pay for more. That framing misses the more powerful dynamic: freemium is an enterprise infiltration strategy.
When an individual employee starts using a freemium tool without organizational permission or IT involvement, they are doing something that a traditional sales team could not easily accomplish: getting the product inside the corporate firewall, demonstrating value at the individual level, and creating an internal advocate who already understands why the product is useful. The subsequent enterprise conversation does not start from zero — it starts from a position of proven value with an engaged internal champion.
Notion, Figma, and Slack all used this mechanism. The individual user was not a consumer customer who happened to use a business tool — they were the first foothold in what would eventually become a six-figure enterprise account. Understanding this reframes freemium from a cost center that must convert to an enterprise investment that must infiltrate.
Phase 1: Individual adoption and activation
The first phase begins at signup. An individual employee — a designer, a developer, a product manager, an operations lead — discovers the product, signs up with their work email, and starts using it.
The critical success factor in this phase is time-to-value. The faster the individual user reaches the activation moment — the point where they understand why the product is genuinely useful — the more likely they are to return, continue using the product, and eventually bring it to their colleagues.
What activation looks like in practice
For Notion, activation is the moment a user creates their first linked database or builds their first interconnected workspace — when they understand that Notion is not just another note-taking app, it is a programmable knowledge base. For Figma, it is the first real-time collaboration session — when the user sees another cursor moving on their canvas and understands that design collaboration has fundamentally changed. For Slack, it is the first time a team member responds to a message in a channel — when the user understands that asynchronous team communication is better than email.
Each of these activation moments is specific, measurable, and achievable in the first session for a motivated user. The product team's job is to identify the equivalent moment in your product and remove every obstacle between signup and that moment.
Identifying individual champions early
Not all free users are equally valuable as future enterprise champions. The users who are most likely to drive organizational adoption share several characteristics: they are in a role where they influence tool decisions (often senior individual contributors or team leads, not junior employees), they use the product frequently and deeply rather than sporadically, and they are at a company with the size and structure where a paid team or enterprise tier makes financial sense.
The signals to track: email domain company size (resolves to a larger organization), activation milestone completion, login frequency in the first 30 days, and role signals in the account name or job title. These are the users who warrant proactive outreach from a sales or expansion team.
Phase 2: Team-level expansion
Individual adoption becomes team expansion when the champion invites their first colleague. This is the inflection point in the bottom-up enterprise motion — the moment the product starts creating network effects within the target organization.
The invitation mechanics
Figma's invitation mechanic is embedded in the core workflow: you share a design file, the recipient sees it, and they sign up because they need to comment or collaborate. The invitation is not a feature — it is a necessary byproduct of using the product properly. Notion's mechanic is similar: you share a page with a teammate, the teammate reads it, and they sign up to comment or edit. Slack invites are even more natural: you cannot have a team conversation without inviting your team.
Not every product has this natural invitation mechanic. If your product is inherently single-player, you need to create deliberate expansion triggers: in-app prompts to invite collaborators, shared report features, or team workspace functionality that only becomes available when a second user joins. The goal is the same: create a structural reason for the first user to bring others in.
Account-level signals during team expansion
When multiple users from the same company email domain are in the product, the account-level picture becomes visible. You can now see:
- How many users from the same organization are active
- Whether they are in the same workspace or in separate silos
- Which features they are using and which they are hitting limits on
- Whether the usage is growing (new invites, new active users) or plateauing
A company with 8 active users across 3 departments, with 2 of them having hit the free-tier workspace limit in the past 30 days, is a materially different opportunity than a company with 8 isolated users each on their own personal workspace. Both show up as "8 users from company X" in a basic report — only account-level analysis reveals the organizational depth.
Phase 3: Organizational commitment and enterprise contract
The transition from team adoption to organizational commitment requires explicit sales involvement. This is where the bottom-up motion connects with the top-down enterprise sales motion that eventually closes the deal.
Enterprise features as the natural upgrade trigger
Enterprise features are not just product capabilities — they are upgrade triggers that create natural commercial conversations. SSO (Single Sign-On) is the most reliable: when a company's IT team wants to manage user access through their existing identity provider (Okta, Azure AD, Google Workspace), they need the enterprise tier. SCIM provisioning, audit logs, custom data retention policies, and advanced admin controls serve the same function.
When a user — especially an IT administrator or security officer — tries to configure SSO or access audit logs in the free tier and hits a paywall, the commercial conversation is already justified from their perspective. They need this capability. The question is only about price and procurement process.
The champion identification and activation playbook
The organizational champion is not always the person who first adopted the product. In many enterprise expansions, the pattern is: individual contributor adopts → team adopts → manager sees value → manager advocates to IT or finance for a paid rollout. The champion in the enterprise deal is often the manager or department head, not the original user.
Your CRM and product data need to track not just individual users, but account-level relationships: who invited whom, which workspace or team is the organizational center of gravity, and which user in the account has the most organizational reach and seniority. That person is your champion for the enterprise conversation.
Expansion MRR as a growth metric
Once the enterprise motion is running, expansion MRR becomes a leading indicator of PLG health. Expansion MRR is the revenue added from existing customers — through additional seats, additional teams, plan upgrades, or adjacent product purchases. For well-functioning PLG companies, expansion MRR often equals or exceeds new customer MRR, creating a compounding revenue dynamic where the existing base grows faster than churn removes it.
A Net Revenue Retention (NRR) above 120% means that even if you stopped acquiring new customers entirely, revenue would grow 20% per year from expansion alone. This is the financial signature of a healthy PLG motion — and it is built through the systematic conversion of freemium teams into enterprise customers.
What you need to run this expansion model
Running the bottom-up enterprise motion requires four operational capabilities:
- Account-level visibility: The ability to see all users from the same organization in aggregate, not just as individual contacts. This requires domain-level grouping in your CRM.
- Champion identification signals: Signals that identify which users in a multi-user account have the organizational role and engagement level to drive an enterprise conversation.
- Enterprise feature triggers: Automated workflows that fire when an account hits enterprise-relevant behaviors — SSO attempts, paywall hits, high seat counts, admin feature access.
- Sales handoff infrastructure: A structured way to give account executives the full product context — usage depth, activation status, feature behavior, team composition — at the moment they start an enterprise conversation.
For how to build this infrastructure in HubSpot, see the article on product data in HubSpot. For the full expansion motion within a RevOps architecture, the article on RevOps for PLG companies covers the operational layer in detail.