The PodKnowledge|← All Episodes
Based on Lenny's Podcast data
Lenny's Knowledge Sketch

From Community to Product-Led Sales:
How Snyk Disrupted Security

Ben Williams
VP of Product, Snyk
SECURITY · PLG
The Insight

Start Narrow, Go Deep

NarrowDeepWide
"The key for Snyk was not to go too wide, too early. Focus on nailing that initial use case for a specific community before expanding wider. You have to build a service and market it well to capture the opportunity."
  • Snyk started with a single persona: Node.js developers
  • Single context: securing open source dependencies
  • Narrow enough to build fast, wide enough to be viable
  • Then expanded language by language after proving the model
The Origin Story

How Snyk Disrupted an Industry

Market moment

Security was centralized, top-down, audit-focused. Developers hated the tools. Time for a different approach.

The realization

DevOps showed security could shift left. Developers increasingly cared about code quality and security. They just needed better tools.

  • Founded 2015 by Guy Podjarny, Danny Grander, Assaf Gilboa
  • Entry point: Node.js developers building apps with open source dependencies
  • The insight: 75% of modern apps are open source code; most vulnerable; least tested for security
  • The hook: "Do you have known vulnerabilities in your code?"
  • The distribution: Velocity Conference in Amsterdam + Node.js community evangelism
  • The product: Free CLI tool that scanned locally or in CI/CD pipelines
Why it workedProduct-led from day one. Developers loved it because it gave them agency and speed, not friction.
Growth Strategy

The Four-Team PLG Machine

  • Acquisition: SEO, content, community, developer evangelism
  • Activation: Onboarding, education, first-run experience
  • Monetization: Conversion loops, packaging, trials for teams
  • Data & Experimentation: Measurement, insights, PLS enablement
The sidecar moment

Built a free scan experience online (no signup needed). Result: huge traffic bump, higher intent users, better activation rates.

Product-Led Sales

The data and behavior insights from the product feed directly to the GTM teams. Sales knows exactly who's ready to convert.

People Architecture

Growing Great Growth Teams

  • Not every great engineer thrives in growth. Find people motivated by speed, iteration, and impact, not perfection.
  • Common vocabulary: everyone understands the growth process, data, and experimentation platform.
  • Start simple with education. Skip multivariate testing and sequential sampling early, it's a recipe for mistakes.
  • Align execution to strategy. If focus is activation, don't hire pricing experts, yet.
The core questionCan this person do their best work in a growth context? Most misalignments aren't about talent, it's about environment fit.
Framework

Vision & Mission for Growth Teams

📖Vision: The Nirvana StateWhat you're enabling →The imagined better future for users (5–10 years). Bound to your target market. Never mention your company or product.
🎯Mission: Your Unique PathHow you'll get there →The iterative approach you'll relentlessly pursue. Encodes your differentiating advantage (e.g., Snyk's unequal security intelligence).
🔗Alignment CascadeConnection points →Growth strategy ↔ product strategy ↔ company direction. Overlapping KPIs so teams swim in the same direction.
The Clarity TestEvery team member can answer →"Why am I here?" and "Why does my work matter?" If they can't, your strategy clarity needs work.
Based on Ben Williams' episode on Lenny's Podcast. All ideas on this page are from the episode.Watch on YouTubeFollow @semanticben on X
Every sketch here began as a transcript.

Send us yours and we’ll draw it. $1 a transcript.

Sketch mine →
𝕏︎ X / Twitterin LinkedIn📸 Instagram🔗 Copy link
0:00