A founder messaged me recently with a situation I’ve now seen probably fifty times. He and his cofounder had been building a product for the enterprise M&A space — a workflow tool that takes a five-day process down to four hours. He’d shown it to two senior leaders he knew well. Both were impressed. He was thrilled for about a day.
Then the doubt crept in. He wrote:
“When I spoke to two senior leaders who I am close with and showed them the product, they were impressed — or so they said. Now, I am thinking that they were being nice to me and it might not be an urgent need. This has created stagnancy where my cofounder and I are in limbo whether to ditch this and move on.”
I want to focus on that line: “impressed — or so they said.”
That parenthetical is the entire problem. He showed his product to people who liked him personally, in a context where the social cost of saying anything negative was higher than the cost of being mildly encouraging. He got mildly encouraging feedback. And now, a few days later, he’s correctly suspicious that the feedback was worth nothing — but he doesn’t know what to replace it with.
This is one of the most common — and most costly — traps in early-stage founding. It’s also one of the easiest to misdiagnose. The founder thinks they’re doing customer validation. What they’re actually doing is collecting compliments from a sample of people biased to give them. The two activities look identical from the outside. They produce wildly different information.
I want to write about how to tell them apart, why the trap is so hard to see while you’re in it, and what real signal actually looks like.
The Politeness Tax
There is a phrase I think every founder should internalize: polite interest is cheap.
Not because they’re dishonest. Because saying nice things is the path of least resistance. It’s faster than explaining why they’re not interested. It avoids social awkwardness. It keeps the door open in case the founder ends up at a different company someday. It costs the listener nothing.
So when a founder asks an industry contact “what do you think?” and the contact says “wow, this is really cool, I can see this being useful, you should definitely keep going” — the founder hears this as positive signal. It is not signal. It is the absence of signal. It is what a sophisticated person says when they want to be kind and they don’t have a strong negative reaction strong enough to override their politeness instinct.
The same person, three weeks later, will not respond to a follow-up email. The founder will be confused. They liked it so much in the meeting. Why are they ghosting now?
The answer is that they didn’t like it in the meeting. They liked the founder. They liked the moment. They didn’t actively dislike the product. Those are three different things, and none of them is the thing the founder needed to find out.
The politeness tax falls hardest on founders who are well-networked, well-spoken, and asking the question to people who know and like them. Which is to say, it falls hardest on exactly the founders most likely to think they’re doing things right.
The “I Am My Own ICP” Trap
There’s a related trap that often comes packaged with this one. The founder who messaged me opened with this:
“I skipped the customer discovery process and validation phase since I am part of this industry and an ideal customer myself.”
I want to be honest about this, because I think it’s a more dangerous trap than the politeness one, and harder to see.
Being your own ICP gives you first-hand insight. It does not give you market validation. Those are different things, and the difference matters a lot.
First-hand insight means: you know what the workflow feels like. You know where the pain points are. You know the vocabulary people use. You know what existing tools fail at. You know what a believable solution looks like. This is genuinely valuable. It compresses the time you’d otherwise spend doing field research to understand the basics of the problem space.
Market validation is something different. It’s the answer to a different question: are there enough other people who feel the pain the way you feel it, and are willing to change their behavior to solve it, and willing to pay what you’d need to charge, and able to push the purchase through whatever decision process exists in their organization? Those are four independent questions, and being your own ICP gives you a confident answer to none of them. Your willingness to use the product tells you nothing about anyone else’s willingness to buy it.
The founder who skips validation because they’re their own ICP is making a subtle category error. They’re treating their personal experience of the problem as a sample. It is not a sample. It is one data point, and that data point is uniquely unreliable because it’s the data point that motivated you to build the thing. Of course you would buy it. You designed it for you. The question is whether anyone else has the same shape of problem, the same priority on solving it, and the same willingness to pay.
The painful truth is that “I am my ICP” is often the strongest possible anti-signal. Founders who say it are often founders who built a solution to a problem they personally feel intensely, in a way that’s idiosyncratic to them or to their specific career path. The market, when you actually go talk to it, looks different. The pain is real but smaller. The workaround is good enough. The priority is lower than they assumed. The willingness to pay is half what they modeled.
Being your own ICP is a starting point, not a finish line. It tells you the territory is worth exploring. It does not tell you there’s a market there.
What Real Signal Looks Like
So if polite interest is cheap and self-validation is unreliable, what does real signal look like?
I want to be specific, because “do better validation” is the kind of advice that sounds useful and does nothing. Here are the markers I look for, in roughly the order they matter.
Marker 1: They describe the pain in their own words, unprompted.
This is the single most important signal. You ask a prospect about their workflow. Without you steering them, without you describing your product, without you giving them the vocabulary, they tell you about the problem you’re trying to solve. They use their own phrases. They get frustrated talking about it. They tell you a specific story about a specific time it cost them something.
If you have to lead them to the pain — if you describe your product and then they nod and agree that yes, that’s a problem — you are not seeing real signal. You’re seeing accommodation. Real pain is what people bring up before you do.
The corollary: if you’ve described your product to ten people and none of them have, on their own, told you about the underlying problem in the conversations you had before the demo, you don’t have a pain. You have a feature people will agree is nice if you describe it well.
Marker 2: They tell you what they’re doing today is broken.
Every problem worth solving already has a workaround. Spreadsheets. Junior employees. Manual processes done late at night. The current state of the world is never literally nothing. Your competitor at the early stage is not another startup — it’s the workaround.
When a prospect describes their current workaround, listen for whether they describe it as adequate or broken. “Yeah, we just use a spreadsheet for this, it’s fine” is a no. “We use a spreadsheet and it’s a disaster, I lose hours every week reconciling things, last quarter we missed a deadline because the spreadsheet was out of date” is a yes.
The difference is whether the current state is generating real, ongoing, felt pain — or whether it’s just suboptimal in a way nobody actually cares enough about to fix.
Marker 3: They ask when they can use it.
After a demo, watch what the prospect does next. Do they say “very cool, send me more info” — which is polite-speak for “I am going to forget this exists” — or do they ask a specific question about access? “When can my team try this?” “What’s the onboarding look like?” “Do you have anyone using this yet in [their industry]?” “Can I send this to my CFO?”
Specific forward-looking questions are real signal. Vague encouragement is not. The forward-looking questions tell you the prospect has already, in their head, started imagining the world in which they’re using your product. The encouragement tells you they’re managing the social moment.
Marker 4: They introduce you to someone else with the same problem.
This is the strongest signal you can get short of someone actually paying you. If a prospect, on their own initiative, introduces you to another person who has the problem — a peer at another company, someone on their own team, a contact in their network — that’s not politeness. That’s belief. Politeness doesn’t extend to making intros, because intros cost the person social capital. They will not spend social capital on a product they don’t actually believe in.
Marker 5: They tell you the buying process.
This one is subtle but powerful. If a prospect, somewhere in the conversation, voluntarily starts describing how a purchase like this would actually happen in their organization — who would need to approve, what budget it would come out of, what the security review looks like, who else would need to be in the room — that’s real engagement. They’re not just reacting to the product. They’re already running the mental simulation of how to acquire it.
Polite prospects don’t do this. They don’t bother. They have no intention of going through the process, so the process never comes up. A prospect who walks you through their procurement workflow is telling you something the words of their compliments don’t tell you: they’re imagining buying this.
A Scorecard You Can Actually Use
Take any prospect conversation you’ve had recently. Run it through these five markers. Be honest.
Did they describe the pain in their own words, before you described your product? Did they tell you their current workaround is broken? Did they ask specific, forward-looking questions about access and onboarding? Did they offer — without prompting — to introduce you to anyone? Did they voluntarily describe how a purchase would actually happen?
Count the yeses.
Five out of five: you have a real prospect. Stop reading. Get on a follow-up call with them this week.
Three or four: you have a genuine signal. Build the relationship. Get them in the early customer cohort. Watch what they actually do, not what they say.
One or two: you got polite interest. Useful as context, not as validation. Move on.
Zero: this person was being nice to you. Do not build anything based on what they said. Do not adjust your roadmap based on their feedback. Do not put their logo on the “customers exploring our product” slide. They are not exploring. They were being kind.
Most founders, when they actually run their recent conversations through this scorecard, discover something uncomfortable: most of the “positive” conversations they were drawing energy from score one or two. The conversations they thought were merely okay sometimes score three or four. The signal was there. It just wasn’t where they’d been looking.
Who to Talk To (And How to Talk to Them)
There’s a practical follow-on question, which is: okay, fine, polite interest from people I know is cheap. Where do I get the real signal?
The answer that’s easy to say and hard to do: people who don’t know you and don’t owe you anything.
When a stranger takes a call with you and gives you their honest reaction, the politeness tax is much lower. They have no relationship to protect. They have no reason to be artificially kind. If they think the problem is real, they’ll tell you. If they think it isn’t, they’ll tell you that too — sometimes bluntly. That bluntness, which feels harsh in the moment, is worth ten times more than the warm compliments from your network. It’s information you can actually act on.
This is why I push founders to do cold outreach in the validation phase, not just the sales phase. Cold outreach is where the politeness tax is lowest. The prospect who takes your call without knowing you is giving you the cleanest possible signal about whether the problem is real and whether your framing of it resonates. They have no incentive to perform interest. They’ll show up if it lands. They’ll ghost if it doesn’t. Both responses are information.
The framing that helps most when you set up these calls: don’t pitch. Ask about their workflow. The bar for a validation call is not “do they like my product.” It is “can they describe the pain in their own words, with conviction, in the first ten minutes, before I’ve shown them anything?” If they can, you’ve found a real prospect. If they can’t, you’ve found a polite stranger — which is still better than a polite friend, because the polite stranger will hang up faster and let you move on.
The Honest Mirror
I want to close with the thing that’s hardest to write, because it’s the thing that matters most.
The reason founders are vulnerable to polite interest is not stupidity. It’s not naivete. It’s that founders, at the early stage, are starved for signal. They’ve been building for months. They’ve been making bets with limited information. They desperately want some external validation that they’re on the right track. And the human brain, presented with ambiguous data and a strong desire for a particular interpretation, will reliably find the interpretation it wants.
So when a senior leader at a big company says “wow, this is cool, you should keep going,” the founder doesn’t process this as the social pleasantry it almost always is. They process it as the validation they’ve been waiting for. They cite it to their cofounder. They put it in their investor updates. They use it to justify building for another three months without doing the harder work of finding real signal.
The fix is not to be smarter. The fix is to be more skeptical of yourself, specifically. Whenever you find yourself relying on a positive piece of feedback to keep going, ask the question that founder asked me — the question that got him out of the loop: were they actually impressed, or were they being nice to me?
If you can’t tell the difference with certainty, assume nice. Then go find the kind of feedback you couldn’t mistake for politeness — the kind that comes from strangers, the kind that comes with intros, the kind that comes with prospects describing their own buying process. That feedback is what you should be running on.
The compliments from people who like you will still be there. They’re not worthless — they’re moral support, and moral support has its place. But moral support is not validation, and treating it as validation will cost you months you can’t get back.
Polite interest is cheap. Real signal is expensive. Spend the time to find the expensive kind. It’s the only kind worth running on.
Filed under: GTM