Look at your customer base. You probably have both segments.
You have users who signed up for the free tier last Tuesday, hit the product alone, and either activated in twenty minutes or never came back. You also have accounts that signed a contract last quarter, ran a kickoff call, and have a CSM tracking adoption across six seats.
Your onboarding playbook was built for one of these segments. The other one is leaking activation. You probably know which one.
One Playbook, Two Customer Segments — You Have an Activation Leak
Most B2B SaaS companies above $5M ARR are running both a PLG motion and a sales-led motion at the same time. The product is the same. The buyers are different. Salesmotion's 2026 GTM analysis lays out the threshold cleanly: PLG works for ACV under $10K, sales-led for ACV above $25K, and almost every B2B SaaS company falls into the hybrid middle.
The problem is most teams built one onboarding playbook for both segments. Two motions, one playbook. The result is structural failure on both sides.
If your playbook was built for sales-led, your PLG users see kickoff calls, schedule-based emails, and feature checklists when they wanted to test the product alone in twenty minutes. Activation rate stalls in the 25–35% range. Top PLG companies hit 40–60%, with best-in-class above 70%. The gap is the cost of the wrong playbook.
If your playbook was built for PLG, your sales-led customers get interactive tours and in-product nudges when their actual problem is multi-stakeholder rollout across an admin, end-users, and an executive sponsor. The contract gets signed, the admin sets up, and at week three the end-users go quiet because nobody designed the part of onboarding that gets them to first value inside a contracted account. The renewal happens at month twelve and the answer is "we didn't see the value."
Both teams blame execution. Both add more onboarding tactics. Neither notices the playbook was built for one motion and is being asked to handle both.
The Two Segments Have Two Different Activation Paths
The cleanest way to think about this: PLG and sales-led aren't different sales processes. They're different definitions of what activation means — and that produces two completely different paths to get there. One asks "did this user get value yet?" The other asks "can this account adopt and expand?" Different questions, different paths.
The PLG path is short, solo, and self-driven. A user lands on the signup page with a problem they're already trying to solve. They create an account. They land in the empty product. They hit one or two early actions that show them what the product can do. They reach an activation event — something concrete that signals first value, like sending the first 2,000 messages in a chat tool, creating and sharing a project in a project management tool, logging the first deal in a CRM. They come back the next day. The whole path runs in minutes to hours, with no human involvement, and either lands or doesn't in the first session.
The sales-led path is long, multi-stakeholder, and structured. A contract gets signed. The admin lands in the product first and runs setup — integrations, permissions, role assignments. The CSM runs a kickoff call to align on outcomes and milestones. End-users get invited and start hitting their role-specific first wins inside the account. The executive sponsor sees the first piece of evidence the contract was the right call — usually an outcome metric, not a feature usage count. The path runs over weeks, sometimes months, with structured CSM touchpoints and product checkpoints along the way. The signal that activation happened isn't one user-level event; it's an account-level pattern that some teams call a Product-Qualified Account: more than three active users including the admin, at least one integration connected, repeat sessions across two different roles within the last fourteen days.
One path is short and binary. The other is long and multi-dimensional. The same five tactics will not move both.
Onboarding · Grow Scalably
Two customer segments.
Two activation paths.
One onboarding playbook can't answer both.
Most B2B SaaS companies above $5M ARR run both PLG and sales-led motions. The product is the same. The buyers are different. Most teams build one onboarding playbook across both — and leak activation on both ends.
The argument: PLG and sales-led aren't different sales processes. They're different definitions of what activation means — and the same five tactics will not move both.
Stage 01
Intent
Why they showed up
Exploratory, bottom-up
User has a job to do. Tries the product alone to see if it solves it.
Defined, top-down
Buying committee evaluates against requirements. Use case is documented.
Stage 02
Complexity
What they have to learn
Low to moderate
Single workflow. Self-evident UI. Activation is one good session.
High
Multi-team rollout. Integrations, permissions, reporting. Adoption takes weeks.
Stage 03
Risk
What's at stake if it fails
Low
User abandons the trial. No contract, no committed budget, no fallout.
High
Six-figure contract, executive sponsor on the line. Reputation damage on churn.
Stage 04
Decision
Where the structural difference is
One user, alone
No champion, no buying committee. The user is the decision.
Multi-stakeholder
Admin, end-users, executive sponsor — three roles, three first-value events.
Stage 05
Time horizon
Window to deliver value
Minutes to hours
If the user doesn't see value in the first session, they don't come back.
Weeks to months
Account-level outcome over a quarter. Renewal sets the actual deadline.
Where to start
Pull activation rates by ACV tier.
Compare self-serve under $10K to contracted above $25K.
If the gap is more than 2x, you have two playbooks running as one.
2x
activation gap between
segments is the signal
Two Playbooks, One Shared Data Bridge
The fix isn't picking one motion. The fix is running two onboarding playbooks and connecting them with a shared data bridge that signals when a user crosses from one motion to the other.
Playbook one: PLG onboarding for self-serve users. Optimized for user-level activation in minutes. The user lands, hits an activation event from cohort data, sees value in their first session, comes back the next day. No human required. The metric is activation rate by signup cohort, target 40–60%. The signals tracked are user-level: time-to-first-value, days-to-second-session, feature usage breadth in week one.
Playbook two: sales-led onboarding for contracted accounts. Optimized for account-level adoption across roles. The contract signs, the admin sets up, the end-users hit their role-level activation events, the executive sponsor sees the first piece of evidence the contract was the right call. The metric is end-user activation rate by account, plus adoption breadth ratio. The signals tracked are account-level: percentage of seats active, role-level activation by week, executive sponsor engagement.
The shared data bridge. This is the part most companies skip. The same product usage data feeds both playbooks. When a PLG user hits a PQA threshold — multiple users from the same domain, integration connected, breadth of usage — they get handed off to the sales-led playbook. Not "added to a CRM." Handed off, with the activation context preserved. The CSM picks up an account that already activated at the user level and now needs help activating at the account level. The handoff is the trough most expansion ARR falls into — the user crosses motions but the activation context disappears, and the CSM starts the relationship from scratch on an account that was already most of the way there. The shared data bridge is what keeps it clean.
Three pieces. Two playbooks plus the bridge. The piece almost everyone gets wrong is treating the bridge as a CRM problem when it's a data problem first and a process problem second.
What Goes Wrong When One Playbook Runs Both Motions
Across the customer operations teams I've worked with, the same five patterns show up when one playbook is being asked to do both jobs.
The PLG users get sales-led-shaped onboarding. They land, see a kickoff call invitation in their inbox, and bounce. The user came in to test the product alone. They didn't want a relationship. The kickoff call mechanism — appropriate for a $50K contracted account — is friction for a $99/month self-serve user. Activation rate collapses below 30%.
The sales-led accounts get PLG-shaped onboarding. The contract signs, the admin lands in the product, and gets the same in-product tour the self-serve users get. Nothing addresses the multi-role rollout. Nobody designs the path for end-users inside the account. By week three, the end-users have stopped logging in and the dashboard still says green because the admin is active.
Activation gets defined once for the whole company. The team picks a single activation event — usually something the admin does, because it's easy to track. PLG users hit the admin event because they're solo, but it doesn't predict their retention. Sales-led accounts hit the admin event but their end-users don't, so the metric falsely says the account is healthy.
The PQL-to-PQA handoff doesn't exist. The PLG user from a 200-person company hits the activation event. Three colleagues sign up the same week. Nobody flags it. By the time anyone notices, they've either signed up paid as individual users (capping ACV at $99/month/seat instead of a $40K team plan) or churned out because nobody helped them go team-wide. Self-serve to sales-assisted is where most expansion ARR leaks.
The CS team's incentives are tied to the wrong layer. CSMs get rewarded for closing kickoff calls and admin-side completions. Neither predicts whether the end-users inside the account got value. When sales gets paid for closing any deal and CS gets paid for any kickoff completion, neither team owns the outcome that actually matters. The metric the company should be tracking — end-user activation rate — has no owner.
None of these are team failures. Each one is a structural choice that made sense when there was only one motion and didn't get revisited when the second motion arrived.
What Each Playbook Has To Solve For
The PLG onboarding playbook has to win one user, alone, in minutes. The sales-led onboarding playbook has to win an account, across roles, over weeks. The mechanics are different by design.
For PLG, the playbook is optimized for speed and self-service. Identify the activation event from cohort data on retained-vs-churned users. Strip the path to it under five minutes for top performers. Pre-load value with templates and demo data so the user doesn't start from empty. Replace generic feature tours with contextual guidance at the friction point. Trigger nudges on behavior, not calendar. Show progress in user language. The full breakdown is in PLG Activation: Why Most Self-Serve SaaS Loses Users in the First Hour.
For sales-led, the playbook is optimized for multi-role coordination. Define an account-level activation event plus role-level events for admin, end-users, and executive sponsor. Run the shortest path to each role's first win. Catch end-users inside the account when CS isn't there — answers in-product instead of dependency on a CSM. Fire nudges on account-level signals like dropping seat count, not on the calendar. Track adoption breadth across the account, not admin-side milestones. The full breakdown is in Why Your Enterprise Customers Sign and Then Go Quiet.
Both playbooks have to be designed. Both have to be measured. The shared data bridge between them is what makes the handoff work — without it, PQL handoffs leak, expansion stalls, and activation context disappears at the moment the customer transitions from self-serve to assisted.
What to Do This Week
Three actions. Each takes under an hour. None require new software.
1. Segment your last fifty new customers by ACV and motion. How many came in self-serve versus through sales? What's the median ACV in each group? If self-serve is more than 20% of new customers, you have a PLG segment whether the company calls itself PLG or not. The onboarding playbook has to handle both segments, which means the question stops being "are we PLG or sales-led" and starts being "are we running two playbooks or one."
2. Pull the activation rates for both segments separately. If the company has been measuring one activation event for everyone, calculate it separately for self-serve users in their first session versus contracted accounts at thirty days. The numbers will diverge. The diverging numbers are evidence that one playbook isn't doing both jobs.
3. Identify the PQL-to-PQA bridge. Pull the last twenty self-serve users from companies above 50 employees. Did anyone hand them off to sales-assisted? If so, was the activation context preserved or did the CSM start over? If not, were any of them companies where a contracted account would have made more sense? That gap is where most hybrid companies leak six-figure expansion ARR every quarter.
One onboarding playbook across two customer segments is the most expensive shortcut in B2B SaaS. The activation rate looks fine in aggregate because it averages a strong number from one segment with a weak one from the other. The renewals look fine in aggregate because the segments age differently. The leak is invisible until you split the data — and then it's the only thing you can see. MatrixFlows is free to start. Two playbooks, or one — but the cost of one is real, and it shows up at renewal.
.svg)
.svg)
.svg)
