Portfolio of small products or one big bet?

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

There is no universally correct answer: a portfolio of small products reduces single-point-of-failure risk and compounds distribution skills, while one big bet concentrates your limited hours into a shot at a much larger outcome. The right choice depends on your runway, your tolerance for context-switching, and whether your advantage comes from volume or depth. Most solo founders answer this question with vibes instead of constraints — that's the actual mistake, not picking "wrong."

The real trade-off isn't risk vs. reward

It's attention vs. optionality.

A single big bet lets you go deep: better onboarding, better SEO, better retention mechanics, because every hour you have goes into one surface area. The cost is that your entire outcome depends on one market, one distribution channel, one set of assumptions about what users want. If the bet is wrong, you find out slowly, because you don't have anything to compare it against.

A portfolio trades depth for information. Ten small products generate ten feedback loops. You learn faster which channels convert, which pricing models hold, which markets are forgiving of a mediocre UI and which aren't. The cost is coordination overhead — you're now running ten sets of metrics, ten support inboxes, ten app store listings, and the attention you give any single product is necessarily thinner.

Neither of these is "safer" in an absolute sense. A portfolio of ten neglected apps can underperform one well-run product by a wide margin. A single bet run by a disciplined founder with real distribution can outperform a scattered portfolio. The frameworks that treat portfolios as automatically de-risked, or focus as automatically superior, are both selling you something.

Questions that actually determine the answer

Where does your edge come from? If your advantage is a specific, deep skill — enterprise sales, a hard technical moat, a long-term brand — a single bet lets you fully exploit it. If your advantage is speed of execution, SEO instinct, or a knack for spotting underserved niches, that edge scales better across many small, cheap experiments than it does inside one product.

What's your actual runway, in months, not vibes? One big bet with 18 months of runway and no revenue pressure is a reasonable gamble. One big bet with 4 months of savings and a mortgage is a different risk profile entirely, even if the idea is identical. Portfolios let you generate small revenue streams while you're still figuring out which one deserves more.

Can you tolerate ambiguity for a long time? Big bets often look like nothing is happening for months before they look like something. If you need visible proof of life weekly, a portfolio gives you more frequent small wins (and losses) to calibrate against. If false signals from early traction mislead you, a single bet's slower feedback can actually be an advantage — you're not reacting to noise every week.

What does "success" mean to you financially? If you need one product to eventually replace a full-time salary and nothing less will do, a portfolio where products stay small by design may never get there — unless one breaks out and you lean into it. If you're optimizing for a stable, diversified income from your own work rather than one big outcome, the portfolio model is a more direct match for that goal.

The hybrid most solo founders actually run

Few successful solo founders are purely one or the other. The common pattern: run two or three small products to generate cash flow and learning, while treating one of them as the de facto "big bet" once it shows signal — reinvesting disproportionate time once a product's numbers justify it. The portfolio isn't the end state; it's the search function. The big bet emerges from the portfolio rather than being chosen upfront.

This only works if you can actually tell which product is showing signal early enough to reallocate. That requires looking at real numbers across every product on a consistent cadence — not vibes about "which one feels most exciting this month." For a sense of what that looks like at a larger scale, see real numbers from a 10-app portfolio.

Signals that should make you reconsider your current path

A few concrete signals, not feelings, worth watching:

• If you're running a portfolio and one product's revenue or growth consistently outpaces the rest for 2-3 consecutive months, that's a signal to reallocate time toward it, not necessarily to kill the others yet.
• If you're running one big bet and 6+ months in you still can't point to a single growing metric (signups, activation, retention, revenue — pick one that matters for your model), that's a signal to either change the approach or diversify some of your time into smaller, faster experiments while you figure out what's broken.
• If support and maintenance load across your portfolio is eating more hours than product work, you've probably taken on too many products for your current capacity — the fix might be sunsetting the weakest ones rather than adding focus to the best one. See what keeping a zombie app alive actually cost for how to think about that math, and consider defining kill criteria before you need them.

What this means in practice, week to week

If you choose a portfolio, the operational cost is real: you need a consistent way to see revenue, retention, and traffic across every product without logging into ten dashboards. If you choose one big bet, you still need to watch leading indicators closely enough to know early if it's not working, rather than finding out eighteen months in.

Disclosure: SoleOS is built by a solo founder running a portfolio of apps, so this blog writes from and about that model — take the portfolio-favoring parts of this post with that in mind. If you've made the single-bet decision, a tool built for tracking twenty products isn't your bottleneck; Stripe's own dashboard plus a spreadsheet will tell you everything you need for one product, and a dedicated SaaS metrics tool will probably serve you better than something designed for aggregating many. If you've got three or more products across web and mobile and you're spending real time reconciling numbers across RevenueCat, Stripe, and app store consoles, that's a different problem — see tracking Stripe and RevenueCat together or try the live demo to see what consolidated portfolio metrics actually look like.

Frequently asked questions

Is a portfolio of small products objectively lower risk than one big bet?

No. It diversifies revenue sources, which reduces the risk of total wipeout from one product failing, but it doesn't reduce execution risk — a portfolio run with divided, shallow attention can underperform a single well-executed product. Risk reduction only happens if each product in the portfolio gets enough attention to actually work.

How many products can one solo founder realistically run at once?

There's no fixed number — it depends on how automated each product's support, billing, and maintenance already are, and how much of your week you can dedicate to new feature work versus upkeep. A good test: track the hours you spend per product per week for a month before adding another one, and see if that number is shrinking or holding steady as the portfolio grows.

Should I kill my other products once my big bet starts working?

Not immediately. If a product is profitable and stable with low maintenance, there's little reason to shut it down even if it's not your main focus — it's still contributing cash flow. The decision to sunset should be based on its own numbers (declining revenue, rising support burden, or opportunity cost of the specific hours it needs) rather than simply being the plan B.

What metrics should I compare across products to decide where to focus?

Revenue growth rate, retention or churn, and the ratio of time spent to revenue generated are the three that matter most for a reallocation decision. Avoid comparing raw revenue alone — a product at $500 MRR growing 15% month over month can be a better bet than a flat $2,000 MRR product. See the metrics dictionary for exact formulas if you want to compare consistently across different data sources.

Can I switch strategies mid-way, like turning a portfolio into one big bet?

Yes, and it's one of the more common paths — founders often start with several small products to find signal, then concentrate time on the one that shows the clearest growth. The risk is switching too early based on noisy early data or too late out of attachment to products that have already plateaued; watching consistent multi-month trends, not single-week spikes, is the safeguard against both.