Sales-led growth is a motion where humans drive every meaningful step from prospect to paid customer: outbound, demo, proposal, negotiation. Product-led growth is a motion where the product itself drives acquisition, activation, and often expansion, with sales involved only at specific moments (team upgrade, security review, enterprise contract). Most successful B2B SaaS companies above $50M ARR run both motions in parallel; the question is which one you start with and how the boundary is governed.
When each motion fits
| Dimension | Sales-led | PLG |
|---|---|---|
| ACV | $25K and up | $0 to $50K, growing through expansion |
| Time to value | Weeks to months | Minutes to hours |
| Buyer | Committee | Individual or small team |
| Onboarding | Implementation services | Self-serve |
| Sales cost | High (CAC payback 12-24 months) | Low at the front; sales reappears at expansion |
Sales-led wins when the product is genuinely complex, the buying group is large, or the contract requires negotiation. PLG wins when the product can demonstrate value in a single session and a credit card can buy enough seats to be useful.
The hybrid reality
The 2026 default for new B2B SaaS is “PLG into mid-market, sales-led for enterprise.” A user signs up free, the product instruments usage, and a sales-assist or AE intervenes when usage crosses a threshold (multiple users, paid tier, enterprise domain). The decisive question is the trigger:
- Account-based trigger. A user from a target account signs up; sales gets routed the lead in real time.
- Usage trigger. A workspace crosses 10 active users or hits a feature limit; sales-assist reaches out.
- Intent trigger. A user views the pricing page or starts a security questionnaire; AE engages.
Common Room, Pocus, and Endgame are the typical instrumentation for PQL routing.
When sales-led poaches PLG (and vice versa)
The bad pattern is sales-led teams treating self-serve users as raw leads to be cold-called the moment they sign up. Users churn from the product when sales cuts off the self-serve flow. The good pattern is sales-assist that contacts the user only after a usage signal that suggests an enterprise need: SSO request, multi-team workspace, security review.
The reverse mistake is PLG teams refusing to staff a sales motion when usage data clearly shows their largest accounts buy through procurement and need a contract. Procurement does not buy through self-serve.
How to choose for a new product
Default to PLG if any are true: time to value under 30 minutes, individual users get value before teams, the product can be instrumented for usage milestones. Default to sales-led if any are true: implementation requires services, the buyer is a non-user (CIO buying for engineers), or the product needs configuration before value.
Common pitfalls
- Free trial without instrumentation. A 14-day trial with no PQL triggers is a missed PLG motion.
- Sales-led commission on PLG signups. Compensating AEs for self-serve revenue they did not influence corrupts both motions. Commission on incremental ARR above the self-serve baseline.
- One funnel, two motions. Each motion needs its own funnel definition, conversion model, and forecast. Mixing them produces nonsense ratios.
Related
- PLG (Product-Led Growth) — deep dive on the PLG motion
- ICP — defines who each motion targets
- Pipeline velocity — the sales-led measurement
- Common Room — PQL signal aggregation