The definitive playbook for a PLG B2B SaaS company adding a sales-led / enterprise motion to move up-market without breaking self-serve. Segment the base, find PQLs/PQAs, design the dual motion, hire the first AEs, get enterprise-ready, and run both motions.
Decide whether you are actually ready to go up-market, where PLG is plateauing, and what the dual-motion thesis is. Get leadership aligned before you spend a dollar on sales headcount.
Prove with data that self-serve alone is leaving enterprise revenue on the table — and that the gap is a motion gap, not a product or activation gap.
Build the PLG ceiling analysis
Before hiring a single AE, prove the motion gap is real. The signal to add sales is not "growth slowed" — it is that larger accounts are self-serving badly: hitting plan limits,…
Pressure-test that PLG itself is healthy
The single most common way up-market expansion fails is bolting expensive sales headcount onto a leaky PLG funnel. Sales then "works" only because reps manually drag deals over…
Write the strategic thesis, the explicit non-goals, and the exec-level commitment so the new motion does not cannibalize PLG.
Write the dual-motion thesis and non-goals
The failure mode is mission creep: sales leadership, hired to chase enterprise, starts "helping" with mid-market self-serve deals because they're easier, and quietly converts your…
Model the investment case and 18-month P&L
A single AE is an experiment that almost always fails — too little pipeline coverage, no manager, no SE support, founder attention spread thin. Fund a minimum viable sales motion…
Align leadership and set the proof gates
A dual motion that isn't explicitly co-owned by product and finance will be sabotaged by the first budget cycle or the first time a product roadmap call collides with an…
Turn your product-usage data into a ranked pipeline. Define PQLs and PQAs, score fit + usage + intent, and surface the expansion accounts hiding in your own user base.
Establish rigorous, data-derived definitions for product-qualified leads (individuals) and product-qualified accounts (accounts) — the spine of the whole motion.
Derive the PQL/PQA signal set from conversion data
A PQL is an individual user who hit a usage signal correlated with buying intent; a PQA is an account with multiple activated users and account-level buying signals. PQLs convert…
Segment the installed base into named tiers
Your next quarter of enterprise pipeline is already inside your product — accounts quietly sprawling on self-serve plans. Segmentation routes each account to the right motion so…
Mine the base for expansion and multi-product whitespace
The fastest enterprise wins aren't new logos — they're accounts you already have that are using a fraction of their potential. The pattern (Datadog's playbook) is land small via…
Stand up the tooling that scores accounts continuously and pushes ranked signals to reps in the CRM.
Select and wire the product-led sales tooling
Reps cannot manually watch product analytics — you need a product-led sales (PLS) platform that ingests usage, scores accounts against your PQL/PQA model, and pushes ranked…
Define PQL/PQA routing rules and SLAs
A scored PQA with no clear owner and no response SLA is a wasted signal. Routing rules turn the score into action and prevent the two failure modes: enterprise signals going…
Validate and calibrate the PQL/PQA model against outcomes
A PQL/PQA model that isn't validated against real outcomes is just a guess with a dashboard. Reps lose trust fast if the "hot" accounts they're handed don't convert — and once…
Architect self-serve + sales-assist + enterprise to coexist, with explicit ownership boundaries, conflict rules, and a compensation design that doesn't pit motions against each other.
Define how self-serve, sales-assist, and enterprise interlock — the handoffs, the rules of engagement, and the boundaries that prevent cannibalization.
Define rules of engagement and ownership boundaries
The central danger of a dual motion is internal channel conflict: sales competing with the self-service channel for the same accounts. The fix is not judgment calls — it's…
Design the sales-assist (hybrid) layer
Sales-assist is the bridge tier most teams skip — and it's where a huge share of expansion lives. Sales-assist helps users who request guidance or hit implementation obstacles…
Design comp so reps don't cannibalize self-serve, so expansion is rewarded, and so the three layers reinforce rather than fight each other.
Design the comp plan that protects PLG
Comp is where dual-motion strategies quietly die. If reps get paid on revenue the product would have generated anyway, you've converted free PLG growth into expensive…
Set territories and the conflict-resolution model
The internal version of channel conflict is two reps fighting over the same logo — or worse, an AE poaching an account a CSM is already expanding. Unmanaged, it poisons team trust…
Hire the first AEs and SEs in the right order, decide on sales leadership, and build the enablement and sales playbook a PLG-native team needs to sell consultatively.
Sequence the first hires, define the profile of a PLG-native AE, and decide founder-led vs. early sales leader.
Sequence the first sales hires
Hire order is a make-or-break decision. Hire a VP of Sales too early and you pay $300K for someone with no motion to manage; hire only one AE and you get no signal. The proven…
Define the PLG-native AE and SE profile
The wrong AE for a PLG-up-market motion is the classic cold-outbound "smile and dial" rep. In product-led sales, the buyer already uses the product — the AE's job is consultative:…
Decide founder-led vs. early sales leadership
The most expensive early mistake is hiring a VP of Sales before the motion is repeatable — you pay $250-300K for someone who needs a playbook you don't have yet, they build…
Build the consultative sales playbook, qualification framework, and enablement that turns usage signals into closed enterprise deals.
Build the consultative sales playbook
The enterprise sales playbook for a PLG company is unusual: the rep starts every deal with data the buyer doesn't know you have — exactly who's using the product, how much, and…
Stand up enablement and a 30-60-90 ramp
A new AE in a PLG-up-market motion has more to learn than a typical rep: the product deeply (they sell off usage), the PQL/PQA model, the routing rules, the RoE, and the…
Wire SE support into the enterprise deal cycle
In a PLG-up-market motion, the technical buyer is in the room early — security, IT, and architecture questions surface in the first or second call, not at the end.…
Remove the deal-blockers enterprise procurement throws at you — SSO/SCIM, SOC 2, MSAs — and build the up-market packaging, pricing, and security posture that lets six-figure deals close.
Build the SSO/SCIM/RBAC/audit-log feature set and the SOC 2 / compliance posture procurement teams require before they'll buy.
Build the enterprise-readiness feature checklist
Enterprise deals don't stall on your core value — they stall on IT/admin and security gaps. Procurement asks about security posture early, and you won't close until you can…
Achieve SOC 2 and stand up the trust posture
SOC 2 Type II is the de-facto enterprise entry ticket — procurement, legal, and security all gate on it, and it becomes the blocker between you and revenue if you start late. Type…
Build the admin experience and onboarding for big teams
Landing an enterprise logo is half the job — if a 400-seat customer can't roll out the product across their org, they churn at renewal and your land-and-expand thesis collapses.…
Design the enterprise tier, pricing model, and commercial terms (MSAs) that convert self-serve users into six-figure contracts.
Design the up-market packaging and pricing
Your self-serve pricing page maxes out where enterprise budgets begin — you need an enterprise tier with the gravity to pull buyers up. The dominant structure is good-better-best…
Stand up enterprise commercial terms and MSAs
Self-serve deals close on click-through ToS; enterprise deals close on a negotiated MSA with legal, procurement, and security all weighing in. Without a contract toolkit, your…
Design the migration path from self-serve to enterprise plans
Your richest enterprise pipeline is existing self-serve accounts that have outgrown their plan — but the move from a credit-card monthly subscription to an annual enterprise…
Operate PLG and SLG together without one starving the other — the RevOps spine, the metrics that prove neither motion broke, and the cross-functional cadence that keeps product, sales, and CS aligned.
Stand up the data model, CRM hygiene, and cross-functional alignment that lets two motions run on one system of record.
Unify the data model and CRM for both motions
Running two motions on two disconnected data systems is how accounts fall through cracks — a self-serve account expands, sales never sees it; an AE closes a deal, lifecycle keeps…
Define the AE → CSM handoff and joint expansion model
The whole up-market thesis rests on expansion — larger accounts that grow 120%+ NRR. But the handoff between the sales rep and the CSM is where it leaks: expansion opportunities…
Establish the cross-functional operating cadence
Dual-motion success requires alignment across product, sales, marketing, and CS — without a cadence, the motions drift and channel conflict festers unseen. The cadence is the…
Define the metric set that proves the new motion is working AND that PLG didn't break, and instrument the dashboards leadership reviews.
Define the dual-motion metric framework
The metric trap in dual-motion is blended numbers hiding a broken motion: total revenue grows while self-serve conversion quietly collapses because sales is dragging deals over…
Run the proof-gate review and decide to scale
The whole investment was tranched against proof gates (Module 1) for a reason: adding sales is reversible if you decide early, ruinous if you scale a broken motion on sunk-cost…
