PLG vs Sales-Led Measurement

First PublishedMay 25, 2026ByAtif Alam

Upstream: Martech Stack & Automation — instrumentation, tooling, and data plumbing. This page covers measurement execution.

The decision this page enables: which funnel definition, lead definitions, and KPI tree match your go-to-market motion — so Marketing, Product, and Sales are counting the same thing.

What PLG vs sales-led measurement is (and why it matters)

Go-to-market motion determines what you measure and where handoffs happen. Product-led growth (PLG) measures in-product behavior and self-serve conversion. Sales-led growth (SLG) measures marketing-qualified demand and rep-assisted pipeline. Hybrid motions need two parallel funnels that reconcile in the warehouse — not one funnel stretched until it breaks.

Use this page when:

• Marketing reports MQLs but Product reports PQLs and the numbers never match.
• You’re adding a sales team to a PLG product (or vice versa) and need a shared vocabulary.
• Leadership asks “which motion is working?” and every team answers with a different metric.

Confusing motions produces classic failure modes: sales chasing signups that will never buy, product optimizing activation while marketing optimizes demo requests, and CAC calculated on the wrong denominator.

Quick motion identification

Signal in your business	Likely primary motion
Majority of revenue closes without a sales call	PLG
Average deal requires discovery + proposal	Sales-led
Free tier exists but enterprise deals need AE	Hybrid
Consumer mobile app, in-app purchase	PLG (B2C)
Outbound SDR team is >30% of marketing-sourced pipeline	Sales-led

If two rows describe you equally, you’re hybrid — read the hybrid section first.

Core concepts

The two primary funnels

Lens	Primary question	Typical entry event	Primary conversion	Handoff signal
PLG	Who activated in-product and is ready to expand or pay?	Signup / install	Activated user → paid	PQL / PQA
Sales-led	Who fits ICP and wants a conversation?	Form fill / demo request	Opportunity → closed-won	MQL → SQL
Hybrid	Which path did this account take — and when do paths merge?	Either	Either (with rules)	PQL or MQL → unified account score

PLG definitions: PQL and PQA

• PQL (Product-Qualified Lead) — a user or account that hit a behavioral threshold indicating buying intent or expansion readiness. Examples: invited 3+ teammates, created 10+ docs, hit a usage limit, viewed pricing twice in 7 days.
• PQA (Product-Qualified Account) — the account-level version of PQL. One PQA may contain multiple users; the account is the unit Sales cares about in B2B PLG.

PQL/PQA thresholds must be defined jointly by Product, Marketing, and Sales — and re-validated quarterly against win rate.

Sales-led definitions: MQL and SQL

• MQL (Marketing-Qualified Lead) — a person who meets firmographic + behavioral criteria indicating fit and interest. Examples: VP Product at 25-person SaaS, downloaded pricing guide, attended webinar.
• SQL (Sales-Qualified Lead) — an MQL accepted by Sales after discovery confirms need, budget, authority, and timeline (or your team’s equivalent).

The MQL→SQL boundary is where most attribution and forecast arguments start. Document the SLA: who accepts, within how many hours, and what “disqualified” means.

Hybrid motion: parallel funnels, unified account

In hybrid GTM, the same company may have:

• Users self-serving in a free tier (PLG path).
• An AE working an enterprise deal (sales path).

Rule: measure both paths, tag the primary motion per account, and define merge rules (e.g., any SQL on an account supersedes PQL routing; PQL on enterprise ICP triggers AE assignment).

flowchart LR
    subgraph PLG["PLG funnel"]
        S1[Signup] --> A1[Activate]
        A1 --> P1[PQL / PQA]
        P1 --> C1[Self-serve paid]
    end
    subgraph SLG["Sales-led funnel"]
        V1[Visit] --> M1[MQL]
        M1 --> Q1[SQL]
        Q1 --> O1[Opportunity]
        O1 --> W1[Closed-won]
    end
    P1 -.->|Enterprise ICP| Q1
    M1 -.->|Starts trial| A1

