Ben Williams on PLG at Snyk, Growth Team Structure, and Loop-Based Strategy

Ben Williams on PLG at Snyk, Growth Team Structure, and Loop-Based Strategy

transcriptlennys-podcastplgproduct-led-growthsnykgrowth-loopsgrowth-teamdeveloper-toolingsecurityactivation

Ben Williams on PLG at Snyk, Growth Team Structure, and Loop-Based Strategy

Source: Lenny’s Podcast Speaker: Ben Williams Date: ~2022 Link: https://www.lennysnewsletter.com/p/how-snyk-built-a-product-led-growth

Key ideas

  • Narrow-first community strategy. Snyk targeted only Node.js developers building apps with open source dependencies — a community small enough to meaningfully influence (Velocity Conference in Amsterdam, meetups) but large enough to be viable (2M+ devs, 200K+ NPM packages). The depth-before-breadth discipline enabled real PMF validation; only then did Snyk expand to additional languages, ecosystems, and personas. A JavaScript developer won’t care about Golang support but will absolutely notice a missing feature for their own ecosystem.
  • Company-generated, company-distributed growth loops. Three main acquisition loops: (a) automated GitHub fix-PRs — Snyk scans connected repos and raises branded, educational pull requests that other developers see and follow back to Snyk, creating a loop with no friction for non-users; (b) Snyk Advisor — programmatic SEO pages for open source package health scores; hundreds of thousands of auto-generated pages rank for package-name searches; (c) free security education lessons — open and paywall-free, designed to democratise developer security knowledge and drive awareness.
  • PLG to product-led sales. Early self-serve monetisation failed despite strong developer adoption: enterprise buyers (CISOs, AppSec leaders) needed governance features and multi-language support that didn’t yet exist. Snyk pivoted — added breadth, built governance features, hired sales — and the developer base became a pipeline of highly qualified leads. “Product-driven revenue” (revenue from accounts with meaningful in-product activity before first sales contact) cohorts show higher net retention than non-product-driven cohorts.
  • Three pillars of growth team effectiveness. (1) People & Process: cross-functional teams with embedded growth marketers (not siloed to marketing); “decision science” team (predictive modelling, not just BI); rapid learning cadence via weekly team-level and monthly group-level impact-and-learnings reviews — the most important meeting in the growth org. (2) Strategy: loop-based qualitative model (Reforge) maps micro and macro growth loops and their connections; augmented with quantitative data to identify constraints and guide quarterly focus. (3) Data: invest early in trustworthy behavioural event tracking; Snyk had abundant data but not the right behavioural data — rebuilding that foundation was critical.
  • Team-based activation. Activation is defined at the team level (not the individual user level) because security is a team sport and some fix activity happens off-platform. Snyk’s habit moment: a team fixing vulnerabilities within 30 days of team creation — derived via ML models correlating early behaviour with 3-month retention. The path: setup moment → aha moment → habit moment, each with specific behavioural triggers the growth team can influence.

Overview

Ben Williams — VP of Product at Snyk (developer security, $8.6B valuation at Series F) — covers the Snyk PLG origin story (Node.js community focus, developer-first disruption of enterprise security), the three company-generated growth loops that drove user acquisition, the transition from pure PLG to a product-led sales motion, how to structure and operate a high-performing growth team across people/process, strategy, and data, and the principles behind defining robust activation metrics. Highly operational episode with specific frameworks and Snyk-specific examples throughout.