Look closer at what actually makes Customer Development work: it is a set of practices for handling a conversation where someone else's honest perspective matters more than your instinct to defend your own.

Founders in our research routinely have these exact conversations with a different audience entirely: investors. And they almost never bring the CustDev discipline with them into the room. The VC meetings understandably get treated as a performance to win over or survive. But they could also be a piece of data to learn from.

One session, one data point

Those, who do CustDev right, share a specific tell: no single interview settles anything. One skeptical answer doesn't kill an idea. One enthusiastic answer doesn't validate it. The value shows up only once a signal repeats (or fails to repeat) across several independent conversations.

Fundraising conversations get treated completely differently. One founder from our research couldn't answer three questions in one VC meeting, and his entire pitch deck got rebuilt. Nothing wrong with taking hard questions seriously. But notice the asymmetry. Analyse that same meeting like a CustDev session, and it stops being "the deck is wrong, rebuild it." It becomes "did the last four investors ask about the same gap that I logged?" One hard meeting is a prompt to watch for a pattern. It is not, by itself, the pattern.

Reappearing signals beat single strong opinions

The second CustDev habit worth importing is patience with the signal itself. A single strongly-worded objection from one interviewee is interesting. The same objection showing up unprompted in the fourth, sixth, and ninth conversation is a finding.

One founder in our research had already narrowed his investor search specifically to people who understood his category, because non-domain investors kept "falling away" at the same point in the pitch. That's a founder who noticed a reappearing signal. Keep a simple log after every fundraising conversation: what questions stopped you, what you couldn't answer cleanly. Every few meetings read it back and look, however painful, for the line that shows up more than once.

The instinct to defend is the thing to catch

In a CustDev interview, when someone tells you your product is confusing, the good practice is to write that down and explore why, as opposed to correcting their understanding on the spot.

Gatekeeper feedback (a VC's question, an accelerator's pushback) pulls hard in the opposite direction, understandably so: an investor's skepticism is an obstacle between you and a check. The natural response is to persuade and win the room, not to sit with the possibility that the skepticism is pointing at something real. Rational in the moment, yet limiting afterward, when there's a chance to reflect and actually learn something.

So it's not about reacting to one hard question, but rather never writing the hard ones down at all. A CustDev-style investor log would force the objection onto paper before you've had the chance to talk yourself out of it.

Where the analogy breaks, and why that's useful too

It would be dishonest to stretch this too far. A VC is not a customer, and an investor's skepticism doesn't carry the same evidentiary weight as a pattern across real product users. Investors are themselves a specific, non-representative audience with their own incentives, blind spots, and pattern-matching habits.

Keep the investor and customer pushbacks separate, and look at where they overlap. Where they diverge, name it; it usually means gatekeepers see a gap customers haven't weighed in on yet, or vice versa.

"I talked to fifty customers, they flagged X. Then you flagged the same thing" is a different sentence than "we believe X is a problem." Investors respond differently to a founder who shows up with a market analysis than one who shows up with a pitch.

A simple protocol to try this out

  • 1After every gatekeeper meeting, write down questions that stopped you cold, in their words if you can. Resist writing your rebuttal in the same breath.
  • 2Before meetings read the log back. One brutal question is a data point. The same question from three people is a signal.
  • 3Cross-reference against your customer log. Where the two agree, that's your highest-confidence finding. Where they don't, say so.
  • 4Separate "narrative for investors" work from "product truth" work on purpose. Both are legitimate.