Help me prepare for a discovery call with [PROSPECT AND COMPANY]. I sell [OFFER], and the relevant context I know is [PROSPECT CONTEXT]. The likely problem or initiative is [SUSPECTED NEED], and the call goal is [CALL GOAL]. Create a call brief that helps me diagnose fit without assuming the prospect has a problem or budget. Include: a 2-sentence opening; 10 questions ordered from context to impact to current approach to desired outcome to decision process; 4 follow-up probes that uncover specifics; likely concerns or alternatives to explore; and a close that earns one concrete next step. Questions must be open enough to invite evidence, but precise enough to reveal the cost of the status quo, who experiences the problem, urgency or timing, success criteria, stakeholders, approval path, and whether doing nothing is a viable option. Do not use manipulative pressure, fake familiarity, or questions that presuppose my offer is the answer. Avoid asking budget early unless it naturally follows an established business case.
Then write a one-page note-taking template with sections for facts heard, exact language worth quoting back, risks, stakeholders, next action, owner, and date. End with three possible next steps matched to different outcomes: strong fit, possible fit needing validation, and poor fit. Do not fabricate account facts, use claims not supported by [PROSPECT CONTEXT], or promise product capabilities. Before answering, check that every question has a distinct diagnostic purpose and that the close is appropriate to [CALL GOAL]. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT AND COMPANY] | Name the buyer, role, and company if known. | Dana Lee, Director of Customer Support at Harborstone Software |
| [OFFER] | Describe the product or service you sell and its relevant capabilities. | A quality-assurance platform that samples support tickets and identifies recurring coaching themes |
| [PROSPECT CONTEXT] | Paste verified notes, public research, prior emails, or referral context. | Dana downloaded our support-operations guide. Harborstone posted roles for 12 new support agents and uses Zendesk. |
| [SUSPECTED NEED] | State the possible problem, initiative, or trigger without presenting it as fact. | Rapid hiring may be making ticket-quality coaching difficult to manage consistently |
| [CALL GOAL] | State the appropriate result for this call, such as qualification or agreement on a technical review. | Determine whether a product walkthrough with Dana and the support operations manager is worthwhile |
How to use
- Paste only verified prospect research, prior conversation notes, and a truthful description of your offer.
- Choose the questions that fill real knowledge gaps rather than reading the full list in order.
- During the call, record evidence and exact phrases separately from your interpretation.
- Follow up with: “Using these call notes, draft a recap with agreed facts, open questions, and the next action only if it was explicitly agreed: [NOTES].”
Variations
Call recap
Use this immediately after a call to turn notes into an accurate follow-up draft.
Turn these discovery-call notes into a concise recap: [CALL NOTES]. The prospect is [PROSPECT], and the agreed next step, if any, was [AGREED NEXT STEP]. Write a 130- to 180-word email with: thanks, the prospect’s stated priorities in their language, the facts we confirmed, any open question, and the next action with owner and date. Do not add capabilities, commitments, dates, or agreement that do not appear in the notes. Flag contradictions or missing ownership before drafting. Use a professional, non-pushy tone.
Account research
Use this before the call when you need a research plan instead of invented personalization.
I am preparing for a discovery call with [COMPANY] about [OFFER]. Based only on these known facts [KNOWN FACTS], create an account-research checklist. Separate facts to verify, useful public sources to consult, likely stakeholders, and five hypotheses labeled as hypotheses. Then write six call questions that could test those hypotheses without making claims about the company. Do not invent company news, technology, priorities, or people. End with a 60-word opening that refers only to confirmed information.
Qualification review
Use this after an early conversation to decide whether to advance an opportunity.
Assess this opportunity using the following call notes: [NOTES]. Our ideal customer profile is [IDEAL CUSTOMER PROFILE], and the next possible sales step is [POSSIBLE NEXT STEP]. Return a table with evidence for problem, impact, urgency, stakeholder access, decision process, fit, and risks. Mark each field as confirmed, suggested, unknown, or contradicted. Then recommend advance, nurture, or disqualify with reasons tied only to evidence. List the minimum questions needed before advancing. Do not treat interest as proof of need or budget.
Tips
- Prepare questions around decisions the prospect must make, not a product feature checklist.
- Keep a clean distinction between what the prospect said, what you observed, and your hypothesis; this prevents misleading recaps and forecasts.
- Ask about the current workflow before proposing change, because the existing process often reveals constraints, owners, and switching costs.
- End with a named owner and date only when both were actually agreed; “send information” is not a usable next step.
FAQ
How many questions should I ask on a discovery call?
Prepare more than you need, but ask only the ones that follow from the conversation. A useful call is a diagnosis, not a questionnaire.
Can AI personalize a discovery call from a company website?
It can organize research you provide, but verify every account-specific assertion. Do not use guessed initiatives or fabricated personal details as rapport-building.
Should I ask about budget on the first call?
Ask when the conversation has established a problem and a likely business case, or when qualification requires it. The wording and timing should fit your sales motion.