Product-Led Growth and Developer Relations.

The single most important strategic shift for DevRel in the 2020s. In a product-led growth (PLG) model, developers adopt the product before they ever talk to sales. The conversion happens inside the product, driven by the quality of the developer’s first experience. Every step of that experience is owned (in whole or in part) by DevRel.

This makes PLG companies structurally dependent on DevRel — not aspirationally, not for brand, but for revenue.

What PLG means for developer products

A traditional sales-led B2B journey:

Awareness → Marketing Lead → SQL → Demo → Pilot → Contract → Implementation

A product-led developer journey:

Awareness → Signup → Activation → Active Usage → Expansion → Paid Conversion → Enterprise (sometimes)

In the sales-led model, the salesperson can compensate for product friction. In the PLG model, product friction is lost revenue — directly, immediately, measurably.

Why this elevates DevRel

In a PLG company, the activation funnel runs through:

1. Marketing copy and SEO — sets expectations.
2. The signup flow — first impression of operational craft.
3. The quickstart docs — the “salesperson” of the moment.
4. The first API call or first deploy — the demo.
5. The sample app or template — proves the use case.
6. The community — answers questions that block adoption.
7. The deeper documentation — supports expansion.
8. Customer success / DevRel-success — closes the loop into production.

Of those eight steps, marketing owns step 1, product owns step 2, and DevRel owns or co-owns steps 3 through 8.

Reducing TTFHW by 30%, lifting activation rate by 10 points, or increasing community-led retention by 5 points all translate directly to revenue at PLG companies — measurably, in the same quarter.

Companies where this is clearly visible

• Stripe. Documentation as primary salesperson. Patrick Collison’s developer-facing public presence.
• Twilio. SIGNAL conference; large DevRel investment; explicit developer-first positioning.
• Postman. Free tier as primary acquisition; community-led learning paths.
• HashiCorp. Open-core + extensive education program.
• MongoDB Atlas. Atlas free tier; MongoDB University; Champions program; conferences.
• Vercel / Next.js. Free tier; framework adoption funnels into platform usage.
• Supabase. Open-source-led PLG; SupaSquad ambassador program; transparent build-in-public.
• Snowflake. Free trial; Data Superheroes; substantial DevRel for developer-facing surfaces.
• OpenAI, Anthropic. API platforms with deep developer-led growth.

Operating model differences

DevRel in a PLG company looks different from DevRel in a sales-led company:

Dimension	Sales-led DevRel	PLG DevRel
Reports to	Often Marketing	Often Product or CEO directly
Primary metrics	Brand, leads, MQLs	Activation, TTFHW, retention, influenced ARR
Primary work	Awareness content, events	Documentation, samples, community, education
Sales relationship	Hand off leads	Coordinate on enterprise expansion only
Conference investment	Heavy booth presence	Often heavier on speaker placement and community
Engineering relationship	Light	Tight; embedded in product teams
Career path	Marketing-aligned	Engineering- or product-aligned
Headcount sizing	Sub-team of marketing	Independent function

The five activities that drive PLG outcomes

For a DevRel team in a PLG company, in approximate priority order:

1. Quickstart and onboarding documentation. The single highest-leverage activity. Every percentage-point improvement in completion compounds across all activation, retention, and revenue.
2. Sample applications and templates. Reduce TTFHW and prove use cases.
3. Active community help. First-response time and answer quality directly affect early-stage retention.
4. Developer education. Workshops, certifications, longer-form content that drive deeper adoption.
5. Selective brand-build. Conference speaking, podcast appearances — important but lower-frequency than the above.

A common failure mode: PLG DevRel teams that over-invest in (5) and under-invest in (1)–(3).

Metrics that change in PLG

The metrics that matter shift dramatically:

Metric	Sales-led weight	PLG weight
MQLs	High	Low
Brand awareness	High	Medium
Activation rate	Low	Very high
TTFHW	Low	Very high
90-day retention	Low	Very high
DQLs	Medium	High
Community NPS	Low	High
Influenced ARR	Hard to measure	Tractable

Activation rate becomes the metric that DevRel teams care about most. Improvement in activation rate is the most direct DevRel-to-revenue translation available.

Why this also makes DevRel more defensible

In the 2022–2024 layoff wave, DevRel teams at PLG companies were generally less affected than DevRel teams at marketing-aligned companies. Reasoning:

• The cost-per-activated-developer calculation favoured DevRel decisively.
• Cutting DevRel produced an immediate measurable drop in activation rate.
• The revenue case was concrete.

DevRel teams structured for PLG outcomes survived the contraction better than DevRel teams structured for “brand.”

Hybrid models

Most real companies are not pure PLG; they have both self-serve and sales-led motions:

• PLG handoff to sales. Self-serve customers reach a usage threshold or use a feature gating to enterprise, then get handed to sales. DevRel produces the conditions in which the handoff can succeed.
• Sales-led with PLG underneath. Enterprise sales motion, but with self-serve trial available. Developers prefer to evaluate before talking to sales.
• PLG-and-PLT. Product-led-growth plus product-led-trust. DevRel produces both the activation and the trust required for enterprise expansion.

In all hybrid models, DevRel is part of the activation engine, not separable from it.

What PLG demands of DevRel

Three operational disciplines:

1. Treat docs and onboarding as a product. Roadmap, owner, metrics, version-controlled improvements.
2. Measure outcomes, not outputs. Activation rate trumps blog post count.
3. Embed with product. DevRel feedback feeds product decisions; product changes are co-launched with DevRel.

Companies that do these three are PLG-effective. Companies that do none are still running sales-led DevRel inside a PLG business — usually unsuccessfully.

Caveats

PLG-style DevRel is not the right answer for every company:

• Pure enterprise products with no self-serve trial may genuinely need sales-led marketing without DevRel-as-revenue.
• Products with regulated/complex sales cycles (financial services, healthcare) may need sales-led primary motion.
• Products developers don’t use directly (where the buyer is an architect or VP, not the engineer) may need a different model.

The growing share of developer-product revenue running through PLG motions, however, makes this the default mental model for most developer-first companies in 2026.

See also

• ./ai-and-llms.md
• ./devex-movement.md
• ../04-metrics/activation-metrics.md
• ../04-metrics/business-impact.md
• ../10-tactics/documentation-as-product.md