60-Min Sales Training: Discovery Call Fundamentals

Two ways to spend the hour: framework-first or reps-first

Every manager who sits down to design a 60-minute discovery training faces the same fork, and picking wrong is why most of these sessions evaporate by Wednesday. Option A is framework-first: you spend the front half of the hour teaching a model — A-P-I-C, MEDDPICC, SPIN, whatever your org standardizes on — with a whiteboard, a call recording, and a Q&A. Reps understand *why* the sequence works. The back half becomes a short demonstration and a homework assignment. Option B is reps-first: you spend eight or nine minutes on the barest possible scaffolding, hand out a printed script card, and burn the remaining fifty minutes on timed role-play rounds with an observer rubric.

The trade-off is real and it is not obvious. Framework-first produces better *understanding* and worse *behavior change*. Reps can explain the three layers of pain probing on Tuesday and still open their next discovery call with "so tell me a little about your role." Understanding a sequence and being able to execute it under the mild social pressure of a live buyer are two different skills, and only one of them transfers from a whiteboard.

Reps-first produces the opposite problem. Reps who have run three role-plays can execute the agenda-set nearly verbatim, but when a buyer goes off-script — asks for pricing at minute four, brings an unexpected second stakeholder, says "we already have a vendor" — they have no model to fall back on. They know the moves, not the logic. They freeze, then default to demo.

There is a third structure worth naming because it is what most experienced sales trainers actually converge on: teach-drill-teach-drill, alternating in tight cycles. Ten minutes of framework, ten minutes of drilling that specific piece, ten more minutes of framework, twenty more minutes of drilling. It's harder to facilitate — you're switching modes four times in an hour and the room's energy has to follow you — but it beats either pure option on retention because each concept gets encoded twice, once declaratively and once procedurally.

For a 60-minute constraint specifically, the honest recommendation is a weighted reps-first: roughly 15 minutes of teaching, 35 minutes of drilling and script work, 10 minutes of accountability setup. You lose depth on the framework. You accept that. The framework can be a one-page card that reps re-read on their own; the muscle memory cannot be acquired asynchronously.

A fourth option deserves mention only so you can rule it out: call-review-first, where you spend the hour listening to recorded discovery calls together and critiquing them. This is excellent coaching and a poor training. Reviewing calls builds evaluative skill — reps get better at hearing what went wrong — without building executional skill. Save it for the weekly 1:1, not the Monday hour.

How to decide which structure fits your team

The choice is not aesthetic. Four variables should decide it for you, and you can assess all four in about five minutes of honest thinking before you build the deck.

Variable one: tenure mix. If more than half the room is under six months in seat, go framework-heavier — closer to 20 minutes of teaching. New reps do not have the pattern library to improvise from, so drilling without a model just encodes whatever they happen to say. If the room is mostly two-plus-year AEs who have run hundreds of discovery calls, go reps-heavier — 8 to 10 minutes of framework, then drill hard. Experienced reps don't need the *why*; they need someone to interrupt their bad habits in real time.

Variable two: the specific failure mode you're fixing. Pull ten recent discovery calls and identify where they actually break. If calls die in the first three minutes — no agenda, no time-box, rep launches into a company overview — you have an opening problem and the whole hour should be agenda-set drilling. If calls have decent openings but never reach a quantified impact, you have a depth problem and the hour goes to the three-layer pain drill. If calls are good throughout and end with "I'll send you some times," you have a closing problem and the hour goes to mutual-close reps. Trying to fix all three in one hour fixes none.

Variable three: whether you can enforce follow-through. Training without a Friday metric decays fast. If you have call recording, a CRM field you can require, and the standing to hold a Friday huddle, you can run a lighter session because the week does the reinforcement. If you have none of those, the hour is all you get and it needs to be maximally procedural.

Variable four: room size. Under six reps, you can run whole-group role-plays where everyone watches and critiques — highest quality feedback, lowest volume of reps. Six to twelve, pair up with an observer rotation. Over twelve, you cannot run meaningful role-play in an hour; split into two sessions or accept that the hour is a framework teach and push the drilling into 1:1s.

