I’m writing this on the last Tuesday of May, which means most of the solo founders I know are doing some version of the same thing this week. They’re looking at June, seeing thirty empty days, and quietly deciding that this time, somehow, they’ll do all of it.
I’ve done this for years. Plan a month at full capacity, ship two-thirds of it, end the month feeling vaguely behind. Then plan the next month the same way. The problem was never the months. The problem was the premise.
So this June I’m trying something different. The plan is built around 60% capacity, on purpose, before anything goes on the calendar.
This isn’t a productivity hack. It’s a planning premise.
The math behind 60%
Cal Newport’s framing of focused work has been around long enough that the four-hour figure is treated as common sense. Most knowledge workers can sustain at most four hours of deep, cognitively demanding work per day. Newport’s point was that anything beyond that is a different kind of work, not the same thing for longer. The follow-up data has been less flattering than the framing. The average knowledge worker manages around 2.5 hours of truly focused work in a working day, with the rest absorbed by context-switching, communication, and shallow tasks.
Two and a half hours. That’s the honest top of the funnel before anything subtracts from it.
Then there’s the seasonal tax. Captivate Network’s workplace research found that summer productivity drops by up to 20%, meeting attendance is missed at 19% higher rates, project turnaround stretches by 13%, and workers are 45% more distracted compared to other times of the year. That’s measured in offices with managers and routines. Solo founders feel it differently, but they feel it.
If 100% capacity is a fiction even in February, June is a fiction in italics. Plan for it.
What 60% actually looks like
The first instinct when someone says “plan less” is to imagine working fewer hours. That isn’t quite what I mean.
60% is a planning ceiling, not an hours target. The day still has its shape. The week still has its rhythm. What changes is the number of commitments that get to live inside it.
For me, that translates into something like this. Two major projects on the month’s docket, not five. One deep-work block per day, defended like an appointment with a paying client. A weekly cadence that assumes one unplanned thing will eat half a day, because one unplanned thing almost always does. Real buffer space between deliverables instead of the fictional buffer space we draw on the calendar and then fill anyway.
It also means saying yes to fewer things in advance. The standard solo-founder failure mode is to fill the calendar three weeks out, assume future-me will handle it, and then watch future-me arrive exhausted and behind. Planning at 60% leaves room for future-me to choose. That choice space is what most of my months have been missing.
There’s a version of this advice that says “block 50% of your calendar for focused work.” That’s fine as far as it goes. It still assumes the remaining 50% is fully usable. It usually isn’t. Better to plan around the smaller number and let the surplus be a real surplus when it shows up.
The objection I had to work through
The fastest pushback when I say this out loud is some variation of: but I have bills. Underplanning sounds like undermining the business.
I had the same reaction. The thing that changed my mind was noticing that I’d been shipping at 60% of my planned month for years anyway. The plan said 100%. The output said 60%. The gap got blamed on me – on not being disciplined enough, focused enough, organised enough.
The planning fallacy is older than productivity culture. Daniel Kahneman and his collaborators have spent decades documenting it: people consistently underestimate how long their tasks will take, even when they know they consistently underestimate how long their tasks will take. Knowing the pattern doesn’t fix the pattern. The fix is structural. Name the realistic capacity and plan inside it.
For solo founders, this matters more than it does for teams. We don’t have a colleague to absorb the gap. We don’t have a manager to catch the dropped piece. The Leapers 2025 Mental Health in Freelancing Report found that 68% of freelancers said stress, anxiety, or poor mental health negatively affected their ability to work in the last year, and 90% reported feeling isolated or disconnected as a self-employed professional. There’s nobody else in the room to check the math. The honest accounting has to come from us.
Underplanning isn’t underearning. It’s the difference between a month you finish standing up and one you finish behind.
Why June, specifically
There’s a separate argument for treating June as its own animal. Half your audience is at 60% too.
In northern Europe, where I work, June is when clients start trailing off. Not all at once, but visibly. Decisions slow. Email replies get longer gaps. The big launch you set live on June 15th lands in inboxes that are mentally already at the cabin. The cost isn’t only that the launch underperforms. The cost is that you spent your good June attention on something that needed to land in September.
This is the part of seasonality that solo founders tend to ignore because the calendar still technically looks open. We can work in June. The question is whether June is where the high-attention work should live.
I’d rather use June for the writing, planning, and structural work that doesn’t need an attentive audience to land. Update the systems. Edit the products. Build the next quarter’s content base. Move the big launches to late August and September, when attention comes back. A 60% June that protects September is doing more real work than a 100% June that just clogs the inbox.
How I’m building the June plan
I’m writing this partly to commit to it in public, so the honest version is this. I’m planning the month in advance, on paper, with deliberate blank space.
Two large projects, not five. The deep-work block defended first, the rest of the day arranged around it. A short list of “would be nice” items that explicitly do not have permission to migrate onto the calendar. An energy check at month-end that asks one question – did the plan match what actually happened? – before the next month gets built.
I don’t have ten months of data on this yet. What I do have is the comparison. Previous Junes, planned at 100%, ending with the same residual feeling of being slightly behind on phantom obligations. The honesty of a 60% plan removes that residual feeling, because the plan and the reality stop being two different documents arguing with each other in the background.
Where this goes next
The harder version of this question isn’t “how should I plan June.” It’s “what is my actual sustainable capacity across the year, without lying to myself about it?” That’s what an energy audit forces you to look at.
If you want a starting structure for that work, the Solo Founder’s Energy Audit walks through it. Same logic as this essay. Count what you actually have, not what the calendar pretends you have.
FAQ
Is 60% just a number, or is there research behind it?
It’s a working planning premise, not a hard finding. The numbers behind it are real: roughly 2.5 hours of focused work per knowledge-worker day, summer productivity dropping by up to 20%, and the planning fallacy that consistently overestimates throughput. 60% is what falls out when you stop planning around fiction.
Doesn’t this just mean I’m working less?
No. The day keeps its shape. What changes is how many commitments live inside it. A 60% capacity plan tends to ship as much real work as a 100% plan – the difference is that you don’t end the month feeling behind on phantom obligations that were never going to fit.
What if my clients won’t accept a slower summer?
Most won’t object, because most clients also experience summer the same way. Captivate Network’s workplace research found 45% more distraction during summer months. Your clients aren’t immune. Plan around their real attention, not their stated availability.
How is this different from time-blocking?
Time-blocking assumes the surrounding time is fully usable. A 60% capacity plan treats the surplus as buffer, not as a hidden second shift. The blocks still work. They just live inside a smaller, honest container.
