Most B2B SaaS companies get this decision wrong by not making it at all.
They call themselves product-led because they have a free trial. They call themselves sales-led because they have AEs. The motion is actually neither — it is a hybrid with no clear dominant logic, and it costs them in every dimension: CAC is too high for a PLG business, close rates are too low for an SLG business, and the team cannot agree on where to invest because the playbook is inconsistent.
PLG and SLG are not philosophies. They are operating models with fundamentally different resource allocation, team structure, and success metrics. Choosing your dominant motion — even if you eventually run both — is one of the most consequential decisions a GTM leader makes. Getting it wrong means hiring the wrong people, building the wrong product instrumentation, and measuring the wrong signals for years.
This guide covers what each motion actually requires, where they work, and how to decide which one to lead with at your current stage.
What Product-Led Growth Actually Means
Product-led growth is a go-to-market motion in which the product itself is the primary driver of acquisition, conversion, and expansion. Users discover and adopt the product — usually through a free tier, free trial, or self-serve experience — before any sales interaction takes place. The product does the selling.
This is not a passive approach. PLG requires deliberate product design choices: an onboarding experience that delivers value quickly without hand-holding, usage patterns that create natural expansion triggers, and in-product upgrade prompts that convert free users to paid at the right moment. The product does not sell itself accidentally. It sells because the activation flow, the feature gates, and the expansion logic are engineered to drive that outcome.
PLG companies measure success differently from SLG companies. The key metrics are activation rate (what percentage of sign-ups reach first meaningful value), time to value (how quickly a new user experiences the core benefit), product qualified lead rate (what percentage of free users hit the usage thresholds that predict conversion), and expansion revenue from existing accounts driven by product adoption rather than sales activity.
The PLG Model Requires
- A product that delivers meaningful value within minutes or hours, not days or weeks
- Self-serve onboarding that works without a customer success manager on every call
- A free tier or trial that is genuinely useful — not a demo, not a locked preview, but a real experience of the product
- In-product instrumentation to identify when users are ready to convert or expand
- A pricing model that makes individual user adoption economically viable before enterprise contracts begin
What Sales-Led Growth Actually Means
Sales-led growth is a go-to-market motion in which a human sales motion is required to acquire and expand accounts. The product alone cannot close the deal — a salesperson is needed to guide the evaluation, build the business case, navigate the buying committee, and manage the commercial terms. The relationship is part of the value.
SLG is not an inferior alternative to PLG — it is the right model for specific product and buyer profiles. When a product requires significant implementation effort, changes multiple workflows across multiple departments, or involves a buying process with legal, security, and finance approvals, a sales motion is not a workaround. It is the appropriate response to a genuinely complex buying journey.
SLG companies invest in outbound prospecting, account-based programmes, structured discovery processes, and multi-stakeholder engagement. The metrics that matter are pipeline coverage, average contract value, sales cycle length, win rate by segment and competitor, and expansion revenue driven by customer success and account management activity.
The SLG Model Requires
- Outbound or inbound pipeline generation capacity — a sales motion does not run without a pipeline
- Discovery and qualification discipline to identify which accounts are worth investing sales time in
- Multi-stakeholder engagement capability — the ability to build relationships across the buying committee, not just with one champion
- Sales enablement infrastructure: battlecards, one-pagers, ROI calculators, and proposal templates that make each rep effective
- Contract and negotiation capability, including legal and procurement workflow management at enterprise scale
Where They Overlap
Most mature SaaS companies operate some version of both motions simultaneously. PLG and SLG are not mutually exclusive — the question is which one dominates your acquisition and expansion model at your current stage, not which one you use to the exclusion of the other.
Both motions require a deep understanding of the buyer. Both need positioning that is specific enough to attract the right accounts and repel the wrong ones. Both suffer when the ICP is poorly defined or the messaging is generic. The shared foundation — positioning, ICP clarity, and competitive differentiation — is necessary regardless of which motion is primary.
Where they diverge is in the operational infrastructure required to make each work, and in the metrics used to evaluate performance. A company that tries to optimise for both simultaneously without sufficient scale almost always ends up under-investing in both.
Where They Diverge
Product design implications
PLG requires the product team to treat activation and expansion as core product problems. Onboarding flows, feature discovery, usage limits, and upgrade triggers are product features, not afterthoughts. SLG products can have longer time-to-value because the sales team guides buyers through the evaluation and implementation — the product does not need to sell itself on the first login.
Team structure
PLG-first companies hire growth PMs, lifecycle marketers, and data analysts earlier in the journey. SLG-first companies hire SDRs, AEs, and sales engineers at comparable stages. The skills required for each motion are genuinely different — a strong SLG sales team does not automatically transition to PLG execution, and vice versa.
Unit economics
PLG's unit economics only work when enough free users convert to paid at an acquisition cost that is covered by the resulting contract value. SLG's unit economics only work when the ACV is high enough to justify the cost of a human sales motion, including rep compensation, management overhead, and enablement investment. These thresholds vary by market, but as a rough guide: under £5,000 ACV is hard to make SLG viable; over £20,000 ACV is hard to build a sustainable PLG model without a sales assist layer.
The operating consequence most teams miss
Motion choice dictates team architecture. PLG-first needs lifecycle PMM, product analytics rigour, and onboarding experimentation. SLG-first needs buyer committee messaging, enablement discipline, and deal-risk management. If you claim PLG but fund only field enablement, growth stalls. If you claim SLG but underinvest in product adoption, pipeline quality falls.
A Concrete Scenario: Choosing the Wrong Motion
A compliance workflow SaaS built for mid-market operations teams launched with a product-led motion. They offered a free trial with a 14-day limit and minimal sales involvement. Within three months, they had accumulated 900 free sign-ups. Eleven converted to paid accounts. The average ACV for those eleven accounts was £22,000.
The activation data told the story. Median time to first meaningful use was 11 days — almost the full length of the trial, leaving almost no time between a user understanding the product and the trial expiring. The product required configuration, data import, and workflow mapping before it delivered value. None of that happened in 14 days without assistance.
The switch to a sales-assist motion — where a short discovery call was offered three days into the trial to help users reach activation faster — changed the conversion profile. More importantly, analysis of the eleven deals that had converted revealed that eight came from inbound requests where a prospect had asked to speak to someone after signing up. The product-led framing was obscuring a fundamentally sales-assisted reality.
The business was always SLG-appropriate. The buying decision was too complex, the implementation too involved, and the ACV too high for unassisted self-serve to carry the motion. Recognising that — and restructuring the trial to feed a sales conversation rather than replace it — was the strategic fix. The PLG framing had been causing under-investment in exactly the sales infrastructure the model required.
Common Mistakes
- Claiming PLG without building for activation: Offering a free trial is not PLG. PLG requires the product to drive users to value quickly and repeatedly. If activation rates are below 30% and time to value is measured in weeks, you do not have a PLG motion — you have a free trial with a conversion problem.
- Running SLG without sufficient ACV to support it: A human sales motion is expensive. If the average contract value is below the threshold where LTV:CAC stays above 3:1, the motion is structurally unviable. Fixing this requires either raising ACV (moving upmarket) or reducing CAC (automating parts of the sales process).
- Treating the two motions as interchangeable: The skills, infrastructure, and metrics required for PLG and SLG are genuinely different. Asking a field sales team to shift to PLG execution, or asking a growth PM to build a high-ACV enterprise motion, usually fails — not because the people are incapable, but because the operating model they are used to does not transfer.
- Not defining a dominant motion: Running both simultaneously without committing to a primary motion creates ambiguity about where to invest, which metrics to optimise, and what "good" looks like. The hybrid approach works — but only after you have established dominance in one motion and have the resources to build a second layer on top of it.
Frequently Asked Questions
Can we run both PLG and SLG at the same time?
Yes, but sequence matters. Most companies that successfully combine both motions established dominance in one first. Slack was PLG-dominant and built an enterprise SLG layer on top. Salesforce is SLG-dominant and has built PLG onboarding for SMB accounts on top. Trying to build both simultaneously without the resources or scale to do each properly usually produces two weak motions rather than one strong one.
Which motion should we choose at Series A?
The motion that matches your product's time-to-value and your buyer's buying complexity. If a new user can reach meaningful value in under 30 minutes without assistance and your ACV is below £10,000, lean PLG. If your product requires configuration, stakeholder alignment, or change management, and your ACV is above £15,000, lean SLG. The ACV thresholds are rough guides, not hard rules — the real test is whether the product can drive conversion without a human sales process.
How do we know if our current motion is the wrong one?
Three signals: your activation rate is consistently below 25% (PLG problem), your sales cycle is consistently over 90 days for deals below £20,000 ACV (SLG efficiency problem), or your team cannot agree on what the primary acquisition driver is. All three suggest the motion and the model are misaligned.
PLG vs SLG: Choosing the Dominant Motion
The debate is often framed as product-led versus sales-led. In practice, mature SaaS companies run both. The strategic question is which motion is dominant for acquisition, conversion, and expansion at your current stage.
When PLG should lead
PLG works when buyers can evaluate value quickly without heavy vendor interaction. Typical signals are low implementation friction, clear self-serve outcomes, and broad user-level adoption potential. PLG is strongest when product usage itself creates buying momentum.
- Simple onboarding with immediate utility.
- Individual users can start without procurement.
- Value scales with collaboration or data accumulation.
- Upsell path is tied to real usage thresholds.
When SLG should lead
SLG wins when decisions are high risk, multi-stakeholder, or economically material. If implementation requires change management, integrations, or executive sponsorship, sales guidance is part of product value. Here, buying confidence matters as much as product capability.
- High ACV and long-term contract commitments.
- Complex security, legal, or procurement workflows.
- Multiple departments affected by adoption.
- Need for solution design and stakeholder alignment.
Diagnostic scorecard for PMMs
Run a quarterly scorecard across five dimensions: activation speed, buying complexity, support intensity, expansion pattern, and payback profile. Score each from 1–5. Scores of 1–2 favour PLG dominance. Scores of 4–5 favour SLG dominance. Mixed scores suggest a hybrid model with segmented entry paths.
Whatever you choose, be explicit. Document your dominant motion, decision logic, and implications for pricing, packaging, and enablement. Ambiguity is expensive.
PMM Field Implementation Notes: Turning Strategy into Repeatable Execution
Frameworks only create value when they survive real operating pressure. In B2B SaaS, that pressure comes from quarterly targets, constrained headcount, and stakeholder disagreement. The way to protect quality is to translate strategy into explicit operating defaults that teams can follow without constant escalation.
Create operating defaults before launch
For product-led vs sales-led decisions, define five non-negotiables before execution starts: target segment, primary success metric, proof asset type, escalation rule, and review cadence. These defaults reduce decision churn and prevent teams from reinventing the approach in every meeting.
- Target segment default: one primary segment with clear inclusion and exclusion criteria.
- Metric default: one behavioural metric and one business metric to avoid local optimisation.
- Proof default: the specific evidence format used in messaging and sales conversations.
- Escalation default: explicit triggers that require cross-functional review.
- Cadence default: weekly tactical review and monthly strategic reliability review.
Build a two-speed execution rhythm
High-performing teams run two speeds simultaneously. The fast loop handles immediate friction and tactical iteration. The slow loop protects strategic coherence and stops teams from overfitting to short-term noise.
Fast loop (weekly): review conversion leakage, objection frequency, and adoption blockers. Ship small fixes quickly. Slow loop (monthly): validate whether messaging, targeting, and proof still match buyer reality. Make structural changes deliberately.
Codify handoffs with acceptance criteria
Most GTM delays are handoff failures disguised as resource issues. Every cross-functional handoff should include acceptance criteria. For example, PMM to Sales handoff should specify message hierarchy, objection map, and required proof links. Product to PMM handoff should include use-case clarity, instrumentation plan, and known limitations.
When handoffs are explicit, accountability improves. When handoffs are implicit, teams blame each other and cycle time slows.
Use leading indicators, not lagging excuses
Revenue is a lagging indicator. To manage execution, track leading signals that predict outcomes early: first-value completion, stakeholder sharing behaviour, proposal acceptance rate, and objection concentration by segment. These signals show whether the go-to-market system is healthy before quarter-end pressure forces reactive decisions.
Advanced checklist for PMM operators
- Can Sales explain the core message without reading notes?
- Can CS map onboarding friction to specific promise gaps?
- Can Product prioritise roadmap requests using the same segment logic?
- Can leadership state one reason deals are won and one reason deals are lost by segment?
- Can you trace every major content asset to a specific funnel job?
If the answer is "no" to more than one question, the issue is likely system design, not individual performance. Fix the operating model first.