If you've Googled "is my business idea good?" you're not looking for a pep talk. You're looking for a way to stop the loop in your head — the one where you've sketched the same product on a napkin four times this month, told two friends about it, gotten polite nods, and still don't actually know if it's worth your weekends.
Here's the honest answer: nobody can tell you yes or no from the outside. But there's a checklist that, if you answer it honestly, makes the answer almost obvious to you. I've walked more than a hundred non-technical founders through some version of this, and the same patterns keep showing up. This is the version I'd hand someone at a coffee shop if they asked me the question cold.
The short answer
A good business idea has three traits, and they all have to be true at once:
- A specific person feels a specific pain — not a vague "wouldn't it be nice if…" but a real, recurring annoyance you could describe in one sentence.
- That person already spends money trying to make the pain go away — on tools, freelancers, courses, duct-taped workarounds, anything.
- You can reach them cheaply — through a community you belong to, a job you've held, a network you've built, or a niche you actually understand.
Miss any one of those and you're either solving a problem nobody has, a problem nobody pays for, or a problem you can't get in front of. That's most failed apps in three sentences. We unpack the "real pain" half of this in Hair-on-Fire Problems: How to Spot Them.
The 10-question checklist
Answer each one out loud. If you mumble, that's a no. If you can't finish the sentence, that's a no. The point is to be brutally honest with yourself — not to talk yourself into the answer you want.
1. Can you name one specific person who has this problem?
Not "small business owners." Not "busy professionals." Name the human: "Solo bookkeepers serving 5–15 e-commerce clients." If you can't get that specific, you don't have a customer — you have a category. More on why specificity wins in Niche Down or Die.
2. How often do they feel the pain?
Daily pain monetizes. Monthly pain barely does. Yearly pain almost never does. Frequency drives willingness to pay more than severity — a small daily annoyance beats a big once-a-year headache almost every time.
3. What do they do about it today?
If the answer is "a spreadsheet, a Zapier hack, and a lot of swearing," that's a green light. If it's "nothing, really," they don't feel the pain enough to act — and they won't act on your product either.
4. Have they ever spent money to make it go away?
Past spending is the strongest demand signal you can get without writing code. Have they paid a freelancer? Bought a course? Subscribed to a tool that almost works? If yes, you're entering a market with proven willingness to pay. If no, you'll be educating andselling — twice the work.
5. Is the pain getting worse or going away?
Tailwinds matter. New regulations, new platforms, AI making old workflows feel ancient — these expand your market while you build. Shrinking markets punish even great execution.
6. Why are you the right person to solve it?
This isn't a confidence question — it's a moat question. What do you know about this audience that a random YC team with the same AI tools doesn't? "I lived this for ten years" is an answer. "I'm a hard worker" isn't. See Domain Expertise Is the New Technical Moat.
7. Can you reach the first 50 customers without paid ads?
Write down their names, communities, Slack groups, subreddits, conferences. If your plan is "post on Twitter and hope," you don't have a plan — you have a wish.
8. Is there a clear way to charge money on day one?
"We'll figure out monetization later" is the most expensive sentence in software. If you can't sketch a price and a payer in one sentence, you're building a hobby.
9. Will you still care about this in six months?
Most ideas don't die from competition. They die from boredom. If the audience or problem feels like a chore today, it'll feel like a prison in November.
10. What would make you quit?
Decide your kill criteria now, while you're still rational. "If I can't get 10 paying customers in 90 days, I move on." Founders who pre-commit to a quit line waste a lot less of their lives.
Green flags vs. red flags
Green flags
- You can describe the customer in one sentence.
- They already pay for a worse version of the solution.
- You belong to the community you're selling to.
- The problem comes up at least weekly.
- You'd happily talk about this audience at a dinner party.
- There are 2–5 mediocre competitors (proves a market exists).
Red flags
- Your target market is "everyone" or "all small businesses."
- You can't name three places your customers hang out online.
- The closest competitor is free and good enough.
- You're more excited about the tech stack than the customer.
- Your monetization plan is "ads" or "we'll figure it out."
- You've already pivoted the idea twice this month.
Three real examples
The good idea
A dental hygienist wants to build a scheduling tool for solo dental practices. She's worked in three of them, knows exactly which two software vendors dominate, and knows both are clunky. She runs a 2,000-person Facebook group of hygienists and front-desk staff. Her target customer pays $200/month already for the worse incumbent. This is a yes — not because the idea is novel, but because she's positioned to win in a way no outsider can replicate.
The bad idea
A consultant wants to build "an AI productivity app for knowledge workers." Target customer: vague. Distribution: "LinkedIn." Pricing: "freemium, probably." Competition: hundreds of well-funded incumbents plus every AI lab on Earth. He's never built or sold software before. This is a no — not because the space is bad, but because he can't compete in it. We dig into this exact failure mode in Should I Build This?
The fixable idea
A wedding photographer wants to build "a tool for photographers." Too broad. But when pushed, she narrows to: "second-shooters who need to deliver edited galleries to the lead photographer within 48 hours." Now there's a specific person, a specific pain, and she's got 400 Instagram followers in exactly that niche. The original idea was a no; the narrowed version is a yes. Most "bad" ideas are actually un-narrowed ideas.
What to do if you can't answer half the questions
That's not a death sentence — it's a homework list. Do not start building. Instead:
- Talk to 10 potential customers in the next two weeks. Not to pitch — to listen. Ask them to walk you through the last time they hit the problem.
- Run a 48-hour demand experiment. A landing page, a waitlist, a manual offer in a Slack group. Cheap signals beat expensive guesses. The full playbook is in 7 Cheap 48-Hour Experiments to Test Demand Before Writing Code.
- Try to sell it before you build it. If nobody will pre-order at half price, nobody will buy at full price either.
Come back to the checklist after the homework. The answers will be sharper, and the yes/no will feel less like a guess.
The 2-minute version
If you don't want to walk through all ten questions yourself, the ShipOrDrop quiz scores your idea across the same dimensions in under four minutes and tells you exactly where it's strong and where you have homework to do. It's the structured version of this checklist — same questions, faster verdict, no email gate. More on what each score means in Validate Your Idea in 2 Minutes.
The honest truth: most people asking "is my business idea good?" already know the answer. They're just hoping someone will tell them otherwise. Don't be that founder. Run the checklist, do the homework, and let the answer be obvious.