How to Run a Weekly Growth Review as a Solo Founder
A 30-minute weekly review that turns scattered metrics into one decision: what to look at, what to ignore, and how to keep it from becoming a ritual.
Published 2026-10-12 · 4 min read
A solo founder either obsesses over metrics daily, which is demoralising because nothing moves that fast, or avoids them entirely, which means decisions get made on feeling. A weekly review is the middle path: frequent enough to catch problems, infrequent enough that the numbers have had time to mean something.
This is a thirty-minute format that produces one decision, not a dashboard you glance at and forget.
Why weekly and not daily
- Daily numbers are noise. A single day's traffic or signups varies for reasons that have nothing to do with what you did. Reading them daily produces emotional decisions.
- Weekly shows a trend. Seven days smooths the noise enough that a real change is visible, and it is frequent enough to catch a problem before it costs a month.
- It matches the pace you can act at. A solo founder can realistically make one or two meaningful changes a week. Reviewing more often than you can act just generates anxiety.
- It is sustainable. A daily metrics habit burns out; a weekly one becomes part of the rhythm.
The 30-minute structure
- 1
Minutes 0-5: the five numbers
Pull the same five every week, in the same order. Activation, week-2 retention, traffic by source, cost per active user, and conversations held. Do not add numbers — five is enough and more dilutes the decision.
- 2
Minutes 5-15: what moved and why
For each number that changed, write one sentence on the likely cause. Not what you hope it means — what you actually did or what actually happened that could explain it.
- 3
Minutes 15-25: the one decision
Pick the single highest-leverage thing the numbers point to. One. Write it down as a specific action with a definition of done, not a vague intention.
- 4
Minutes 25-30: record and close
Log the five numbers and the decision somewhere you will see next week. Then stop looking until the next review. The discipline is as much about not checking as about checking.
The five numbers, and the one question each answers
| Number | Question | Act when |
|---|---|---|
| Activation rate | Do new users reach the value? | It drops, or a change you made should have raised it and did not |
| Week-2 retention | Do they come back? | It is flat at near-zero — a product problem outranking everything else |
| Traffic by source | Which channel produces users who stay? | One source clearly outperforms on activation, not volume |
| Cost per active user | Does serving them cost more than they are worth? | It rises faster than your users or your revenue |
| Conversations held | Are you still learning? | It hit zero — you have stopped talking to users, which precedes every other failure |
What to ignore
- Follower count and social vanity numbers. They move independently of your business and produce no decision.
- Total pageviews. Rises with traffic regardless of whether the product works; activation tells you more.
- Daily fluctuations. This is why the review is weekly. A bad Tuesday is not information.
- Revenue without cost, for an AI product. A revenue number that ignores your per-use cost can show growth that is actually a widening loss.
- Metrics you cannot act on. If a number moves and there is nothing you could do about it, it does not belong in a thirty-minute review.
Keeping the record
The review only produces insight if you can see the trend, and the trend only exists if you keep the record. This does not need a tool:
- A simple table, one row per week: the five numbers, the decision, and one line on what happened. A spreadsheet or even a document is fine.
- Review the trend monthly. Four weeks of rows shows whether the line is moving, which a single week cannot.
- Note the decisions, not just the numbers. Six months later, the log of what you decided and what happened is more valuable than the metrics themselves — it is a record of what actually worked for your product.
Making it stick
- Same time every week, on the calendar. A review that happens "when I have time" does not happen.
- Time-boxed to thirty minutes. An open-ended review becomes an anxious deep-dive and gets avoided next week.
- Ends with one written decision. The output is the decision, not the analysis. A review that produces no decision was not a review.
- Do not check the numbers between reviews. The whole point is to stop reacting to noise. Checking daily undoes the discipline and reintroduces the emotional decisions the weekly cadence exists to prevent.
A growth review is not about knowing your numbers. It is about making one better decision a week than you would have made by feel — and the numbers are only useful to the extent that they change what you do next.
More in Measuring growth
- How to Tell Whether Your AI Launch WorkedA launch feels like a success or a failure based on the spike, but the spike misleads. The four questions that actually tell you whether a launch worked.
- How to Reuse a Failed Launch as a Second LaunchA launch that flopped leaves feedback, a fixed product and material. How to turn a failed first launch into a stronger second one, not start over.
- The 90-Day AI Product Growth PlanA sequenced 90-day growth plan for a new AI product, tying together cold start, distribution, content and measurement into one ordered path.