Nice idea is the most dangerous phrase in validation — it means free-only interest, not demand. How to read red, yellow and green signals in 20 conversations.
"Nice idea" is the most dangerous phrase in the founder vocabulary, because it sounds like validation but means the exact opposite. It means: I would accept this if it were free, but I would never go out of my way to find it. Free products are not businesses. Here is how to read what your validation conversations are actually telling you — and what to do about each signal.
The compliment that ends six-month builds
A head of product we'll call Marc — an archetype, not a case study — spent six months building a scheduling tool for freight forwarders. Nights, weekends, a genuinely impressive working product: authentication, multi-tenant database, role-based permissions, real-time updates. Then he sent the link to twenty freight forwarders he'd found on LinkedIn. Three replied. One tried it for ten minutes and sent back a single line: "Looks great, but we already use TMS-Connect for this and it's bundled with our customs software, so I don't think we'd switch."
"Looks great" is the compliment. The rest of the sentence is the business. Marc's customers weren't refusing because his product was worse — they were refusing because the switching cost wasn't his price, it was the price of unbundling from a workflow that had eighteen other things wired into it. No feature would fix that. He'd spent four thousand euros on tools, two hundred evenings, and sixty weekends to learn something a two-hour conversation in week one would have told him for free.
The founders who avoid Marc's fate aren't smarter and don't work harder. They run the twenty-conversation validation sprint first — and then they read the signals honestly. The second part is where most people fail, because founders are wired to hear encouragement in everything. So here is the honest read-out, signal by signal.
Red lights: kill the idea
When you sit down with twenty conversations logged in a spreadsheet, these patterns mean stop:
- Most people don't have the problem you're describing. Kill it.
- They have the problem but can't quantify the cost. If nobody can put hours or euros on the pain, the problem is theoretical — and theoretical problems don't get paid for. Kill it.
- They say it's "interesting" or "a nice idea" but can't describe what they'd pay. Kill it.
- Everyone says they'd "probably use it," but nobody says they'd pay for it. Kill it.
Notice the pattern: every red light is a version of enthusiasm without money attached. Politeness is free. Attention is cheap. The only signal that survives politeness is payment — which is why serious validation ends with a presell, not a survey.
Yellow lights: tighten and go again
The most common outcome is neither red nor green. Most people have the problem. Some can quantify the cost. A few have actively tried to solve it. Price expectations are scattered, and you collected two or three soft commitments to be early customers.
Yellow doesn't mean build, and it doesn't mean quit. It means there's something there, but you haven't found the sharp version of the offer yet. The move: run another ten conversations with a tighter customer definition — a narrower segment, a more specific pain. The pattern will sharpen, into green or into red. Either answer is progress, and both are cheaper than guessing.
Green lights: build it
Green looks like this, and it's unambiguous when you see it:
- Most people have the problem and can quantify the cost in real money or real hours.
- They've actively tried to solve it with existing tools they don't love.
- Price expectations cluster in a range you can charge profitably.
- At least five people explicitly want to be early customers.
When all four line up, you've found a market. Build, move fast, and keep talking to ten more people while you're building so the feedback never stops.
There's also a bonus green light that's easy to miss: your potential customers are already paying for something that almost solves their problem. That's the easiest sale a solopreneur can make. They've crossed the budget threshold. You don't have to convince them that spending money on this category is sane — only that spending it on your version instead is smart.
| Signal | What you hear | What it means | What to do |
|---|---|---|---|
| Red | "Nice idea," "I'd probably use it" | Free-only interest | Kill it, gratefully |
| Yellow | Real problem, scattered prices, 2–3 soft commitments | The offer isn't sharp yet | Ten more conversations, tighter segment |
| Green | Quantified cost, tools they don't love, 5+ early customers | A market | Build, fast |
| Bonus green | Already paying for a near-solution | Budget threshold crossed | The easiest sale you'll make |
Trust the spreadsheet, not your gut
Founders are terrible at killing their own ideas. You've invested time, you've imagined what success looks like, you have an emotional commitment — and your brain will pattern-match any conversation toward "yes, this is signal." That's why the read-out has to come from a spreadsheet of exact quotes, not from your memory of how the calls felt.
Write down what people actually said, not your interpretation of it. When you read the rows a week later, the quotes either support the idea or they don't. The spreadsheet is impersonal. It doesn't care about your feelings. Trust it over your gut — especially when your gut insists the spreadsheet is wrong.
And when the verdict comes back "nice idea"? Kill the project and be grateful. Two weeks of conversations is the cheapest tuition you'll ever pay — and it just saved you Marc's six months.
Frequently asked questions
What does it mean when people call your business idea a "nice idea"?
It means they'd accept the product if it were free but would never go out of their way to find it or pay for it. It sounds like validation but is a red light: enthusiasm without money attached is not demand, and free products are not businesses.
How many customer conversations do you need to read the signals?
Twenty. At ten conversations you can convince yourself of anything; at twenty the pattern is undeniable; at fifty you're refining what you already know. Log every conversation in a spreadsheet with exact quotes so the pattern is readable.
What are the green lights that an idea is worth building?
Most people have the problem and can quantify its cost, they've actively tried existing tools they don't love, price expectations cluster in a profitable range, and at least five people explicitly ask to be early customers. Bonus: they're already paying for a near-solution.
What should you do if the validation signals are mixed?
Treat it as a yellow light: there's something there, but the offer isn't sharp yet. Run another ten conversations with a tighter customer definition and let the pattern resolve into green or red before you write any code.