One hour of structure a week. Without it, urgency picks your priorities — and urgency always picks support tickets over the work that compounds.
A solo founder operating cadence is a fixed weekly rhythm that decides what gets attention before the week starts. Without one, urgency chooses for you — and urgency always chooses support tickets and small bugs over the work that grows the business.
One hour of structure a week. The point is not productivity — it is preventing four months of drift.
The cost of having no cadence is not lost hours. It is that a quarter passes and the same bottleneck is still there, because it was never anyone's job to notice.
Thirty minutes. Look at four numbers and nothing else.
| Number | What it tells you |
|---|---|
| MRR, and the change from last week | Direction |
| New signups | Whether the channel is running |
| Activation rate | Whether signups reach value |
| Cancellations, with reasons | Whether the leak is growing |
Four numbers, not twelve. A dashboard with twenty metrics gets read once and then ignored, because scanning it produces no decision.
Then write one sentence: the single thing that matters this week. If you cannot write it without using "and", you have not chosen yet.
The priority gets the first working block of each day, before email, before support, before anything reactive.
This ordering matters more than the number of hours. Reactive work expands to fill whatever time it is given, and it always feels more urgent than the thing that compounds. Support answered at 2pm rather than 9am costs you almost nothing; growth work perpetually deferred to "after the inbox" costs you the quarter.
Two habits, thirty minutes total, and they are the highest-return part of the week.
Talk to one customer. Any customer, any format. A message thread counts. Doing this weekly means fifty conversations a year, which is more customer contact than most funded companies manage per founder. The interview guide covers what to ask.
Write one thing down. What you learned, what changed, what you decided. Two sentences. The value is not the note — it is that in three months you can see whether you have been circling the same problem.
Sixty minutes once a month, checking that your weekly priorities have been pointed at the actual constraint.
The failure this catches is consistency in the wrong direction. Four weeks of disciplined work on acquisition while the real problem was activation feels like progress and produces none. Work through the five pillars in the Ghost OS framework and confirm the bottleneck has not moved.
Whichever pillar you cannot describe specifically is usually where the constraint now sits. That check takes ten minutes and redirects the next four weeks.
The Operator plan sends a Monday digest with your four numbers and the week's recommendation, so the cadence runs without you remembering it.
See the plans →Three predictable causes, all fixable.
Too many numbers. A twenty-metric review gets skipped by week three because reading it produces no decision. Four numbers that each imply an action survive.
No decision attached. A review that ends without one named priority is a status update to yourself. The output of Monday is a sentence, not a feeling.
Scheduled at the wrong time. A Friday afternoon review competes with wanting the week to end. Monday morning, before the inbox, is the slot that survives contact with reality.
If you have one hour a week for structure, spend all of it on Monday. The review that sets direction is worth more than the retrospective that records what happened.
Below $1k MRR, the Monday number that matters is conversations, not MRR — see the $0 to $1k playbook. Revenue at that stage moves too slowly to steer by weekly.
Between $1k and $10k, activation and churn become the numbers that decide whether growth continues; that playbook covers the four shifts to work through. Past $10k, the weekly review shifts toward what can be removed rather than added — scaling without hiring covers that.
A fixed weekly rhythm that decides what gets attention before the week starts: a thirty-minute Monday review of four numbers ending in one named priority, that priority taking the first block of each day, and a short Friday customer conversation.
Four: MRR and its weekly change, new signups, activation rate, and cancellations with reasons. Four numbers that each imply an action survive as a habit; a twenty-metric dashboard gets read once and then skipped.
Monday morning, before the inbox. Friday afternoon reviews compete with wanting the week to end and get skipped. The review that sets direction is worth more than the retrospective that records what happened.
Three causes: too many numbers, so reading them produces no decision; no decision attached, so it becomes a status update to yourself; or scheduling at a time that competes with something else. The output of a review should be one sentence naming the week's priority.
About an hour a week — thirty minutes on Monday, thirty on Friday — plus an hour once a month to confirm the priority still points at the real constraint. The point is not productivity but preventing four months of consistent work in the wrong direction.
Bring your four numbers. Marcus names the week's priority and tells you what to defer until it is done.
Try GhostCoach free →14-day free trial · cancel anytime · 30-day money-back on Lifetime