In a product-led growth (PLG) model, developers adopt the product before they talk to sales. Conversion happens inside the product and depends on the developer’s first experience. DevRel owns or influences many steps in that path, so its work can affect revenue directly.
What PLG means for developer products
A traditional sales-led B2B path:
Awareness → Marketing Lead → SQL → Demo → Pilot → Contract → ImplementationA product-led developer path:
Awareness → Signup → Activation → Active Usage → Expansion → Paid Conversion → Enterprise (sometimes)In a sales-led model, a salesperson can help a customer through product friction. In a PLG model, that friction can stop an evaluation before the company has a chance to intervene.
Where DevRel enters the conversion path
In a PLG company, the activation funnel runs through:
- Marketing copy and SEO. Sets expectations.
- The signup flow. First impression of operational craft.
- The quickstart docs. Determine whether the developer can reach first use without assistance.
- The first API call or first deploy. The demo.
- The sample app or template. Proves the use case.
- The community. Answers questions that block adoption.
- Reference documentation. Supports expansion.
- 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 can affect revenue at a PLG company within the same reporting period.
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:
- Quickstart and onboarding documentation. Improvements in completion can raise activation and create more opportunities for later retention and conversion.
- Sample applications and templates. Reduce TTFHW and prove use cases.
- Active community help. First-response time and answer quality directly affect early-stage retention.
- Developer education. Workshops, certifications, longer-form content that drive deeper adoption.
- 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) through (3).
Metrics that change in PLG
PLG gives activation and retention measures more weight:
| 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
Accounts of the 2022 to 2024 layoff wave suggest that DevRel teams with measurable PLG responsibilities could defend their budgets through:
- Cost-per-activated-developer calculations.
- Activation-rate changes associated with documentation, onboarding, or community work.
- A documented route from those measures to revenue.
The examples here do not establish field-wide comparative survival rates, but PLG measures gave some teams more specific evidence than brand activity alone.
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 with enterprise trust-building. DevRel supports self-serve activation and gives enterprise evaluators technical evidence for expansion decisions.
In each hybrid model, DevRel contributes to activation through documentation, examples, education, and community support.
What PLG demands of DevRel
Three operational disciplines:
- Treat docs and onboarding as a product. Roadmap, owner, metrics, version-controlled improvements.
- Connect outputs to outcomes. Track whether a tutorial or programme helps developers activate, retain, or expand their use.
- Embed with product. DevRel feedback feeds product decisions; product changes are co-launched with DevRel.
These three practices align DevRel with a PLG business. Without them, the programme still depends on sales-led assumptions about how developers evaluate and adopt the product.
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.
For developer products with self-serve adoption, PLG is the relevant starting model; products without that route need a different one.