Why indie devs are ditching single apps for 30 small bets

In 2014, the indie hacker playbook was simple: build one product, focus relentlessly, and scale to profitability. Fast-forward to 2026, and the reality has shifted dramatically. Eight solo founders now cross $20,000 per month in revenue—not by doubling down on a single app, but by running a portfolio of 30 or more small products. The strategy isn’t just a trend; it’s a response to measurable shifts in development costs, market feedback, and success rates.

The traditional "one big bet" model assumes that a single product can dominate a large market with a defensible moat. But as build costs plummeted from 400 hours to just 25 hours for a fully functional SaaS, the economics of experimentation flipped. Where founders once had one shot per year, they now have twenty. For those willing to embrace a portfolio approach, the math suggests a clear advantage.

The portfolio’s hidden advantage: speed over scale

The core argument for a portfolio isn’t philosophical—it’s mathematical. Three key trends have reshaped the indie founder’s toolkit since 2014:

• Build cost per product dropped from ~400 hours to ~25 hours, including authentication, payments, and a usable UI.
• Cost per signal fell from requiring 6–12 months of runway to just 30–90 days of testing.
• Success rate per attempt remains low (around 1 in 10 for indie SaaS), but the ability to run more experiments changes the equation.

With these shifts, the single-shot strategy—where founders bet everything on one product—now yields a paying product roughly once per decade. A portfolio strategy, by contrast, averages two paying products per year. The difference isn’t innovation; it’s iteration.

How revenue really flows in a portfolio

Portfolios don’t produce flat revenue streams. They follow a power law distribution, where a handful of apps generate the majority of income while the rest act as exploratory bets. Take Max, a solo founder earning $22K MRR across 30 apps. His revenue breaks down like this:

• Top 2 apps account for 50–70% of total revenue ($7,700–$15,400 combined).
• Apps 3–6 contribute another 10–25% ($2,200–$5,500 combined).
• Apps 7–15 generate modest returns ($220–$660 each).
• Apps 16+ are effectively rounding errors.

This isn’t a failure of the portfolio—it’s the expected outcome. The goal isn’t to make every app profitable; it’s to ship enough bets that one or two land in the power law’s top tier. Pieter Levels, who has run a 12+ product portfolio for years, has been transparent about this dynamic for years.

The kill rule: your portfolio’s survival depends on it

A portfolio without discipline is a graveyard of half-finished projects. Each abandoned app piles up maintenance debt—support tickets, dependency updates, expired domains, and broken payment integrations. The key to avoiding this trap? A strict kill rule.

The rule has three components:

1. Time horizon: Set a hard deadline before launch. For SaaS products, 30 days is standard. For content or marketplaces, extend to 60–90 days.
2. Signal threshold: Define what "success" looks like. Common thresholds include:

• 3 paying customers
• $50 MRR
• 100 active users with 20%+ stickiness

1. Kill action: Decide upfront what "killing" entails. Typical steps include archiving the repository, sunsetting the domain, refunding subscribers, and writing a postmortem.

A working kill rule removes emotion from the decision. The version of you that built the product will resist killing it—a side project after 25 hours of work feels personal. But the version of you that signed the contract enforces the rule. Without it, portfolios collapse under maintenance debt.

Should you build a portfolio? A simple calculator

Pasting the following into a spreadsheet will help you decide if a portfolio fits your situation. Inputs:

• H: Hours to ship a working version (include auth, payments, and UI).
• S: Expected success rate per attempt (default to 0.10 if unknown).
• D: Distribution multiplier (use 1.0 for cold launches, 3.0 if you have existing traffic).

Revenue potential per year = (52 / time horizon) * S * (H * hourly rate) * D

For example, if you can ship a product in 25 hours (H=25), expect a 10% success rate (S=0.10), and have no existing traffic (D=1.0), the formula becomes:

Revenue potential per year = (52 / 30) * 0.10 * (25 * hourly rate) * 1.0

Compare this to the revenue you’d expect from a single product over the same period. If the portfolio’s potential exceeds your single-product expectations, the portfolio approach may be worth testing.

The bottom line: portfolios aren’t for everyone

The portfolio strategy isn’t a silver bullet. It demands speed, ruthless prioritization, and a willingness to abandon work that doesn’t pay off. But for solo founders in 2026, the alternative—betting everything on one product—is statistically riskier than ever. The tools have improved, the costs have dropped, and the market rewards experimentation. The question isn’t whether a portfolio will work for you, but whether you’re ready to embrace its discipline.