Compliments are the counterfeit currency of entrepreneurship. They feel satisfying, bolster founder morale, and validate long evenings spent writing product roadmaps. However, in customer research, compliments are the leading cause of premature building and product failure.
In The Mom Test, author Rob Fitzpatrick warns that flattery almost always disguises lack of genuine interest. When someone says, "That is such a neat concept, let me know when it launches," what they are actually saying is: "I respect your ambition, but I am politely declining to invest my time, capital, or attention into this."
Recognizing the Anatomy of a False Compliment
Polite stakeholders employ predictable linguistic patterns when they want to end an interaction without hurting your feelings:
- The Visionary Endorsement: "This is definitely the future of this industry." (Zero commitment, pure abstraction).
- The Referral Deflection: "I don’t need this myself, but I know dozens of managers at other companies who would die for this." (Transferring hypothetical need to absent third parties).
- The Feature Add-On: "If you just added blockchain reconciliation and a CRM integration, I’d totally consider it." (Inventing imaginary requirements to avoid immediate commitment).
✘ Absorbing the Compliment
Customer: "Wow, this analytics dashboard UI looks clean. I’d definitely use something like that!"
Founder: "Thanks so much! We spent weeks refining the design. Would you want a dark mode option too?"
✔ Deflecting Back to Reality
Customer: "Wow, this analytics dashboard UI looks clean. I’d definitely use something like that!"
Founder: "I appreciate that. When was the last time you logged into your current reporting system? What were you looking for?"
The Tactical 3-Step Redirection Sequence
- Acknowledge with Minimal Friction: Do not spend three minutes celebrating the praise. A simple, flat "Thank you" is sufficient to acknowledge their sentiment without feeding the ego loop.
- Identify the Root Underlying Anchor: Pinpoint what exact element of their statement was grounded in real life. Did they compliment scheduling because their team regularly double-books calendar slots?
- Redirect with a Past-Tense Query: Pivot straight to historical execution. Ask: "How are you currently handling that problem right now?" or "What did you pay last quarter to solve that?"
Compliment Types and Tactical Responses
| Compliment Type | Underlying Reality | Deflection Script |
|---|---|---|
| "I love this idea!" | Social courtesy / excitement without commitment | "Thanks. How do you tackle that workflow today?" |
| "It would be huge for enterprise" | Shifting the problem to someone else | "Does your company struggle with that currently?" |
| "I'd buy that for sure" | Non-binding hypothetical future prediction | "When was the last time you bought tools for this?" |
| "You should pitch this to VCs" | A polite exit maneuver | "Before funding, what's your biggest blocker right now?" |
Pros and Cons of Rigidly Filtering Flattery
Pros: Protects your runway by preventing you from developing software based on polite encouragement; surfaces the true friction points users will actually pay to fix.
Cons: Can occasionally feel blunt in casual networking settings; requires deliberate conversational discipline to avoid enjoying self-gratifying compliments.
True validation does not arrive wrapped in enthusiastic accolades. It comes in the form of messy spreadsheets, disgruntled operators complaining about existing software invoices, and customers offering you cash or scheduling time to test rudimentary MVPs.