Most solopreneurs plan as if their best week is their average week. It isn’t.
The best week happens four or five times a year. The average week is something else. Designing capacity means planning around the version of you that turns up on a Tuesday in February – not the version that wrote January’s goals. That single move changes what fits in a week, what gets deferred, what gets deleted, and which weeks count as failures.
The shortfall compounds
When you plan to your best week and turn up an average one, the gap doesn’t stay contained. It becomes next week’s load. Next week’s load doesn’t fit either, so it becomes the week after’s. Three weeks in, you’re carrying a deficit that started as ambition.
Most solo founders don’t notice the compounding because each individual gap looks small. A missed article. A client follow-up that slipped a day. The newsletter that went out Friday instead of Thursday. The math feels manageable at the unit level. It isn’t manageable at the quarter level.
I started designing my own capacity around 60% in late May 2026, after watching three months of similar shortfall. The math wasn’t elegant. The shortfall was. Once you see the same gap show up across three planning cycles, the gap stops being about willpower and starts being about the plan.
Capacity is not time
The instinct is to define capacity as time. 168 hours a week, minus sleep, minus admin, minus client work, gives you X hours for the things that matter. The number is reassuring. It’s also wrong.
Capacity is the floor of what you’ll execute on a tired Tuesday in February. It’s not the ceiling of a fresh Monday in September. The energy you have at 9 AM after a clean weekend isn’t the energy you’ll have at 3 PM on a week with an invoice problem and a head cold.
Time treats every hour as identical. They aren’t. The first 90 minutes of focused work in your day are worth more than the last 90 minutes of dragged work. A capacity calculation that ignores that asymmetry is a calculation that consistently overestimates what fits. Tony Schwartz made a version of this argument in HBR back in 2007, and the underlying physics hasn’t changed: energy is the constraint that produces time’s value, not the other way around.
This is also why time-blocking advice fails for so many solo founders. Time blocks treat the calendar as the only constraint. The calendar is one constraint. Energy is another. Decision quality is a third. Planning around all three at once is more honest – and produces a smaller number.
Cal Newport’s Slow Productivity argues for a related shift: do fewer things, work at a natural pace, obsess over quality. The frame here is narrower and more operational: design your weekly plan around the version of you you’ll actually be, not the version you wish you were.
Plan around the bad week
The move is mechanical, almost embarrassingly so: estimate what you’d produce on your worst plausible week and plan to that.
Not your worst-ever week (a sick week, a crisis week). Your worst plausible normal week – a week with one client problem, one personal disruption, and average energy. That’s the floor. The good week is what happens on top of the floor.
For me, the floor is around 60% of what I could produce on a peak week. Three published articles instead of five. One client deliverable instead of two. The minor admin block that always gets done, plus one bigger admin item that sometimes does.
If I plan to peak-week (five articles, two deliverables, three admin items), I miss four or five weeks per quarter and rebuild from a deficit. If I plan to floor-week (three articles, one deliverable, the steady admin), I hit the plan most weeks and bank the surplus when energy is high.
The bonus weeks become real bonuses – not just relief from the catching up.
Three signals you’re overcommitting
Three patterns tell you the gap is real before you can see the deficit.
The slipped commitment that becomes “next week.” If something is moving from this week to next more than once a month, you’re not deferring – you’re planning to a capacity that doesn’t exist. Decision 3 in the four-decision frame draws the line between deferring and drift.
The constant Saturday catch-up. A Saturday on the laptop once or twice a quarter is fine. A Saturday on the laptop every weekend is a capacity problem dressed as a work ethic. You’re not behind. The plan was wrong.
The 11 PM project review. If you’re reviewing tomorrow’s plan late at night because the day didn’t go the way you’d written, your plan was too big. Late-night planning isn’t strategy. It’s the system trying to absorb the deficit.
When all three show up in the same month, your plan is at least 30% above your real capacity. The fix isn’t more discipline. It’s a smaller plan.
A capacity design move that works
The 60% heuristic is simple enough to run on a Sunday morning. List what you’d do on a great week. Multiply each item by 0.6. The number that comes out is your real plan.
Some items don’t divide cleanly. A client deliverable is binary – it ships or it doesn’t. For those, the 60% rule applies to count, not size: if you can ship two on a great week, plan for one. The second one is the bonus when energy holds.
Other items scale: writing word counts, admin batches, learning blocks. For those, 60% of the peak number is a useful first estimate. Refine it after three cycles. The number stabilises.
The third move is harder. Decide in advance what gets deleted when energy doesn’t show up. Not deferred – deleted. The common move is to keep everything by sliding it down the queue. That’s the path to the compounding shortfall. The honest move is to name the things that don’t survive a bad week before the bad week arrives.
The minimum viable system for client work, content, and admin shows what this looks like in practice – the work-block layout that protects capacity inside the actual week, not just on Sunday morning.
What changes downstream
When capacity is designed, three things shift.
The four decisions get sharper. Decision 1 (what the week is for) becomes easier because the volume of candidates is smaller. Decision 4 (what to delete) becomes routine because the bar for fitting the week is lower – fewer things fit, and the decision to cut a candidate is less emotionally expensive.
Deletion stops being failure. When the plan is built around the bad week, cutting an ambitious item isn’t a concession. It’s the design. The work that does ship becomes the work that mattered most. The work that didn’t was the surplus that didn’t survive the constraint.
The system holds on bad weeks. The bad week stops breaking the plan because the plan was built for it. Bad weeks produce the same output as designed-capacity weeks. The relationship between you and the work becomes less adversarial. You stop fighting the week.
This is the move that makes the Solo Operating System feel sustainable rather than aspirational. The frame works because the volume is honest.
The rest of the Solo Business archive – including the next pieces in this cluster – lives at the Solo Business category.
FAQ
What if my capacity is genuinely higher than 60%?
Then your floor is higher than 60%, and the heuristic shifts. Run three cycles at 60% and measure. If you consistently finish the plan with two or three days of true bonus time, raise the floor to 70% or 75%. The number isn’t sacred. The principle is: plan to the floor, not the ceiling.
Doesn’t planning low encourage laziness?
The opposite, in my experience. Planning to peak-week capacity produces shame loops and Saturday catch-up. Planning to floor capacity produces finished work most weeks and unexpected bonus output on the good weeks. Output goes up, not down.
How do I know my actual capacity?
Track three normal weeks – nothing special, no big project, no holidays. Count what shipped, finished, or closed. The average is approximately your floor. Multiply your peak-week aspirations by your floor-to-peak ratio. Across one-person operations the ratio usually lands between 50% and 70%.
What if I’m a perfectionist?
The 60% rule helps perfectionists more than anyone else. Perfectionism produces good first drafts and unfinished projects. A capacity-designed plan ships fewer drafts and finishes more projects. The constraint protects the perfectionist from their own depth.
Does this apply to seasonal businesses?
Yes, but the heuristic adjusts. A seasonal solo business has two floors – the in-season floor and the off-season floor – and they’re different numbers. Run the 60% rule against each separately. The off-season floor is usually lower than people assume, which is fine. Less output is the design during the slow part of the year.
What changes after three weeks
The first three weeks of running at designed capacity feel like surrender. Then you start finishing things. The output stops shrinking. The relationship between you and the work changes shape. The plan starts holding because it was honest.
The Solo OS Starter Kit. A printable four-part frame, a five-question audit, and a 15-minute weekly routine. Built for the version of you that turns up on a Tuesday in February. Download the kit →
