The 12 Customer Discovery Questions Every B2B Founder Should Memorize

The high cost of polite feedback

Most founders treat customer discovery like a first date. They want to be liked. They ask soft questions designed to elicit "That sounds cool" or "I could see us using that."

In B2B, "That looks interesting" is the sound of a dead deal. Early-stage teams waste six months building features based on polite lies from VPs who were just trying to be helpful. Real discovery requires friction. You need to hunt for the reasons someone won't buy, not the reasons they might.

If you are a VP of Product at a Series B or a solo founder at seed, these 12 questions strip away the politeness. They force the interviewee to give you data, not opinions.

Testing for the level of pain

If a prospect hasn't tried to solve the problem yet, it isn't a problem. It’s a minor inconvenience. They might complain about it for an hour, but they won't sign a $50k contract to fix it.

1. "What are you doing today to solve this, and why isn't it working?" If the answer is "nothing," walk away. If the answer is "a giant, fragile Excel sheet that the Director of RevOps spends four hours on every Friday," you have a business.
2. "When was the last time this problem caused a missed KPI or a significant loss?" Specific dates and numbers matter here. "Last quarter we missed our retention target by 3% because of data latency" is a buying trigger.
3. "If you didn’t solve this for another year, what would happen to your team’s headcount?" This identifies if the problem is a "nice to have" or a structural bottleneck.

Understanding the internal physics

You aren't just selling to a person; you are selling into a workflow and a political map. These questions map the obstacles before you hit them in a sales cycle.

4. "Whose budget does this come out of, and what do they hate spending money on?" Financial transparency tells you who the real villain is. It might be a CFO who hates seat-based pricing or a CTO who refuses to buy anything that isn't SOC2 Type II compliant.
5. "What was the last piece of internal software you bought, and how long did the implementation actually take?" If they say "three weeks" but it was actually nine months, you know their internal IT team is a bottleneck.
6. "If I gave you this tool for free tomorrow, what would be the first reason your team stopped using it after a month?" This is the "pre-mortem" question. It exposes UI friction, data entry burdens, or lack of integration with Slack or Jira.

Navigating the "why now"

Timing is more important than features. You need to know if you're a priority or a distraction.

7. "Where does fixing this rank on your top three priorities for this quarter?" If it's number four, it’s not happening. B2B leaders only have bandwidth for the top two.
8. "Who at your company would be most incentivized to see this fail?" Every new tool threatens someone’s domain. Maybe it’s a DevTools manager who built a homegrown version and doesn’t want it replaced. BuyerSignal helps founders find these specific roles—people who actually live the problem daily—so you aren't guessing about internal dynamics.
9. "What happens if you buy this and it works perfectly, but your boss still isn't impressed?" This helps you find the "hidden" metric. Usually, it’s something like "it didn't make our board deck look better" or "it didn't reduce our cloud spend fast enough."

Forcing a commitment

The final stage of discovery is testing for "skin in the game." If they won't give you something of value now (time, data, or an intro), they won't give you money later.

10. "Who else in your organization would be furious if they weren't involved in this decision?" Identify the "silent no" early. In Fintech, this is usually the Head of Compliance or Legal.
11. "What is the one feature that, if missing, makes this a total non-starter?" This prevents you from building a broad, shallow product. You need to know the "minimum viable hurdle."
12. "Can you introduce me to the person who currently manages the budget for this category?" An intro is a form of currency. If they won't vouch for you internally, you haven't convinced them the problem is big enough.

The contrarian take: Stop "building in public"

Most founders think sharing their roadmap on LinkedIn is discovery. It isn't. It's marketing. True discovery happens in private, recorded conversations where the prospect feels comfortable telling you your UI is confusing or your main value prop is irrelevant.

Avoid "What do you think of this feature?" That invites a lie. Instead, focus on "Tell me about the last time you tried to do X." Focus on past behavior, never future intent. People are terrible at predicting what they will do, but they are very accurate at describing what they have already done.

If you want to validate these questions against real practitioners without the noise of a cold sales pitch, BuyerSignal connects you directly with the right professionals for honest, structured research. Stop guessing what the market wants and start running the loop with the people who actually sign the checks.