Working at a resturant in Lekki, while I wait for my friend to submit his visa application

I Spent Years Building Other People’s Dreams. Then I Finally Found One Worth Chasing.

For the last few years, I’ve had the privilege of helping founders turn ideas into real products.

Some of those products raised funding. Some found their first customers. Some pivoted halfway through development. Some never made it past launch.

That’s the nature of building startups.

As a software engineer and the founder of a product development agency, my job has always been to help other people bring their visions to life. I’ve spent countless hours writing product requirement documents, designing system architectures, leading engineering teams, and watching ideas transform into software that people actually use.

I genuinely love what I do.

But after every successful launch, there was always a quiet question sitting at the back of my mind.

When will I find my idea?

Not just another SaaS product.

Not another tool that solves a minor inconvenience.

Not something I’d build simply because the market looked attractive or because it could generate recurring revenue.

I wanted something different.

I wanted a problem that would still matter to me five or ten years from now.

The temptation of building “just another SaaS”

If you spend enough time in the startup world, you start noticing a pattern.

Every week there’s another opportunity.

Another AI tool.

Another automation platform.

Another idea that promises recurring revenue.

And to be honest, I’ve been tempted many times.

One of my long-term goals is to build a portfolio of software businesses capable of generating over $100,000 in monthly recurring revenue.

Maybe one of them will become a unicorn.

You have to dream a little.

Because of that goal, friends constantly send me ideas.

Sometimes it’s a late-night phone call.

“Caleb, I just thought of something.”

Other times it’s a voice note.

“We should build this.”

Or a long message explaining why this particular market is about to explode.

Most of the time, my answer has been the same.

“No.”

Not because the ideas were bad.

Many of them were genuinely interesting.

But none of them made me feel the kind of conviction I was searching for.

Deep down, I knew I wasn’t looking for the next trending SaaS category.

I was looking for a problem I’d willingly dedicate a significant part of my career to solving.

The conversation that changed everything

Yesterday evening started like any other.

My fiancée and I were making dinner together, talking about life, work, and everything in between.

Somewhere in the middle of that conversation, an idea we had discussed almost a year ago resurfaced.

At first, it was just another “remember when we talked about…” moment.

But this time, something felt different.

Over the past several months, we’d personally experienced the problem more than once.

It wasn’t theoretical anymore.

It had become real.

The more we talked, the more obvious it became that this wasn’t an isolated frustration.

It was a recurring problem that affected how we lived.

By the time dinner was over, I couldn’t stop thinking about it.

I opened my laptop.

One Google search turned into another.

Hours passed without me noticing.

And instead of becoming less convinced, I became more convinced.

For the first time in a long time, I wasn’t researching because I wanted to validate a business opportunity.

I was researching because I genuinely wanted someone to solve this problem.

Then it hit me.

Maybe that someone should be me.

This feels different

I’ve had plenty of exciting ideas before.

This doesn’t feel like excitement.

It feels like responsibility.

There’s a difference.

Excitement fades.

Responsibility stays.

I don’t know if this product will succeed.

I don’t know if thousands of people will use it.

I don’t know if it’ll become a profitable company or simply become another lesson in my entrepreneurial journey.

But for the first time, I’m okay with that uncertainty.

Because I’m no longer building something simply to increase my MRR.

I’m building something because I believe the problem deserves a solution.

If it succeeds, incredible.

If it doesn’t, I’ll know I spent my time solving something that actually mattered to me.

Building in public, for the first time

One decision became clear after that evening.

For the first time in my career, I’m going to build in public.

Not because it’s trendy.

Not because it’s good for marketing.

But because I want to document what it actually looks like to build a company from the very beginning.

The uncertainty.

The research.

The product decisions.

The mistakes.

The moments of doubt.

The small wins that nobody sees.

I hope that, years from now, I’ll be able to look back at these early entries and remember exactly how the journey began.

Maybe they’ll become a roadmap for someone else chasing their own idea.

Maybe they’ll simply remind me why I started.

Either way, I think it’s worth documenting.

What’s next

Tomorrow, I’ll share something we’ve quietly practiced at EachBlock for years.

Whenever a founder comes to us with an idea, we don’t open Figma.

We don’t write code.

We don’t even discuss technology.

Instead, we create 13 documents before a single line of code is written.

Those documents have saved our clients thousands of dollars, prevented months of unnecessary development, and forced founders, including me, to answer the hard questions before they become expensive mistakes.

I’ll walk through each of them and explain why they matter.

And this time, I’ll be using them on my own product.

For the first time, I won’t just be helping someone else build their dream.

I’ll finally be building my own.

If you’re a founder, builder, engineer, or simply someone curious about what it really takes to go from an idea to a company, I’d love to have you along for the journey.