Is your startup idea worth building?

Most startup ideas die quietly. Not in a blaze of failed funding rounds or bad press - just slowly, as the founder runs out of energy, money, and the will to keep explaining what the thing actually does. The brutal truth? Almost none of those failures were inevitable. They were just never properly tested.

Here's the thing about startup ideas: everyone has them. And most people, if you catch them on the right day, are completely convinced theirs is the one. The market's huge. The timing's perfect. The competitors are doing it all wrong. Sound familiar?

The problem isn't having a bad idea. It's not testing it properly before you spend eighteen months and your savings building it. So if you're here, reading this, asking yourself whether your idea is actually worth pursuing - that's already a better starting position than most founders find themselves in.

Let me walk you through how to find out.

Why most "good ideas" aren't good enough

There's a meaningful difference between an idea that's interesting and an idea that's a business. Interesting ideas make for great dinner table conversation. Business ideas solve a real problem, for a real set of people, in a way those people will actually pay for. And that last part - the paying - is where a surprising number of founders get tripped up.

"An idea is not a business. A problem worth solving, for people who'll pay to have it solved - that's a business."

We've written about this in more depth in The difference between a product idea and a business idea, but the short version is this: if your idea starts with a feature ("I want to build an app that...") rather than a problem ("people who do X really struggle with Y..."), you've probably skipped the most important question. And the most important question is always: who's hurting, and why?

We covered that in a lot more detail in Your idea might be brilliant. But is anyone actually struggling without it? - worth a read if you haven't already.

The five questions worth asking before you build anything

You don't need a 40-slide pitch deck or a six-month market research project to test whether an idea has legs. You need honest answers to a handful of questions. These aren't comfortable questions, which is exactly why most founders avoid them.

1. Is there a real, specific problem here? Not a vague inconvenience, not a marginal improvement on something that already works fine - a genuine, recurring pain that people are actively trying to solve. The best indicator? People are already cobbling together workarounds with spreadsheets, WhatsApp groups, or tools they clearly hate. If they've given up and just accept the problem as part of life, that's a yellow flag. If they're spending real time or money managing around it, that's a green one.
2. Are there enough people with this problem? A problem that affects twelve people and their pets is not a market. But a problem that affects a relatively small, niche group - who are hard to reach, willing to pay well, and currently underserved - might be a very good market indeed. Don't fall into the trap of picking a big number to make yourself feel better. Pick an honest one, then work out if the maths actually stacks up. We broke this down in Market size reality check: how big does your market need to be?
3. Why hasn't someone already built this? This is the question that founders tend to either brush past ("nobody's thought of it yet!") or catastrophise over ("there's already a competitor, it's over"). Neither reaction is particularly useful. The honest answer is usually one of three things: someone has built it and it didn't work, the market wasn't ready before but it might be now, or the idea is genuinely novel. Each of those scenarios has very different implications for what you should do next.
4. Can you get in front of your target customer quickly and cheaply? This is a distribution question, and it matters earlier than most founders think. A brilliant product that's expensive or slow to reach its audience is a struggling business. If you can't picture how you'd find your first ten customers - who they are, where they hang out, why they'd trust you enough to try something new - that's something to work out before you write a single line of code.
5. Would you pay for this yourself, or do you know someone who would? Not in a vague, hypothetical way. Specifically: if this product existed today, would it sit on your credit card statement or your colleague's? Because if the answer is genuinely yes, and you can name actual people, that's a meaningful data point. If you're not sure, or you're thinking well, I wouldn't personally, but I'm sure others would - that's worth sitting with for a moment.

None of these questions have right or wrong answers in themselves. But taken together, they start to paint a picture. And you want an honest picture now, not an expensive one later.

Validation isn't about proving yourself right

This is where a lot of founders come unstuck. They hear "validate your idea" and they go looking for evidence that they're correct. They survey their friends. They get encouraging nods from people who don't want to hurt their feelings. They find the one stat that backs their thesis and screenshot it for the pitch deck.

That's not validation. That's confirmation bias with a Notion board.

"Real validation means actively looking for the reasons your idea might not work - and being willing to find them."

The goal is to disprove your assumptions, one by one, as cheaply as possible. Talk to people who'd be your target customers - and ask them about the problem, not the solution. Ask them how they currently deal with it. Ask them what they've tried. Ask them how much it costs them, in time or money, to live with it. And then listen, rather than selling.

If you're not sure where to start with shaping the idea before those conversations, we've put together a 30-minute idea shaping exercise that's worth doing first. It won't take long, but it'll sharpen the thinking considerably.

So, what if you've got more than one idea?

This is more common than people admit. Some founders aren't wrestling with whether their idea is good - they're wrestling with which of three ideas to back. And that's a genuinely hard decision, because you can't do all of them well, and the opportunity cost of picking the wrong one is real.

We've written specifically about this in How to choose between ideas when you've got more than one, but the simple version is: apply the same five questions above to each, compare the answers honestly, and look for the one where the problem is sharpest, the market is most accessible, and you have some genuine advantage - knowledge, network, or credibility - that someone else building the same thing wouldn't.

What comes after "yes, this is worth pursuing"?

If you've worked through the questions, done some early conversations, and still feel like there's something real here - that's a good sign. But it's the start of the process, not the end of it. The next step isn't to build the full product. It's to figure out the smallest possible version of the thing that lets you learn whether people will actually use it and pay for it.

That's what we mean when we talk about an MVP - and it's one of the most misunderstood concepts in startup land. An MVP isn't a half-finished product. It's a deliberately constrained version of the idea designed to answer a specific question. From business idea to product: a straight-talking guide for founders covers exactly how to think about making that leap, without overbuilding before you've proven the core assumption.

And if the honest answer to some of those five questions is "I don't know yet" - that's fine. That's what the validation phase is for. Why most "good ideas" fail - and how to test yours early goes into the mechanics of that process in detail.

"The founders who succeed aren't the ones who had the best idea. They're the ones who found out fastest whether their idea was worth betting on."

One last thing - on the emotional side of all this

Testing your idea can feel threatening. Your idea is probably tied up with a lot of hope and identity and, if you've already told people about it, some social stakes too. That's completely normal, and it doesn't make you fragile - it makes you human. But it does mean that the process of genuinely stress-testing an idea requires a degree of psychological safety that not everyone finds easy to give themselves.

We talked about this honestly in The emotional reality of starting: fear, imposter syndrome, and loneliness. Because these things are real, and pretending the founder journey is all bold vision and upward momentum doesn't help anyone.

The thing to hold onto is this: testing your idea early, and finding out it needs work, is not failure. It's the job. The founders who test early spend less money, learn faster, and build things people actually want. The ones who don't test - and there are a lot of them - find out the hard way, usually much later and at much greater cost.