Everyone loved it but no one bought it: how to read what people are actually telling you

The most common email I get from a founder goes like this. I talked to twenty people, every single one of them said they loved it, I built the thing, I launched, and the room went quiet. What happened.

What happened is that you mistook politeness for signal. You asked people about your idea, they said something nice, you treated that as evidence, and the evidence wasn't evidence. This isn't a personal failing. It's the default failure mode of asking humans about a thing you made, and the gap between what people say in conversation and what they'll do with their money or their time is the single most expensive thing for early founders to misread.

Reading the signal correctly is a learnable skill. The first move is to stop weighting words and start weighting behavior. Anyone can say they love an idea. Almost no one will give you their email address for it. Even fewer will give you twenty dollars. Behavior beats stated preference every single time. If you're weighing what people said over what people did, you're reading the wrong data.

The second move is to notice the shape of the enthusiasm. Real excitement is specific. It comes with a use case, a moment in their week, a person they'd tell about it. Polite excitement is general. It comes with phrases like sounds great, I could see that being useful, that's a good idea. If the only data you have is the general kind, you have no data. You have politeness.

The third move is to listen for what people aren't saying. When someone is genuinely sold they ask a follow-up question. They ask when it ships, what it costs, whether you can let them try the beta. When someone is being polite they end the conversation. The absence of a follow-up question is itself a signal, and it's the signal founders often ignore because it doesn't feel like data.

The fourth move, which is harder, is to ask people to do something small that costs them something. Not a survey. A small commitment. Will you put your email on this list. Will you pay ten dollars to lock in. Will you introduce me to the person at your company who would actually buy this. The commitment doesn't need to be large. It needs to cost them something, because the conversation that tells you the truth is the one where the other person has something at stake.

The last move is the one founders resist the most. You have to be willing to hear no. If you go into a conversation hoping for validation, you'll find it whether or not it's there. The only way to read the signal straight is to genuinely want the answer either way, which means you have to actually be willing to walk away from the idea if the signal isn't there. Founders who can't do that will keep getting yeses and keep being surprised by the silence after launch.

The good news is that all of this is learnable, and most of the time the data you need is already in your inbox. You probably have ten conversations sitting in your sent folder right now that, read carefully, would tell you whether the idea is real. The skill isn't getting more conversations. The skill is reading the ones you already have.

This connects to a question I answer in depth: Why does my product have no users after launch and How do I know if my startup idea is worth building.