How do you coach a rep to choose between discovery questions and demo features when time is tight in 2027?

The two plays competing for the same twenty minutes

Every compressed call forces the same allocation problem. A rep has a fixed block — twenty-five minutes on the calendar, twenty in practice once the buyer joins late and someone's audio cuts out — and two fundamentally different ways to spend it. Understanding what each one actually buys is the precondition for coaching the choice.

Discovery questions buy information asymmetry in your favor. Each good question surfaces something you didn't know: who signs, what broke last quarter, what they already tried, what the alternative to buying is. That information compounds. It shapes the proposal, the pricing conversation, the mutual action plan, and the objection handling three calls later. Discovery is the only activity in the sales motion that makes every *subsequent* activity cheaper. A rep who learns that procurement requires a security review in week one avoids the four-week surprise in week nine.

Demo features buy belief. A buyer who has never seen the product working carries an unresolved doubt — "can it actually do the thing?" — and that doubt blocks internal advocacy. You cannot ask someone to champion a product they can't picture. Demo also buys *specificity*: a buyer who has watched the workflow can describe it to their boss in concrete terms, which is what actually moves deals inside the buying committee.

The trap is treating these as interchangeable minutes. They are not. Discovery is an investment with delayed, compounding returns. Demo is a purchase with immediate, decaying returns — belief fades if nothing else happens, and a demo without a follow-up loses most of its force within a week or two.

There's a third competitor most coaching ignores: framing and mutual agenda-setting. The ninety seconds spent at the top saying "here's what I think we're solving, here's what I'd like to cover, does that match?" is neither discovery nor demo, but it makes both cheaper. Skipping it is the most common cause of a call where the rep demos the wrong module confidently for eleven minutes. In RevOps terms, that ninety seconds has the highest return per second of any block on the call, and it's the one reps cut first when they're nervous about time.

Adjacent to all of this sits a fourth option nobody schedules but everyone should: ending early with a clear next step. A fourteen-minute call that ends with a scheduled technical deep-dive and a named security stakeholder beats a twenty-five-minute call that ends with "I'll send over some materials." Coaching reps that finishing early is a legitimate, high-status outcome removes the pressure that causes feature-dumping in the final five minutes.

Reading the call to decide in real time

The decision isn't made once at the start. It's made continuously, and the signal a rep should read is *whether the last thing they said produced new information or new belief*. If neither, change modes.

Here's the practical decision architecture to coach:

The loop matters more than any single branch. Reps who internalize "check, act, re-check" stop treating the call as a script and start treating it as a control system. The failure mode of a scripted rep is finishing all twelve discovery questions on a buyer who answered the important one in question three, or running the full eleven-minute demo path on a buyer who only needed to see the integration screen.

Three real-time cues worth coaching explicitly:

Cue one — the buyer starts asking product questions. "Does it connect to our data warehouse?" is the buyer telling you they've moved from *whether* to *how*. Stop discovery. Answer with the screen, not with words. A rep who responds to a product question with another discovery question ("great question — what does your current warehouse setup look like?") is technically doing good discovery and is losing the room. Answer first, then ask.

Cue two — the buyer's answers get shorter. When four-sentence answers become four-word answers, discovery has hit diminishing returns for this call. Either the questions have gotten abstract, or the buyer feels interrogated. Switch to showing. You can always resume discovery after a demo segment, and the questions land better because the buyer now has vocabulary for their own problem.

Cue three — nobody in the room has named a metric. If eight minutes in, the conversation contains no number — no volume, no cycle time, no headcount, no dollar figure — the rep does not have enough to demo against. Feature selection without a metric to anchor to is guessing. Keep asking, even at the cost of the demo, because a demo aimed at the wrong pain doesn't just fail to help, it actively teaches the buyer that your product solves a problem they don't have.

Adjacent workflow note: the same read applies to renewal and expansion conversations, where the "demo" is a new module and "discovery" is understanding what changed since the last cycle. The cue set transfers cleanly — customer success teams running compressed QBRs benefit from the identical framework, with "have they seen this module work" substituting for the first-time belief question.

