Nov 6, 2022 · 1h 31m · lennys-podcast
How Snyk built a product-led growth juggernaut | Ben Williams (VP of Product at Snyk)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, Ben Williams, VP of Product at Snyk, breaks down how Snyk built a multi-billion-dollar product-led growth engine through developer-centric acquisition loops, cross-functional growth teams, and a hybrid product-led sales motion. He shares practical frameworks on team structuring, experimentation cadences, behavioral data infrastructure, and activation metrics.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 24.4% of the talking time here. How this is scored →
Lenny as informed peer 3.7 Guest teaching 3.6 Guest disagreement 0.1 Lenny pushing back 0.3
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 27:30 Rejecting the assumption that pure self-serve was viable early
Ben firmly explains that early self-serve monetization efforts failed because enterprise security teams required broad multi-stack coverage and governance tooling that developer-only self-serve couldn't provide.
Hardest push from Lenny ▶ 55:56 Host pushes back on learnings as an outcomeLenny challenges Ben's premise that experimentation is primarily about generating learnings, noting that leaders ultimately demand tangible business metrics and output.
Biggest teaching moment ▶ 9:46 Educating on the paradigm shift to developer-first securityBen provides a deep historical breakdown of why legacy security audit models alienated engineers, showing how Snyk flipped the industry standard by meeting developers inside their workflows.
Lenny holds their own ▶ 15:15 Lenny connects Snyk's early tactics to his growth strategy frameworkLenny demonstrates his product growth expertise by deconstructing Snyk's initial traction into target persona, core hook, and discovery channels from his own published framework.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Identifying Micro and Macro Growth Loops | 0 | 0 | 0 | 0 | Introductory teaser quote followed by Lenny's solo host introduction and sponsor ad reads for Coda and Athletic Greens. As a monologue segment, all interactive host scores remain at zero. | |
| Sponsor Segment: Athletic Greens AG1 | 3 | 1 | 0 | 0 | Lenny finishes the AG1 ad read, formally welcomes Ben, and asks about his background. Ben details his path from developer tooling solutions engineering to IBM, CloudBees, and Snyk in a warm, collaborative exchange. | |
| The Scope, Scale, and Mission of Snyk | 3 | 3 | 0 | 0 | Lenny prompts Ben for key business metrics and company scope. Ben explains Snyk's developer security mission and company valuation metrics without friction. | |
| Snyk's Origin and Acquiring the First Hundred Users | 2 | 5 | 1 | 0 | Ben delivers an extensive history of why traditional security failed developers and how Snyk pioneered bottom-up adoption in the Node.js open-source ecosystem, educating Lenny on the early days. | |
| Validating Product-Market Fit Through Depth Over Breadth | 6 | 2 | 0 | 0 | Lenny actively connects Ben's narrative to his own consumer growth framework (who, hook, where) and presses on the exact constraints of the target persona. Ben agrees and validates the depth-over-breadth playbook. | |
| Designing Snyk's Automated GitHub PR Growth Loop | 4 | 5 | 0 | 0 | Ben explains the mechanics of Snyk's automated GitHub fix pull request loop as an acquisition and engagement mechanism. Lenny expresses genuine admiration for the innovative growth tactic. | |
| Programmatic SEO and Democratizing Security Education | 4 | 4 | 0 | 0 | Ben discusses Snyk Advisor and un-gated security education as programmatic SEO content loops. Lenny highlights the smart data leverage behind auto-generating package health scores. | |
| Early Monetization Struggles and Adopting Product-Led Sales | 4 | 4 | 1 | 1 | Ben shares how early self-serve monetization stalled due to enterprise governance requirements, necessitating product-led sales and expanding language breadth. Lenny probes the counter-intuitive timeline where sales preceded mature self-serve. | |
| Winning Developer Mindshare by Protecting Developer Flow | 4 | 4 | 0 | 1 | Lenny asks why early monetization was difficult when the value proposition seemed obvious in hindsight. Ben clarifies that user adoption never stalled, but institutional security buying habits took time to catch up. | |
| Establishing Snyk's Cross-Functional Developer Growth Group | 5 | 4 | 0 | 0 | Ben describes building Snyk's Developer Growth Group with cross-functional pods, decision scientists, and embedded growth marketers. Lenny explores the novelty of the decision science role and marketing integration. | |
| Growth Pod Pillars and Product-Led Sales Enablement | 4 | 3 | 0 | 0 | Lenny and Ben discuss the structure of the growth pods, their collaboration with product-led sales, and the role of specialized SEO leadership. | |
| Sponsor Segment: Vanta Security Compliance | 2 | 6 | 0 | 0 | Following a Vanta mid-roll ad read, Ben lays out his three-pillar growth framework (People, Process, Strategy/Data) and details his vision vs. mission construct. | |
| Establishing Rapid Learning Cadences in Growth Process | 6 | 4 | 1 | 4 | Lenny challenges Ben's assertion that experimentation is primarily about learning rather than business outcomes. Ben concedes that impact is the goal, but frames learnings as the necessary stepping stones. | |
| Developing Loop-Based Growth Strategies | 5 | 3 | 0 | 0 | Ben explains how loop-based growth modeling directs quarterly team focus to key constraints. Lenny synthesizes the methodology into concrete operational examples like expanding GitHub loops to GitLab and Bitbucket. | |
| Investing Early in Behavioral Data Infrastructure | 3 | 5 | 0 | 0 | Ben emphasizes investing early in trustworthy behavioral telemetry rather than amassing noisy data, explaining how Snyk enforces schema compliance in CI pipelines. | |
| Socializing Experiment Learnings Across the Organization | 4 | 4 | 0 | 0 | Lenny asks how growth teams systematically socialize findings to sales and engineering. Ben outlines their weekly impact and monthly group-level learning reviews. | |
| Snyk's Overall Product and R&D Organization Structure | 3 | 4 | 0 | 0 | Ben explains the structural distinction between functional domain R&D squads and outcome-focused growth teams, including experiment planning guardrails. | |
| Freemium Packaging, Trials, and Product-Driven Revenue | 5 | 4 | 0 | 1 | Ben discusses freemium gating, usage-based trials, and product-driven revenue metrics. Lenny asks whether higher net retention on product leads stems from discounted starting points, which Ben notes is an open question. | |
| Defining Team-Based Activation and Habit Moments | 4 | 5 | 0 | 0 | Ben outlines Snyk's team-level activation metric: fixing vulnerabilities within 30 days of creation due to strong 3-month retention correlation. Lenny validates the methodology against his industry research. | |
| Essential SaaS Tools for Growth and Product Teams | 3 | 3 | 0 | 0 | Lenny tests a new recurring question about top five SaaS tools; Ben names Amplitude, Segment, FullStory, UserInterviews, Sprig, and Airtable. | |
| Lightning Round: Recommendations, Culture, and Product Operations | 4 | 2 | 0 | 0 | Lenny conducts the lightning round covering books, podcasts, interview questions, and thought leaders. Lenny praises Ben for citing prior podcast episodes and closes the show. |
Statements from this episode (27)
Snyk reached an $8.6B valuation post-Series F with over 2,000 customers
“Last valuation after our Series F was at 8.6 billion. We're securing the software of millions of developers now, well over 2000 paying customers, now around 1300 people, of which around 500 in R&D, with nearly 70 folks in our product org.”
The average modern software application is at least 75% open-source
“The average software application today is at least 75% of open source libraries and components.”
Snyk acquired its first 100 users directly through the Node.js community
“The first hundred or so users really just came from the founders engaging with the Node.js community and the interest that drove.”
Snyk acquired roughly 5,000 free users before attempting to monetize
“I think we probably had maybe around 5000 free users before there were any attempts at monetization.”
Developers prioritize deep ecosystem features over broad multi-language support
“A JavaScript developer just won't care if you support Golang or Rust, but will absolutely care if a key feature like automated package upgrades just isn't available for their ecosystem.”
Williams: Product-led founders must intentionally design early acquisition loops into the product
“So if your acquisition strategy is product led, then understanding and being intentional about your early acquisition growth loops, I think is an essential founder's responsibility. Dedicating time there to design those loops into the product. It's key.”
Snyk was the first to integrate security scanning with automated pull requests
“First of all, that, that integration in terms of connecting your code with security scanning like that was a first of a kind integration. Like no one had done that before.”
Snyk Advisor programmatically generates hundreds of thousands of package pages for SEO
“There are hundreds of thousands of these package pages, but they're just automatically being generated continuously.”
Snyk made its developer security education content completely free and public
“All the traditional solutions you need to sign up, you need to pay to get access beyond more than a couple, but these were just, they're all out there in the public domain.”
Snyk's initial self-serve monetization completely failed to convert large enterprise customers
“But the first self-serve monetization efforts only really saw traction with individual developers paying a hundred dollars a month or purchases in larger companies. They just didn't happen as everyone had hoped.”
Developers wield software buying influence regardless of who holds the budget
“What was always true though, even back then was the influencing power of developers, regardless of where the buying center was.”
Developer tool adoption requires integrating directly into workflows to protect flow
“Flow is just this incredibly important concept for developers and you want to strive to keep them in that flow for as long as possible. So the GitHub kind of pull requests are a great example of that. Someone can sign up for Snyk and they could theoretically b…”
Embedding growth marketers within product teams will become the industry norm
“I've actually learned to my surprise that inclusion of growth marketers in the product teams is not all that common. And I personally think there's just a lot of opportunity being missed there. And I expect that to start to become the norm rather than the exce…”
Snyk's ungated sidecar code scanner drove massive user acquisition and activation
“The team went on to build out a functional sidecar product that Allowed users to basically try sneak without needing to sign up by simply pasting their code in for us to scan and giving them some results there and then. So, you know, we saw really great result…”
Snyk's Growth Platform team feeds product usage data to go-to-market teams
“Product led sales is a really important motion for us. And so taking the knowledge we have, the insight we have around behavior With the users and their teams and their companies within the product and making that available to the GTM teams outside in smart wa…”
Effective growth engineers happily discard code and embrace imperfection
“The devs that really thrive in a growth context are the ones that are motivated by moving quickly, iterating to create measurable impact. They're not attached to their work. They embrace imperfection as part of the process. They happily discard their code, the…”
Ben Williams: Vision statements must describe end states without mentioning products or solutions
“The vision is the Nirvana state that you aim to enable for your users and customers in five to 10 years. It's something that could equally be enabled by your competitors if you don't execute effectively or efficiently or quickly enough. You can always prefix a…”
Assigning growth to core product teams without new processes usually fails
“Teams in growth need to work differently in some ways from R and D teams working on core product, assuming otherwise, and just giving growth responsibility to an existing team without working with them. To implement appropriate ways of working, I think it's a …”
Growth experimentation generates organizational learnings rather than delivering immediate outcomes
“And if you think about experimentation, It's not about delivering outcomes. It's about generating learnings that the organization can leverage effectively to deliver outcomes.”
Loop-based models are the most effective way to articulate growth strategy
“The best way I've found to articulate a growth strategy that fulfills the promise of usefully guiding the team's execution. It's the loop based model we forge as specific kind of documentation that, that I think is great around that. Being able to identify the…”
Snyk verifies product analytics schema conformance directly within CI pipelines
“And now we test conformance to schema of the instrumented code in our CI processes. So we have absolute confidence in the data.”
Early-stage startups must invest in behavioral data tracking to define activation
“But the reason I say invest early here is that to remember that it also takes time to accrue enough data that you can learn about and make some key decisions around retention, for example, or so that you have enough data to run regressions on, be able to infor…”
Team-level impact and learnings reviews are the most important growth meetings
“And if I had to pick one meeting that is the most important in the growth team, it would be this.”
Snyk structures core product teams by function and growth teams by outcome
“So most of the org is functional ownership based. There are a lot of really complex domains in the core product. So having that localized knowledge is important to be able to kind of own and run the code that team ship. The growth teams on the other hand are s…”
Snyk users upgrade to paid plans to secure business-critical code
“For Sneak, the real drivers to move from free to a paid plan, for example, is when you want to secure business critical code. And you start having needs around governance and compliance.”
Product-led customer cohorts generate significantly higher net revenue retention at Snyk
“And what's, what's fascinating there is that the product driven cohort contribute a relatively greater amount to net retention.”
Fixing vulnerabilities within 30 days is Snyk's core activation metric
“Now, habit moment that we define as a team being activated, it's related to fixing vulnerabilities within 30 days of team creation. And the reason that is, is chosen, it's because there is a significant correlation with downstream, and in that case with activa…”