Discovery is diagnosis, not pitching. The best reps spend 70 percent of the call listening, ask quantified questions about impact, and leave with enough context to decide if the deal is worth working.
A discovery call is the first substantive sales conversation between a seller and a prospect, usually 30 to 45 minutes, used to understand whether there is a real fit. The rep learns the buyer's pain, business impact, buying process, decision criteria, and timing. The call ends with a mutual decision to continue, pause, or disqualify. Nothing is sold on a discovery call.
The six things a discovery call has to do, and the one that most reps skip in a hurry to show the product.
A discovery call is not a pitch. The seller is trying to answer three questions: is there a real pain, can we actually solve it, and is the buyer in a position to buy right now. Everything on the call serves one of those three. Products, pricing, and roadmap come later, after you know what you are selling against.
Half an hour is enough for a focused call with a prepared buyer. Forty-five is the ceiling. Anything shorter rushes the pain conversation. Anything longer burns executive calendar for a stage that has not yet earned it. If you cannot run discovery in 45 minutes, you have not booked the right next step on this call.
A six-beat agenda in that order. Open with an upfront contract so both sides agree on scope. Get context on the business. Dig into pain. Quantify impact. Walk the buying process. Set a mutual next step. The order matters: skipping the contract turns the call into an interview, skipping impact turns it into a vendor meeting.
SPIN sequences questions from Situation to Problem to Implication to Need-payoff, which is the diagnostic arc of a good call. MEDDIC checks whether a deal is actually workable: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. Together they cover both the conversation and the qualification.
Three signals that the deal is not real yet. Nobody internal is motivated to drive it. The timeline is "sometime this year." No executive has signed off on solving the problem. Any one of these on its own is survivable. All three together means you are the prospect's research project, not their vendor shortlist.
The call is captured, transcribed, and summarized by AI into the deal timeline so the whole team has context. The rep sends a brief recap with pain, impact, decision criteria, and the next step both sides agreed to. If there is no next step, there is no deal, which is useful information to find out on call one instead of call four.
A discovery call that works has a shape. Reps who wing it come out with notes that read like a feature wishlist and a vague promise to "circle back next week." Reps who run the six beats below come out with a quantified pain, a named decision maker, a buying process the buyer walked them through, and a next step both sides committed to on the call. That is the difference between a stage change and a stalled deal.
Open by stating the time you have, the topics you want to cover, and what a good outcome looks like for both sides. Ask the buyer to add or trade. The contract gives you permission to ask hard questions later. It also surfaces hidden agendas early, like a buyer who thought this was a demo.
Five minutes on company, team, role, and what the buyer owns. The point is not research you should have done before the call. The point is hearing how the buyer frames their own world, because the words they use are the words you will use back to them in the proposal.
Walk from current state to the gap. Open-ended questions, no leading. If the buyer says "our pipeline reporting is painful," do not jump to "we have great pipeline reports." Ask what makes it painful, how often it comes up, who else feels it. The specific description of pain is what you quote back in every follow-up.
Quantify. If reports are painful, how many hours a week does the team spend building them, and what does that mean in forecast misses or hiring plans. If data is stale, how often does leadership make a call off bad data. Unquantified pain does not fund projects. Quantified pain survives the budget conversation.
Ask the buyer to walk you through the last time they bought something similar. Who was involved. What killed the deals that failed. What approved the deals that landed. You are mapping the buying committee, the budget cycle, and the procurement pattern before you waste a quarter trying to guess them.
End with an agreed next step booked before you hang up. A technical validation call with the champion plus one engineer, next Thursday at 2pm. Not "I will send you some materials and we will see." If the buyer will not commit to a next step on the call, the deal is a maybe at best and a courtesy call at worst.
The two frameworks every discovery call draws from. SPIN gives you the question arc that moves a buyer from describing a situation to admitting a payoff. MEDDIC gives you a qualification scorecard that tells you if the deal is worth pursuing after the call ends. Use SPIN during the call. Use MEDDIC after. Teams that do both consistently out-forecast teams that lean on one or the other.
Open the discovery arc. What tools, what team, what process. Keep it brief, because situation questions do not sell anything on their own. They set the stage for the problem questions that do. Over-indexing on situation is the number one mistake in rep onboarding.
The pivot. What breaks, where, how often. Use the buyer's words. "What happens when the forecast misses?" is a better question than "Do you have forecasting problems?" because the first invites a story and the second invites a yes-or-no answer that goes nowhere.
The move most reps skip. If the forecast misses, what does leadership do, what gets cut, who gets questioned. Implication questions make the pain bigger in the buyer's own head without the rep ever claiming anything. By the time you reach the solution, the buyer is already selling themselves.
Flip the frame. If forecast accuracy went from 60 percent to 85 percent, what would change. The buyer describes the payoff, which becomes the ROI story in the proposal. You are not telling them what you are worth. They are telling you.
Metrics are the quantified outcome the buyer is tracking. Pain is the specific break causing the metric to miss. If you cannot write down both after the call, the deal has not been qualified yet. Both come straight out of the implication and need-payoff conversation.
The economic buyer is the single person who can approve the spend. The champion is the person inside the account who wants this to happen and will work for it when the rep is not in the room. Deals without a named champion stall. Deals without a confirmed economic buyer never close in-quarter.
The failure modes in a discovery call are predictable. Reps pitch before they diagnose. They skip the money question because it feels rude. They let the buyer run the agenda. They walk out without a next step. Every one of these mistakes shows up in CPR coaching, and every one is fixable with structure. The list below is the review the sales manager runs on the recording after the call.
The buyer says one thing that reminds the rep of a feature, and the rep is off to the races on a mini-demo. The buyer stops talking. The pain conversation never happens. The call ends on time with no quantified impact and no next step, because the rep sold a feature instead of diagnosing a problem.
If your notes read "forecasting is painful" instead of "the team spends 12 hours a week in spreadsheets and the forecast still misses by 20 percent," you did not do discovery. You did an interview. Pitch an interview to a CFO and you will lose. Pitch a quantified number and the deal funds itself.
A buyer who answered questions politely but has no stake in the outcome is not a champion. A champion asks you to come back, pulls other people in, and tells you what will kill the deal internally. If nobody on the call fits that description, the deal is a courtesy, not a pipeline entry.
When a buyer cannot name a decision window with a reason behind it, there is no event forcing the deal. No event, no deal in-quarter. Ask what has to be true for them to decide, and when that becomes true. If the answer is unclear, the forecast slot is unclear, so stop treating it as this-quarter pipeline.
Deals above a certain size always get kicked to an executive for approval. If the discovery call never names that executive and the champion will not commit to looping them in, the deal has a ceiling. Learn it on call one, not after a six-week POC. Multi-threading starts here.
The sentence that means no. If the buyer will not book the next meeting on the call, the deal does not have momentum, and your follow-up email is landing in an inbox that does not care. Push for the specific next step before you hang up. It is awkward exactly once, then it becomes the standard.
Discovery does not end when the call does. The recording is captured. The transcript is summarized. The deal fields are updated. The follow-up email is drafted. The next step is on the calendar before anyone forgets what was said. The sales manager reviews the recording for coaching the same day. Teams that automate this layer run twice as many quality discoveries per rep without burning out the reps.
The recording and transcript land on the deal timeline automatically. Nobody retypes the call. Nobody digs through a video platform. The next person on the deal, including the sales engineer and the manager, has the full context on the record, not in a rep's inbox or notes app.
Strkr AI reads the transcript and writes a structured recap into the deal: pain, impact metrics, decision criteria, next step. The rep edits for nuance instead of writing the summary from scratch. The whole deal team reads the same paragraph instead of each person building their own mental model.
Economic buyer, champion, pain, metrics, decision process, decision criteria. The qualification fields on the deal auto-populate from the summary with the rep as the final approver. The forecast review stops being a guessing game, because every open deal has the same six fields filled honestly.
A follow-up email draft lands in the rep's inbox within minutes of the call. Opening with the pain, the impact, the agreed next step, and the time of the next meeting. The rep sends in two minutes instead of writing it over coffee the next morning, which is where most follow-ups go to die.
Discovery calls get flagged into a coaching queue with the parts the manager should listen to: the pain pivot, the first time price came up, the next-step close. Two or three focused minutes of coaching per call, five days a week, moves a team more than one 90-minute monthly review ever did.
The next step, and the one after it, are written into a mutual action plan the buyer can see. Both sides agree on dates. When the plan slips, it slips visibly, which is a feature not a bug. The alternative is a deal that quietly drifts for three weeks before the rep realizes nobody is driving it anymore.
Strkr records every discovery call, writes AI summaries into the deal, updates MEDDIC fields from the transcript, and keeps the next step on the calendar before anyone forgets. One login for CRM, calling, and the forecast that runs off them.
Thirty to forty-five minutes. Half an hour is the sweet spot for a focused call with a prepared buyer and a six-beat agenda. Forty-five is the ceiling before you burn executive calendar on a stage that has not earned it. If you cannot complete contract, context, pain, impact, process, and next step in 45 minutes, split the conversation into two calls instead of running one that overruns.
A discovery call diagnoses the buyer. A demo shows the product. Discovery comes first and answers whether a deal is worth working. Demo comes second, after you know the pain, the metrics, the decision process, and the champion. Running them backwards is the most common reason deals stall in a long qualification cycle: the rep showed features before they understood what was being evaluated against them.
Open-ended questions that move through the SPIN arc: situation (how things work today), problem (what is not working), implication (what the problem costs downstream), need-payoff (what solving it is worth). Then qualification questions from MEDDIC: who approves the spend, who is the champion, what decision criteria matter, what the buying process looks like, what the timeline is driven by. Avoid yes-or-no questions that stop the conversation.
A thirty-second opener where the rep states the time available, the topics to cover, and what a successful outcome looks like for both sides, then asks the buyer to confirm, add, or trade. The contract gives the rep permission to ask hard qualification questions later without feeling pushy, and surfaces any hidden expectations before the call runs into them. It is the single highest-ROI minute of a discovery call.
Three to watch for. No champion, meaning nobody internal is motivated to drive the deal when the rep is not in the room. Vague timeline, meaning the buyer cannot name a quarter or an event forcing a decision. No exec sponsor, meaning no one above the champion has signed off on solving the problem. Any one of these is survivable with good execution. All three together usually means the deal is not real pipeline yet.
Yes, with the buyer's consent at the start of the call. Recording lets the rep stay present instead of typing notes, feeds AI summaries that update the deal automatically, gives sales managers coaching artifacts without having to sit on every call, and preserves the exact buyer language for proposals and follow-ups. Teams that record discovery consistently out-forecast teams that rely on hand-written notes, because the data is honest and shared instead of trapped in one person's notebook.
The recording and transcript land on the deal timeline. An AI summary writes a structured recap with pain, impact, decision criteria, and the agreed next step. The MEDDIC fields update on the deal. The rep sends a brief recap email the same day. The next step is already on the calendar from the call. The sales manager reviews the recording for coaching within 24 hours. Done well, the whole post-call sequence takes the rep less than ten minutes.
Use MEDDIC as the scorecard. By the end of the call you should be able to name the Metrics the buyer cares about, the Economic buyer who approves the spend, the Decision criteria the buyer will evaluate against, the Decision process the deal has to run through, the Pain the buyer wants to fix, and the Champion inside the account who will drive it when you are not there. If three or more fields are empty, the deal is not qualified yet, no matter how friendly the call felt.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
