Strategic Growth Hacking for solo founders
Strategic Growth Hacking is a four-phase cycle: analyze, hypothesize, prioritize, test. Built for cross-functional growth teams, it works even better solo — because you already are cross-functional. Here's how to run it every week.
Strategic Growth Hacking (SGH) is a framework developed by growth operator Mari Luukkainen and used in hundreds of startups across the Nordics and Baltics, including Freska, Yousician, and Paxful. Its core claim is simple: high-growth companies don't have magic tactics. They have a systematic testing process they repeat every week, for years.
The framework was written for companies building a growth team. But its engine — a weekly cycle of analysis, hypothesis, prioritization, and testing, tied to one clear goal — needs no team at all. As a solo founder you skip the hardest parts of SGH (cross-department buy-in, mandate battles, meeting cadences) and keep the part that compounds: finished tests and documented learnings, every single week.
The four-phase cycle
Everything in SGH hangs off one measurable goal. Pick the metric that matters most right now — revenue, signups, activation rate, retained users — and set a target. Every test you run should exist to move that number. Tests with no connection to the goal are the first thing the framework tells you to cut.
The cycle itself has four phases, repeated weekly or bi-weekly. Analysis: look at the current situation and what the last cycle taught you, and find the bottleneck. Hypothesis: propose one to three bets that could improve the metric, grounded in data or customer conversations. Prioritization: rank them by likelihood of success, cost, and scalability — ICE scoring does this job. Testing: ship the top one and finish it inside the cycle.
The word finish carries most of the weight. SGH's most common pitfall is the unfinished test — started, drifted, quietly abandoned. An unfinished test teaches you nothing. A finished test that fails teaches you plenty: the framework treats every completed cycle as a learning, and learnings are the actual output. Results compound later.
One week, one loop
The cadence is the framework. A test you can execute within a week beats a grander one that takes six, because the point is learning velocity, not any single result. If a test can't be finished in a cycle, shrink it until it can.
A weekly loop as a solo founder looks like this. Monday: look at last week's results and log what you learned. Pick the bottleneck. Tuesday: write one to three hypotheses and score them. Midweek: ship the winner. Friday: check the numbers, mark the test finished or call it inconclusive, and write two sentences about what you learned. That's the whole process. It fits in a few hours around building your product.
Expect the first weeks to feel underwhelming. SGH is explicit about this: early cycles mostly surface internal bottlenecks — missing data, missing skills, tests that were too big. Those are learnings too. The founders who win are the ones still running the loop in month six.
Communicate, even when it's just you
SGH puts unusual weight on communication. Testing looks vague from the outside — weeks can pass without visible results — so the framework prescribes a weekly report: progress toward the goal, what was tested and why, what was learned, and what runs next with a named owner.
Solo, you have no team to reassure, but the report still earns its keep. Writing the week down forces you to admit whether you finished your test, and a public or semi-public version — an investor update, a build-in-public post, a message to your community — creates the accountability a team would otherwise provide. The format stays the same: metric, test, learning, next step.
Find the bottleneck with pirate metrics
SGH uses the pirate-metrics funnel (awareness, acquisition, activation, revenue, retention, referral) to keep you honest about where the problem actually is. The job of a growth process is to find the bottleneck in the whole business, fix it, and move to the next one — not to keep testing the stage you happen to enjoy.
Most founders over-test acquisition and never test the rest. If you've run eight acquisition tests and zero retention tests, your next bottleneck is almost certainly not at the top of the funnel. Map your finished tests against the funnel stages now and then; the empty stages are where the surprises live.
Running SGH in Golden Gecko
Golden Gecko is built around the same loop, so the framework maps one-to-one. Your goal with its metric, target, and baseline is the SGH input. The playbook library covers the hypothesis phase with 200+ proven tests, each shipped with a ready hypothesis and suggested ICE scores, so prioritization is a comparison instead of a guess. The test itself tracks status from idea to finished, and when you log results, the AI analysis writes the learning — the artifact SGH says you must never skip.
The dashboard frames each week as one cycle — insights logged, ideas ready, top pick, tests running — and nudges you when a test has been running past two weeks, which is SGH's cue to call it. The Weekly Update button writes the framework's weekly report from your actual data, ready to paste into Slack or an investor email. Funnel coverage on each goal shows which pirate-metric stages you've tested and which you've never touched.
If you want the full framework — including the team-scale parts you'll grow into — it's published free at mariluukkainen.com/sgh. Start with one goal, one metric, and one test you can finish this week.
Problems this guide helps with
You can't find your first 100 users
Your product is built but you have no idea where to find users. You've told friends and family, posted on social media, and... nothing. Finding early users feels impossible. Here's the truth from founders who've done it: your first 100 users almost never come from scalable channels. They come from manual, unscalable effort. Stripe's first users came from the Collison brothers walking up to people at tech meetups and offering to install the product on their laptops right there. Pieter Levels found his first users by being active in nomad communities for years before launching Nomad List. The Indie Hackers community is full of stories where founders' first 100 users came from one Reddit thread, one Hacker News post, or one conversation in a Slack group. Stop looking for a growth hack and start doing things that don't scale.
Users sign up and disappear
Your signup numbers look good, but users vanish after day one. They create an account, maybe poke around, then never return. You're filling a leaky bucket.
Put this into practice
Golden Gecko gives you proven playbooks matched to your goals, step-by-step guidance, and AI that tells you what results mean.