The Portfolio Pattern: Why Top Indie Makers Run Multiple Products
Lessons from Marc Lou, Pieter Levels, Tony Dinh and others who refuse to bet everything on a single SaaS.
- MRR
- Combined high six figures across founders
- Users
- Indie maker community
- Founded
- Ongoing
- Team
- Solo each
- Stack
- Various
Why do the most visible indie makers run portfolios instead of one product?
Single-product risk is real. Algorithms change. Competitors appear. AI absorbs features that used to be differentiating. Customer tastes shift. A product that is the majority of revenue this year can be a minority next year.
Marc Lou’s ShipFast was once the clear center of his income. Later TrustMRR and DataFast took the lead while ShipFast continued at a lower level. Pieter Levels keeps Nomad List, Remote OK, Photo AI, Interior AI and other experiments running in parallel. Tony Dinh runs TypingMind alongside other tools. The pattern repeats among founders who have lasted more than a few years at meaningful revenue.
A portfolio does not mean random side projects. It means a small number of products that share distribution, audience, and operational knowledge, so that the failure or decline of one does not end the business.
What does a healthy indie portfolio look like?
One or two products that currently pay the bills. Several smaller products or experiments that can become the next main product. Shared distribution — usually an X account, a newsletter, or a community that already trusts the founder. High margins so that a weak quarter on one product does not create a cash crisis. And a willingness to kill or sunset products that no longer earn their keep.
The portfolio is also a learning system. Each launch teaches something about positioning, pricing, or channels. That knowledge transfers. The second and third products are usually faster to validate because the founder already has the audience and the operational habits.
Common mistakes when people try to copy the pattern
Spreading too thin before any product has real traction. A portfolio of five half-built ideas is not a portfolio; it is procrastination. The discipline is to get one product to the point where it generates meaningful revenue or clear learning, then start the next while maintaining the first.
Another mistake is refusing to start the second product because the first one “might still grow.” Growth is never guaranteed. Starting the next experiment while the first is still working is how the portfolio compounds instead of stagnating.
A third mistake is building products that have no shared audience or operational overlap. Completely unrelated products multiply support and marketing cost without multiplying leverage.
How building in public interacts with the portfolio
Public building supplies the shared distribution layer. Followers who watched one launch are more likely to notice the next. Public numbers create accountability and trust. They also make it easier to see when a product is declining so that attention can move to stronger ones.
The risk of building in public is that competitors can see what is working. The portfolio response is to keep moving. By the time a competitor copies product A, the founder is already testing product B and C.
Practical takeaway
Build an audience once. Let multiple products feed from it and feed back into it. Keep margins high and operations simple enough that one person (or a very small team) can maintain the set. Never let any single product own your entire future. The founders who are still shipping and still profitable after several years are usually the ones who treated their work as a portfolio from relatively early on.