The difference between a discovery conversation and a sales pitch is one question

My friend Tim and I were messaging a couple of weeks ago, just catching up. Toward the end, I asked him if he knew any startups that needed focused customer interviews. He typed back almost immediately, saying, “All of them.”

He’s not wrong and that's a big question for How This Works co, especially because my main services involve some form of customer discovery and customer interviews. To that end, I’ve been asking about how others approach the subject — talking to other service practitioners, founders, and early-stage teams. But I’m not pitching; I’m asking questions, I’m listening, keeping it casual. When someone asks me about a Listening Cycle or the Bullseye Customer Sprint, I deflect. What are they doing instead? How do they run interviews now? What have they tried?

I’ve run into very few people who say they don’t talk to customers. Or are looking for customers. I’ve even had some of them show me their calendars, which are full of friendly check-ins, support calls, and other outreach. But then I ask what kinds of questions they’re asking in those calls. More often than not, they admit something like, "We ask them to sign up on a trial, sometimes free or with a discount."

Pitching has its place — but not before your team knows what they're building toward. Discovery isn't a phase you finish and move on from. It runs alongside your building, for the life of your company. Teresa Torres puts it simply: weekly interviews, same time, every week. Every Thu at 1p, for instance. It's not instead of growing your business — it's what makes growing your business possible.

The goal of a discovery interview is to pull as much value in minimum time from conversations so you can get back to what really matters: building your business.

And it's hard not to sell, especially in an early-stage startup. It feels like sell or sink — I get it. And it's easier to start with the feature set because it's something we know and because we want to be helpful; to say, "Look, this is how we can fix this for you." I still trip over this myself — even having run more than 150 interviews in the last year. Hell, I lead gen pitched at my friend Tim.

Yes, I still feel that itch to offer a solution when a customer mentions a pain point. Because selling feels like "doing the work." And it feels like that’s what we should do. Be a helper, be a fixer.

But a discovery conversation has a wholly different job. In it, you want to learn about who they are, what’s hard, how they make decisions, what they’ve tried in the past. The moment it turns transactional, when you turn on the sell, the customer feels it. They become increasingly polite and that stiff version of themselves shuts the door — lips get tighter and they’re looking for the exit. You think you’re still learning more about them, but they’re just trying to get off the phone. It breaks the trust, it breaks the mood.

A discovery conversation should be mostly listening, asking, “Tell me more about that," and hunting for clues. You aren't there to confirm what you already believe; you’re there to find out what you might not yet know.

Most of us default to our own assumptions without realizing it, whether they’re individual ones or a whole group’s. We don't realize that by "being helpful" with our features, we’ve actually shut the door on the truth. And if you kill the truth, they probably won't talk to you again.

And that’s the real test for a good discovery interview: Do they actually want to talk to you a second or third time? Not did you get the data, not did they validate your hypothesis, did the human on the other end feel heard enough to want to do it again?

Most founders couldn’t honestly answer this about their last customer conversation.

And that’s the difference between a conversation where you learn something that’s worth putting into your roadmap or just a polite answer from someone who probably won’t sign up for your product or will cancel as soon as they are able.

Every sprint cycle built on polite answers is runway you won't get back; you're not just missing data, you're building your future on false positives. The pattern I keep seeing: the teams furthest from real discovery are almost always the ones most confident that they’re doing it well. They mistake activity for insight, and by the time they realize their helpful discovery calls haven't actually moved the needle, the runway is already gone.

I’m still working on this myself, reworking my own service offerings by staying curious instead of selling. It’s slower. And it’s uncomfortable. But it’s also the only way I’ve found to hear the thing that actually changes what you build.

And Tim's right. It's all of them. Not just startups, me too.

But the pitch reflex isn't the only way a discovery conversation goes sideways. More on that next time.around

Skipper Chong Warson

_{Only humans buy anything, stop building for the wrong customer}

_—

_{If you want to know what a real discovery conversation looks like for your team, let’s talk: howthisworks.co/start}