Signup to paid. Product owns the instrumentation; the PQL threshold and the account-size split decide who ever talks to Sales.

GTM Operating Model › Product-led
Product-led: signup to paid
Signup
free tier or trial; the work email is matched to an account, or a new one is created and enriched
Activated
the first-value event: a project created, a report run, a teammate invited
PQL
usage threshold crossed; rolled up from users to the account; written to the CRM
Account size?
Self-serve upgrade
in-app paywall, card on file; no human; straight to Onboard
↗
Sales-assist
routed to a rep as a warm lead; to the Qualify gate and Sell
↗
Dormant
signed up, never activated; automated re-engagement; most of the volume
Expansion signal
the same PQL logic re-applied to paying customers; see Keep and grow
↗
owner · Product instruments and writes the PQL; Sales acts on sales-assist; Customer Success feeds back which usage predicts retention; RevOps owns the threshold and the routing. measured by · signup to activation, activation to PQL, PQL to paid, time to each
WHAT MAKES A PQL
Depth
how much of the product they use: features touched, volume processed, integrations connected
Breadth
how many people: seats active, teams invited, admin roles assigned; the account signal, not the user signal
Frequency
how often they come back: weekly active, sessions per user; decays like a lead score
Fit
company size and industry from enrichment; this is what decides self-serve vs. sales-assist, not the usage
When a company runs both motions, an account can be an MQL and a PQL at the same time. The rule has to be written down: usually the PQL wins because it is evidence of behavior, and the MQL source is kept for attribution. Sales-assist reps are usually a separate, lower-cost pool from the outbound AE team, because the lead is already warm and the deal is smaller.
small account
large account
no activation

Boxes marked ↗ open the page for that part of the model.

How to read this

  • Activation is the first-value event in the product, and most signups never reach it.
  • A PQL is a usage threshold rolled up from users to the account and written to the CRM.
  • Fit, not usage, decides self-serve vs. sales-assist: small accounts upgrade in-app, large ones route to a rep as a warm lead.
  • The same PQL logic re-applied to paying customers is the expansion signal.

Where it connects

Diagram source: 14-product-led.drawio 14-product-led.svg