Discovery Call Teardown: How a Rep Burned 25 Minutes and Learned Nothing
Twelve questions, twenty-five minutes, and nothing a manager could act on. Here is exactly where the call broke, and the structure I would run instead.
The call
What follows is a composite. I have heard some version of it more times than I can count, and if you record your calls you have probably heard yourself do a version of it too. Names and details are made up. The shape is real.
Rep is selling a sales enablement product. Buyer is a VP of Sales at a mid-market software company. Twenty-five minutes on the calendar. Here is the skeleton of what happened.
Minute 0-2. Small talk about the weather where the buyer lives. Rep confirms they still have twenty-five minutes. Buyer says yes.
Minute 2. "So, are you currently using any kind of enablement platform?" Buyer: "We have Highspot."
Minute 3. "Got it. And how many reps do you have?" Buyer gives a number.
Minute 4. "Are they mostly inbound or outbound?" Buyer: "Mix of both."
Minute 5. "Do you have a formal onboarding process for new hires?" Buyer: "Yeah, we have a thirty-day ramp plan."
Minute 6. "And is that working?" Buyer: "Honestly, not really. We keep losing people in month four. The ones who make it through onboarding fine still don't hit quota, and then they leave, and I'm back to square one with a new req."
Minute 6:40. "Okay, makes sense. And who owns enablement today, is that you or is there a dedicated person?" Buyer: "It's me and a manager."
Minute 7. "Do you run call reviews?" Buyer: "Sometimes."
Minute 8. "Are you happy with your current call recording setup?" Buyer: "It's fine."
Minute 9. "Great, so what I'd love to do is show you a little bit about what we do..." Screen share goes up. Sixteen minutes of product.
Minute 24. "So what do you think?" Buyer: "This is interesting. Let me talk to the team and I'll get back to you."
Minute 25. "Sounds great, I'll follow up next week."
Twelve questions. Twenty-five minutes. And if you asked that rep to write down, in one sentence, what problem this buyer has, what it costs them, and who else in the building cares, they could not do it. They have a logo, a headcount, and a competitor name. That is a CRM record, not discovery.
Where it broke
Every question had a one-word exit
Look at the first five questions again. "Are you currently using..." "How many reps..." "Are they mostly inbound or outbound..." "Do you have a formal onboarding process..." "Is that working..."
Four of those five can be closed out with a single word. The buyer answered exactly as asked. That is not a difficult buyer. That is a rep who built a form and handed the buyer a pen.
When you ask a closed question, you are deciding in advance what the interesting information is. You are saying: the thing I need to know is whether you have an enablement platform, yes or no. But you do not know that. You do not know anything yet. The whole point of the first ten minutes is to let the buyer show you where the pain lives, and closed questions make that structurally impossible.
The fix is not complicated and every rep has heard it. Ask questions that start with "walk me through," "what happens when," "tell me about the last time." Instead of "do you have a formal onboarding process," try: "Walk me through what happens the week a new AE starts. Who do they sit with, what are they doing on day three?" Now the buyer has to narrate, and inside the narration are all the seams.
The reason reps do not do this is not ignorance. It is that open questions produce long answers, and long answers are hard to steer, and steering is uncomfortable when you are new. Closed questions feel efficient. They are efficient at producing nothing.
The golden moment at minute six, walked straight past
This is the part that hurts.
At minute six the buyer said: "We keep losing people in month four. The ones who make it through onboarding fine still don't hit quota, and then they leave, and I'm back to square one with a new req."
That is the whole call. That is a VP of Sales telling you, unprompted, that he has an attrition problem tied to ramp, that he knows the ramp plan is not the actual problem, that he is personally the one absorbing the cost, and that the pain repeats on a cycle. There is emotion in the phrasing. "Back to square one." That is a man who is tired.
And the rep said "okay, makes sense" and asked who owns enablement.
When a buyer volunteers a problem you did not ask about, that is the most valuable sentence in the call, because it is the one thing they were thinking about before you dialed. Everything else is them answering your agenda. That sentence is theirs.
The correct response is to stop and go three layers down. Not one question. Three.
"Month four. Tell me about the last person you lost at month four — what was the conversation like when they told you?"
"When you say they don't hit quota, is it that they're not getting meetings or they're not closing the meetings they get?"
"How many did that happen to last year?"
That last one is the money question and it costs you nothing to ask. You have just been handed a repeating, quantifiable failure. Get the count. The count becomes the business case.
The second golden moment nobody noticed
Minute 7: "Do you run call reviews?" Buyer: "Sometimes."
"Sometimes" is a confession. Nobody says "sometimes" about a thing that is working. A buyer who runs call reviews every Tuesday says "yes, every Tuesday." A buyer who says "sometimes" is telling you the process exists on paper and dies in practice, and that they feel slightly bad about it.
The follow-up is one sentence: "Sometimes meaning what — when did you last do one?" Silence. Let them count backwards. Whatever they say next is real information, and it is information they gave you against their own interest, which is the only kind worth having.
Instead the rep moved on, because "sometimes" was close enough to "yes" and the rep had eight more questions on the list.
That is the tell. The rep was working through a list, not listening. A list makes you deaf. You cannot hear a soft answer when you are already reading the next line.
Minute nine, the pitch
Sixteen of the twenty-five minutes went to product. That is the majority of the call spent talking about a solution to a problem that had not been established, sized, or agreed on.
Here is what that demo could not do. It could not connect a single feature to month-four attrition, because the rep never asked what month-four attrition costs. It could not name the manager who would be the internal champion, because the rep never asked what that manager's week looks like. It could not create urgency, because nothing had been established as urgent.
So the demo was a feature tour. The buyer watched politely. Feature tours generate exactly one response, and the buyer gave it at minute twenty-four: "this is interesting."
I have never once seen "this is interesting" turn into a signed contract without something else happening in between.
The reason reps pitch early is not that they think it works. It is that discovery is uncomfortable and demoing is comfortable. You know the product. You have said those words a hundred times. Nobody pushes back during a demo. Minute nine is a rep taking shelter.
No next step, at all
"Let me talk to the team and I'll get back to you." "Sounds great, I'll follow up next week."
The rep just handed control of the deal to a man who is currently drowning in reqs and attrition. He will not get back to them. Not out of malice — he has a job.
A next step is not a promise to follow up. A next step is a calendar invite with a date, a named attendee, and a stated purpose, agreed to out loud before the call ends. Everything else is hope.
Rebuilding the same twenty-five minutes
Same buyer, same clock. Here is the structure I would run, and the reason I like it is that it moves in one direction and each stage earns the next.
Minutes 0-3: frame and permission
"I've got twenty-five minutes with you. My plan is to spend most of it asking about how your team ramps and where reps stall, because I don't know yet whether what we do is relevant to you. If it looks relevant I'll show you the piece that matters and we'll book time to go deeper. If it doesn't, I'll say so and give you the time back. Does that work?"
Thirty seconds. It does three things: it tells the buyer questions are coming so they do not feel interrogated, it removes the pressure to pitch, and it puts a next step on the table before minute one.
Minutes 3-9: current state
Not "do you have a process." Narrate it.
"Walk me through what happens when a new AE starts. Day one to day thirty. Who owns them?"
Then shut up. When they finish, pick the softest thing they said and go into it. Soft things sound like: "we try to," "sometimes," "in theory," "it depends," "honestly." Every one of those is a door.
By minute nine you should be able to describe their process back to them in your own words, and they should say "yeah, that's basically it." If you cannot do that, do not move on.
Minutes 9-14: cost of the current state
This is the stage most reps skip, and skipping it is why deals die at procurement.
"You said you keep losing people at month four. How many times did that happen last year?"
"When one of them leaves, what does it take you to replace them — recruiter fee, your time, the manager's time?"
"And in the months where the seat is empty, what happens to that territory?"
You are not doing this to build an ROI slide. You are doing it because a buyer who says the number out loud has done the arithmetic in their own head, in their own voice, and cannot un-hear it. Your job is to ask; theirs is to count.
If they do not know the number, that is also useful: "Would it be worth pulling? I ask because if we get to a point where you need to justify spend, that's the figure your CFO will want." Now you are already helping them sell internally.
Minutes 14-18: who else feels it
"Besides you, who else in the building notices when a rep washes out at month four?"
You are looking for names and reactions. The manager who has to run the desk short-handed. The recruiter who gets the req again. The RevOps lead whose forecast keeps missing because capacity assumptions are wrong. The CFO who signed off on headcount that never produced.
This is where you find out whether you have one frustrated person or a company-level problem, and it is where champions come from. It also tells you what the buying group looks like without asking the dead question "who else is involved in the decision," which every buyer has learned to deflect.
Minutes 18-21: what happens if nothing changes
"If you do nothing about this — same ramp plan, same tooling — what does next year look like?"
Watch the answer. If they say "honestly, probably the same," you have a status-quo problem, not a competitor problem, and you should plan the deal accordingly. If they say "I can't do another year of this, I've got a number to hit and I can't hit it with this team," you have a compelling event and you should ask when the pressure lands.
Ask about the deadline behind the pain: board meeting, fiscal year, a new number, a headcount plan that has already been approved. Urgency lives on a calendar or it does not exist.
Minutes 21-25: the next step, controlled
Do not ask "what do you think." Summarize, then propose.
"Here's what I heard. You've lost people at month four repeatedly, it costs you a recruiter fee plus a quarter of dead territory each time, your manager is absorbing coaching she doesn't have hours for, and you've got a bigger number next year with the same ramp process. Did I get that right, or did I miss something?"
Then: "The next thing I'd suggest is forty-five minutes with you and your manager, where I show you specifically how teams handle the month-three-to-four coaching gap. I've got Thursday at 10 or Friday at 2 — which is easier, and can she make either?"
Name the attendee. Name the purpose. Offer two times. Get the invite accepted while you are still on the phone.
The questions differ by market — what "current state" means to a claims director is nothing like what it means to a CRO — which is why I keep separate versions. If you sell software, the twenty-five-minute diagnostic for CROs, RevOps and growth buyers maps this structure onto a SaaS buying group. Selling into claims, where the cost of the current state is measured in cycle time and leakage rather than quota attainment, follows a different path, and I laid that out in the insurance discovery playbook. Staffing and recruiting deserves its own treatment because the buyer's pain almost always surfaces as "reqs go dark," and that playbook works the conversation backwards from there. Law firm buyers are different again, and the legal version accounts for partners who bill by the hour and therefore price their own time differently than anyone else you will ever sell to.
The summary email
The call is not over when you hang up. The email you send afterwards is the artifact your buyer forwards internally, and most reps waste it on "great speaking with you today."
Here is the shape I would send after the rebuilt call.
Subject: month-four attrition — recap + Thursday 10am
Mark,
Recapping so you can check my understanding and forward it if useful.
Where things stand today: new AEs go through a thirty-day ramp with you and Dana. Ramp itself works. Reps stall between month three and four, don't hit quota, and leave. Call reviews happen when there's time, which lately there hasn't been.
What it costs: each washout is a recruiter fee plus a territory sitting idle until the replacement ramps. You said this happened more than once last year.
Who else it hits: Dana absorbs the coaching, and she's already running a full desk. Recruiting gets the same req back.
If nothing changes: same process against a bigger number next year.
Next step: Thursday 10am, 45 minutes, you and Dana. I'll walk through exactly how teams close the month-three-to-four coaching gap and what it takes to stand up. Invite is in your inbox.
If I got any of that wrong, correct me before Thursday so I don't waste Dana's time.
Tim
Notice what is not in there. No product description. No "as discussed, our platform offers." No PDF. The email is the buyer's own problem, in the buyer's own words, organized so a CFO could read it in forty seconds. That last line — correct me before Thursday — gets replies, because people will not confirm but they will absolutely correct.
What I would actually do this week
Pull your last five recorded discovery calls. For each one, write down three things: the problem in one sentence, what it costs, and the name of one other person who feels it. If you cannot fill in all three from the recording, that call was a conversation, not discovery, and the deal in your pipeline behind it is softer than the stage says.
Then count how many minutes in you started pitching. If the answer is under ten, that is your single highest-leverage fix and it is free.
The part you cannot fix by reading is the reflex — hearing "sometimes" and stopping on it, hearing "back to square one" and going three layers down instead of moving to your next question. That is muscle, and muscle comes from reps, which is the entire reason I built DrillCall: so you can run the same discovery opening thirty times against an AI buyer who pushes back, before you run it once against a VP who only gives you twenty-five minutes. If I were starting over in this job today, I would drill the follow-up question, not the opener. The opener gets you into the call. The follow-up is what gets you the deal.