Growth hacking was never a discipline. It was marketing with a new name, sold back to founders who never had a marketing budget to begin with.
I've spent twenty years watching this pattern repeat. Someone takes an old idea, gives it a sharper name, and a whole industry treats it like a discovery.
Growth hacking is a clean example. Find something that gets attention, measure it, repeat it. That's not a hack. That's marketing with better instrumentation attached to it.
Tactics were never the problem
The term originally meant something narrower: unconventional, low-cost ways to grow a product fast, usually inside a company too early or too broke for a real marketing budget.
That's a fine idea. What happened to it since then is that nearly every tactic marketers have used for decades got folded under the same umbrella.
Growth loops, referral programs, Product Hunt launches, SEO experiments, cold outreach, landing page tests, email sequences, a "viral" feature bolted onto a product that never needed one.
Read also: Indie Devs ignore SEO, and they shouldn't
None of that is inherently bad. Every one of those can work. The problem is treating the label like it's the strategy, as if calling something a growth hack makes it more effective than calling it what it is:
An experiment in getting more people to notice your product.
I've watched solo founders burn an entire day optimizing a funnel for a product nobody wanted yet.
That's the real hidden cost of the term. It gives you permission to spend more energy thinking about distribution than building something worth distributing.
As someone who's sat on both sides of that equation, the ordering is more critical than any tactic on the list. You can't hack your way around a weak offer.
What solo builders get wrong (I think)
Most solo builders treat marketing as something that starts after the product ships. So they launch on Product Hunt, they wire up a funnel, they try to reverse-engineer whatever grew someone else's SaaS, and none of it sticks, because there's no material behind it yet.
Meanwhile they're sitting on the best marketing asset they'll ever have: the process of building the thing, in real time, with all its wrong turns still visible.
The simpler loop
Write it down instead. Build, document, publish, see what happens. That loop is simpler than any funnel, and it doesn't require inventing content for an audience that doesn't exist yet.
You already have something to talk about. Why you built it, what broke, what you changed, what a customer said that surprised you, the number that didn't move, the useless feature.
The work is the content. You don't have to manufacture it, and you don't have to pretend every post is a growth campaign, even if, in effect, it is one.
This is also where the case for documentation gets stronger the more campaigns you've watched die.
A tweet disappears in a day. A paid campaign stops producing the moment you stop paying for it. A blog post about a real decision you made keeps getting found for years, because it answers a question someone is searching for, not a keyword someone guessed at.
The trust problem
There's a trust issue too, specific to this moment in the indie space. We've all seen the MRR screenshot with the hockey-stick line, posted by someone nobody had heard of a week earlier, followed a few weeks later by a course selling the exact blueprint.
The audience has gotten sharper about calling that out. A trail that starts on day one is much harder to fake.
If someone can scroll back through eighteen months of real posts and watch a product take shape, badly at first, then less badly, that's not something a course can replicate, and it's not something you can backfill once you're already successful.
Writing about your own decisions also does something a tactic can't: it forces you to understand them. I've found this on my own personal blog, where there's a running archive of questions I've asked myself while building, including the parts where I got it wrong and had to pivot.
Documenting a decision, even badly, usually reveals what you really think about it. That's not a distribution benefit. That's a thinking benefit that happens to also produce distribution.
The label isn't the enemy
None of this means growth hacking is a scam or that the tactics don't work. Most of what gets called growth hacking is just normal business activity wrapped in more exciting language, and normal business activity is fine.
Run the SEO experiments. Test the landing page. Send the cold emails. Just don't confuse any of that with a substitute for having something worth writing about in the first place.
If you're a solo founder building more than one thing at once, documentation solves a problem tactics can't: it gives you a content engine that doesn't require a second job called marketing.
Read also: Single-tasking is better for your productivity
Growth hacking means trying things to get more users. Writing means showing people what you're already doing. Most days, that's enough, and it's usually the cheaper, more honest version of the same goal.
