Should Solo Devs Focus or Run a Portfolio of Apps?

Why do multiple small SaaS apps make you feel scattered?

Running three or four apps that each generate modest revenue is a classic solo-dev trap. Each one demands maintenance, none gets your full obsession, and you can't tell which deserves your future. The framework's first move is to stop treating this as a resource-allocation problem and start treating it as a self-knowledge problem. The choice between a portfolio and focused deep work is personality-based — not universally answerable. You have to know yourself first.

How do you decide which app to focus on?

Run the Problem Obsession Test on each app. Ask: which of these problems do you genuinely care about, and would you be happy working on for 5–10 years? The most impactful software gets built because founders care deeply about the problem, not because the app happened to make a little money. The app you'd still be excited about in a decade is your focus candidate.

Then check for market pull. When you're on the right idea, revenue takes off immediately — it's not subtle. If one app is quietly pulling users and revenue toward it while the others require you to push, that's your signal. The absence of market pull is the signal to pivot away ruthlessly.

Should you focus or run a sequential portfolio?

Now apply the personality test honestly. Are you a deep-focus obsessive who locks onto one thing, or a genuine multitasker? If you're an obsessive, spreading across a parallel portfolio costs you the very thing that wins: the obsession needed to run circles around competitors. Pick the app with the most market pull, and kill the others or put them on autopilot.

If market pull is genuinely unclear across all your apps, that's a legitimate reason to run a portfolio — but run it sequentially, not in parallel. Commit fully to one, kill it fast (within 1–3 months) if traction doesn't appear, then move to the next. AI tooling may make true parallelism more viable than before, but only if you can honestly multitask. Most solo devs can't, and pretending otherwise means none of the apps ever gets obsessive attention.

What should you optimize once you've picked one?

Follow the strict order: engagement → retention → activation → growth → monetization. Solve stickiness first. Build something people organically rely on, not just something they test. Watch five real users qualitatively — early on, vibes-based observation beats any dashboard. Once you have some users, plot a retention curve and find the elbow where it flattens. Identify the behavioral threshold that predicts crossing that elbow — that's your north star metric, not revenue.

Do you ever need to raise money?

Probably not as a default. Bootstrapping is the right fit for most solo SaaS work because it keeps the two-way door open and passes the Sound Business Model Test — surviving on revenue alone proves your model works. But if one of your apps turns out to solve a venture-scale problem in a market where well-funded competitors will inevitably enter, run the Can You Name One? filter. If you can't name a bootstrapped company of similar ambition, capital may be required.

Next step: List your apps, run the Problem Obsession Test on each, then honestly type your personality. If you're an obsessive, commit to one this week and put the rest on autopilot.