Solo founder burnout is trending again. Every week, someone posts the same story: too much to do, too little time, grinding to a halt.
But after running 4 SaaS products simultaneously this year, I think we're diagnosing the wrong problem.
The burnout conversation is stuck on hours
Most burnout posts read like time management problems. "I work 80-hour weeks." "I have no weekends." "I can't switch off."
And sure, those things are real. But I've watched myself work a calm 45-hour week and still feel completely fried by Thursday. And I've pushed hard 60-hour weeks that felt energizing.
The difference? Attention quality — not time quantity.
What I'm actually dealing with this week
Right now I'm building ListingVid (AI video for real estate agents), OhMyLead (lead gen for indie hackers), EST8 (real estate CRM), and AIAnswer.to (a WordPress SEO plugin for AI citations).
Each one is alive. Each one has users asking questions, features half-finished, and a roadmap that makes sense on paper.
This week I did deep UI work on ListingVid during the morning — the kind of work that requires actual thinking. By noon I was context-switched into OhMyLead onboarding emails. By 3pm I was debugging an EST8 integration. By 9pm I was answering AIAnswer.to waitlist questions.
All of it was productive by time-tracking standards. Zero of it felt like good work except the morning.
The burnout didn't come from the hours. It came from burning my sharpest attention on ListingVid, then expecting to do equally sharp work on everything else.
Attention is the actual finite resource
Time is easy to manage. Attention isn't.
Every founder gets the same 24 hours. But you only get a few hours of actual high-quality thinking per day — the state where hard decisions feel clear and good code happens. After that, you're running on fumes, doing admin, responding to Slack, shipping things you'll regret.
When you're running multiple products solo, the danger isn't overwork. It's distributing your best-thinking windows so thinly that nothing gets the version of you that actually moves the needle.
I've seen founders with fewer products burn out harder than me — not because they worked more, but because everything got the same priority, so everything got mediocre attention.
What I'm doing about it (imperfect, but working)
- One product gets the morning slot. Rotating weekly, not daily — context switching daily is the real killer.
- The other products get maintenance mode. Async replies, small fixes, no architecture decisions.
- I track "attention debt" — if a product went 2+ weeks without my full brain, that's a red flag before it's a crisis.
This doesn't solve multi-product burnout. But it makes it legible. And legible problems are solvable ones.
Takeaways for solo founders juggling multiple things
- Burnout audit question: Is your best 2 hours going to the highest-leverage product, or the loudest one?
- Context switching daily is expensive. Even 30-minute task switches cost hours of recovery in complex problem domains.
- "Working on it" and "thinking hard about it" are different things. Most days you're doing the former and calling it the latter.
- Your products don't need equal time. They need appropriate attention at the right moments.
- The goal isn't to work less. It's to protect the hours where you're actually good.
If you're building solo and juggling more than one thing, curious how you handle the attention allocation problem — not the time one.
I'm @lmoncany on X. Building ListingVid (AI video for real estate agents) and a few other things in public.
Top comments (0)