The GTM Engineer's Guide to Bottom-Up GTM

Overview

Bottom-up GTM flips the traditional sales model on its head. Instead of convincing a VP to buy your product and then pushing it down to their team, you get individual users to adopt it first -- and then let usage, value, and internal advocacy pull the deal upward through the organization. Slack did not start by pitching CIOs. Figma did not start by selling to heads of design. They started with individual contributors who loved the product, told their teammates, and eventually made the tool impossible to remove.

For GTM Engineers, bottom-up is both exhilarating and terrifying. The good news: your product does much of the selling. The bad news: the infrastructure required to detect, nurture, and convert bottom-up adoption is fundamentally different from top-down sales infrastructure. You are not tracking deals in a pipeline -- you are tracking usage patterns, team-level expansion signals, and the moment an organic user becomes an enterprise buyer.

This guide covers how bottom-up GTM actually works end-to-end: from individual user acquisition through team adoption, usage tracking infrastructure, expansion signal detection, and the viral loops that make the whole thing compound. Whether you are building a product-led growth motion or layering bottom-up adoption onto an existing sales motion, this is the operational playbook.

The Anatomy of Bottom-Up Adoption

Bottom-up GTM follows a predictable pattern, even though it rarely feels predictable while you are living it. Understanding the stages helps you build infrastructure that supports each transition point rather than hoping users figure it out themselves.

Stage 1: Individual User Acquisition

The first user at a company finds your product through organic search, a community recommendation, a colleague's referral, or developer documentation. They sign up for a free tier or trial. At this point, you know almost nothing about them -- maybe an email address and a company domain. Your job is to reduce time-to-value to minutes, not days.

This stage is all about product experience. Your speed-to-value metrics matter more than your sales response times. The user does not want a demo -- they want to solve a problem. Onboarding flows, in-app guidance, and templates that show immediate value are your GTM infrastructure here.

Stage 2: Habit Formation

The individual user starts using your product regularly. They integrate it into their daily workflow. This is where most bottom-up funnels leak. Acquisition is easy; retention is the hard part. Your GTM Engineering focus at this stage is building usage tracking infrastructure that identifies which users are forming habits and which are drifting away.

Key metrics to instrument: daily active usage, feature depth (how many features they use, not just login frequency), integration connections (did they connect their CRM, their Slack, their data warehouse?), and content creation (are they building things in your product that would be painful to migrate?).

Stage 3: Team Adoption

The individual user invites a colleague. Or shares a link. Or presents something built in your tool during a team meeting. This is the viral moment -- the point where one user becomes a team of users. Your infrastructure needs to detect this transition and respond to it differently than individual signups.

Stage 4: Enterprise Conversion

Multiple teams are using your product. The IT or procurement team notices. Someone asks about SSO, admin controls, or a volume discount. The bottom-up motion has generated enough internal demand that a top-down purchase becomes inevitable. This is where your sales-led motion layers in -- but you are selling to a buyer who already has internal champions and proven value.

The Bottom-Up Advantage in Enterprise Sales

Deals sourced through bottom-up adoption close 40-60% faster than pure top-down deals because the "why" question is already answered. Users have already proven the value. The sales conversation shifts from "should we buy this?" to "how do we buy this at scale?" -- a fundamentally easier conversation.

Building Usage Tracking Infrastructure

If your GTM stack for top-down sales is built on CRM data, your stack for bottom-up GTM is built on product usage data. This is the single biggest infrastructure investment a bottom-up company makes, and getting it right determines whether you can operationalize expansion or just hope it happens.

What to Track

Not all product usage signals are created equal. You need to distinguish between vanity metrics (logins, page views) and value signals (actions that correlate with conversion and retention).

Signal Category	Examples	Why It Matters
Activation signals	Completed onboarding, created first project, connected integration	Predicts whether a user will retain
Depth signals	Used 3+ features, built a workflow, set up automations	Indicates product stickiness and switching cost
Collaboration signals	Invited a teammate, shared a resource, commented on shared content	Predicts team-level expansion
Volume signals	Number of records processed, API calls made, storage consumed	Indicates approaching plan limits and upgrade potential
Enterprise readiness signals	Asked about SSO, requested admin dashboard, inquired about SLAs	Signals transition from user-level to org-level purchase

