The notebook you've been ignoring for seven years.

Mindset · 5 min read

You've got a notebook. Or a notes app. Or a voice memo you recorded driving home from work three years ago. Somewhere in there is an app idea you've been carrying around for years. Maybe five. Maybe seven. Maybe longer. You keep coming back to it. You keep refining it in your head. And you keep not doing anything about it.

I hear this story constantly. Someone sits down with me, slightly embarrassed, and says something like "I've had this idea for ages but I never knew where to start." They say it like the delay is a problem. Like they should have acted sooner. I think the opposite is true. The fact that you've been thinking about this for years is one of the strongest signals that the idea is worth pursuing.

Ideas that stick are ideas that matter

Most ideas don't survive a week. You have a shower thought, get excited about it for a day, then move on. The ideas that nag at you for years are fundamentally different. They're connected to real problems you've experienced firsthand, usually problems you encounter in your work, your industry, your daily life. They persist because the problem persists.

Research from MIT and Northwestern's Kellogg School found that founders who were previously employed in the same industry as their startup were 125% more likely to build a successful company. The average age of the most successful founders was 45, not 25. Experience and sustained exposure to a problem aren't liabilities. They're the biggest advantages you can have.

That notebook isn't evidence of procrastination. It's evidence of pattern recognition. You've been unconsciously gathering data for years: what works, what doesn't, what frustrates people, what they'd pay for. That's market research you didn't even realise you were doing.

Why you haven't started yet

It's usually not laziness or lack of motivation. The most common reasons people sit on an idea for years are practical ones. They don't know where to start. They don't know how much it costs. They're worried it might not work. They've heard horror stories about app projects going wrong.

All of those are reasonable concerns. The cost of building an app is significant. The process is unfamiliar. And yes, a lot of app projects do fail, often because people skip the homework and jump straight to building.

But here's the thing those concerns have in common: they're all about the process, not the idea. The idea has already survived years of your own scrutiny. The question isn't whether the idea is good enough. It's whether you can find the right process to bring it to life without wasting your time and money.

The cost of waiting another year

People rarely think about the cost of not acting. Every year you sit on the idea, the market moves. Someone else might build something similar. The problem you've identified might evolve. Your competitors keep using the same broken processes, and so do you.

More practically, every year that passes is a year of potential revenue you didn't earn. A year of users you didn't help. A year of feedback you didn't collect that would have made version two better. The longer you wait, the further behind you start when you finally do begin.

This doesn't mean you should rush. It means you should start the process, not necessarily the build. There's a big difference. Validating your idea costs nothing. Having a conversation with a designer about what's possible costs nothing. You can take the first step without committing to the full journey.

You don't need to have it all figured out

One thing I notice with long-time idea holders is that they've been refining the concept in their head for so long that they feel pressure to present it perfectly. They want to have the full spec, every screen mapped out, every feature defined before they talk to anyone.

You don't need any of that. In fact, coming in with a rigid, fully-formed concept can sometimes work against you. The best outcomes happen when you bring the problem and the insight, the core of what you're trying to solve, and work with someone who can help shape it into a product. That's how to prepare for your first project.

Your notebook is a starting point, not a blueprint. And that's exactly what it should be.

What the first step actually looks like

The first step isn't hiring a developer. It's not building a prototype. It's not even writing a business plan. The first step is talking to someone who builds apps and having an honest conversation about whether your idea has legs, what it might cost, and what the right approach would be.

A good designer will tell you the truth. They'll tell you if your idea needs more research. They'll tell you if you're trying to build too much for version one. They'll help you understand the MVP approach and why starting focused is smarter than trying to build the complete vision. And they'll give you a realistic picture of what it costs and how long it takes.

That conversation, a real one with someone who's not trying to sell you something, is the bridge between the notebook and the product. You've been doing the thinking for years. Now it's time to see what happens when you say it out loud to someone who can help you build it.

Sources
Age and High-Growth Entrepreneurship (Azoulay et al., American Economic Review, 2020) - Founders in the same industry were 125% more likely to succeed. Average age of top-performing founders was 45.

Related blog posts:

Why subject matter experts build the best apps →

How to validate your app idea before spending a cent →

Self-funding your app →