Your prospect books a call, doesn't show up, and then emails "we're moving forward with someone else" two weeks later. Or they show up, you demo for 30 minutes, they say "sounds great, I'll think about it," and you never hear from them again. Ninety percent of discovery calls fail because they're not actually discovery — they're one-way pitches disguised as conversations. You talk for 20 minutes, demo for 15, and ask "any questions?" at the end. By then, you've already lost them. Bad discovery calls cost you closes, wasted pipeline time, and zero insights into what your buyer actually needs. Good discovery calls flip the ratio: *them* talking 60%, *you* listening 30%, *you* guiding 10%. Here's the exact 45-minute format Aidxn runs that flips no-shows into signed contracts.
Why Discovery Calls Fail (Before They Even Start)
Most SaaS founders run discovery calls like job interviews: you ask questions, they answer, you probe, they get defensive. They leave feeling like they've been interrogated. They don't call back. Here's what actually happens on a failing discovery call:
You start by talking about your company for 3 minutes. They zone out. You ask them about their current workflow for 5 minutes. They give surface answers because they don't trust you yet. You jump into the demo because silence is uncomfortable. You show 8 features. They remember 1. You ask "any objections?" and they politely demur. You leave thinking "they're interested" and follow up 5 times with zero response. Reality: they weren't listening because you never gave them permission to actually tell you what they're stuck on.
Good discovery inverts this. *They* do 60% of the talking. *You* ask clarifying questions that make them feel heard. By minute 20, they've told you more than they've told anyone else about this problem. That's when they start leaning in. That's when a close becomes possible.
The 5-Block Discovery Call Format (45 Minutes Exact)
Block 1: Context & Rapport (0–5 minutes)
Start soft. No pitch. "Hey [name], thanks for taking the time. Before we dive in, I'd love to know — what made you reach out to us? And how'd you find us?" Let them answer. You're listening for two things: (1) What problem is hot enough to interrupt their day? (2) What language do they use to describe it? That language becomes your sales language going forward.
Follow up: "And what's your role in [their company]? What does your day-to-day look like?" You're building rapport by showing genuine curiosity. You're also qualifying: are they the decision-maker or a delegate? Can they actually buy, or are they just exploring?
Red flag: if they don't know who you are or what you do, they booked the wrong call. Don't waste time. "Sounds like we might not be the right fit, but let me ask: is there a specific problem you're trying to solve right now?" If the answer is vague, end early. Don't pretend urgency exists where it doesn't.
Block 2: Problem Discovery — Let Them Talk (5–20 minutes)
This is where 95% of salespeople fail. They jump to the demo. You don't. You ask one question and *shut up*.
"Walk me through your current workflow. Show me the tools you're using, the people involved, and where the biggest friction is." Then silence. They'll fill it. Most people won't stop for 3–4 minutes once they start. Let them go. You're not gathering information — you're giving them permission to vent.
As they talk, you listen for pain language: "we waste hours," "nobody likes this tool," "it breaks constantly," "we're shipping [solution] manually." Jot it down. When they pause, mirror it back: "So you're spending 5 hours a week on something that should take 30 minutes?" They'll nod and elaborate. You've just validated their pain. They'll like you more.
Problem discovery questions to follow:
1. "How long have you been managing this this way?" (Timeline builds frustration — the longer, the more they want relief.)
2. "What's the biggest frustration with your current setup?" (Gets to core pain. Listen for emotion, not features.)
3. "If you could change one thing about this process, what would it be?" (Reveals their priority, not your roadmap.)
4. "How much time does this cost you per week?" or "What's the business impact if this breaks?" (Quantifies pain. Makes ROI stick.)
5. "Have you tried solving this before?" (Red flag if they've tried 3 competitors and nothing worked. You might not be the fit.)
6. "Who else is involved in making a decision if you want to move forward?" (Identifies if you're talking to the buyer or an influencer.)
Rule: ask and *wait for the answer*. Don't fill silence with nervous talking. The person who talks least wins the negotiation.
Block 3: Mutual Fit Assessment (20–30 minutes)
Now you've heard the problem. Before you demo, confirm you're actually a fit. Nothing's worse than demoing something they don't need.
"Based on what you've described, here's what I think might help: [restate problem in their words]. Does that land?" They'll nod or push back. If they push back, *listen harder*. You might have missed something. Ask again: "What am I missing?"
Then ask the fit question: "If we could solve [specific problem they named], would that be valuable for your team?" Listen for commitment language: "absolutely," "definitely," "yes, but..." vs. "maybe," "potentially," "I'd need to think about it." The first is a buyer. The second is a tire-kicker. Spend your demo time on buyers.
Next, disqualify if needed: "I want to be straight with you — this solution works best for teams with [X constraint]. Do you have that?" Example: "It works best if you're already using Slack." Or "It requires at least a basic API integration." If they don't have it, say so now. You'll lose this deal anyway, and they'll respect the honesty. Plus, you'll seem competent, not desperate.
Lastly, get timeline: "If this worked for you, when would you want it live?" If the answer is "next quarter," that's a long sales cycle. If it's "next week," that's a close. Adjust your energy accordingly.
Block 4: The Demo + Objections + Price (30–40 minutes)
Now you demo. But *not* the full tour. Show them *one path* through your app that solves the problem they named. Not the five things you're proud of. One thing. Two minutes max.
"Here's how this would work for your specific use case: [show flow]. Does that look like what you were imagining?" They'll say yes, or they'll say "but what about [feature]?" If they ask, that's a buying signal — they're already imagining using it. Answer the question: "Great question. We handle that by [answer]. What else?"
When objections come, probe instead of defending: "I hear you. Tell me more about that concern. When you say [objection], what specifically worries you?" Most "objections" are actually negotiations. They're saying "I'm interested, but I need reassurance on X." That's a close, not a no.
Price reveal timing is critical. Never reveal price before they're bought on the problem. You've just spent 20 minutes proving you understand them. Now they see value. *Now* you can say price.
"We start at $X per month for teams like yours. What does your budget typically look like for a tool like this?" Ask *their* budget first. Half the time, they'll say a higher number than you quoted. Let silence hang. Don't fill it with discounts.
If they flinch: "I get that. Here's what I can do: if you commit to [longer contract / more seats / beta feedback], I can lock in [lower price]. What matters more to you — immediate savings or lower commitment?"
Block 5: Next Steps & Calendar Lock (40–45 minutes)
No wishy-washy "I'll follow up." Three paths:
Path 1 (They're buying): "You seem like a great fit. Here's what I propose: let's schedule a 30-minute call with your team lead so they see this too. How does Thursday afternoon look?" Lock the calendar *on the call*. Don't say "I'll send you a calendar invite." They'll ghost.
Path 2 (They're interested but need convincing): "Perfect. I'll send over a proposal, a customer case study from a similar company, and a price breakdown. I'll follow up on Thursday — does that work?" Send the assets *same day*. Make the follow-up a calendar block, not "I'll reach out." Specificity drives action.
Path 3 (They're not a fit): "I don't think we're the right fit for your specific workflow, but I have a colleague at [competitor] who does X really well. Want me to intro?" You've just become helpful, not pushy. They'll remember you. Referrals come back.
End every call with: "Is there anything else you want to ask before we wrap?" Silence. Then: "Great. I'm excited about the possibility of working together. Talk soon." No over-selling at the end. They're either in or they're not.
The Problem-Discovery Question Bank (Copy This)
Adjust to your product, but the structure stays the same. Ask, listen, probe, don't pitch.
Current state: "Walk me through your workflow." "How many people does this involve?" "What tools do you use?" "Where do things typically break?"
Pain quantification: "How much time does this cost?" "How often does this go wrong?" "What's the business impact?" "Who gets frustrated?" "How much revenue is tied to this process?"
Past attempts: "Have you tried solving this before?" "What didn't work?" "Why did you switch away?" "What would be different this time?" (Last one is crucial — it reveals if they're looking for magic or willing to change.)
Decision making: "Who else would need to sign off?" "What's your approval process?" "What's the budget?" "What's your timeline?" "What would success look like?"
Fit confirmation: "Does this sound like something that would help?" "If we could fix [problem], would it be worth it?" "What would need to be true for you to move forward?"
When To Reveal Price (And How Not To Screw It Up)
Price comes *after* they're bought on the problem, never before. Timeline: minute 32–35. By then, you've spent 20 minutes earning credibility. They're leaning in. That's when numbers stick.
Script: "For teams in your situation, we typically structure it as $X/month, plus a one-time setup of $Y. What does your budget usually look like for something like this?" You've anchored the number. Now ask *their* budget. This is where you learn if they're price-sensitive or problem-sensitive. If they say "we'd need to keep it under $Z," they're negotiating, not rejecting. That's a close.
Never discount on the call. Ever. "I appreciate that. Here's what I can do: if you commit to a quarterly contract instead of monthly, I can offer $X instead. What works for you?" Tie discounts to *commitment*, not just number-shopping.
Recording Calls: The Unfair Advantage
Ask permission: "I like to record so I can take better notes and make sure I'm remembering everything correctly — is that okay?" Nine out of ten say yes. Record everything. Transcribe with Otter, Fireflies, or your CRM transcription tool.
Why? By call 30, you have a searchable database of exact customer language. You see patterns you missed live. You hear yourself repeating an explanation that confuses people. You spot the moment someone stops listening. You find the exact phrase that makes someone lean in. That's worth 10x any "sales training course." You're training yourself on real data.
Six FAQs
What if they don't show up?
No-show rate is 60% because most people don't have skin in the game. Two fixes: (1) Charge for the call ($49–499). Even small fees change behavior. (2) Send a reminder 24 hours before with the Zoom link and your personal phone number. "If you have any questions before we talk, text me." Shows you're serious.
What if they go silent after the call?
Three follow-ups: (1) Same day: "Great talking to you today. Here's the proposal we discussed." (2) 3 days later: "Wanted to circle back — do you have questions on the proposal?" (3) 7 days later: "Haven't heard back. Is this still a priority for your team?" If they don't respond to three touches, they're not interested. Move on. Don't haunt them.
What if they ask "Can you send a demo link instead of a call?"
No. "I could, but I'd rather talk first so I understand your specific use case. The self-serve demo is great for exploration, but you'll get a lot more value if I walk you through it tailored to your situation. Sound fair?" Most will say yes. Self-serve kills deals because there's no human in the loop to answer "wait, but how does X work?"
What if they mention a competitor?
Don't trash-talk. "Oh, we actually respect them. Here's how we're different: [genuine difference]. Does that matter for your use case?" You'll seem mature. They'll trust you more. If the competitor is genuinely better for them, say so. Honesty builds credibility that turns into referrals.
What if they want to get your team involved early?
Good sign. "Absolutely. Let me understand your needs a bit more first, then I'll loop in [engineer / success lead / whoever] so they can answer technical questions. Sound good?" You prevent "we have 10 people on this call and nobody's clear on the problem" meetings. Tight internal pre-calls beat loose group calls every time.
Should I share pricing before the call?
No. You lose negotiation leverage. Pricing triggers anchoring bias — they'll evaluate value against the number, not against their pain. Keep it off the website if you can. "Pricing depends on your use case — let's talk first" creates urgency and gets them on the call. Once they're bought on the problem, price becomes secondary.
The Bottom Line
Discovery calls fail because you're talking, not listening. Flip it. Let them own 60% of the conversation. Ask one question and wait. Quantify pain in their language. Demo only *one* solution path. Reveal price after they're bought on the problem. Lock next steps on the call, not via email. That's it. No special closing techniques, no high-pressure objection handling, no manipulation. Just rigor.
You want to explore a discovery call format for your business? Read the founder-led sales post for the philosophy, then check our pricing page to see how we structure paid discovery. We run these calls with intention, and they close. Ready to talk?