Company-Generated, Company-Distributed Content Loops
Build loops where your product creates branded content and distributes it into other people's workflows.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
Snyk's most powerful acquisition engine is a class of growth loop where the company both generates the content and controls its distribution — so it is neither dependent on user goodwill nor on a platform's algorithm. The canonical example: Snyk scans a connected GitHub repo, finds vulnerabilities, and opens a Snyk-branded pull request that fixes them. Every other developer in that repo sees the PR, reads the educational description, and some click through and sign up. It is simultaneously an acquisition loop and an engagement loop.
Origin
Ben Williams (VP of Product, Snyk) describing Snyk's loop portfolio; the loop taxonomy vocabulary (company-generated/company-distributed content loops, micro/macro loops) comes from Reforge, which Williams credits explicitly elsewhere in the episode.
Core principles
- 01You control the content, so you control the CTA, the branding and the education inside it.
- 02The best distribution is inside a workflow your user is already in — not a channel you must drag them to.
- 03The same loop can serve acquisition and engagement at once.
- 04A working loop is a template: clone it onto adjacent surfaces to multiply it.
- 05Programmatic assets compound — hundreds of thousands of pages generated continuously beat hand-written ones.
How to run it
- 1
Find a workflow surface your product can write into
Identify a place where your product can legitimately produce an artifact that other people in your user's orbit will see. For Snyk, connecting a GitHub account let it raise pull requests visible to every developer in the repo.
Pro tip The surface should be one where the artifact is genuinely useful on its own — the PR actually fixes the vulnerability.
- 2
Own the content of the artifact
Do not just perform an action — wrap it in content you author. Snyk's PR descriptions explained the vulnerability, educated the reader, carried Snyk branding, and ended with a CTA: if you find this useful, click here, learn more, sign up.
Pro tip Embed the original hook question in the artifact ('do you have known vulnerabilities in your codebase — click here to find out').
Watch out If the artifact is pure automation with no narrative, you get the utility but none of the loop.
- 3
Close the loop back into signup and connection
New viewers follow the link, create accounts, connect their own repos — which produces more branded artifacts in more repos. Make sure each of those steps is instrumented so you can see where the loop leaks.
- 4
Layer programmatic SEO assets as a second loop
Snyk built Snyk Advisor: it indexes every package manager, augments packages with security scans and maintenance signals into a package health score, and generates hundreds of thousands of pages continuously. Developers searching Google for a package land on a Snyk property with a CTA.
Pro tip Pick data only you can produce (Snyk's scans) so the pages cannot be trivially cloned.
- 5
Give away the education, ungated
Snyk publishes high-quality, bite-sized developer-security lessons with no paywall and no signup — deliberately different from incumbents who gate everything after a couple of lessons. It functions as another company-generated, company-distributed loop.
- 6
Clone the working loop onto adjacent surfaces
Once the GitHub loop was proven and its performance was growing, Snyk expanded scope by adding Bitbucket, then GitLab — spinning up the same loop again on each new source control system.
Pro tip Expanding a proven loop is usually a better quarterly bet than inventing a new one.
In the wild
A user signs up, connects their GitHub account, Snyk scans the code and finds vulnerabilities, then automatically raises Snyk-branded pull requests that fix them. Other developers in the repo see and interact with those PRs, read the educational description, follow the links, create accounts, connect their own repos — and the loop continues.
→ A first-of-its-kind integration that became both an acquisition loop and an engagement loop, bringing in a large volume of new users while keeping existing ones coming back.
A sidecar product that indexes all package managers and builds a package health score from security scans plus source-repo maintenance activity. Anyone Googling a package by name or capability finds Snyk Advisor high in the results, on a Snyk-owned page with a CTA to secure their app on a perpetual basis.
→ Hundreds of thousands of automatically and continuously generated pages that became one of the instrumental drivers of new user growth.
Common mistakes
Relying on loops you don't distribute
Referral and invite loops depend on users choosing to act. Company-generated, company-distributed loops fire whether or not the user evangelizes, which is why they carried Snyk's growth.
Treating the artifact as a coupon rather than as value
The PR worked because it actually fixed the code and taught the reader something. Branding without utility is spam inside someone's repo, and gets your integration removed.
Is it for you?
Best for
Product and growth teams at bottom-up B2B or dev-tool companies whose product can create visible artifacts inside a shared workflow (repos, docs, dashboards, tickets).
Not ideal for
Products used entirely in private with no shared surface, or in workflows where writing into the user's system would be perceived as intrusive.
From the transcript
“company generated company distributed content Lube it's actually really powerful for us because it's both an acquisition Loop and an engagement Loop”
“but the key was that we ultimately controlled the content So Not only was the fixed pull request doing something useful in terms of the…”
“so anyone searching on Google for a package that does XYZ or a specific package by name sneak advisor will be right up there in…”
“let's expand that by adding support for bitbucket and now all of a sudden we spin up that same loop with bitbucket and then gitlab”
From the episode
How Snyk built a product-led growth juggernaut
Ben Williams (VP of Product at Snyk)