Can a solo founder build multiple products at once?

Yes, but only with a system, not by improvising each one. What makes it survivable is: the same repeated stack so nothing is bespoke, a hard filter so you only build problems worth building, defining the outcome before the screen so each product stays pointed, explicit kill criteria so weak ones die fast, and — the real lesson — sequencing attention so products take turns being the focus rather than all demanding it at once. Without that system, multiple products just means multiple half-finished things.

How do you focus when building several products?

By redefining focus. Focus isn't working on only one thing forever — it's giving one thing your full attention at a time, and having a system that decides which thing, when. Products don't all need equal attention simultaneously; they need the right attention at the right moment. The discipline is sequencing — letting one product be the active focus while others sit stable — and ruthlessly killing anything that can't earn a turn. Spreading yourself evenly across everything is the opposite of focus, and it's how solo portfolios die.

What is the biggest mistake building multiple products?

Spreading attention evenly across all of them at once. It feels productive and responsible, but it means nothing gets the concentrated push it needs to actually move, and everything stays perpetually half-done. The fix is to accept that products take turns: one is the active focus, the others are maintained but stable, and weak ones are killed rather than kept on life support. Trying to move everything a little every day moves nothing meaningfully.

What I Learned Building Multiple Products at Once

Building several products solo taught me one counterintuitive thing above all: focus isn't doing one thing — it's a system that gives each product the right attention at the right time, and kills what doesn't earn it. I used to think a portfolio meant divided attention, and divided attention meant nothing ships. It can — but the failure isn't the multiplicity, it's the lack of a system for it. With the right disciplines, multiple products don't compete for a fixed pot of focus; they take turns. These are the lessons that made it survivable instead of a pile of half-finished apps.

Lesson 1: Sameness is what buys the capacity

You cannot hold several bespoke things in one head. The only reason a portfolio is possible is that everything runs on the same repeated stack — same deployment, same patterns, same mental model — so moving between products doesn't mean re-learning your own architecture. Every product that's special costs you the capacity to run another. Boring sameness is what creates the room for multiplicity in the first place.

Lesson 2: Products take turns

Focus isn't working on one thing forever — it's giving one thing your full attention at a time, and having a system that decides which, when. Products don't need equal attention simultaneously; they need the right attention at the right moment.

This was the real unlock. I stopped trying to move everything a little every day — which moves nothing — and started letting products take turns. One product is the active focus, getting the concentrated push that actually moves it; the others sit maintained but stable. Then the focus rotates as needs change. Spreading yourself evenly across everything feels responsible and is exactly how solo portfolios die: perpetual half-done.

Lesson 3: The filter has to be ruthless up front

More products means more chances to build the wrong one, and the wrong one costs the same solo whether it's your first or your fifth. So the idea filter gets more important with a portfolio, not less. Every product that shouldn't exist isn't just wasted — it's a permanent tax on the attention of all the others. The discipline that felt optional with one product becomes survival with several.

Lesson 4: Kill fast, or the portfolio kills you

The counterpart to taking turns is that some products don't deserve a turn. Kill criteria go from useful to essential: a portfolio with no killing is a graveyard where dead products drain the attention of the living. The hardest and most important skill in running multiple products isn't building — it's ending the ones that aren't earning their place, cleanly and without agonizing, so the attention flows to what's working.

Lesson 5: You need a portfolio view

With one product, the state is in your head. With several, you need to see them all at once — what each one is, its honest status, what it needs next. Without that view, the loudest or most recent product hijacks your attention regardless of which one actually deserves it. The products page with honest status labels isn't just for visitors; it's the discipline of looking at the whole portfolio straight and deciding where the next turn goes.

What usually goes wrong

Even spreading. Moving everything a little every day, so nothing moves meaningfully.
Bespoke everything. A special stack per product, until the maintenance burden caps you at one.
No killing. Keeping dead products on life support, quietly draining the live ones.
Loudest-wins attention. Letting the most recent or noisiest product take the focus instead of the one that earned it.

Run everything on the same stack, let products take turns rather than spreading thin, filter ruthlessly up front, kill what doesn't earn a turn, and keep a portfolio view — and building multiple products becomes a sustainable studio instead of a scatter of half-done apps. It's all one operating system, and building several products at once is what proves whether you actually have one.

Part of Building AI Products. See also my product operating system and my kill criteria for product experiments. The newsletter sends one practical build lesson every two weeks.