The numbers that make the trade-off concrete

Coaching improves sharply when the guidance is quantified rather than philosophical. These are working ranges to calibrate against and then adjust with your own call data — not universal constants, and any team should replace them with observed numbers from their own recordings.

The one-third rule. On any call under thirty minutes, budget roughly the first third to discovery, the middle half to demo, and the last sixth to next steps. For a twenty-minute working block: about seven minutes discovery, about ten demo, about three closing. Reps who write these as literal clock times on a sticky note — "7 min discovery ends at 2:07" — hit them far more reliably than reps holding proportions in their head.

The two-to-three feature ceiling. Under time pressure, cap the demo at two or three features. Every additional feature dilutes recall. Buyers relaying a demo internally typically reproduce a small handful of specifics accurately; anything past that blurs. Three features shown well and tied to a named pain travel further through a buying committee than nine features shown quickly.

The three-question core. If a rep only gets three questions, the highest-yield set is: (1) what's happening today that made you take this call, (2) what have you already tried and why didn't it stick, and (3) what happens if you do nothing for another two quarters. Question two is the one reps skip and the one that most reliably prevents a demo aimed at a solved problem.

The recall decay window. Belief built in a demo decays. Coach the recap email as part of the call, not as follow-up admin — sent within a couple of hours, containing the two or three features shown, the pain each addressed in the buyer's own words, and the agreed next step. The recap is what the champion forwards; the demo itself is what they can't forward.

The silence budget. After asking a discovery question, coach a deliberate three-to-four second pause before filling the gap. Most reps under time pressure fill silence in under two seconds, which truncates the most valuable part of the answer — the part after the buyer's first, rehearsed sentence. Three extra seconds of quiet routinely produces the sentence that determines what to demo.

Question-to-statement ratio. A rough diagnostic from call-recording review: in the discovery segment, the rep should be producing meaningfully fewer words than the buyer. If a call recording shows the rep talking for the majority of a segment nominally labeled discovery, it wasn't discovery — it was a pitch with question marks appended. Most conversation-intelligence platforms surface talk-ratio automatically, which makes this the cheapest coaching metric a RevOps team can operationalize.

Cost of the wrong choice. These aren't symmetric. A call that was all discovery and no demo produces a buyer who is understood but unconvinced — recoverable with one scheduled follow-up. A call that was all demo and no discovery produces a buyer who is unconvinced *and* mis-served, plus a rep who now has no information to plan the next step with. The recovery cost is roughly an extra cycle. Coach reps that when genuinely torn, discovery is the lower-variance error.

Building the coaching system that makes this automatic

Individual call judgment doesn't scale from advice. It scales from a system: a repeatable pre-call artifact, a scoring rubric applied to recordings, and a feedback loop tight enough that a rep changes behavior within a week rather than a quarter. This is squarely RevOps territory — the enablement content is only as good as the operational scaffolding underneath it.

Step one — the pre-call one-pager. Before every compressed call the rep writes six lines: three things they must learn, three features they'd show if the call goes well. It takes four minutes. Its whole purpose is to force the choose-in-advance decision while the rep is calm, so that in the call they're executing a plan rather than improvising under time pressure. The most common finding when managers first read these is that reps can't articulate three must-learns — which is the actual coaching problem, revealed cheaply.

Step two — instrument the calls. Recording and transcription is table stakes; the useful layer is extracting two numbers per call: rep talk ratio during the first third, and count of open questions asked before the first feature was shown. Both are mechanically extractable, and both correlate with the behavior you want. RevOps should own this pipeline and pipe the numbers into the CRM at the opportunity level so they're queryable alongside stage progression and win rate.

Step three — score one call per rep per week, not five. Coaching volume is not the constraint; coaching specificity is. One call, one rubric, one named behavior to change. A rubric that works: did the rep name the buyer's pain in the buyer's own words before showing anything; were shown features tied back explicitly to that pain; was a next step agreed with named owners; did the recap go out same-day. Four binary checks, scored in six minutes.

