How Snyk built a product-led growth juggernaut | Ben Williams (VP of Product at Snyk)
Grew from a free, narrow Node.js tool to a company valued at $8.6 billion with over 2,000 paying customers. It used built-in loops like fix pull requests and Snyk Advisor, about 5,000 free users came before monetization, and enterprise features plus sales unlocked revenue. Activation is defined as a team fixing a vulnerability within 30 days. Auto-generates hundreds of thousands of package pages with health scores that pull in search traffic. Each page carries calls to action inviting visitors to secure their own apps with Snyk.
Tips
- Start with one narrow persona, context and use case▶ 17:02The first hundred or so users came from the founders engaging the node.js community, and about 5,000 free users existed before any monetization attempt.
- Design company-generated content loops into the product from the start▶ 21:20It was a first-of-its-kind integration and brought a lot of new users. Snyk later extended the loop to other source control systems such as Bitbucket and GitLab.
- Build a free programmatic SEO sidecar product from data you already have▶ 24:00There are hundreds of thousands of these package pages, generated automatically and continuously.
- Publish bite-sized educational content with no signup or paywall▶ 25:35
- Add the table-stakes features enterprise buyers need before pushing monetization▶ 28:20Self-serve only landed individual developers at $100 a month, while free developer adoption kept growing; after the changes it was 'rocket ship time'.
- Meet developers in their workflow instead of pulling them out of it▶ 32:50
- Staff growth teams cross-functionally with a growth marketer on each team▶ 38:20A growth marketer built a high-performing SEO page without engineering, which led the team to build a paste-your-code scan sidecar. Traffic rose significantly, sign-up rate dropped a little, new users jumped and activation rates rose.
- Sequence growth teams by biggest constraint and defer monetization investment▶ 37:50
- Hire growth team members for fit, not just talent▶ 48:20
- Start experimentation simple and go deeper as teams gain experience▶ 50:05
- Document your growth model as connected loops, then add the numbers▶ 57:55
- Invest early in trustworthy behavioral data and test tracking in CI▶ 1:03:10
- Run weekly team and monthly group impact and learnings reviews▶ 1:07:20Williams calls it the most important meeting in the growth team, loosely modeled on a Brian Balfour HubSpot-era ceremony.
- Treat experiments as generating learnings that lead to impact▶ 55:00
- Review experiment plans with owners of the surfaces you test on▶ 1:12:10
- Define activation as a team habit moment found through data▶ 1:20:50Teams that fix a vulnerability in their first 30 days are much more likely to still be fixing three months later.
- Map the drivers between plans and keep challenging your trial design▶ 1:15:40Different company sizes and industries need different evaluation lengths, so dynamic or usage-based trials matter.
- Track product-driven revenue to measure plg efficiency▶ 1:16:55The product-driven cohort contributes relatively more to net retention.







