Growth Hacking for SaaS

The growth hacking canon was written between 2012 and 2016, and most of it no longer runs. Not because the ideas were bad, but because the conditions they exploited have been closed one by one: open platform APIs, cheap email delivery, permissive cross site tracking, and a review ecosystem nobody was policing yet.

What replaced it is less fun and more durable. Here is the post mortem, then the list of what still works.

What growth hacking meant, and why the name changed

Sean Ellis coined the term in 2010 to describe a marketer whose primary skill was finding a repeatable acquisition mechanic rather than running campaigns. For about five years that meant unusual exploits: integrating with someone else’s platform, gaming a listing, giving away something with near zero marginal cost.

The job title mostly disappeared by 2020 and came back as growth engineering, which is a more accurate description of who does the work now. The mechanics that still function need product code, data infrastructure and a review by whoever owns your privacy posture. A marketer cannot ship them alone, and that is the actual change.

Eight tactics that still work in 2026

These compound. Each one turns its own output into the input for the next cycle, which is the property that separates a growth loop from a campaign.

Programmatic integration and comparison pages remain the highest return work in B2B SaaS. Zapier built thousands of app pair pages and turned other companies’ brand demand into its own organic footprint, and the model still works because every new integration you ship creates a new page with genuine search demand behind it.

In product invite loops work when collaboration is native to the job. Figma, Miro and Loom all grew this way: the product does not function fully alone, so sharing is usage rather than advocacy. Bolting an invite prompt onto a single player tool produces nothing.

Free tools remain underrated. A calculator, checker or generator that solves one job in thirty seconds earns links and rankings that a blog post cannot, and it keeps performing after the team that built it has moved on.

Template galleries are the same mechanic with user supplied fuel. Notion, Canva and Webflow all built libraries where users publish templates, creating indexable pages the company did not have to write.

Reverse trials, community sourced user generated content, onboarding personalisation based on a single role question, and usage triggered outreach round out the list. All four sit in the product, not in the marketing stack.

The last three are worth doing precisely because they are fast. The first four are worth doing because in three years they will still be producing. A sensible plan funds both, and the B2B SaaS growth strategy by stage guidance covers which to start with at your size.

Six tactics that are dead or dangerous

High volume scraped cold email is the big one. Google and Yahoo introduced bulk sender requirements in February 2024 that put a hard ceiling on spam complaint rates at 0.3 percent and mandated authentication and one click unsubscribe. A scraped list cannot stay under that ceiling. Teams that kept sending burned their primary domain, which is why the secondary sending domain industry exists and why it is a symptom rather than a fix.

Reverse IP personalisation, the trick of showing a visitor their own company logo on the landing page, broke for two reasons at once. Privacy enforcement made the data sourcing questionable in Europe, and residential IPv6 plus VPN adoption made the matching unreliable. A meaningful share of visitors now get identified as the wrong company, and there is no worse first impression than greeting a prospect by a competitor’s name.

Fake scarcity and resetting countdown timers now attract consumer protection attention in the UK and EU, and any technically literate buyer spots the reset in a private window. Contact scraping without a lawful basis remains a GDPR exposure that most teams have simply not been caught for yet.

Mass Product Hunt gaming stopped working when the ranking algorithm started weighting account age and engagement quality, and incentivised review farming violates G2 and Capterra terms as well as FTC endorsement guidance.

Why Dropbox and Airbnb cannot be copied

These two cases appear in every growth hacking article, and both are historically interesting and practically useless as templates.

Dropbox’s double sided referral programme gave 500MB to each side. It worked because storage had near zero marginal cost, because cloud storage was genuinely scarce in 2010, and because the product was consumer and viral by nature. B2B SaaS referral programmes typically source 2 to 8 percent of signups, and only after you have a user base that already loves the product. The programme amplifies delight, it does not create it.

Airbnb’s Craigslist integration was an unofficial reverse engineering of another platform’s posting flow. It would now breach terms of service, trigger a legal response, and probably fail technically. Anyone presenting it as a playbook in 2026 is teaching history as strategy.

The transferable lesson from both is narrower than the stories suggest: find the distribution your buyers already use and meet them inside it, legitimately. That is what integration marketplace listings, community presence and partner ecosystems now do.

The constraints that decide what is buildable

Before designing any loop, know the three boundaries that will be enforced whether you respect them or not.

That last item is the one teams skip. A growth mechanic without an owning engineer is a mechanic that breaks silently during a refactor and is discovered three months later in a traffic report.

How to run this as a discipline, not a tactic hunt

The teams that get results share a boring structure. A weekly cadence, a written hypothesis per experiment, a single primary metric, and a rule that nothing ships without an owner in engineering.

Onboarding is usually where the first wins are, because the leak is largest and the fix is cheapest. The patterns in SaaS onboarding teardowns and the mechanics catalogued in 12 SaaS growth loop examples are the right places to look for hypotheses before inventing your own. For the B2B specific variations, growth hacking for B2B SaaS covers where the consumer patterns break down.

The honest tradeoff

Growth engineering is slower than growth hacking was. A loop takes a quarter to build and two quarters to prove, and during that time a paid campaign would have produced numbers you could show a board. Plenty of teams cannot survive that patience gap, and for them the right answer is to fund demand capture, get to predictable pipeline, and build loops from a position of stability rather than desperation.

The other cost is organisational. Loops need engineering time that product leadership would rather spend on features, and winning that argument repeatedly is most of the job. If you cannot win it, accept that you are running channels rather than loops and plan the budget accordingly.

What to do next

Audit what you already run against the two lists above. Anything in the dead column should stop this week, particularly anything touching email volume, because the cost of that one compounds against you.

Then pick a single loop from the surviving eight, the one whose fuel you already have. If you ship integrations, build the integration pages. If your product is collaborative, build the invite loop. The product led growth examples library shows what finished versions look like, the growth experimentation course covers the testing discipline, and the SaaS growth model template will tell you whether the loop you picked can carry the number. The wider context sits in SaaS growth marketing.