Step four — drill the specific gap, in ten minutes, live. Role-play is unpopular and effective. The discovery drill: the manager plays a terse buyer and the rep has three questions to get to a metric. The demo drill: the rep is given a stated pain and has ninety seconds to show two features and tie both back. Ten minutes weekly, on the specific gap, beats an hour of generic call review monthly.

Step five — one focus metric at a time, reviewed at two weeks. A rep working on "ask better questions and demo tighter and improve next steps" improves at none of them. Pick one. Two weeks. Keep or change.

Sequencing across a ramp. New reps should not be choosing at all for their first several weeks — give them a fixed script with the allocation baked in, because judgment requires a baseline to deviate from. Around the point where they've run enough live calls to have pattern recognition, introduce the decision framework and let them start deviating deliberately. Experienced reps get the opposite treatment: they usually over-index on demo because features are comfortable and questions risk awkward silence, so their coaching is almost always "ask one more question before you share your screen."

Where the system tends to break. Managers score calls inconsistently, so the rubric drifts and reps stop trusting it — fix by having two managers score the same call quarterly and reconciling. Pre-call one-pagers get filled in retroactively — fix by timestamping them or making them a required field before the meeting. And the drill gets dropped first when the quarter gets tight, which is exactly when demo-dumping spikes. Protect the ten minutes.

Adjacent situations where the same allocation logic applies

The discovery-versus-demo tension is one instance of a general pattern: limited time, one activity that gathers information, another that creates conviction. Recognizing the pattern elsewhere makes the core skill transferable and gives coaches more reps to practice on.

Inbound calls versus outbound. An inbound lead arrives with self-diagnosed pain and often a competitor already in view. Discovery here is shorter and sharper — confirm the self-diagnosis, find the part they got wrong, establish the buying process. Outbound calls carry no such head start; the buyer hasn't decided anything is broken, so discovery has to do the additional work of building problem awareness before any feature has meaning. Same framework, different starting allocation: roughly half the call on discovery for cold outbound, closer to a quarter for a warm inbound with a filled-out form.

Technical evaluations and second calls. When a solutions engineer joins, the allocation inverts. The buyer's questions are now specific and the SE's job is proof, not exploration — but the rep should still protect a slice for process discovery, because technical calls are where security requirements, data residency constraints, and unnamed stakeholders surface. A common miss: the SE nails the technical proof, nobody asks about the procurement path, and the deal stalls in legal for weeks.

Renewals and expansion. The "demo" is a module the customer hasn't used; the "discovery" is what changed in their business since the last cycle. Customer success teams under QBR time pressure make the identical error — walking through a product roadmap when they should be asking what the customer's new priorities are. The tell is the same: no metric named, features being shown anyway.

Multi-threaded committee calls. With five people on the line, discovery and demo aren't sequential — different attendees need different things simultaneously. The economic buyer needs three minutes of business-outcome discovery; the end user needs to see the workflow; the technical stakeholder needs the integration screen. Coach reps to name the split out loud: "I want to spend a few minutes on outcomes with you, then show the workflow — flag me if I'm spending too long on either." Explicit agenda-setting converts an unwinnable allocation problem into a negotiated one.

Partner and channel motions. When a partner rep is running the call, the vendor's rep often has fifteen minutes as a guest. Almost all of it should be demo — the partner already did discovery, and re-interrogating a buyer who has already told their story is the fastest way to burn goodwill. The discovery that matters happens with the *partner*, before the call.

Support-to-expansion handoffs. A support conversation that reveals an unmet need is discovery that already happened, for free, in someone else's queue. RevOps teams that route those signals to the account owner effectively pre-fund the discovery budget on the next call, which is one of the highest-leverage plumbing projects available and almost never prioritized.

