The first real sales call most founders take is a disaster, and not because they’re bad at selling. It’s because they treat it like a demo. They talk for forty minutes, show every feature, and hang up feeling great, then never hear back. Knowing how to run a discovery call is the fix, and the whole shift is simple: you’re there to find out if this person has a problem you can solve, not to prove your product is clever. The best ones feel less like a pitch and more like a doctor figuring out what hurts.
You don’t need a sales background to do this well. You need to talk less than feels natural and get genuinely curious about the person on the other end. Here’s the shape of a call that actually tells you something.
How to run a discovery call without pitching
Open by handing them the floor. “Tell me what made you take this call” beats any intro you could give about yourself. Then shut up and listen. The person who booked time with you has a reason, and your only job in the first ten minutes is to understand it well enough to repeat it back. If you’re talking more than they are, you’re doing it wrong, and you’re learning nothing you can use to actually help them.
Resist the urge to solve things the second you hear a problem. Keep pulling the thread. “How are you handling that today?” and “what does that cost you?” turn a vague complaint into a real, sized problem. By the time you do mention your product, you’ll know exactly which part to point at and which parts to skip entirely.
Listen for the cost, not just the complaint
Everyone has annoyances. Not everyone has a problem worth paying to fix. The difference is cost: time bleeding away, money lost, a customer who churned, a launch that slipped. When someone can put a number or a real consequence on their pain, you’ve found a buyer. When they shrug and call it a minor irritation, you’ve found a tire-kicker, and that’s useful to know on minute fifteen instead of week three.
This is also how you avoid building for people who’ll never pay. The loudest complaint isn’t always the most expensive one. Follow the cost and you follow the money.
End with a clear next step or a clean no
The worst way to close a call is “I’ll send some info, let me know what you think.” That’s where deals go to die. Either there’s a real fit, in which case you name the next step out loud and put it on the calendar before you hang up, or there isn’t, in which case you say so kindly and free both of you. A clean no on the call is worth ten polite maybes that haunt your pipeline for a month.
The questions you ask are what make or break all of this, and having a few good ones ready beats improvising. A solid set of discovery call questions gives you the prompts that get people talking about the cost of their problem instead of trading pleasantries.
The call goes better when the person was right to begin with
Here’s the part no technique fixes: a discovery call with the wrong person is just a pleasant waste of thirty minutes. All the listening in the world won’t surface a cost that isn’t there. The calls that flow are the ones where the person already had the exact problem you solve, and you both feel it within the first two questions.
That’s the work we built Unbound Compute to do before the call ever happens: finding the specific people publicly showing the problem you fix, so the person across from you is pre-qualified by the fact that they have the pain. You still run the call. We just make sure it’s a call worth running.