Most B2B SaaS companies pick their GTM motion by copying a competitor or following investor advice. The board says "you should do PLG" because Slack did PLG. Or the founder says "we need enterprise sales" because that is what they know. Few actually analyse which motion fits their product, buyer, and market.
That mismatch is expensive. A product that requires onboarding, configuration, and change management does not work well as self-serve. A product with a £30/month price point does not justify a six-month enterprise sales cycle. The motion has to match the product.
Bottom-up and top-down adoption are not just sales strategies. They are fundamentally different operating models. They require different teams, different metrics, different pricing, and different GTM investments. Choosing the wrong one — or trying to run both simultaneously before you have the resources — is one of the most common early-stage GTM mistakes.
This guide helps you understand both models clearly, see which fits your situation, and build the right motion from the start.
What Bottom-Up Adoption Actually Means
Bottom-up adoption means individual users adopt your product before the organisation decides to pay for it. The user discovers the product, gets value from it, and then creates internal demand that eventually converts to a commercial relationship.
This is sometimes called product-led growth (PLG), though the two are not identical. PLG is a broader strategy. Bottom-up adoption is specifically about the direction of the adoption vector: individuals and teams first, organisational buying decision second.
The classic examples are Slack, Notion, Figma, and Dropbox. Users signed up individually. Teams formed. Teams wanted more features. IT noticed the tool in their stack. Finance got an invoice. The buying decision arrived after the value was already proven.
What Makes Bottom-Up Work
Bottom-up adoption requires specific conditions to succeed. If these are not present, the motion will stall.
- The product delivers value in a single session. If a user cannot see the point within minutes of signing up, they will not come back. There is no sales rep to hold their hand.
- The product is better with more users. Collaboration tools, communication tools, and shared workflow tools naturally spread within organisations because value increases with adoption.
- The individual can make the decision to adopt. If the user needs IT approval to install or access the product, bottom-up adoption is blocked at the entry point.
- The price point allows individual or team purchase. Products priced above £500/month are hard to expense without procurement involvement, which slows individual adoption.
What Top-Down Adoption Actually Means
Top-down adoption means an executive or buying committee makes a purchase decision before users engage with the product. The organisation buys first. Users adopt after.
This is the traditional enterprise software model. A CISO decides on a security platform. A CFO approves an ERP implementation. A VP of Sales signs a contract for a sales intelligence tool. Users get access through mandate, not through organic discovery.
The examples here are Salesforce, Workday, SAP, ServiceNow. No individual ever wandered into using these tools. The organisation decided, deployed, and trained users into adoption.
What Makes Top-Down Work
- The product requires organisational change to deliver value. If deploying your product requires process changes, integrations, or data migration, individuals cannot do it alone. You need executive buy-in from day one.
- The buyer and the user are different people. When the person who pays is different from the person who uses, you are already in a top-down motion. Sell to the buyer. Enable the user.
- Your deal size justifies the sales motion cost. A top-down enterprise sales cycle costs real money — sales rep time, solution engineering, legal, procurement. This only makes sense when the contract value supports it.
- The category requires trust before trial. Cybersecurity, finance, and healthcare tools often cannot be trialled without organisational approval. The compliance and risk considerations push the decision to senior stakeholders.
The GTM Implications of Each Motion
The choice between bottom-up and top-down is not just a sales question. It reshapes your entire operating model.
Bottom-Up GTM Requirements
- Product: Frictionless onboarding. Self-service activation. In-product guidance and education. A free tier or trial that delivers genuine value without a sales conversation.
- Marketing: High-volume content and SEO to drive top-of-funnel discovery. Community and word-of-mouth programmes. Developer relations if technical users are the entry point.
- Sales: Product-qualified lead (PQL) scoring to identify accounts worth engaging. Low-touch inbound motion for team-level upgrades. Enterprise sales layer for accounts that have grown organically to deal-ready scale.
- Metrics: Activation rate. Time to first value. Viral coefficient. Free-to-paid conversion rate. Expansion revenue from organic team growth.
Top-Down GTM Requirements
- Product: Admin controls and SSO from day one. Compliance certifications (SOC 2, ISO 27001). Customisation and configurability that individual tools do not need.
- Marketing: Demand generation targeting specific titles (VP, Director, C-suite). Account-based marketing programmes for named accounts. Analyst and industry relations to build credibility with risk-averse buyers.
- Sales: Outbound development reps (BDRs) targeting specific accounts. Solution engineers for technical validation. Procurement and legal process management. Multi-threaded account selling across the buying committee.
- Metrics: Pipeline coverage. Average contract value. Sales cycle length. Win rate by segment. Net revenue retention from expansion.
When the Two Motions Coexist
Most mature SaaS companies run both motions — bottom-up for acquisition, top-down for expansion. But they usually get to this by starting with one and adding the other when the business reaches sufficient scale.
The typical pattern for a PLG company moving upmarket: individual users adopt the product. Usage clusters in certain accounts. A product-qualified account (PQA) threshold triggers sales outreach. An account executive comes in to convert organic usage into a formal enterprise contract. Customer success expands the footprint across the organisation.
The mistake is trying to run both motions simultaneously from day one without the resources to do either well. A ten-person startup cannot maintain a world-class self-serve product while also running a mature enterprise sales motion. Pick your primary motion for the first two years.
Scenario: Choosing the Wrong Motion
A compliance workflow SaaS launched with a self-serve freemium model because the founders admired Notion and wanted similar organic growth. The product required IT deployment, data migration from existing systems, and training for compliance teams. Average deal size was £18,000/year.
Twelve months in: 900 free signups, 11 paid conversions, average revenue per converted customer £4,200 (all small teams, not the enterprise buyers the product was built for). The funnel looked busy. The revenue was not.
The product required top-down adoption. The compliance team could not sign up individually — they needed IT approval. The buying committee was a VP of Compliance and a CIO. Neither was going to discover the product through a free tier. They needed outbound, demos, and enterprise sales.
Switching to an outbound enterprise motion six months later generated three deals in the first quarter worth £62,000 combined. The free tier was retained for SMB but stopped being the primary acquisition channel.
The Decision Framework
Which Motion Is Right for You? Five Questions
- Who decides to adopt? If individuals can decide without IT or procurement, bottom-up is viable. If organisational sign-off is required, you are in a top-down motion whether you intended it or not.
- How long does it take to see value? Under 10 minutes — bottom-up. More than a week of configuration — top-down.
- What is your average contract value? Under £3,000/year — bottom-up economics work. Above £15,000/year — top-down sales motion is justified. Between £3,000 and £15,000 — evaluate both.
- Does value increase with organisational scale? Yes — bottom-up has natural viral mechanics. No — you need to drive adoption through sales, not product.
- What does your product require at the point of deployment? Configuration, data migration, or change management — top-down. Sign up and go — bottom-up.
Common Mistakes When Choosing Your GTM Motion
- Assuming PLG is right because it worked for Slack. Slack is a horizontal communication tool used by every function. Your compliance workflow tool is not. The motion that works depends on your product, not someone else's.
- Building a free tier without a conversion path. Bottom-up only works if free users convert to paying. If your product requires sales to convert enterprise accounts, the free tier is a cost centre without a conversion engine.
- Running enterprise sales at self-serve price points. A six-month sales cycle does not make economic sense for a £1,200/year contract. Either raise the price or change the motion.
- Ignoring your current data. Look at where your revenue is actually coming from. If 80% of your customers came through inbound self-serve and 80% of your revenue came from three enterprise deals, that tells you something about where to invest.
- Trying to switch motions mid-cycle. Changing from PLG to enterprise sales or vice versa is expensive. Build the right motion early. If you need to switch, do it deliberately with a clear transition plan.
Implementation Checklist
- Answer the five decision framework questions honestly. Write down your answers.
- Look at your current customer acquisition data: where are customers coming from, and what are they worth?
- Identify your primary motion: bottom-up, top-down, or hybrid (only choose hybrid if you have resources for both).
- If bottom-up: audit your onboarding. Can a user get to value without help in under 15 minutes?
- If top-down: identify your ICP title and build your outbound targeting list.
- Set one primary metric for your chosen motion: activation rate (bottom-up) or pipeline generated (top-down).
- Identify the first point at which you will consider adding the secondary motion.
- Review in 90 days: is the motion generating revenue, or just activity?
The best GTM motion is the one that fits your product and your buyer. Not the one your investor recommends. Not the one your competitor uses. The one that generates revenue with the resources you actually have.
Execution Rhythm and Review Cadence
A strong framework on paper does not create pipeline or revenue on its own. The teams that get value from bottom-up vs top-down adoption treat it as an operating system, not a one-off workshop. Set a fixed monthly rhythm with PMM, product growth and sales. Keep the meeting to forty-five minutes. Start with what changed in the market, then what changed in buyer behaviour, then what changed in your own performance. If nothing changed, keep the current plan and spend your time on execution. If something shifted, update only the part that moved instead of rewriting the whole framework.
Use a simple scorecard with three columns: still true, partly true, no longer true. This keeps the discussion practical and stops the team from drifting into theory. For B2B SaaS PMMs, this is critical because teams often run multiple motions at once. You might have self-serve trials, mid-market sales cycles, and partner influence in the same quarter. Your framework needs to reflect that complexity without becoming unreadable.
What to review every month
- Message and proof fit: Which value statements are landing in calls, demos, and onboarding conversations, and which are being ignored.
- Segment behaviour: Whether your target accounts are buying in the same way, at the same speed, and with the same decision group as last month.
- Friction points: The top objections, process blockers, and handoff failures that slowed deals or delayed adoption.
- Asset performance: Which enablement assets were used by sales or buyers, and which assets are dead weight.
- Next actions: Three owners, three deadlines, and one clear outcome per action. No owner means no action.
This cadence also protects PMM focus. Without it, PMMs get pulled into reactive requests and lose strategic control. With it, every request is filtered through current priorities and expected business impact.
Practical Implementation Plan for the Next 90 Days
If you want this framework to matter, run it as a ninety-day implementation sprint. The goal is not perfection. The goal is to make your decision quality better each week.
Weeks 1-2: baseline and alignment
Run five interviews with internal stakeholders and five with customers or prospects. Pull real call clips, sales notes, and onboarding feedback into one document. Confirm where opinions differ. Most teams discover that their biggest issue is not missing content. It is inconsistent interpretation of the same buyer signals.
Weeks 3-6: field test in live motions
Choose one segment and one core use case. Train the frontline teams quickly, then test the updated approach in live deals and customer conversations. Ask reps and CSMs to flag where the framework helped and where it created confusion. Keep changes small and frequent. A weekly adjustment cycle is better than a quarterly rewrite.
Weeks 7-10: scale what worked
Package the winning patterns into practical artefacts: one-page briefs, short call guides, and reusable narrative snippets for email, decks, and pages. Avoid huge slide decks. Teams use what is fast to find and easy to adapt. If an asset takes ten minutes to locate, it is not an asset. It is an archive item.
Weeks 11-12: lock the operating model
Finish the quarter with a retro. Document what drove results and what failed. Update your source of truth and archive outdated material. For bottom-up vs top-down adoption, consistency compounds. Small, disciplined updates beat dramatic rebrands every time.
Common failure pattern to avoid
The biggest failure mode is predictable: ignoring admin workflows, no expansion path, mismatched onboarding. You can prevent this by setting clear ownership, reviewing evidence monthly, and refusing to ship major changes without customer or field validation. PMM quality is mostly cadence quality.
How to Keep This Useful as the Business Scales
As soon as the company adds new segments, geographies, or packaging tiers, this work can drift. The fix is simple. Protect one source of truth, assign one owner, and schedule one recurring quality check. If multiple teams create their own versions, confidence drops and execution slows. For PMMs, governance is not bureaucracy. It is how you keep speed without losing consistency.
Create a lightweight governance note with three parts: what changed, why it changed, and where teams should apply it first. Share it in Slack, pin it, and link it inside onboarding material for new hires. This prevents old documents from resurfacing and keeps frontline teams from using stale language in customer conversations.
Quarterly quality checks
- Review the ten most recent opportunities and tag where the framework improved decision quality.
- Audit five customer-facing assets for message consistency and practical usefulness.
- Collect feedback from sales, CS, and product on what is clear, unclear, and missing.
- Retire outdated artefacts so teams are not choosing between old and new guidance.
Most importantly, keep the standard high on evidence. When you update content, include examples from real calls, onboarding moments, or implementation projects. Practical evidence builds trust faster than polished prose. That trust is what turns PMM frameworks into everyday operating behaviour.