Should I Focus on One App or Keep Building New Ones?
For Solo indie hackers with multiple small SaaS apps · Based on SF Founder Clarity: Bootstrap vs. VC Decision Framework
// TL;DR
If you are an indie hacker with several small SaaS apps generating modest revenue, this framework helps you decide whether to consolidate around one product, continue building sequentially, or raise capital for the strongest candidate. It matches the decision to your personality type (deep-focus vs. multitasker), tests each product for market pull and problem obsession, and uses the two-way door principle to keep your options open. The default is to stay bootstrapped and go sequential until one product shows unmistakable traction.
Should I focus on one SaaS app or keep running multiple products?
The answer depends on your personality, not on a universal rule. The SF Founder Clarity framework divides founders into two types: deep-focus obsessives who lock onto one thing and sequential multitaskers who thrive across projects. If you are the first type, pick the product with the strongest market pull and go all in. If you are the second type, run your portfolio sequentially — commit to one idea at a time, give it 1–3 months of focused effort, and kill it ruthlessly if you do not feel the market pulling it toward customers.
The critical mistake most indie hackers make is running a true parallel portfolio. Spreading attention across three or four live products means you never get obsessed enough to run circles around competitors in any single market. AI tooling may make some parallelism more viable, but be honest about whether you are actually an exceptional multitasker or just avoiding the discomfort of going deep.
How do I know which app to double down on?
Run the Problem Obsession Test on each product. Ask yourself: which of these problems would I happily work on for 5–10 years? The one that passes this test is your candidate for focus. Then check for market pull — is one product seeing customers arrive more easily, convert faster, or generate more organic word-of-mouth? Market pull is felt, not measured. If you are not feeling it after 1–3 months of focused effort, that is your signal to pivot.
Next, apply the 'Can You Name One?' filter. Can you name a bootstrapped company that achieved similar ambitions in the same category? If yes, the bootstrapped path is proven. If no, consider whether the market dynamics require capital to win. Finally, assess the competitive landscape: are well-funded competitors already attacking this space? If so, bootstrapping into third place in a winner-take-all market is nearly impossible.
When should an indie hacker consider raising money instead of bootstrapping?
Bootstrapping is the default because it preserves the two-way door — you can always raise later. Consider raising only when three conditions align: your problem obsession is genuine (10-year commitment), the market is large enough for a venture-scale outcome, and well-funded competitors make capital a competitive necessity.
Before raising, validate stickiness first. Plot your retention curve and find the elbow — the point where retained users stop churning. If you cannot identify this, raising money will only hide a broken engagement model behind VC dollars. The Sound Business Model Test is one of bootstrapping's greatest advantages: if your business survives on revenue, you know the model works.
What should I do right now?
Rank your apps by market pull. Run the problem obsession test on the top candidate. If it passes, check market size and competitive landscape. If everything points to focus, put the other apps on autopilot or sell them. If nothing passes, continue the sequential portfolio approach but commit to faster kill decisions. Start watching five real users interact with your top product qualitatively — this will tell you more than any dashboard at this stage.
// FREQUENTLY ASKED QUESTIONS
How long should I give a SaaS app before killing it?
Give each idea 1–3 months of focused effort. If you are not feeling market pull — customers arriving easily, organic interest, immediate revenue movement — that is the signal to pivot. When you land on the right idea, traction is not subtle. Founders who have found product-market fit describe it as unmistakable. Extending the timeline past three months without clear pull is usually just avoiding the emotional pain of letting go.
Can I run a portfolio of SaaS apps and still raise VC for one?
Yes, but investors will expect you to go all in on the one they fund. Running a portfolio is a discovery phase — it helps you find the product with the strongest market pull. Once you identify that product and decide to raise, you will need to shut down or hand off the others. VCs invest in founders who are perpetually dissatisfied and obsessively focused, not founders splitting attention across multiple products.
Should I track revenue or engagement metrics for my indie SaaS apps?
Track engagement and retention before revenue. The correct order is engagement → retention → activation → growth → monetization. Revenue is the last metric that matters. Early on, use vibes-based evaluation — watch five users interact with your product qualitatively. Only build formal measurement systems once you have established stickiness and cannot tell qualitatively what needs fixing. Premature dashboards create false confidence and slow you down.