I stepped away from this blog for a few weeks. Not because I ran out of things to say, but because I finally had one thing to say. I picked a single app to build, closed every other tab, and the difference showed up faster than I expected.
That's the whole argument of this post. Most indie hackers running five projects at once aren't being strategic. They're gambling, throwing ideas at the wall and hoping one sticks before the runway runs out.
Read also: You need 18 months of runway before you quit your job
The tax nobody puts on your bill
Shipping fast isn't the problem. AI tools made it trivially easy to spin up several products in a month, and that speed convinced a lot of builders that more surface area means more chances at revenue.
It doesn't work that way. Every project you're running charges rent, whether you're touching it today or not. Technical debt piles up quietly in the background. But the higher cost sits upstream of that, and it's cognitive.
Every time you switch from one project to another, your brain has to reload context.
What was I building?
Why did I make that decision last week?
What's still broken?
That reload isn't instant, and it isn't free. Do it a dozen times a day across a dozen projects, and you've spent your best hours re-orienting instead of producing.
Fewer projects finish more
I've watched this pattern in my own work for two decades, and the personal version of it is blunt:
I lose the thread. Each switch means reconstructing where I left off, and half my "working" hours go into rebuilding yesterday's thinking instead of extending it.
I stall before I start. Ten open projects means ten small decisions before I've written a line of code. One project removes the decision entirely.
I finish things. With one target, I ship it, instead of leaving six things at eighty percent, which feels worse than three things done.
My work holds together. What I decide on Monday reinforces what I decided on Friday, because there's only one thread to keep straight.
It's also why single focus feels less stressful than juggling everything. Your brain isn't holding six open loops at once.
What deep work buys you
Deep work needs focus, obviously, but the part people miss is where good ideas come from. They rarely show up in the first five minutes of sitting down.
They show up after you've sat with the problem long enough that the easy answers are exhausted and you're forced into something better. You don't get there switching contexts every ninety minutes.
Uninterrupted time isn't a nice-to-have for creative or complex problem-solving. It's the mechanism.
There's a quieter payoff too: fewer careless mistakes. Most of what looks like carelessness is attention split across contexts it shouldn't be split across.
Multiple goals, one priority
None of this means picking a single goal for life. You can care about five things. What you can't have is five things you're prioritizing at the same moment, because priority by definition means one thing outranks the rest.
Ten priorities is the same as none. The skill worth building isn't time management. It's deciding, on purpose, what you're not touching today.
That's harder than it sounds. Everything feels urgent when you run your own company, and nobody's telling you what matters.
Single focus forces the question you'd otherwise dodge: if I could only move one thing forward this week, what would it be? Answer that honestly, and the rest of the list stops mattering as much as it did an hour ago.
Know your own limits
Single-tasking isn't a mode you run at full intensity forever. It works because it channels your energy, and energy still has a ceiling. I've pushed through stretches of deep focus that felt great for two weeks and then hit a wall in week three, because I ignored the signs that I needed to stop.
Recognizing your limits is part of the discipline, not a break from it. Build in the pause before you need it, not after you've already burned out. A focused sprint followed by a real break beats a focused sprint that never ends.
The industry keeps selling productivity as a systems problem: more tools, better workflows, smarter task managers.
Most of the time it isn't a systems problem. It's a decision problem. The builders I respect most aren't the ones juggling the most projects. They're the ones who know exactly what they're ignoring this month, and why.
