How to Build Your Second Product While Your First Is Running

The founders who build lasting income as independents rarely rely on a single product. But starting a second product while running the first is a genuine operational challenge. Here is how to do it without one cannibalizing the other.

First: systemize the first product

Before you start anything new, the first product needs to run without your daily involvement. This means documented support workflows, automated monitoring, and a customer base that is stable enough to survive a month of reduced attention. If the first product falls apart the moment you look away, it is not ready to be left alone.

Start the second product in the gaps

You do not need a new block of dedicated time — you need to use the time between first-product tasks. Early mornings, weekends, or the 2 hours between support tickets are enough to build a validation experiment. The second product should start as a research project, not a building project.

Keep them related if possible

Products that share a customer base, a distribution channel, or a technology stack are much easier to run in parallel. If your first product serves indie founders, your second product should probably serve indie founders too. The same audience, the same channels, and half the distribution work.

Do not split your attention equally

The first product is generating revenue. It deserves primary attention until the second product demonstrates it can do the same. A 70/30 split is often right — 70% on the running product, 30% on the new experiment.