How do you Get Real Feedback on your product Before Launch?

Your product didn't fail because it was bad. It failed because you confused a great conversation for real demand.

Every founder and product leader has heard it: "Customers loved the idea in our interviews." The product launches, the team celebrates, and then... nobody adopts it. The uncomfortable truth is that the interviews probably weren't wrong. They just weren't validation.

What is the difference between product discovery and product validation?

To stop building in the dark, you have to separate insight from evidence. Bill Albert, founder of Greenlight Idea Lab, compares product building to constructing a house. Customer discovery is how you identify the customer's pain,  the foundation. If you don't get the foundation right, the rest of the house is doomed to fail. Product validation is how you build the walls, your value proposition, and the interior, your product solution. It proves that your specific execution of the idea actually drives demand.

You need both, but you cannot confuse the first for the second. Insight gives you permission to explore; evidence gives you permission to commit the roadmap.

Not Every Pain Point Is Worth Solving

Before you can validate a solution, you have to validate the pain itself, and not every frustration a customer names in an interview is something they'll actually spend money to fix.

This is where a lot of teams get burned. A customer mentions a problem. The team gets excited. Nobody stops to ask: how much does this actually hurt?

At Greenlight, we use a tool called the Spend Exercise to force that question into the open. Give users $100 in virtual money and ask them to distribute it across their biggest problems. What you find is almost always clarifying, some problems get $40, others get $5. The exercise reveals urgency in a way that polite conversation never does, because it forces trade-offs. That's where the signal lives.

What Emotional Signals Tell You (And What They Don't)

There's a layer of customer feedback that sits between a polite opinion and hard behavioral data,  and most founders either miss it completely or over-index on it.

It's the emotional signal.

You'll know it when you hear it. A customer stops mid-sentence and says "honestly, this drives me insane." Their voice changes. They lean in. They stop being polite and start being real. That's not the same as "yeah, I'd probably use something like that." That's pain talking.

Emotional signals matter because they tell you something urgency-based interviews can't always surface cleanly, whether the problem actually lives in the customer's day, or whether it's just theoretically annoying. A problem that triggers a genuine emotional response is a problem that's close enough to hurt. That's the filter.

But here's where founders trick themselves: emotional resonance feels like validation. It isn't. It's a strong signal that you're worth investigating further, not a green light to build. A customer can be genuinely frustrated by a problem and still not change their behavior to fix it. Emotion tells you the pain is real. Behavior tells you it's urgent enough to act on.

Think of it as a hierarchy. Factual reporting, "yes, this is a problem we have", is the floor. Emotional signals, "this actually costs us every week and it's exhausting”,  sit above that. Behavioral evidence, deposits, commitments, referrals, is the ceiling. You want to climb all three levels, not stop at the one that feels best.

Why do customers say one thing and do another?

People are naturally kind in interviews, optimistic about hypothetical futures, and genuinely terrible at predicting their own behavior. When a user says, "I'd totally use this," that is enthusiasm, not evidence.

Bill shared a story on the Creating Better Products podcast with a classic industry story: a focus group evaluating a wireless speaker enthusiastically requested red, blue, and green options. But when offered a free speaker to take home, everyone chose the black one.

Even if they truly love your idea, switching costs can kill adoption. Bill recalled a construction software tool that users thought was highly valuable, but the pain of abandoning their legacy spreadsheets was simply too high. Desirability is necessary, but if the barrier to entry outweighs the pain of the status quo, the product will still fail.

How do you validate customer demand before building?

If you want to measure true demand, stop asking for opinions and start watching behavior. The goal is to move potential customers up what Bill calls the "Ladder of Commitment", a progression where each step requires them to pay with something real.

1. Attention. Before anyone gives you an email, they give you their focus. A click on "Learn More" isn't much, but it validates that your hook is sharp and the problem is top of mind.

2. Identity. They trade their contact information for something valuable, a waitlist spot, a demo, access to early content. Anonymous visitor becomes known lead. They've paid with their time.

3. Reputation. They introduce you to their manager or a decision-maker inside their organization. That's internal social capital on the line. People don't spend it on things they don't believe in.

4. Intent. They sign a Memorandum of Understanding or Letter of Intent. Not a contract, not a payment, but a behavioral "yes" that goes far beyond a verbal "maybe."

5. Cash. A deposit, a pre-order, a paid pilot. This is the only metric that actually proves you have an indispensable solution. Everything else is signal. This is truth.

6. The discomfort of asking for each of these is exactly the point. Friction is information.

When should a startup use customer discovery?

If you're sitting on a pile of positive interview feedback and you're about to lock in a roadmap, pause.

Ask yourself: what would a real customer actually do today if this product existed? And can you get them to take a proxy of that action right now?

Listen to what customers say to sharpen your product. Watch what they do to validate your business. Those are two different jobs, and mixing them up is one of the most expensive mistakes a product team can make.

Have promising customer feedback but not sure if it's real demand? Let's find out before you build. Book a validation consult with Greenlight Idea Lab.