Read time: 3 minutes 37 seconds

3 things going βviralβ this week:
My first viral Twitter thread (2.1k saves and counting!)
The flu I caught over the weekend (hitting send then Iβm back to bedβ¦ @ 2pm π€)
The βDeploy to Netlifyβ button (keep reading to understand)
β Tom


The first tool I recommend to every startup
Notion powers just about everything at Strategy Breakdowns.
Social content, newsletter content, tasks, company wiki.
By moving from βgoalsβ to βsystemsβ (and building all systems in Notion), Iβve been able to:
built an audience of 180k+ across email and LinkedIn
grow a side-hustle enough to quit my job and go βall-inβ
grown my business to more than my salary in 1 year full-time
If youβre a startup, youβll get 3 months of the Notion Plus plan for free with Unlimited AI (over $6,000 in savings)!
Your AI sales team is ready for deployment
Attio's AI agents automatically research companies, classify prospects, and send personalised emails based on natural language logic.
Stop wasting time doing sales like it's still 2020. Get the CRM built for 2030.
Thank you for supporting our sponsors, who keep this newsletter free.



Chess Move
The what: A TLDR explanation of the strategy
In 2016, one-year-old cloud infrastructure startup Netlify turned the worldβs biggest developer community, GitHub, into a viral distribution engine.
They released a feature called βDeploy to Netlifyβ - a button that allowed users to deploy a website directly from a GitHub repo to Netlify in just one click.

GitHub repository + βDeploy to Netlifyβ button = one of the most elegant growth hacks of all time.
For those of you not so technical, imagine it like this:
Youβve made a cool lego creation (i.e. piece of software) and you want to share how you made it with the world
You put your list of Lego pieces and instruction manual (i.e. code) on the public Lego forums (i.e. GitHub)
When someone clicks βDeploy to Netlifyβ it takes your instructions and instantly builds your Lego creation in their living room (i.e. replicates your code to their Netlify account)
So rather than having to create their own Deathstar with a solid design foundation and build quality, they can instantly copy yours, fully assembled and functional, then tweak it for their use case.
A massive time-saver for users.
A frictionless onboarding machine for Netlify.

One-click and youβre into Netlifyβs site creation workflow (a few clicks if you havenβt signed up yet).
This simple workflow turned Netlify into the de facto standard tool for letting other developers instantly copy and deploy your code.
Meanwhile, every time someone added a Deploy button to their public repository, they distribute another Netlify funnel into GitHub's 100M+ userbase.
The result? Within 4 years, Netlify surpassed 1+ million developers, and millions of projects shipped via the βDeploy to Netlifyβ button.
Today, they have 5+ million devs, 35+ million live sites, and are generating 10,000 sites a day (mostly from AI codegen platforms, but thatβs a breakdown for another day depending on how viral todayβs article goes!)

π‘
Strategy Playbook: One-click traffic hijacking.


Breakdown
The how: The strategic playbook boiled down to 3x key takeaways
1. Β Remove friction, become the default
Deploying a website is a complicated and lengthy process.
You have to:
Set up and pay for servers that can handle your traffic
Configure multiple environments (staging, production, etc.)
Create systems to test your code before it goes live
Manage domain settings and security certificates
Plus an array (π) of technical and time-consuming steps in between.
Netlify abstracts away this complexity with one click-deployment.
For developers this means:
Instantly deploy code without managing servers
Automatic updates whenever you push changes to GitHub
Built-in security and performance optimisations
Preview features before they go live
By completely removing the friction, Netlify makes deployment easy for devs as well as less technical users.
The βDeploy to Netlifyβ button compresses all of this simplification into single funnel, where users viewing a repo are only ever a few clicks away from cloning it and spinning up a live website.
2. Create a viral, self-serve adoption loop
Every time a developer adds a 'Deploy to Netlify' button to their project README, it acts as free marketing for Netlify.
Not just any marketing - an direct entry point for prospective users to sign up in a few clicks.
To use a practical example:
A developer includes a 'Deploy to Netlify' button in their open-source GitHub project
Other developers click it β Sign up to Netlify β deploy their own sites β experience Netlifyβs product firsthand
Some of those developers convert into customers and use Netlify themselves
Some add 'Deploy to Netlify' buttons to their own projects
The cycle repeats
This PLG motion turns Netlify users' projects into a built-in distribution channel that leverages the largest developer community in the world, GitHub.

GitHub is 60th most popular website on the internet - over 450M visits per month.
To put this into perspective: it contributes ~25% (almost 6M visits) of Netlifyβs total traffic.
~10 years after the feature was released.
Entirely for free.

Bolt now being the top referrer really shows the era weβre living in.
π P.S. I recorded a free tutorial showing exactly how you can find traffic data like the examples above for any website. Check it out by clicking "Get free tutorial" here
Each deployment also adds to Netlifyβs powerful proprietary datasets, allowing them to monitor popular frameworks, workflows, trends, and guide product decisions (integrations, framework templates) accordingly.
3. A self-replicating PLG motion
Marketing is one thing.
Social proof is another.
Each βDeploy to Netlifyβ button is a statement from a proud Netlify user (as opposed to Netlify themselves) that proves the product is valuable.

By adding the button to their projects, Netlify users distribute social proof across the web.
But the βDeploy to Netlifyβ button doesnβt just create free marketing, it also creates a compounding flywheel.

Each button generates more buttons.
How?
Every time someone clicks the 'Deploy to Netlify' button, they copy the button into their new repository.
If they make it public, anyone who views it will see another 'Deploy to Netlify' button in the new project README.
Other users can then click the button and deploy their own version of the copied project (and button), without ever seeing the original.
The cycle continues with each button clicked.
Every PLG disciple's dream: a signup funnel that multiplies organically.


Rabbit Hole
The where: 3x high-signal resources to learn more
[11 minute read]
A behind-the-scenes journal from the Netlify founders on their road to 1 million users, and the milestones they achieved along the way.
Spoiler: βDeploy to Netlifyβ was an important moment.
[33 minute watch]
From bootstrapping Netlify as a two-person startup to creating the industry standard deployment ecosystem serving over 5 million developers.
Hereβs Biilmann going deep on their core product strategy: eliminating friction to help teams focus on building, rather than managing infrastructure.
[13 minute read]
Our friends over at Contrary Research write some of the internetβs cleanest memos on private hypergrowth companies.
Hereβs their thesis (market sizing, competitive analysis, risk assessment, etc) on Netlify.
Enjoy.
If you enjoyed, please forward it to a pal. Itβs free, and only takes 10 seconds.
Who knows, maybe this article will go viral too.
β Written by Sheldon Bishop and Tom Alder


Whenever you're ready, there are 3 ways we can help you:
Our flagship course on how to use free internet data to make better strategic decisions. Contains 5 years of strategy expertise, proven methods, and actionable tactics to accelerate your career with modern-day strategy skills.
We have a growing audience of 80,000+ strategists from top companies like Google, Meta, Atlassian, Stripe, and Netflix. Apply to feature your business in front of Strategy Breakdowns readers.
One of the most common questions we get asked is: βWhat tools do you use to run Strategy Breakdowns?β So, weβve open-sourced our tech stack to give you an inside-look at exactly what tools weβre using to power each corner of this operation.






