Sales Discovery Preparation

Discovery Call Preparation

Purpose

Discovery calls fail when the seller arrives with a product walkthrough and a generic question list, learns nothing testable, and leaves with "send me some information". This skill converts account research into hypotheses that a question plan can confirm or kill within the call, and fixes the qualification threshold and the next step before the conversation starts.

Prerequisites

• Inputs: the account name, the attendees with their roles, the meeting length, and how the meeting originated (inbound, outbound, referral, renewal, expansion). Origin changes the entire plan.
• Access: your CRM record for the account, any prior interaction history, and public sources — the company's own published material, filings or annual reports where public, job postings, and product documentation.
• Also required: your current qualification framework, whichever one your team uses. If your team has none, use the fields in step 6 as the minimum.

If the attendee list is unknown, ask for it before preparing. A plan built for a practitioner and delivered to an executive wastes the meeting.

Data classification

Confidential. Account research and CRM extracts are restricted; do not distribute outside the deal team. Do not record or store personal data about attendees beyond role and business contact details. If anyone pastes customer account numbers, positions, balances, or personal identifiers into the working notes, flag it and remove it before the notes are shared.

Procedure

1. State the meeting's origin and what it implies.

   Origin	What is already true	Opening posture
   Inbound request	A trigger exists; they will not always say what	Find the trigger first, before anything else
   Outbound cold	No acknowledged problem	Earn the right to ask; lead with a hypothesis, expect to be wrong
   Referral	Borrowed credibility, unverified fit	Verify fit early; do not assume the referrer's problem is theirs
   Renewal or expansion	History exists, including any friction	Review support and delivery history before writing questions
   Inbound RFP or tender	Requirements may be pre-written to another vendor	Establish who wrote the requirements and whether influence is still possible

2. Build the account picture from sources, each cited. Capture: what the company does and for whom; how it is structured and where the attendees sit; recent public changes — leadership, funding, expansion, regulation, product launches; observable technology or vendor signals from job postings and public documentation; and prior history with you from the CRM. Record the source and date for each item. An uncited "insight" is a guess that will be repeated aloud on the call and contradicted.

3. Map the attendees. For each: their role, what they are likely measured on, what a win looks like for them personally, and whether they can sign, block, or only influence. Where you do not know, mark it unknown — this becomes a question, not an assumption.

4. Form two or three hypotheses, each falsifiable. Format: "We believe [specific situation] causes [specific cost or risk], because [evidence from step 2]." A hypothesis that cannot be proven wrong in conversation is not a hypothesis; it is a pitch. Write next to each what answer would kill it.

5. Write the question plan, ordered. Roughly: situation questions to confirm the facts you inferred (few — do not re-ask what research already answered), then problem questions that test each hypothesis, then impact questions that establish size and who feels it, then questions about what they have already tried and why it did not hold. Reserve time: a discovery call that is more than about a quarter you talking has stopped being discovery.

   Include for every deal, regardless of framework:

   • What happens if you do nothing? (tests whether a real driver exists)
   • What is the timeline being driven by, and by whom?
   • Who else needs to agree, and what does their approval process involve?
   • What has to be true for this to be funded this period?

6. Set the qualification threshold before the call. Decide in advance what you must learn for this to remain an active opportunity: an acknowledged problem with an owner, an impact the buyer can size, a decision process you can name, and a compelling event or timeline. Write the threshold down. Deciding afterwards produces a pipeline of hopeful entries.

7. Prepare the next step, with two options. Name the specific commitment you will ask for — a technical session with a named person, access to data for an assessment, an executive conversation — and a smaller fallback. "I will send information" is not a next step and should not be offered.

8. Prepare the three objections most likely to appear, based on the account picture and on objections recorded in the CRM for similar accounts. For each, write the acknowledgement, the question that clarifies what is really being objected to, and the evidence you would use — noting that any performance or comparative claim you plan to state must already be substantiated (see marketing-claim-substantiation). Do not improvise numbers on a call.

9. Write the post-call capture plan. Which CRM fields you will update, within what time, and what the notes must contain: the confirmed problem in the buyer's own words, the impact and its source, the decision process, the agreed next step with a date, and which hypotheses were killed. Records written from memory days later are the reason forecast reviews go badly.

Failure modes

• Research as trivia. Reciting a funding round with no link to a hypothesis signals preparation without producing insight. Every researched item should either feed a hypothesis or be cut.
• Confirmation questioning. Leading questions ("so that must be painful?") produce agreement, not information. Ask what happens, not whether it hurts.
• Demoing on discovery. Any product walkthrough before the problem is confirmed converts the call into an evaluation of features against an unknown need.
• Single-threading. Leaving with one contact and no path to the other approvers is how deals stall late.
• Unverified impact numbers. An impact the buyer cannot source is not a business case; carrying it into a proposal creates a claim you cannot defend.
• Stale research. Public information gathered weeks earlier may predate a reorganisation. Re-check anything decision-relevant the day before.

Boundaries

• Writing the proposal, business case, or RFP response after discovery — use sales-proposal-assembly.
• Segment- or market-level audience definition for campaigns — use marketing-campaign-brief.
• Substantiating a claim you intend to state on the call — use marketing-claim-substantiation.
• Codifying your team's standing discovery process and CRM hygiene rules — use operations-sop-authoring.

Hand-offs

• Receives from: marketing-campaign-brief (the proposition and audience evidence behind an inbound lead).
• Routes to: sales-proposal-assembly with the confirmed problem, sized impact, decision process, and objections; marketing-seo-content-brief and marketing-campaign-brief with the real questions and objections heard, which are better content input than keyword lists.