Pull, Not Praise: Reading Real Product-Market Fit Signals
Judge customer calls by the questions they ask, not the compliments they give.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 95%
A signal-detection framework for early customer discovery calls that separates polite affirmation from genuine buying intent. Use it when you're pre-product-market-fit and running many discovery calls, so you can tell whether interest is real before betting engineering time on it.
Origin
At Wiz (founded as Beyond Networks during the March 2020 shutdown), Herzberg was the first PM sitting in on 10-15 customer calls a day. Every call ended with 'oh, sounds interesting, would love to hear more' and the team read that as validation. Only when she admitted she still didn't understand what they were building did the team realize prospects weren't incentivized to dig in, and that they were mistaking affirmation for enthusiasm. Reframing the signal is what pivoted them to cloud security.
Core principles
- 01Humans are biased to seek affirmation over the feedback they don't want to hear; consciously invert that bias.
- 02Praise ('sounds interesting, keep me posted') is a soft no; process questions are a hard yes.
- 03Real buying intent shows up as the prospect pushing for the next concrete step, not you pushing them.
How to run it
- 1
Run discovery at volume
Book as many prospect calls as you can (Wiz did 10-15/day back-to-back) so the difference between weak and strong signals becomes obvious through contrast.
Pro tip Constraints can help: lockdown meant busy buyers were all home, so calls that were normally impossible became easy.
- 2
Classify the reaction, not the sentiment
After each call, ask whether the prospect gave vague enthusiasm or concrete process signals: pricing questions, PO/timeline questions, or an offer to connect you to their team.
Watch out A warm feeling at the end of a call is deceptive, especially when the prospect assumes a smart-sounding team must be building something good.
- 3
Treat 'how much / when / who' as the green light
Questions like 'how are you pricing this,' 'when can we start a PO,' or 'I know exactly who to connect you to' are the type of indications worth chasing. Vague 'super cool, update me' is not.
- 4
Require the pull before you build
Only commit engineering resources once you feel the prospect pulling for the next step, because they need to test and deploy in B2B and that requires real passion, not politeness.
In the wild
Once Wiz shifted its pitch to cloud security, the calls changed character entirely: prospects asked to start a POV immediately and asked about pricing and next steps. 'Once we found the right path you could just... easy to distinguish it from the wrong path.'
→ Wiz hit $100M ARR 18 months after founding, the fastest in software history.
Common mistakes
Mistaking interest for intent
Reading 'oh yes, interesting, love to hear more' as validation. Prospects say this to be polite to a smart team; it carries no commitment.
Listening for reinforcement
Filtering calls for signals that confirm your idea instead of intently listening for the absence of deep enthusiasm.
Is it for you?
Best for
Founders and first PMs at pre-PMF B2B startups running customer discovery.
Not ideal for
Late-stage companies with established demand where the buying process is already instrumented.
From the transcript
“we really felt the type of questions changed right suddenly the call didn't end was like oh this sounds super interesting sure like please update…”
“you have a bias to look for affirmation versus is like a bias to look for what you don't want to hear that's just natural…”
“we were looking for like positive reinforcements but not really listening intently to like signs of deep enthusiasm”
From the episode
Building Wiz: the fastest-growing startup in history
Raaz Herzberg (CMO and VP Product Strategy)