The decision tree above is worth walking literally, on paper, before you build the session. Managers who skip it tend to build the training they personally enjoy running rather than the one their team's call recordings say they need.

What each block actually costs in minutes

Abstract structure advice is useless without a clock. Here is what each option consumes, with the trade-off made explicit.

The framework teach: 10 to 20 minutes. Teaching A-P-I-C properly — four beats, what each one is for, what it looks like when it fails — takes about 12 minutes if you talk fast and don't take questions mid-stream. Add a recorded call excerpt as illustration and you're at 18. Add open Q&A and it will expand to fill whatever you give it, which is the main way these sessions die. Hard-cap it and park questions on the whiteboard for the last block.

The four beats and their in-call budget, assuming a 30-minute discovery call:

• A — Agenda set: 2 to 3 minutes of the call. State your purpose, ask theirs, agree on the time-box, pre-commit to a decision at the end.
• P — Pain: 10 to 12 minutes. Three layers: surface symptom, operational cost, personal cost to the buyer's own number.
• I — Impact: 8 to 10 minutes. Convert the pain into a figure the buyer will repeat internally.
• C — Close the loop: 3 to 5 minutes. Recap in their words, propose a specific next step, book it while both calendars are open.

Note the shape: pain and impact together are two-thirds of the call. Most reps invert this and spend two-thirds on discovery-flavored pitching.

The script block: 15 to 20 minutes. Reading five scripts aloud as a group, with a one-line rationale for each, runs about 15 minutes. Reps highlight the lines they'll use that week. The cost here is that reading is passive — this block feels productive and produces less transfer per minute than drilling does. Its real value is standardization: after this block everyone in the room is working from the same words, which makes the Friday debrief comparable across reps.

Role-play rounds: 15 to 30 minutes. The unit is a 5-minute round — 4 minutes of play, 1 minute of observer feedback — and you need to run it twice per pair so both reps get a turn, so budget 10 minutes per scenario for a paired room. Three scenarios is 30 minutes and is the most valuable half-hour in the session. Two scenarios at 20 minutes is the practical compromise inside 60. One scenario is not a training, it's a demonstration.

Accountability setup: 5 to 10 minutes. Naming the metric, the CRM field, the Slack channel for call links, and the Friday time. This block gets cut first when the session runs long and it is the block that determines whether anything survives to Thursday. Protect it: put it at minute 50 and start it on time even if role-plays are unfinished.

The realistic 60-minute allocation, if you want one number to start from: 5 setup, 15 framework, 15 scripts, 20 role-play (two scenarios), 5 accountability. That's a full hour with zero slack, which means you will run over unless you use a visible timer. Use one.

A note on group size math. With 8 reps you have 4 pairs; a 5-minute round run twice is 10 minutes of wall-clock regardless of how many pairs there are, since pairs run in parallel. With an odd number, the manager takes the spare rep as a buyer — which is also the best use of the manager's time, since you get to feel firsthand where the scripts break.

Running the hour and the week that follows

Sequencing matters more than content here. The same material in a different order produces a different Friday.

Minute 0-5, the setup. Open on time. Put the agenda on screen before anyone sits. State the one thing the hour is for in a single sentence — "we are fixing the first three minutes and the last three minutes of every discovery call" — and name the Friday metric immediately. Naming the metric at minute one rather than minute 55 changes how reps listen for the whole hour, because they now know what they'll be measured on.

Minute 5-20, the framework. Teach A-P-I-C. Draw it on the whiteboard with the in-call minute budget next to each beat, because the budget is the part reps remember. Flag the two killer mistakes up front: skipping the agenda-set because it "sounds robotic," and drifting into demo when the buyer asks to see the product. Both get recovery lines later; naming them now primes reps to notice them during the role-plays.

Minute 20-35, the scripts. Hand out a one-page card. Five blocks:

*The agenda set.* "Here's what I had planned for the next 30 minutes. I want to spend the first fifteen understanding what triggered you to take this call. Then I'll share two or three things I've learned working with similar teams that may or may not apply. We end with a clear yes or no on whether a second conversation makes sense. Anything you'd add or change?" The "yes or no" phrasing matters — giving the buyer explicit permission to decline lowers their guard and raises the quality of what they tell you.

