I could validate until the cows come home. That's the whole problem.

I run a GTM product for early-stage B2B founders, and I have spent the last few weeks not doing customer discovery. I want to write down why, because I don't think the usual answer is the real one.

The usual answer is fear. That's not it. The real reason is that discovery produces nothing you can point at.

If I ship a feature, there's a thing. If I run five calls, there are notes. No demo, no commit, no deal, no checkbox. So at the end of the day my brain scores it as zero, and building scores as one, and I keep picking building. Progress in the right direction gets almost no credit from the person making it.

Two other things I've noticed about myself:

#1- I can't hear straight about my own product. Everyone knows the version where you hear "interesting" as "I'd buy that." Here's the version I didn't expect. A founder recently told me he would pay. My immediate reaction was to explain it away: he's unusually thoughtful, probably not a typical user. I had built a brain that could neutralize a yes. That's how hard I'm protecting the story I've already decided on.

#2- I default to talking about the product when I should be asking about the pain. When I stop pitching and just ask what's broken in someone's week, the dynamic flips. They stop evaluating my thing and start describing their own problem, and I become the person taking notes. Those are the only calls that have ever changed what I build.

Someone on Reddit recently told me that I should not burn my energy on the idea and design phase: design partners are a draining loop.

They are more right than I wanted them to be. A design partner program can quietly become the thing you do instead of the thing you're avoiding. It looks like customer contact. It generates meetings and roadmap input and goodwill and it can run for months without producing a decision. I have a few of those sitting paused right now, which is its own kind of answer.

But those are two different things. A design partnership is a long co-building engagement. A discovery call is 30 minutes where you ask what's broken and leave. The first drains you. The second is cheap, and I avoid it for a completely different reason: it leaves nothing behind.

So, here's what I am trying now: discovery should stay fast and cheap. Design partnerships should be rare, and the partner commits something real (time on a calendar, a pilot, intent to buy). If nobody's committing anything, it's not a partnership, it's a friendship with meetings.

Also, a smaller lesson: I sent 15 cold notes to early-stage founders yesterday, got zero replies, and by evening had decided it wasn't working. It had been one day. Turns out patience is a discovery skill, and I don't have it.

Question for anyone further along than me: how do you make discovery feel like progress? Do you track calls as a metric, force a decision out of every batch, something else? Because "it's important" hasn't been enough to get me to do it.