What is a discovery call, and what makes a good one?
A discovery call is the first scheduled conversation after a prospect raises their hand. The job is to understand the buyer: what prompted the search, what they have tried, who else is involved, and what success looks like 90 days from now. A good discovery call runs 25 to 45 minutes, is driven by open questions, and ends with a mutual agreement on next steps. If you leave the call without a scheduled follow-up and a clear statement of the business problem, the call was a conversation, not qualification.
Read the full answer →
What is a sales demo, and when is a prospect ready for one?
A sales demo is a tailored walkthrough that shows the buyer how your product solves the specific problems they described in discovery. A prospect is ready when you can name their pain in their words, you know who else needs to see the demo, and you have agreed on what a successful outcome would prove. If any of the three is missing, you are running a product tour, not a demo, and the buyer will leave remembering features instead of fit.
Full demo breakdown →
What is the difference between a discovery call and a demo?
Discovery is diagnostic; the demo is prescriptive. In discovery you are the doctor asking questions, in the demo you are the specialist showing the treatment. Collapse them and you get the worst of both: a generic product tour wrapped around shallow questions. Keep them separate, even by 15 minutes, and both calls get sharper. In Strkr, model this as two activity types on the opportunity so your conversion report can tell you which call is leaking deals.
Read the full answer →
How long should a discovery call be?
Published research on recorded sales calls suggests the strongest discovery conversations fall between 25 and 45 minutes, with a talk-to-listen ratio around 40 to 60 in favor of the buyer. Shorter calls rarely surface enough pain to justify a demo; longer calls drift into pitching before the problem is understood. Book 45 minutes, aim to finish by 40, and leave the last five for scheduling the next step and recapping what you heard.
Read the full answer →
What questions should I ask on a discovery call?
Open with context: what prompted the search, what else they considered, and what they are using today. Move into impact: what the problem is costing in hours, dollars, or risk, and who feels it. Close with process: who else needs to be convinced, what the evaluation looks like, and what has to be true to move forward. SPIN, MEDDIC, and Sandler frameworks all give you question banks, but the common thread is replacing yes-or-no questions with ones that force the buyer to think out loud.
Read the full answer →
What is BANT, and should I still use it on discovery calls?
BANT stands for Budget, Authority, Need, and Timing. It is a lead-stage filter from IBM in the 1960s. On a modern discovery call, BANT is useful as a mental checklist but weak as an agenda because committee buying has blurred Authority and Budget often forms after Need is proven. Use BANT to confirm you are not wasting the hour, then run a deeper framework like MEDDIC or SPIN during the actual conversation. In Strkr, log BANT as four fields that gate lead-to-opportunity conversion.
Read the full answer →
What does a strong demo agenda look like?
A strong demo has four blocks. Recap the pain in the buyer words, in two minutes. Show the three to five flows that solve those specific problems, no more. Pause for reactions after each flow, not at the end. Close with a mutual next step and a trial or pilot proposal. Avoid feature tours, hidden navigation, and any slide that starts with "about us." The best demos feel like a conversation with a demo environment open on screen, not a presentation with questions tacked on.
Read the full answer →
What signals predict a demo will win?
Research published by call-recording vendors on tens of thousands of B2B calls points to three repeat signals: the buyer talking more than the seller after minute 15, specific next-step language ("so if we did X, when could we start"), and multiple stakeholders joining or being named on the call. Weak signals include the buyer going silent, generic praise ("looks great"), and the champion saying they will "share internally" without a date. Track these as fields on the opportunity and your forecast will tighten within a quarter.
Read the full answer →
How many people should be on a demo call?
For mid-market and enterprise deals, two to five stakeholders on the buyer side correlates with the highest win rates in published research. One-on-one demos skew toward reference calls after the fact and slower cycles. Six or more usually means the buyer is comparison shopping and the deal is further along than it feels. On your side, bring the AE always, a solutions engineer when the product has configuration, and an executive only when matched by one on the buyer side.
Read the full answer →
Should I send a recap after discovery and demo calls?
Yes, within the same business day. The recap serves three purposes: it confirms you heard the problem correctly, it gives the champion a document to forward internally, and it timestamps mutual next steps so nothing slides. Keep it short: the problem in their words, what you discussed, the next step with date and owner, and any open questions. In Strkr, auto-attach the recap to the opportunity and set a reminder if the next-step date passes without activity.
Read the full answer →
How do I handle a demo request before discovery is done?
Many buyers ask for a demo on first contact because that is the ask they know how to make. Honor the intent, not the format. Offer a 20-minute discovery call now and a tailored demo later, framed as respect for their time: a generic demo will not answer the questions they actually care about. If they insist, run a short qualified demo with a tight scope and treat it as paid discovery; log the gap in your CRM so your pipeline reflects that qualification happened at the demo, not before.
Read the full answer →
How does Strkr help me run better discovery and demo calls?
Strkr opportunity records carry structured fields for pain, metrics, stakeholders, and next steps so reps capture discovery output the same way across the team. Activity types separate discovery calls from demos so your conversion reports show which meeting is leaking. Playbooks link from the opportunity surface, which means SPIN or MEDDIC question banks live where the rep is already working. Call recordings and recaps attach to the deal, and forecast categories move only when the required discovery fields are filled.