*The trigger question,* which replaces "tell me about your role": "What changed in the last 90 days that made looking at this worth your time this quarter?" Generic questions get generic answers; this one gets a story, and the story contains the compelling event.

*The three-layer drill,* used after the first pain surfaces. Layer one: "Walk me through the last time that happened — what did it look like?" Layer two: "When it happens, what does it cost the team — hours, headcount, missed pipeline?" Layer three: "And how does that show up for you personally — your quarter, your board update, your team's bandwidth?" Layer three is where champions are made. Most reps stop at layer one.

*The impact pivot.* "You said you're losing roughly two reps a quarter to manual data entry. If I asked your CFO what fully-loaded cost that represents, what number would they give me?" The point is not the number you get; it's that the buyer sourced it themselves and will now repeat it internally on your behalf.

*The mutual close.* "Quick recap so I know I heard you right — you said [pain], it's costing you [figure], you want to be live by [date]. Did I get that? The natural next step is a 45-minute working session with you, me, and [economic buyer]. I have Thursday at 10 or Friday at 2 — which works? Let's pin it now while we're both here." Three moves in one breath: recap, confirm, book live.

Minute 35-50, the role-plays. Two scenarios, paired, with an observer scoring on three dimensions each rated 1 to 3: script fidelity, earned the next question, and closed the loop. Scenario one, the buyer says "our forecast is always off by 20%" and the selling rep must run all three pain layers without pitching. Scenario two, the buyer gives a lukewarm "this seems interesting, send me some info" and the rep must run the mutual close and book live. Swap roles after each. The observer rubric is what makes this training rather than theater — without it, feedback defaults to "yeah, that was good."

Minute 50-60, the commitments. Three, written down: use the agenda-set and mutual close verbatim on every discovery call Tuesday through Thursday; post one call recording link per day to a shared channel, timestamped to the moment you want feedback on; log second-meeting outcome in the CRM by Thursday end of day. Close the hour on the minute.

The four pitfalls and their recovery lines, which belong on the back of the script card:

*Skipping the agenda-set because "the SDR already covered it."* The SDR's framing evaporates when a new person joins. Recovery: "I know [SDR] walked you through the basics — I want to make sure we're aligned on what today's thirty minutes covers."

*Drifting into demo at minute twelve.* The buyer asks to see the product and the rep capitulates. Recovery: "Happy to — and I want to make sure I show you the right two screens. Give me three more minutes on what you're trying to solve so the demo actually lands."

*Accepting a vague impact number.* "A few hundred thousand" moves no CFO. Recovery: "Help me get sharper — is it closer to 200K, 500K, or seven figures? I want my proposal to match the size of the problem."

*"I'll send you some times."* Recovery: "Let's not bounce emails — my calendar's open right now, yours is too. Let's pick something before we hop off."

And the universal save when a call goes sideways: "I want to pause for ten seconds — are we still on track for what you wanted out of this call, or has something shifted?" Re-contracting mid-call recovers more discovery calls than any other single move.

When one hour isn't enough

Be honest about the ceiling. A 60-minute session can install two behaviors reliably. It cannot install six. If your discovery calls are broken at the opening, the middle, and the close simultaneously, you are looking at a three-week program, not a Monday meeting — one hour per week, one failure mode per hour, with the Friday metric changing each week to match what you drilled.

The sequencing for a three-week version: week one is the opening (agenda-set and trigger question, metric = percentage of calls with a stated time-box, verifiable from recordings), week two is depth (three-layer drill, metric = percentage of calls containing a quantified impact figure), week three is the close (mutual close, metric = second-meeting set rate, which is the one that actually matters commercially). Running them in that order matters, because a rep who can't hold the opening has no standing to run the drill, and a rep who never quantified impact has nothing to recap in the close.

The other ceiling worth naming: training does not fix a targeting problem. If reps are running discovery calls with people who have no budget, no compelling event, and no authority, better questions produce clearer confirmation that the deal isn't real. That's actually a win for pipeline hygiene — a fast disqualification beats a slow one — but it will show up as *lower* second-meeting set rate in the first two weeks. Warn the team about this before it happens or they'll conclude the training made things worse. The metric to watch alongside set rate is second-meeting *show* rate; if set rate dips while show rate climbs, the discovery fundamentals are working exactly as intended.