The Product-to-CRM Data Pipeline

The technical challenge is getting product usage data into your GTM systems in a form that sales and marketing can act on. Most bottom-up companies struggle here because product data lives in a data warehouse (Snowflake, BigQuery) while GTM data lives in the CRM (Salesforce, HubSpot). Bridging this gap is core GTM Engineering work.

Define your Product Qualified Lead (PQL) criteria. A PQL is a user or account that has hit usage thresholds indicating they are ready for a sales conversation. This should be based on patterns you have observed in users who convert, not arbitrary thresholds. Analyze your best customers' usage patterns in the 30 days before they converted.

Build the data pipeline. Extract usage events from your product database, transform them into account-level summaries, and load them into your CRM or a reverse ETL tool. Key fields: account usage score, last active date, team size, feature adoption breadth, and collaboration activity.

Set up PQL-triggered workflows. When an account crosses your PQL threshold, automatically enroll them in the appropriate sales motion. This might be a product-qualified outreach sequence, an in-app upgrade prompt, or a notification to an account executive -- depending on the account's size and signals.

Close the feedback loop. Track which PQLs convert, at what rate, and with what deal size. Use this data to refine your PQL criteria quarterly. The model should get better over time as you accumulate more conversion data.

Expansion Signal Detection and Viral Loops

The magic of bottom-up GTM is that growth compounds. One user becomes a team, one team becomes a department, one department becomes an enterprise deal. But this compounding only happens if you build the right infrastructure to detect and accelerate it.

Detecting Expansion Signals

Expansion signals are behavioral patterns that predict an account is about to grow. They are different from engagement signals (which predict retention) and enterprise signals (which predict a purchase conversation). Getting these categories right matters because each triggers a different response sequence.

Signal Type	What to Watch	Appropriate Response
Seat expansion	User invites sent, team members added, workspace creation	In-app team plan messaging, automated upsell prompts
Use-case expansion	New features adopted, new integrations connected, new workflows created	Product education content, use-case expansion sequences
Cross-department	New email domains within same company, different team workspaces	Account executive notification, enterprise pitch preparation
Champion movement	Power user changes company, invites from new company domain	Land-and-expand playbook at new company

Engineering Viral Loops

Viral loops are product mechanics that naturally create new users as a byproduct of existing users getting value. They are not gimmicks or referral programs -- they are structural features of the product that make sharing the default behavior.

There are three types of viral loops that matter for B2B bottom-up GTM:

Collaboration loops: Using the product requires inviting others. Google Docs, Figma, and Notion all have this -- the product is better (or only works) when shared. Every invited collaborator is a potential new user.
Output loops: The product creates artifacts that are visible to non-users. Calendly links, Loom videos, and Typeform surveys all expose the brand to prospects' contacts. Every output is an acquisition channel.
Integration loops: Connecting your product to other tools in the stack creates visibility and dependency. When your product sends data to Slack, updates the CRM, or posts to a dashboard, it becomes part of the team's workflow infrastructure.

Measuring Viral Coefficient

Your viral coefficient (K-factor) is the average number of new users each existing user brings in. K > 1 means organic growth without spending on acquisition. Most B2B tools have K between 0.3 and 0.8 -- enough to significantly reduce CAC but not enough to grow purely through virality. Track K by cohort and by feature to understand which product triggers drive the most referrals.

Common Mistakes in Bottom-Up GTM

The most frequent failure mode is what I call "premature monetization" -- trying to layer sales onto a bottom-up motion before users have formed habits and generated internal advocacy. If you start sending outbound sequences to every free user who signs up, you will kill the organic adoption that makes bottom-up work.

Other common mistakes include:

Gating essential features too aggressively: If the free tier is not genuinely useful, users will not form the habits that drive expansion. The free tier should be good enough that users become dependent on your product, creating natural upgrade pressure when they hit limits.
Ignoring the team-to-enterprise gap: Many companies build great individual user experiences and great enterprise sales motions but neglect the middle -- the team-level experience where 5-20 users need collaboration features, light admin controls, and a way to consolidate billing.
Not instrumenting early enough: If you do not have product usage tracking from day one, you will miss the behavioral patterns that distinguish users who convert from those who churn. Retroactive instrumentation always has gaps.

