The Solo Founder Weekly Review That Actually Sticks
⏱ 7 min read
TL;DR
- What it is: a solo founder weekly review is two 15-minute bookends — a Monday plan and a Friday lookback — plus a decision log that survives the week.
- Who it's for: anyone running a business alone — part of the bigger picture in AI for solo founders.
- How it works: the review replaces the manager, the standup, and the meeting rhythm a team would force on you. AI removes the friction that kills it.
- Bottom line: weekly reviews die from friction, not from lack of willpower. Cut the friction to near zero and the habit holds.
What is a solo founder weekly review?
A solo founder weekly review is a short, fixed rhythm that replaces the structure a team would give you: a Monday plan (three priorities, fifteen minutes), a Friday lookback (what moved, what didn't, what you decided and why), and a running decision log. It works because it's small enough to survive a bad week and structured enough to compound — each Friday feeds the next Monday, and the decision log becomes the institutional memory a one-person company otherwise doesn't have.
Best for: founders whose Mondays start in fog — the ready-made version is the weekly-operating-cadence skill in the Solo Founder Skills Pack.
The solo founder weekly review is the highest-leverage habit in a one-person business, and the most commonly abandoned one. Almost every founder has started one. Almost every founder has quietly stopped by week three. The problem was never discipline. It was that the review cost more than it returned — a blank template, twenty minutes of "what did I even do this week?", and no memory of why last month's decisions were made.
Why weekly systems die when you work alone
On a team, the operating rhythm is enforced by other people. The standup happens because five people showed up. The weekly business review happens because it's on six calendars. Alone, every ritual is opt-in — and anything opt-in loses to a customer email at 8:04 on Monday morning.
So the design goal for a solo review is different from a team's. It's not thoroughness. It's survivability. The version that sticks is the version that costs fifteen minutes on the worst Monday of the quarter.
Key insight: big companies run weekly business reviews with dashboards and a room full of people. The discipline transfers to a team of one — the machinery doesn't. Keep the rhythm, shrink the machinery. That's the adaptation the whole system turns on.
The three artifacts
A working solo review produces exactly three artifacts. Not a productivity system. Not a second brain in fourteen linked databases. Three small documents:
- The Monday plan. Three priorities for the week, each tied to a business outcome, plus the one thing that must be true by Friday. If a priority survives from last week untouched, it gets named as stuck — not silently re-listed.
- The Friday lookback. What moved, what didn't, and why — in that order. The "why" on what didn't move is the whole value. Three honest sentences beat a page of retrospective theater.
- The decision log. Every non-trivial decision, one line each: what you decided, when, and the reasoning. This is the artifact solo founders skip and most regret skipping — six months later, "why did I price it that way?" has an answer.
Before and after, honestly
| Moment | Without a review rhythm | With one |
|---|---|---|
| Monday, 9am | Fog. Inbox decides your week. | Three priorities, already written. |
| Wednesday detour | Untracked. The week quietly reroutes. | Weighed against a plan that exists. |
| Friday, 5pm | "Busy, I think?" | Moved / didn't move / why — on paper. |
| Six months later | "Why did we do that?" | The decision log answers. |
Where AI changes the survival odds
Here's the friction math. Hand-run, the review costs 30–45 minutes plus the willpower to start from a blank page twice a week. That's the cost that kills it by week three.
An installed AI skill collapses the cost. Say "plan the week" and it opens the Monday template pre-filled with last Friday's lookback and the stuck items. Say "Friday recap" and it walks the three questions and appends to the decision log. You're editing, not composing — and the trigger is a phrase you'd say anyway, not a template you have to go find. That active-vs-passive difference is the same reason skills beat prompt packs everywhere else, which we cover in Claude skills for founders.
The weekly-operating-cadence skill in the Solo Founder Skills Pack ships exactly this: a Monday plan template, a Friday lookback, an async standup format for when you add collaborators, and a decision log that survives the week — big-company weekly-review discipline, adapted for a team of one.
Make the review self-starting
The Solo Founder Skills Pack ($79, one-time) includes the weekly operating cadence skill — it triggers on "plan the week," "Friday recap," or "weekly review" — plus five more skills for the other founder jobs that keep slipping. Deploys in about 20 minutes.
Get the Solo Founder Skills Pack — $79 →The money check that belongs in the loop
One addition worth making once the rhythm holds: a monthly money check. The Friday lookback tells you whether the work moved; it doesn't tell you whether the company can afford next quarter. Once a month, refresh the runway model as part of the review — cash, burn, months left, and whether the trend is default-alive or default-dead. It's a 20-minute job with the right setup, and we walk through it in solo founder runway.
Decision Guide
Use this rhythm if: you work alone, Mondays start reactive, and you've abandoned at least one review system before.
Skip it if: a team or a co-founder already enforces a working weekly cadence — don't double-book the ritual.
Best first step: this Friday, write three sentences: what moved, what didn't, why. That's the whole entry fee.
FAQ
How long should a solo founder weekly review take?
About fifteen minutes Monday and fifteen Friday. If it regularly takes longer, the format is too heavy and it will die — cut it back to three priorities, three questions, and one-line decisions.
What should be in a Monday plan?
Three priorities tied to business outcomes, the one thing that must be true by Friday, and an honest flag on anything carried over from last week. Not a task list — your task manager already has one.
What is a decision log and why keep one?
A running list of non-trivial decisions: what you decided, when, and why, one line each. Alone, you have no colleague who remembers the reasoning. The log is that memory — it stops you re-litigating settled questions and shows patterns in your own judgment.
Why do my weekly reviews keep failing?
Almost always friction, not willpower. Blank templates, too many questions, and no connection between weeks make the review cost more than it returns. Shrink it, pre-fill it, and tie Friday's output to Monday's input.
Can AI run the weekly review for me?
It can run the structure: open the template pre-filled, walk the questions, keep the decision log. The honest answers are still yours. That split — AI carries the format, you carry the judgment — is what makes the habit survivable.
What triggers the weekly cadence skill?
Ordinary phrases like "plan the week," "Monday plan," "Friday recap," or "weekly review." No menu to remember — the skill loads itself when the request matches, which is exactly why it sticks where templates don't.
The manager you don't have, for $79
Six self-loading skills, including the weekly cadence that keeps the other five on schedule. One-time purchase, 30-day refund.
Get the Pack →