Side-by-side funnel comparison

flowchart TD
    subgraph PLG_side["PLG — SaaS workspace example"]
        p_visit[Organic / paid visit]
        p_sign[Signup]
        p_act["Activate: 3+ teammates + 1 doc"]
        p_pql[PQL: usage limit hit]
        p_pay[Upgrade to paid]
        p_visit --> p_sign --> p_act --> p_pql --> p_pay
    end
    subgraph SLG_side["Sales-led — same product, enterprise tier"]
        s_visit[ABM / content visit]
        s_mql[MQL: demo request]
        s_sql[SQL: discovery held]
        s_opp[Opportunity]
        s_win[Closed-won]
        s_visit --> s_mql --> s_sql --> s_opp --> s_win
    end

The same product can run both funnels. The mistake is using PLG stage names for sales pipeline or MQL definitions for in-product users who never filled a form.

How to do it (step by step)

1. Name your primary motion. Pick PLG, sales-led, or hybrid. If hybrid, assign a default path per segment (e.g., SMB = PLG, 200+ employees = sales-led).
2. Define stage events in the data layer. Each stage needs one canonical event in product analytics or CRM — not a spreadsheet column maintained by one person.
3. Write lead definitions as formulas. PQL = {event X within Y days} AND {ICP fit score ≥ Z}. MQL = {form submit OR high-intent action} AND {firmographic fit}. Publish definitions in a shared doc.
4. Set SLAs for handoffs. PLG → Sales: PQL routes to AE within 4 business hours. Marketing → Sales: MQL accepted or rejected within 48 hours with reason code.
5. Build parallel dashboards. One view for PLG (signup → activation → PQL → revenue). One for sales (MQL → SQL → pipeline → win). One account rollup for hybrid.
6. Reconcile weekly in RevOps. Compare product-analytics counts to CRM counts. Investigate gaps >5% before they become quarterly surprises.
7. Review thresholds quarterly. Pull win rate by PQL rule and MQL source. Kill rules that don’t predict revenue.

Reconciling PLG and sales numbers in the warehouse

Product analytics and CRM will disagree. A practical join pattern:

1. Identity key: account_id (B2B) or user_id → email hash → CRM contact.
2. Product events table: signup, activation, PQL flag, upgrade — from Amplitude/Mixpanel/PostHog export.
3. CRM table: MQL date, SQL date, opportunity stage, closed-won amount — from Salesforce/HubSpot.
4. Unified account view: one row per account with columns plg_stage, crm_stage, primary_motion, revenue.

Primary motion assignment (apply in priority order):

1. CRM closed-won and opportunity existed before PQL → sales_led
2. Product self-serve paid date recorded → plg
3. PQL date exists and account has 50+ employees → hybrid_escalation
4. PQL date exists (smaller accounts) → plg
5. CRM MQL date exists (no PQL yet) → sales_led
6. None of the above → unknown (investigate identity gaps)

Review unknown monthly — it should be <5% of accounts. Higher means identity or event gaps.

Templates

Motion-fit scorecard

Score each dimension 1–5 (1 = poor fit, 5 = excellent fit). Sum ≥32 → lean PLG; 24–31 → hybrid; ≤23 → lean sales-led.

Dimension	Question	Score (1–5)	Notes
Product complexity	Can a new user reach first value without a call?
ACV / deal size	Is average contract ≥$15k (sales-led pressure)?
Buyer committee	Single user vs. 3+ stakeholders?
Time-to-value	<1 day self-serve vs. weeks implementation?
ICP concentration	Can you score accounts firmographically at signup?
Expansion motion	Land-and-expand in-product vs. upsell via AE?
Competitive displacement	Do buyers need education / rip-and-replace help?
Data on behavior	Do you have product analytics on key actions?
Total		/40

PQL definition worksheet

Product:           [name]
Segment:           [e.g., SMB workspace teams]
Review cadence:    [quarterly]

Behavioral trigger (pick 1 primary):
  Event name:      [e.g., workspace_invite_sent]
  Threshold:       [e.g., ≥3 invites in 14 days]
  Supporting:      [e.g., doc_created ≥1]

