You already know how this goes. You described the idea to your spouse, a friend, maybe a colleague, and they said some version of "oh, that's a great idea." That sentence feels like data and it isn't. People who like you will tell you your idea is good the same way they'll tell you a haircut looks fine — to be kind, and to move on with their day. The useful question is a colder one: is there a real problem here that specific people are already spending time or money trying to solve?
Grade the problem, not the idea
An idea is a proposed solution, and solutions are easy to fall in love with and hard to judge — the cleverness lives in your head where nobody can argue with it. The problem underneath is where the truth is. If the problem is sharp (it hurts, it happens often, and the people who have it are already paying for a bad fix), then a rough first version of your idea will still find customers. If the problem is soft, the most polished app in the world will sit unused. So before you grade the app, grade the ache it's supposed to remove.
The fastest way to tell a strong idea from a flattering one: ask people to describe the last time the problem actually bit them. A vivid, specific, recent story means the pain is real. A vague, hypothetical answer — "yeah, I'd probably use something like that" — means you're collecting politeness, not evidence.
Why "is it good" is the wrong question to sit with
Good is subjective, and it invites the wrong crowd into the decision. Ask ten people whether your idea is good and you'll get ten opinions, most of them uninformed and all of them kind. Ask instead whether a dental-office manager, a plumber, or a real-estate broker — whoever your actual user is — has this exact problem badly enough to change what they do on a Tuesday, and the fog clears. You're no longer defending a concept. You're checking a fact about someone else's behavior, and behavior is the one thing you can't argue your way past.
Nobody has ever paid for a good idea. They pay to make a specific, recurring pain go away — and they'll pay even when the thing that removes it is rough around the edges.
A one-week gut check you can actually run
- 1Write the problem in one sentence, with a name attached. Not "help businesses do X," but "[specific person] loses [specific thing] every [time period] because [reason]." If you can't fill that in, that gap is your first finding.
- 2Talk to ten people who have the problem. Don't pitch. Ask them to walk you through the last time it happened and what they did about it. Listen for money already spent and workarounds already running.
- 3Look for what they pay for today. A competitor, a freelancer, a manual process, a duct-taped stack of tools. Existing spend is the strongest proof a problem is worth solving.
- 4Ask for a small, costly commitment. A deposit, a spot on a paid waitlist, an intro to the person who actually holds the budget. Interest that survives a small cost beats a hundred compliments.
- 5Decide in advance what would change your mind. Write down what a "no" looks like before you start, so you can't quietly move the goalposts when the answers disappoint you.
When a good idea still isn't yours to build
Sometimes the problem is real, the pain is sharp, and the honest answer is still don't — at least not you, not now. Maybe you have no way to reach the people who have it, and a product you can't distribute is a hobby with a login screen. Maybe it has to be free to win, and there's no path to money underneath. Maybe two funded companies already own the space and you bring nothing they lack. A strong idea in a lane you can't run in is worse than a modest idea where you hold an unfair advantage — a network, deep knowledge of the field, or a way to reach buyers other people can't touch.
So stop asking whether your idea is good. Ask whether the problem is real, whether you can reach the people who have it, and whether they'll pay to make it stop. If those three come back yes, you don't have a good idea — you have a reason to start. Who builds it, and how you do that without wrecking your week, is a separate question with real answers once the evidence is in.
Common follow-up questions
How many people do I need to talk to before I trust the answer?
Ten to fifteen focused conversations with people who genuinely have the problem is usually enough to see a pattern. You're not running a statistical survey; you're listening for the same painful story to repeat. If the first ten all shrug, you have your answer faster than you hoped — and you've saved yourself a year of building the wrong thing.
My friends and family love the idea. Doesn't that count for anything?
It counts as encouragement, not evidence. The people close to you are answering a different question — whether they support you — and they'll say yes regardless of the market. Trust strangers who have the problem, and above all trust behavior: what they've already spent time or money trying to fix.
What if I can't find anyone who has the problem?
That's one of the most valuable results you can get, and it's cheap. If you struggle to find even ten people with the pain, either the problem is rarer than you assumed or you're describing it in a way that doesn't match how sufferers see it. Better to learn that in a week of conversations than after months of building.
Want this answered for your exact situation?
We build and co-found software for people who have the idea and the network but not the technical team. Tell us where you're stuck and we'll give you a straight read — even if the honest answer is "don't build it yet."
See how we work