Should I Focus on One App or Keep Building a Portfolio?

How do I know whether to focus on one app or keep building more?

The portfolio versus focus decision is personality-based, not universally correct. If you're a deep-focus obsessive who does best work when locked onto a single problem, pick the product with the strongest market pull and go all-in. If you naturally operate well across multiple tracks, run a sequential portfolio — commit to one idea fully, give it 1–3 months, and kill it if you don't feel the market pulling.

The key mistake indie hackers make is running a true parallel portfolio. This looks productive but usually means you never get obsessed enough about any one product to run circles around competitors. AI tools are making parallelism slightly more viable, but they don't change your fundamental cognitive style.

How do I decide which of my apps deserves full focus?

Run the Problem Obsession Test on each product. Which problem would you genuinely work on for 5–10 years? Then check for market pull — the felt sense that customers are arriving easily and revenue moves immediately. If one app has clear market pull and the others feel like pushing a boulder uphill, that's your answer.

Next, apply the Sound Business Model Test. Since you're bootstrapped, your surviving apps already prove they have real business models. But 'surviving' isn't the same as 'thriving.' The app where revenue is growing on its own, without you forcing it, is the one with genuine product-market fit potential.

If no app has clear market pull, that's okay — it means you haven't found the right idea yet. Keep running the sequential portfolio, but kill ideas fast. One to three months without traction is your signal to move on.

When should an indie hacker consider raising VC instead of staying bootstrapped?

Apply the framework's three filters in order. First, the market size assessment: is the opportunity large enough for a venture-scale outcome? If you're building a niche tool for a small audience, VC doesn't make sense. Second, the 'Can You Name One?' test: can you name a company with similar ambitions that succeeded without funding? If you can't, capital may be required. Third, the competitive capital landscape: will well-funded competitors inevitably enter your market?

Remember the two-way door principle. While bootstrapped, the option to raise is always open. You can decide at any point to raise money if your ambition outgrows the model. But once you raise, you're committed to pursuing a venture-scale outcome — extremely big or zero. Most indie hackers are better served by staying bootstrapped and using traction as leverage if they do eventually decide to raise.

What should I validate before making any big strategic move?

Follow the engagement → retention → activation → growth → monetization order strictly. Plot your retention curve and find the elbow — the point where users stop churning. Identify the behavioral threshold that predicts crossing that elbow. This becomes your north star metric.

Early on, use vibes-based evaluation. Watch five real users interact with your product. Are they testing it or actually using it as part of their daily workflow? The 'Use It vs. Test It' distinction is critical: stickiness is only real when people stop consciously evaluating and start organically relying on your product.

Once you have validated stickiness and can see a clear retention elbow, you have the foundation to make confident decisions about focus, scaling, or raising money.

Next step: List your current products, run the Problem Obsession Test on each, and honestly assess which one has the strongest market pull. If none do, commit to killing one this week and doubling down on testing the most promising candidate.