Fit filter:
  ICP rule:        [e.g., company size 10–200 OR email domain not personal]
  Exclude:         [e.g., competitor domains, student emails]

Routing:
  Destination:     [AE name / pool / self-serve only]
  SLA:             [hours to first outreach]
  CRM object:      [Lead / Contact / Account flag]

Validation (last 90 days):
  PQL count:       [___]
  Opp created:     [___]  (conversion: ___%)
  Closed-won:      [___]  (win rate: ___%)
  False positive:  [describe users who PQL'd but never had budget]

MQL → SQL handoff SLA

Step	Owner	Target	Escalation if missed
MQL created	Marketing automation	Real-time	—
MQL reviewed	SDR / BDR	≤4 business hours	Manager alert at 8h
Accept / reject SQL	SDR + AE	≤48 hours of MQL	RevOps weekly report
Discovery held	AE	≤5 business days of SQL	Pipeline review flag
Reason codes required	Sales	100% on reject	No reject without code

When-to-use decision tree

flowchart TD
    start["What motion are you measuring?"]
    start --> q1{"Can users reach paid<br/>without talking to sales?"}
    q1 -->|Yes, majority| plg["Use PLG funnel:<br/>Signup → Activate → PQL → Paid"]
    q1 -->|No| slg["Use sales-led funnel:<br/>MQL → SQL → Opp → Won"]
    q1 -->|Some segments yes| hybrid["Hybrid: segment by ICP<br/>Run both funnels + account rollup"]
    plg --> q2{"Enterprise tier<br/>or ACV > $15k?"}
    q2 -->|Yes| hybrid
    q2 -->|No| done1["Primary KPIs: activation rate,<br/>PQL rate, free-to-paid"]
    slg --> done2["Primary KPIs: MQL→SQL,<br/>pipeline coverage, win rate"]
    hybrid --> done3["Primary KPIs: both +<br/>motion mix, blended CAC"]

Metrics to track

Metric	PLG target (healthy growth)	Sales-led target (healthy growth)	Notes
Signup → activation rate	25–45% (B2B SaaS)	N/A (use MQL→SQL instead)	Activation definition must be stable 90+ days
Activation → PQL rate	8–20% of activated	N/A	Depends on PQL threshold strictness
PQL → opportunity rate	15–35%	N/A	Below 10% → threshold too loose or routing broken
Free → paid conversion (30d)	3–8% (B2B freemium)	N/A	B2C app: 5–15% trial-to-paid
MQL → SQL acceptance	N/A	25–40%	Below 20% → MQL definition too loose
SQL → opportunity	N/A	60–80%	Tracks discovery quality
Win rate (SQL → won)	N/A	20–35% (SMB) / 15–25% (mid-market)	Segment by source
Sales cycle (days)	N/A	30–90 (SMB) / 90–180 (mid-market)	PLG self-serve: days to first payment
Blended CAC payback	<12 months	<18 months	Calculate per motion, then blend
PQL/MQL definition drift	0 undocumented changes / quarter	0 undocumented changes / quarter	Any change resets baselines

Worked examples

SaaS workspace (B2B) — hybrid motion

Context: Unified team workspace for 10–49 person product teams. Freemium PLG for SMB; sales-led for 50+ employee accounts with SSO requirements.

PLG funnel:

Stage	Definition	Monthly volume	Conversion
Signup	Work email, workspace created	4,200	—
Activate	≥3 members + ≥1 doc in 14 days	1,260	30%
PQL	Hit 10-doc limit OR viewed pricing 2× in 7 days	189	15% of activated
Self-serve paid	Upgraded without AE	34	18% of PQL

Sales-led funnel (same product, enterprise track):

Stage	Definition	Monthly volume	Conversion
MQL	Demo request OR ABM form fill, 50+ employees	85	—
SQL	Discovery completed, budget confirmed	28	33%
Opportunity	Proposal sent	19	68%
Closed-won	Contract signed	6	32% win rate

Hybrid rule: Any account with employee_count ≥ 50 that hits PQL routes to enterprise AE instead of self-serve upgrade flow. Product analytics tags motion = hybrid_escalation.

Dashboard cadence: Growth reviews PLG weekly; Sales reviews pipeline weekly; RevOps reconciles account-level revenue monthly.

Weekly PLG dashboard (minimum viable):

Widget	Definition	Target
Signups (work email)	workspace_created	950/week
Activation rate (14d)	≥3 members + ≥1 doc	30%
PQL count	Limit hit OR 2× pricing view	45/week
PQL → opp (enterprise route)	Opp within 14d of PQL	25%
Self-serve MRR	Upgrades without opp	+$12k/week net

Weekly sales-led dashboard (minimum viable):

Widget	Definition	Target
MQLs (50+ employees)	Demo + ABM forms	20/week
MQL → SQL (48h)	Accepted with discovery scheduled	35%
Pipeline created	$ from new opps	$180k/week
Win rate (rolling 90d)	Closed-won ÷ closed	30%

Consumer fitness app (B2C) — PLG-primary

Context: Bodyweight workout app, 14-day trial, no sales team. “Sales-led” is limited to B2B corporate wellness partnerships (small slice of revenue).

PLG funnel (95% of revenue):

Stage	Definition	Monthly volume	Conversion
Install	App Store / Play install	28,000	—
Activate	Completed 1 workout in first 72 hours	11,200	40%
PQL proxy	4+ workouts in first 14 days (expansion-ready for annual plan)	2,240	20% of activated
Trial → paid	Subscribed before trial end	1,680	75% of PQL proxy

Corporate wellness (sales-led slice):

Stage	Definition	Quarterly volume	Conversion
MQL	HR leader downloaded corporate deck	12	—
SQL	Discovery call held, 100+ eligible employees	4	33%
Closed-won	Annual corporate contract	1	25%

Lesson: B2C measurement is almost entirely PLG. Don’t force MQL/SQL vocabulary onto consumer installs — use activation and retention cohorts instead (see Cohort Analysis). Reserve sales-led metrics for the B2B partnership track only.

Common pitfalls

• One funnel for everything. Stretching “MQL” to mean “any signup” destroys forecast credibility.
• PQL thresholds set by Product alone. Sales must validate that PQLs convert; otherwise you’re spamming AEs with tire-kickers.
• No reason codes on MQL reject. Without reject reasons, Marketing can’t fix source quality.
• Ignoring activation in sales-led motions. Even demo-led products have in-product trials; measure activation separately from MQL.
• Blended CAC without motion tags. Blending PLG and SLG CAC hides that enterprise deals cost 5× more to close.
• Changing definitions mid-quarter. Renaming “activated” resets every dashboard; batch definition changes quarterly.
• Hybrid without account object. Person-level PLG + account-level sales pipeline requires a CDP or warehouse join on account_id.

Tools / further reading

• Product analytics: Amplitude, Mixpanel, PostHog — PLG funnel and PQL rule engines.
• CRM: HubSpot, Salesforce — MQL/SQL stages and routing.
• Reverse-ETL / CDP: Hightouch, Census, Segment — unify product events with CRM accounts.
• PLG CRM overlays: Pocus, Common Room, Endgame — PQA scoring for sales-assist.
• Canonical read: Product-Led Growth ( Wes Bush ) — PQL framework; Predictable Revenue ( Aaron Ross ) — sales-led pipeline anatomy.

Cross-links

• Funnel: Overview — the A→C→R lens that both motions roll up to.
• Funnel: Conversion — activation, pricing-page funnel, MQL→SQL handoff detail.
• Sales Analytics & Forecasting — pipeline coverage, win rate, forecast (downstream of marketing-qualified demand).
• Place: Logistics — activation and time-to-first-value; fix the middle before scaling either motion.
• Martech Stack & Automation — wiring product analytics to CRM for hybrid measurement.
• KPIs & Metrics — North Star hierarchy across motions.