Is My Business Idea Any Good? Here's How to Know in 2 Minutes

I've had probably 200 business ideas over the last decade. Maybe more. I kept a note on my phone for a while — every shower thought, every "what if someone built..." moment. The list got long. The number of ideas I actually pursued? Four. The number that made money? One. And even that one took a year to break even.

The problem was never the ideas themselves. Some of them were genuinely clever. The problem was I had no way of knowing which ones were clever and viable. I'd get excited, spend a weekend building something, show it to three friends who said "yeah that's cool," and then realize six weeks later that nobody actually needed it.

If that sounds familiar, you're in the right place.

The gut feeling trap

Here's something nobody tells you when you're starting out: your gut feeling about a business idea is almost always wrong. Not because you're dumb — because you're biased. You want the idea to work, so you unconsciously filter out the red flags.

A study by CB Insights analyzed 101 startup post-mortems and found that 42% of startups fail because there's no market need. Not because the founder was lazy, not because the tech was bad — because nobody actually wanted what they were building. Forty-two percent. That's almost half.

The founders behind those startups weren't amateurs. Many had raised money, built teams, worked for months or years. They just never stopped to ask the right questions early enough.

Five questions that actually matter

Forget the 50-page business plan. Forget the lean canvas (for now). If you can answer these five questions honestly, you'll know more about your idea's viability than most founders know after three months of building.

1. How painful is the problem?

There's a huge difference between "nice to have" and "I need this yesterday." Think about the problem you're solving. Are people actively searching for solutions? Are they complaining about it on Reddit, in Facebook groups, on Twitter? Or is it something they'd vaguely appreciate but never actually pay for?

I once built a tool that helped people organize their browser bookmarks. Technically useful. Nobody cared. Because messy bookmarks are annoying, sure, but nobody loses sleep over them. Compare that to, say, a tool that helps freelancers chase unpaid invoices — that's a problem people will throw money at because it directly affects their income.

If your idea solves a "meh" problem, it doesn't matter how beautifully you build it.

2. Who exactly will pay for this?

"Everyone" is not an answer. Neither is "small businesses" or "millennials." You need to be specific enough that you could describe one person — their job, their day, the moment they'd reach for your product.

When Slack launched, they didn't target "companies." They targeted small tech teams who were drowning in email threads and needed a faster way to communicate during the workday. That specificity shaped every feature they built.

If you can't picture one specific person using your product on a Tuesday afternoon, you probably haven't narrowed down your audience enough.

3. What exists already?

This is where most people either panic ("oh no, someone already did it") or get delusional ("there's nothing like this out there, which means it's a huge opportunity").

Both reactions are usually wrong. Having competitors is generally a good sign — it means there's demand. Having zero competitors often means there's no market, not that you've stumbled onto a goldmine.

The real question is: what are existing solutions getting wrong? What gap can you fill? Maybe they're too expensive, too complicated, too focused on enterprise when there's a huge underserved segment of solo users. That gap is your opportunity.

4. Can you build version one yourself?

I don't mean the final, polished, funded-by-Sequoia version. I mean: can you put something out there in two weeks that lets one real person get value from it?

If the answer is no — if you need to hire developers, find a co-founder, raise money, learn an entirely new skill stack — you've added enormous risk before you've validated anything. The best ideas for solo founders are the ones where you can build the MVP yourself, test it, and iterate based on real feedback. You can always scale the team later.

5. Would you use this every day for a year?

This is the question people skip, and it's the one that kills most side projects. Building a product is a slog. There will be weeks where nothing works, where no one signs up, where you wonder why you started. If you're not genuinely interested in the problem space, you'll quit. Guaranteed.

I'm not saying you need to be "passionate" in some TED-talk sense. But you should at least find the problem interesting enough that you'd work on it even when it's not fun.

The scoring approach

Those five questions map to the four dimensions that actually predict whether a business idea will work:

Market fit — is the problem real, is the audience big enough, and is there room for you among competitors? Revenue potential — will people pay, and does your pricing model make mathematical sense? Execution feasibility — can you actually build and ship this thing? Financial health — do the costs work out, or will you burn through savings before earning a dollar?

Each dimension gets a score. Together, they give you a number between 0 and 100 that tells you — roughly, imperfectly, but usefully — whether this idea deserves your next six months.

What your score actually means

Let me be honest about what a score can and can't do. It can't predict the future. No tool can. What it can do is surface the blind spots you're ignoring.

If you score 85, it doesn't mean you'll succeed. It means the fundamentals look solid and you should start validating with real users. If you score 35, it doesn't mean you're wrong about everything. It means there are specific, identifiable weaknesses that need fixing before you invest serious time.

Think of it like a health checkup. A good result doesn't make you immortal. A bad result tells you where to focus.

What to do after you score your idea

Regardless of your score, here's what I'd recommend:

If you scored above 60 — talk to 10 potential users this week. Not friends, not family. Real people who match your target audience. Ask them about the problem, not your solution. Listen more than you talk. If they light up when describing the problem, you're onto something.

If you scored between 40 and 60 — look at which category dragged you down. Was it market? Maybe your audience is too small. Revenue? Maybe people won't pay what you think. Execution? Maybe scope it down to something you can build in two weeks instead of two months. Fix the weak spot, then score again.

If you scored below 40 — don't build. Not yet. Go back to the problem. Talk to people. Read forums. Figure out what they're actually struggling with, not what you think they're struggling with. Your idea might be in the right neighborhood but pointed at the wrong house.

One more thing

Scoring your idea isn't a one-time event. The best founders I know scored their idea, talked to users, adjusted, and scored again. Then again. The idea you end up building is almost never the idea you started with — and that's a feature, not a bug.

The worst thing you can do is sit on an idea for months, "perfecting" it in your head, afraid to test it because you might find out it's flawed. News flash: it's flawed. Every idea is. The question is whether the flaws are fixable.

Go find out.