Should a new app use a self-serve (PLG) motion or a sales-led one — which is more common?
Of the 599 companies Lazyweb tags with a growth engine, 30% (179) run a product-led self-serve (PLG) motion versus just 10% (59) that are sales-led — a roughly 3-to-1 tilt toward self-serve[1]. Counting any product-led motion (PLG or product-led sales) gets you to 36% (213), while any sales motion stays at 10% (59)[1]. The two camps barely overlap: not one PLG company in the set also carries a sales-led tag, so this is genuinely an either/or choice for most teams, not a blend[1].
Product-led self-serve outnumbers sales-led roughly 3 to 1 across tagged apps — 179 vs 59 of 599, July 2026.
| Item | Share of 599 |
|---|---|
| Product-led self-serve (PLG) | 30% |
| Any product-led (PLG or PLS) | 36% |
| Sales-led (B2B) | 10% |
| Product-led sales (PLS) | 6% |
| Any sales motion (Sales-led or PLS) | 10% |
The finding: self-serve is the default, sales-led is the exception
Among the 599 companies with a growth-engine tag, self-serve product-led growth is the far more common acquisition motion, and pure sales-led is a minority play[1].
| Motion | Companies | Share of 599 |
|---|---|---|
| Product-led self-serve (PLG) | 179 | 30% |
| Any product-led (PLG or PLS) | 213 | 36% |
| Sales-led (B2B) | 59 | 10% |
| Product-led sales (PLS) | 34 | 6% |
| Any sales motion (Sales-led or PLS) | 59 | 10% |
Two structural facts make the choice cleaner than it looks: every PLS (product-led sales) company in the set also carries the Sales-led tag, so PLS is a subset of B2B sales here, not a separate camp[1]. And PLG has zero overlap with any sales motion — the 179 PLG companies are all pure self-serve[1].
How to apply it
If you are building a consumer, prosumer, or subscription app, self-serve is the modal, lower-risk default — the tagged corpus picks it 3x as often as sales-led[1]. Reach for a sales-led motion when your model is genuinely enterprise: the sales tag concentrates almost entirely in Enterprise, Collaborative, and B2B-licensing companies (covered in the sibling archetype pages), not in the broad consumer base[1]. Because the two motions almost never co-occur in the data, treat this as a real fork in your GTM plan rather than assuming you will run both at once.
Caveats
The honest denominator is the 599 companies that carry a growth_engine tag inside Lazyweb's ~600-900-company tagged subset — never the full 62,376-company table[1]. growth_engine is a multi-select array, so a single company can hold several engines; the PLG/sales figures above are deduplicated head-counts of companies carrying each motion, not a partition[1]. 'Self-serve' here means the Product-led self-serve (PLG) tag specifically.
The numbers
| Stat | Computed from |
|---|---|
| 179 of 599 (30%) | selfServeVsSalesOverall: PLG 179 / 599 |
| 213 of 599 (36%) | selfServeVsSalesOverall: Any product-led 213 / 599 |
| 59 of 599 (10%) | selfServeVsSalesOverall: Sales-led 59 / 599 |
| 34 of 599 (6%) | selfServeVsSalesOverall: PLS 34 / 599 |
| 59 of 599 (10%) | selfServeVsSalesOverall: Any sales motion 59 / 599 |
| ~3 to 1 | 179 PLG / 59 Sales-led = 3.03 |
| 0 overlap | selfServeVsSalesOverall note: PLG with no sales motion == PLG total (179) |
Sources & citations
- [1] Lazyweb Research analysis of 599 companies, July 2026. Deduplicated head-counts of product-led vs sales-led motions among the 599 companies carrying a growth_engine tag; growth_engine is a multi-select enum array. ↩
Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-07-09.