FAQ

How do we know when to layer sales onto a bottom-up motion?

Look for three signals: (1) accounts with 5+ active users organically, (2) usage patterns that match your enterprise customer profile, and (3) enterprise-readiness signals like SSO inquiries or admin feature requests. When you see these consistently, it is time to build a PQL-driven sales motion -- but it should feel like a concierge service for users who already love your product, not a cold outbound campaign.

What is the right free-to-paid conversion rate for bottom-up?

Benchmarks vary wildly by category, but most successful bottom-up B2B companies see 2-5% of free users converting to paid individually, with the real revenue coming from enterprise conversions that account for 60-80% of total ARR. The free tier is an acquisition and habit-formation channel, not a primary revenue driver. Optimize the free tier for adoption breadth and the paid tier for organizational value.

How do we attribute revenue in a bottom-up model?

Traditional first-touch and last-touch attribution breaks in bottom-up GTM because the "marketing" that sold the deal was the product itself. Build attribution models that credit product usage alongside marketing touches. Track the chain from first user signup to team adoption to enterprise deal, and assign value to each stage. Your qualification system should reflect this multi-stage reality.

Can bottom-up work for complex enterprise products?

Yes, but the "bottom" is different. For developer tools, bottom-up starts with individual engineers. For analytics platforms, it might start with a data analyst who uses the free tier for a personal project. For security tools, it could start with a single team running a pilot. The key is finding the smallest unit of value your product can deliver without requiring an org-wide deployment, then building expansion paths from there.

How does bottom-up GTM interact with outbound?

The best bottom-up companies use outbound to accelerate organic adoption, not replace it. Identify accounts with existing free users and target other stakeholders in the same org with messaging that references internal usage: "Three people on your team are already using [Product]. Here is how teams like yours are getting even more value." This is dramatically more effective than cold outbound because you have built-in social proof. Your multi-channel outreach should reference product activity.

What Changes at Scale

At 1,000 free users and 50 paying accounts, you can manually identify expansion opportunities and trigger sales conversations with a Slack notification and a spreadsheet. At 50,000 free users across 3,000 companies with 200 paying accounts and a dozen expansion plays running simultaneously, everything breaks. The product usage data is too noisy to parse manually. The expansion signals are too numerous to track in a CRM. And the gap between "this account looks ready" and "a rep actually reached out with the right message" grows wider every week.

What you need is a system that continuously synthesizes product usage signals, account-level context, and engagement history into a unified view that your sales and marketing motions can act on automatically. You need PQL scoring that updates in real time, expansion signal detection that triggers the right playbook without human intervention, and messaging that adapts to where each account sits in the bottom-up adoption curve.

Octave is built to power exactly this kind of expansion motion. The Qualify Company Agent scores accounts against your products using configurable qualifying questions, assessing expansion fit with a confidence score and reasoning. The Prospector Agent finds the right stakeholders at expanding accounts — configurable by job title, location, and LinkedIn presence — in both single-company and lookalike modes. The Enrich Person Agent returns each contact's role, expertise, and career arc with persona fit and value prop resonance scores. And the Sequence Agent generates personalized expansion sequences using Playbooks that draw from the Library's products, use cases, and reference customers auto-matched to the prospect. For teams running bottom-up motions at scale, Octave replaces the manual PQL-to-outreach scramble with an automated expansion pipeline that qualifies, prospects, enriches, and messages in one system.

Conclusion

Bottom-up GTM is not a cheaper alternative to hiring salespeople. It is a fundamentally different growth architecture that requires its own infrastructure, its own metrics, and its own operational playbook. The product does the selling, but the GTM Engineer builds the systems that detect when selling has happened, identify who is ready for more, and orchestrate the transition from individual user to enterprise customer.

The companies that win at bottom-up GTM invest early in usage tracking, build clear PQL models, engineer viral loops into their product, and resist the temptation to monetize too early. They treat their free tier as a growth engine, not a cost center. And when they layer sales on top, they use product usage data to make every sales conversation feel like a natural next step rather than a cold pitch. Start by instrumenting your product, define your PQL criteria, and build the pipeline that connects usage signals to the right sales motion. The users are already telling you what they need -- your job is to build the infrastructure that listens.