Should you focus on one product or build many?

I got asked in my replies today if I can drive four cars at the same time.

I'm sat at £0 MRR juggling 4 builds at once.

That advice was a wake up call for me.

I'm parking three of them and picking one daily driver for the next 30 days.

♥ 25 · the post on X

Yes!

A great founder shouldn't get attached to their ideas.

And don't work on more than 2-3 at most at the same time.

If you want to start a new one and you're handling 3 already, kill one before you start on new one. Believe me on this!

♥ 3 · the post on X

"i'll just build another app" is the easiest way to avoid doing the hard thing

and the hard thing is: market the apps you already built

i have a new language learning app that needs content, consistency, tiktok posts, instagram reels

i have animalworldmap(.)com, a website with traffic that needs to be monetized

and my brain's response to all of that was... "what if i started something new" but no

today i work on what already exists
grow it, market it, monetize it, or die trying

new ideas can wait
execution on old ones can't

♥ 2 · the post on X

Nobody knows how hard I'm fighting my own brain every day.

Not because I don't have ideas.
Because I have too many.

Every few days, a new idea shows up that feels impossible to ignore.

"Build this."
"This could be huge."
"Why isn't someone solving this?"
"Maybe this is the one."

And that's exactly the problem.
It's easy to start things.
It's much harder to keep building the one thing you already chose.

So I made myself a rule:
100 paid customers for Solandra. Nothing new until then.

No matter how interesting the next idea looks.

Because while building Solandra, I keep noticing something about customer support:

Everyone is building better ways for AI to answer.

But what happens when it can't?

- A customer asks something your AI doesn't know.
- A human steps in and solves it.
- The customer leaves happy.
- The conversation is closed.

And then...

What changed in your knowledge base?

Usually, nothing.

The business knows a customer asked a question it couldn't answer.

But it still has to figure out:

- What exactly was missing?
- Should we add a new article?
- Should we change an existing one?
- What part was unclear?
- Was this even a documentation problem?

And most importantly:
How many other customers are going to ask the same thing?

That's the part I'm building Solandra around.

Not just answering customer questions.

Finding the questions your business doesn't know how to answer yet - and turning those conversations into something your support system can actually learn from.

The chatbot is only the visible part.
The interesting part happens after the conversation is over.

And I have a feeling this is one of those problems people don't notice until someone points it out.

Maybe you've seen it too.

What do you think is missing from today's AI support tools?

♥ 2 · the post on X

I'm starting to realize that the biggest challenge isn't coming up with ideas or building fast. It's knowing when NOT to build.

You don't need fewer ideas. You need fewer active projects.

100 ideas in the backlog. One main bet. 🎯

the post on X