The unifying principle across all of these: you cannot choose which features to show until you know what problem you're solving, and you cannot know that without asking. Whenever a rep is unsure, the question is not "discovery or demo" — it's "do I know enough to demo?" If the answer is no, the choice was never real.

Related questions

How long should discovery be on a 15-minute call?

Roughly five minutes, and cut it to three if the buyer arrives with a self-diagnosed problem. On a fifteen-minute block, aim for two or three high-yield questions, one feature shown, and a firm next step. Trying to do more produces a call that accomplishes nothing completely.

What if the buyer demands a demo immediately?

Give a ninety-second overview demo, then ask. "Happy to show you — so I show the right part, what made you look at this?" Buyers rarely refuse one question. The overview buys permission for the discovery you actually need.

Should the rep or the solutions engineer drive discovery?

The rep owns business and process discovery; the SE owns technical discovery. Split explicitly before the call or both will ask the same opening question and neither will cover procurement, security review, or the timeline that determines whether the deal closes this quarter.

How do you tell if discovery was actually good?

Check whether the rep can state the buyer's pain in the buyer's own words, name a number, and name the person who signs. If any of those three is missing after the call, discovery was conversation, not discovery — regardless of how many questions got asked.

Does this change for product-led or self-serve motions?

Yes. When the buyer has already used the product, belief exists and demo has low marginal value. Shift almost the entire call to discovery about scale, governance, and internal expansion blockers — the things usage data can't tell you.

FAQ

Is it ever right to skip discovery entirely?

Rarely, but yes — on a partner-led call where the partner already ran discovery and briefed you, on a renewal where you have complete account history, or when a buyer explicitly says "I've read everything, I just need to see it work." In each case the discovery happened; it just didn't happen on this call. What's never right is skipping discovery because you're nervous about time.

How many discovery questions is too many in a compressed call?

Past five or six in a short call, you're interrogating rather than exploring, and buyer answers get shorter as a result. Depth beats count — one question followed by two well-placed follow-ups produces more usable information than six unrelated questions. Coach the follow-up, not the list.

What should a rep do when they realize mid-demo they're showing the wrong thing?

Stop and say so. "I'm showing you the reporting side, but it sounds like the bottleneck is upstream — can I switch?" Buyers read this as competence, not failure. Continuing a wrong demo to avoid awkwardness costs the deal more than the ten-second correction ever will.

How does RevOps support this without adding admin burden?

Automate the measurement, keep the judgment human. Pull talk ratio and question counts from the conversation-intelligence tool automatically, surface them on the opportunity record, and let managers spend their time on the coaching conversation rather than on data entry. If a rep has to fill out a form to make the system work, the system will not work by week three.

Do these ratios hold for enterprise deals with long cycles?

The per-call ratio holds, but the stakes change. In enterprise, discovery extends across many calls and many stakeholders, so any single call carries less pressure to learn everything. What tightens instead is coverage: track which stakeholders have been discovered and which features each has seen, because the gaps are where enterprise deals quietly die.

What's the single highest-leverage coaching intervention here?

Make reps write the three things they must learn before the call and then compare that list to what they actually learned. The gap is self-evident, requires no manager judgment to identify, and produces behavior change faster than any rubric, because the rep grades themselves against their own stated intent.

Sources

• https://hbr.org/2018/05/the-right-way-to-run-a-sales-call
• https://www.gartner.com/en/sales/topics/sales-enablement
• https://www.salesforce.com/resources/articles/sales-discovery-call/
• https://www.gong.io/resources/
• https://blog.hubspot.com/sales/sales-discovery-call
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://corporatevisions.com/blog/
• https://www.saleshacker.com/

Related on PULSE

• How do you structure a 15-minute discovery call that still qualifies the deal?
• What belongs in a pre-call plan for a compressed sales meeting?
• How should a rep and solutions engineer split discovery on a technical call?
• What does good call-recording coaching look like in a RevOps org?
• How do you measure whether a demo actually moved a deal forward?
• When should a rep end a sales call early?