Related questions

Should the manager role-play or just observe?

Both, in that order. Demonstrate the agenda-set once badly and once well so reps can hear the difference, then step out and observe. If the rep count is odd, take the spare rep as a buyer — it's the fastest way to find where your own scripts break.

How often should this hour be repeated?

Re-run the full session when the team composition changes materially or the metric slips two weeks running. Otherwise a 10-minute drill at the start of the weekly pipeline meeting maintains it. Full re-training more than quarterly signals a hiring or enablement problem, not a skills gap.

What if reps say the scripts sound unnatural?

They will, and they're partly right — verbatim delivery sounds stiff for about five calls. Require verbatim for one week to build the pattern, then allow paraphrase on everything except the agenda-set and the close, which stay word-for-word because they're the highest-leverage sentences on the call.

Can this training run remotely?

Yes, and role-plays work better over video because that's the actual medium. Use breakout rooms for pairs, keep rounds to 5 minutes, and have observers post rubric scores in chat so you can see them. The one thing you lose is the whiteboard warm-up; replace it with a shared doc.

What is the single metric to hold reps to?

Second-meeting set rate, logged Thursday, compared Friday. It's downstream of every behavior you taught and it's hard to fake. Pair it with second-meeting show rate so reps can't game the number by booking meetings nobody attends.

FAQ

What is the A-P-I-C sequence?

Agenda, Pain, Impact, Close-the-loop — four beats that map to a 30-minute discovery call. Agenda takes 2 to 3 minutes, pain 10 to 12, impact 8 to 10, close 3 to 5. It's a scaffolding for sequencing, not a script; the words are yours, the order isn't.

How long should a discovery call be?

Thirty minutes is the practical default for a first call, and the training is built around that budget. Longer calls aren't better calls — a 45-minute discovery that spends 20 minutes on product is worse than a tight 30 that reaches a quantified impact and a booked next step.

Do new reps and tenured reps need different versions of this hour?

They need different weightings, not different content. New reps need more framework time because they have no pattern library to improvise from. Tenured reps need more drilling because their problem is habit, not knowledge. Same script card, different clock.

What if we don't have call recording?

Run the session anyway, but shift the accountability block toward self-reported CRM fields and a Friday huddle where reps narrate one call each. It's weaker — you're trusting recall over evidence — so compensate by sitting in on live calls yourself, at least one per rep in the week following.

How do we keep the training from decaying by Wednesday?

Name the metric in minute one, require the CRM field, and hold the Friday huddle without exception. Decay comes from the absence of a checkpoint, not from the quality of the training. The hour installs the behavior; the week is what keeps it.

Is it worth buying an AI role-play tool for this?

Only if you're running the drill more than weekly or your team is distributed enough that pairing is hard. For a co-located team doing this monthly, paired role-play with a printed observer rubric gets most of the value at zero cost. Evaluate tooling after the manual version is working, never before.

Sources

• https://www.sandler.com/blog/the-up-front-contract/
• https://www.gong.io/resources/
• https://hbr.org/2018/05/the-surprising-power-of-questions
• https://www.saleshacker.com/discovery-call-questions/
• https://blog.hubspot.com/sales/sales-discovery-call
• https://www.rainsalestraining.com/blog/sales-discovery-questions
• https://www.richardson.com/sales-resources/
• https://corporatevisions.com/sales-discovery-questions/

Related on PULSE

• [60-Min Sales Training: Cold Calling Fundamentals](/knowledge/st0432)
• [Mastering the Discovery Call: A 30-Minute Ready-to-Run Sales Meeting Template](/knowledge/st0776)
• [Top 10 Discovery Call Templates for Sales Training Workshops](/knowledge/st0733)
• [Top 10 discovery call role-play scenarios for sales teams](/knowledge/st0532)
• [Top 10 discovery call training drills for B2B sales reps](/knowledge/st0531)
• [Discovery Call Script A/B Testing: Compare and Contrast Session](/knowledge/st0742)