The Portfolio of Bets Strategy: How Solo Founders Hit $1M ARR Without a Unicorn

TL;DR / Key Takeaways

• The "portfolio of bets" startup strategy means running multiple small products instead of betting everything on one
• Marc Lou hit $1M/year ARR this way — revenue spread across multiple micro-SaaS solving different problems
• The key discipline: kill fast, ship small, and never let your loudest customer dictate your roadmap
• This post breaks down how the strategy works, why it beats the all-in approach for solo founders, and the specific signals I use to decide when to double down

Most startup advice is written for founders who raised money.

Raise a round, pick a market, go all-in, hire fast, grow or die. That playbook makes sense when you have investors who need a 100x return and a board that expects quarterly updates.

It makes almost no sense if you're building alone and trying to reach $1M ARR without burning through savings.

The portfolio of bets startup strategy is different — and it's producing real results. Marc Lou recently crossed $1M/year ARR not from a single breakout product, but from a collection of micro-SaaS products each solving a specific problem for a specific audience. Pieter Levels built a $3M ARR portfolio the same way. I hit $1M ARR once. The approach I used looked a lot more like this than the VC playbook.

Here's what the strategy actually means in practice, and why it works.

What "Portfolio of Bets" Actually Means

It doesn't mean building 10 things at once and hoping one sticks. That's just chaos with extra steps.

The portfolio of bets startup strategy means:

1. Ship one thing quickly — small, focused, solving one real problem
2. Measure real signal — paying users, not compliments
3. Kill fast or double down — based on that signal, not gut feel
4. Repeat — with what you learned from the last bet

Each product is a bet. Some bets fail. Some break even. A few pay off. The aggregate is what matters.

This is fundamentally different from the "one big idea" approach, where you spend 18 months building something before you know if anyone will pay for it.

Why It Works for Solo Founders Specifically

The portfolio model has structural advantages for a one-person team that don't apply to funded startups.

You can't afford to be stuck. A funded company can spend 6 months iterating on a product that isn't working because there's runway to burn. A solo founder who spends 6 months on the wrong thing just lost 6 months. The portfolio model forces you to make go/no-go decisions faster — because you have other bets to place.

You learn faster across markets. When you run a single product, you optimize for that product's feedback loop. You get good at understanding one customer segment. When you run multiple products, you develop pattern recognition across different markets, different price points, different acquisition channels. That compounding insight is worth more than any individual product.

Failure has a lower floor. If your one product fails, you're starting over. If one bet in a portfolio fails, you move to the next one with better information than you had before. The psychological difference matters more than people admit.

The Trap: Saying Yes to the Loudest Customer

The fastest way to kill a micro-SaaS on the path to $1M ARR is building exactly what your loudest customer asks for.

I learned this the hard way. Early in building my first SaaS, I had a customer who was vocal, enthusiastic, and gave detailed feature requests. I built most of what they asked for. Three months later, I realized they were an edge case — their workflow was unusual, their needs were specific to their industry, and the features I built for them had almost no adoption from anyone else.

The portfolio model gives you a forcing function against this trap. When you have multiple bets in flight, you simply don't have the bandwidth to over-invest in one customer's edge cases. You're forced to ask: does this feature matter to 10 different customers, or just this one?

The discipline of saying no is a core skill, not a failure. The path to $1M ARR isn't built on yes.

How to Read the Signal: When to Double Down

The hardest part of the portfolio strategy isn't building the products. It's deciding which ones deserve more investment.

Here's the signal hierarchy I use:

1. Unsolicited payment — Someone pays before you've even asked. This is the clearest signal in existence. It means the problem is real enough that they didn't wait for you to pitch them.

2. Repeat usage without prompting — They come back on their own. Not because you emailed them. Not because you added a feature they requested. They just keep showing up.

3. Word of mouth you didn't engineer — Someone refers a friend without a referral program. This means the product is solving the problem well enough that they're willing to stake their reputation on it.

4. Specific, unsolicited feedback about what's missing — Not "this is great" but "I wish it could do X because I'm trying to do Y." This tells you the problem space is real and they're invested enough to think about it.

If you're getting signals 1 and 2, double down. If you're only getting compliments, kill it and move on.

The Mechanics: How to Run Multiple Bets Without Losing Your Mind

The portfolio approach only works if each product is genuinely small. Here's how I think about scope:

Time-box the first version. If you can't ship something testable in 2-4 weeks, the scope is too big. Cut it until it fits. The goal of the first version is to get to signal, not to build a complete product.

Separate the codebases, share the infrastructure. Authentication, payments, email — build these once as reusable modules. Each new product plugs into the same stack. This is where being a technical founder compounds: your second product takes half as long as your first because you're not rebuilding the plumbing.

Set a kill threshold before you start. Before you build anything, decide: if I don't hit X paying users in Y weeks, I'm moving on. Write it down. The threshold keeps you honest when you're emotionally invested in something that isn't working.

Don't context-switch daily. Run one product in "active building" mode at a time. Others are in maintenance mode. This isn't about focus — it's about the cognitive overhead of switching between different customer contexts.

The Multilingual Multiplier

One underrated advantage of the portfolio approach: each product you build is an opportunity to capture international SEO.

I run mynameisfeng.com in 23+ languages. A recent case study showed REVIEWS.io achieving a 120% increase in German traffic simply by implementing automated hreflang tags. Polaar generated 39% international revenue growth through AI-powered localization.

For each product in your portfolio, you're not just competing in English. You're competing in Japanese, Spanish, German — markets where English-only competitors don't exist yet. This is a structural advantage that compounds over time as each product builds its own international search presence.

What Marc Lou Got Right

Marc Lou's $1M ARR milestone is instructive not because of the number, but because of the architecture behind it.

His revenue isn't concentrated in one product. It's spread across multiple bets, each solving a real problem for a specific audience. Some products are small. Some are bigger. The portfolio as a whole is resilient in a way that a single-product company isn't.

He also built in public throughout — not as a marketing tactic, but as a feedback mechanism. Every post about what he was building attracted the exact audience he was building for. The content and the product compounded together.

That's the model. Not one big swing. A series of small, informed bets, each one smarter than the last.

FAQ

How many products should I run at once? For a solo founder, one in active development, one or two in maintenance mode. More than that and you're not running a portfolio — you're running a chaos operation.

When do I stop running a portfolio and go all-in on one product? When one product is generating enough revenue to justify full attention — typically when it's producing 60-70% of your total portfolio revenue and showing clear growth trajectory. At that point, the portfolio has done its job: it found the winner.

What if none of my bets are working? That's signal too. If you've run 4-5 bets and none have produced paying users, the problem isn't the products — it's the customer selection or the problem definition. Go back to customer discovery before building the next one.

Does this work for AI products specifically? Yes, and AI actually accelerates the model. With LLM APIs commoditizing the hard parts of AI, you can ship a working AI product faster than ever. The limiting factor is finding the right problem, not building the solution.

How do you handle marketing across multiple products? Shared infrastructure where possible. A personal brand (like this blog) that covers the space broadly and funnels readers to specific products based on their interests. Each product doesn't need its own marketing engine — the portfolio brand handles discovery.

The portfolio of bets startup strategy isn't a hedge against commitment. It's a structured way to find what's worth committing to.

The founders hitting $1M ARR without VC money aren't betting on one idea. They're running a process — ship, measure, kill or double down, repeat — until the signal is undeniable.

That's the game.