Sales Discovery Sheet Template: 9 Essential Questions with Good vs. Bad Answer Examples

"Every call follows whatever direction the conversation happens to take." "Discovery depth varies wildly from rep to rep, so proposal quality is unstable." "The previous owner of this account left, and nobody knows what was already asked." If you are searching for a discovery sheet template, you are probably starting from one of these situations.

This guide is written for B2B sales teams. Intake forms used in web design projects, recruiting interviews, or insurance consultations share the same name but serve a different purpose (we cover the difference in the FAQ).

Most articles on this topic explain what a discovery sheet is and then hide the actual template behind a download form. This guide takes the opposite approach: the complete template, three purpose-specific variants, and good-vs-bad answer examples for every field are all published right here in the article. Copy them straight into a spreadsheet and start using them today.

Key takeaways

• A discovery sheet is not just a checklist against forgetfulness. Its real job is to standardize discovery quality across the team and turn deal information into a shared asset.
• Start with 9 core fields (current state / pain / root cause / desired outcome / budget / decision process / timeline / competition / concerns). Too many fields turns discovery into an interrogation.
• The sheet's value is decided by how answers are written, not whether fields are filled. "Budget: TBD" is a wasted field; "~$50K budgeted for next fiscal year, board approval required above that" is a deal strategy input.
• SPIN, BANT, and MEDDIC only work in the field when they are embedded into the sheet itself. A reverse-mapping table is included below.
• Spreadsheets scatter. Plan from day one how discovery notes will be centralized per deal and shared with the buyer — that is where most discovery programs quietly die.

---

What Is a Sales Discovery Sheet?

A sales discovery sheet is a working document that lists what to confirm with a prospect before and during sales meetings, with space to record the answers. Because the questions are prepared in advance, even junior reps can run discovery without missing critical items, and the recorded answers feed directly into proposals, internal reviews, and handoffs.

The three jobs of a discovery sheet

1. Prevent missed questions. Items that are essential but awkward to ask — budget, decision process — are exactly the ones that get skipped in the flow of conversation. Making them explicit fields prevents the classic failure of discovering a budget mismatch after the proposal.
2. Standardize discovery quality. Codifying what top performers naturally ask raises the floor for the entire team. Managers can coach against a shared standard instead of vibes.
3. Turn conversations into assets. A filled sheet becomes proposal input, a handoff document, and raw material for win/loss analysis. It also prevents the trust-destroying experience of asking the customer the same question twice because nobody recorded the first answer.

Three types of discovery sheets and when to use each

When this article says "discovery sheet" without qualification, it means the second type. Keep pre-meeting intake forms short — three to five fields. Asking a prospect to fill out a long form before you have earned their time depresses response rates and costs you meetings.

---

The Copy-Paste Discovery Sheet Template: 9 Core Fields

The backbone of a B2B discovery sheet follows the customer's story — current state → pain → desired outcome — plus the purchase conditions that decide deal strategy: budget, decision process, timeline, competition, and concerns. The template below is complete; no download form required.

To turn this into a working sheet, add columns for the answer, the date confirmed, and open items for the next meeting. In a spreadsheet, keep one row per deal so the team gets a cross-deal view for free.

Why these 9 fields

• Fields 1–4 decide what you propose. The larger the gap between current and desired state — and the more structural the root cause — the more your solution is worth. Field 3 is the one most often skipped: stopping at "the pain is manual work" produces a symptomatic proposal, while asking why the manual work exploded (attrition? growth? a process that never scaled?) changes the angle of the entire pitch.
• Fields 5–7 decide deal probability and pacing. These are the classic BANT conditions and the hardest to ask directly. Techniques for asking them without sounding like a loan officer are covered in the answer-examples section below.
• Fields 8–9 decide whether you win. Knowing the evaluation criteria tells you what to emphasize; knowing the internal concerns lets you defuse them early. Learning about a competitor after you lose is the outcome this sheet exists to prevent.

How many fields is too many?

Aim for the 9 core fields plus two or three product-specific ones — roughly 10 in total. There is data behind this: Gong's analysis of more than 519,000 recorded B2B sales calls found that asking 11–14 questions in a discovery call correlates with the highest success rates, and going beyond that drops outcomes back to average (source: Gong Labs, "Nailing your sales discovery calls"). Nine fields, each with one or two follow-ups, lands exactly in that band.

If your sheet is creeping past 20 fields, kickoff-sheet items (delivery requirements) have probably leaked into your discovery sheet. Asking for implementation details before the deal exists feels like an interrogation to the buyer.

---

Answer Examples: Good vs. Bad, Field by Field

A discovery sheet does not work because the fields exist; it works because of how the answers are written. Below is a good-vs-bad contrast for all nine fields.

All examples below are fictional samples, not real companies or deals.

Three patterns behind every good entry

1. Numbers, dates, and proper nouns. Not "be more efficient" but "halve handoff effort"; not "ASAP" but "contract by end of February." Vague answers are not answers — they are signals to keep digging. The moment names and departments appear, your read on the decision process sharpens dramatically.
2. Separate facts from interpretation, and cite the source. "Pricey — per the champion" makes clear this is the customer's statement, not the rep's guess. Recording guesses as facts leads teammates to make bad calls on bad data.
3. Write for the next action. "Exec meeting is the 2nd Wednesday monthly" lets you schedule the proposal backwards from it. "Onboarding support weighs heavily" tells you to add an onboarding section to the deck. The sheet is not a diary; it is an input to the next move.

When the answer is "TBD" or "no concerns"

A "TBD" in the budget field usually means the rep stopped asking, not that the customer refused to answer. When budget comes back vague, downshift to a more answerable question:

• "So the budget isn't locked yet — if it were to be requested, when would that happen?" (ask about the process of budgeting)
• "Tools in this category typically run $2–4K per month — is that a realistic range?" (anchor with a range and watch the reaction)
• "When your team made a similar investment in the past, how did the budget come together?" (infer from precedent)

Even without a number, knowing the budgeting timeline, the approval threshold, and the precedent is enough to build deal strategy.

Asking the awkward fields: decision process, competition, concerns

The trick that works across all three is to ask about the process or the criteria, never the person or the vendor by name.

• Decision process: "Who is the decision-maker?" can make your champion feel distrusted. "How do purchases like this usually get decided at your company?" gets you the same map — the approvers emerge naturally as the customer describes the flow. For a deeper playbook on identifying and engaging the actual decision-maker, see our decision-maker guide.
• Competition: Rather than "Which competitors are you evaluating?", ask "What criteria will matter most when you compare options?" Criteria are easier to share than vendor names, and they feed your proposal directly. Once criteria are on the table, confirming names becomes natural.
• Concerns: Near the end of the meeting, ask "Is there anything your colleagues might push back on?" Framing it as other people's objections gives your champion permission to voice their own.

Whatever you could not ask, do not leave blank — write "unconfirmed, ask next meeting." A blank field and an open item are completely different things.

---

How to Build a Discovery Sheet in 5 Steps

Building a discovery sheet comes down to five steps: ① define the purpose and the moment of use → ② design the fields → ③ choose the format → ④ pilot it with a filled-in example → ⑤ review it against lost deals. This section covers each step, whether you start from scratch or adapt the template above.

Step 1: Define purpose and moment of use

Write one sentence: which meeting stage, used by whom, for what. "First meetings, all reps including juniors, to gather what proposals and manager reviews need." That sentence settles every later argument about which fields belong.

Step 2: Design the fields

Start from the 9 core fields and add at most two or three product-specific ones. For SaaS: integration requirements, seat count, security review. For services: prior experience with external vendors, internal staffing for the project. For hardware: current equipment and replacement cycle, installation constraints.

Cutting matters as much as adding. The test is: can you write the proposal without this information? Keep only the fields that fail that test. Interviewing your top performers — "what did you always confirm on deals you won?" — is one of the fastest ways to mine implicit knowledge into the sheet.

Field order matters too. The principle is "natural conversation flow = top to bottom": start with easy facts (current state), put what the customer wants to talk about in the middle (pain, desired outcome), and leave the awkward purchase conditions (budget, decision process, competition) for the back half, after trust is established. A sheet ordered this way doubles as a natural meeting script.

Step 3: Choose the format

If in doubt, start with Google Sheets. Starting with Excel almost guarantees the "discovery_sheet_FINAL_v3_tanaka.xlsx" problem — files scattered across personal folders (we address the structural fix in a later section).

Step 4: Pilot with a filled-in example

Never distribute an empty sheet. Fill in one complete example deal first — the good-entry column above is a usable model. Without a model, entry quality fragments instantly and you harvest a crop of "TBD"s.

Pilot with two or three reps across five to ten meetings. Check: are there too many fields, does the question order flow as a conversation, how long does entry take? Set three entry rules and only three: ① the rep who ran the meeting fills it in the same day, ② record what the customer said, as close to verbatim as practical, not a paraphrase, ③ never leave a field blank — write "unconfirmed, ask next time."

Step 5: Review against lost deals

Revisit the sheet quarterly. The best input is your lost deals: line up loss reasons against what the sheet captured. "We never knew who the real decision-maker was" or "we learned about the competitor at the end" tells you exactly which fields are being skipped or answered superficially.

Pre-rollout checklist

• Purpose and moment of use defined in one sentence
• Around 10 fields (no kickoff/delivery items mixed in)
• Every field has an example question
• One fully worked example is filled in as a model
• Storage location and sharing rules are decided
• A review cadence (quarterly) is on the calendar

---

Purpose-Specific Templates: New Business, Expansion, and Inside Sales

The 9 core fields assume a first meeting with a new prospect. Two other situations come up constantly and deserve their own variants.

New-business discovery sheet

Add two fields on top of the core nine, because where the lead came from changes how much they already know and how warm they are.

In a first meeting, do not force all nine fields. Go deep on 1–4 (the pain story), light on 5–9 (the purchase conditions). Grilling a prospect on budget and approvals before pain is mutually established feels like being credit-scored.

Expansion (existing customer) discovery sheet

For upsell and cross-sell conversations, the starting point is not "what's your pain" — you should know that — but what changed: in their usage and in their organization. Reusing the new-business sheet on an existing customer signals that you have not been paying attention.

Inside sales (SDR) qualification sheet

On a 15-minute call, nine deep fields are unrealistic. Trim to six BANT-centered items, track a status per item, and tie them to your handoff criteria so the SDR-to-AE toss-up is governed by data instead of optimism.

Adapting the sheet to your product category

The rule for customization: add at most two or three, and when you add one, cut one. If you are unsure what to add, compare recent wins against recent losses and prioritize the fields that were filled on wins and blank on losses.

---

Framework Reverse-Mapping: Implementing SPIN, BANT, and MEDDIC in Your Sheet

The most common reason sales frameworks die after training is that they never get embedded into the tools reps touch daily. Map the framework questions onto sheet fields, and filling the sheet is practicing the framework.

When to reach for which:

• SPIN is a question-ordering framework for surfacing latent pain. Fields 1–4 in order (current → pain → cause → outcome) are literally the SPIN sequence, so run the first half of discovery in SPIN mode. Question construction is covered in our SPIN selling guide.
• BANT is a deal-scoring checklist mapped to fields 5–7 — the yardstick for "should we keep investing in this deal?" after the meeting. See the BANT framework guide.
• MEDDIC is for complex enterprise deals with many stakeholders and long cycles. When nine fields stop being enough (multiple approvers, formal selection criteria), extend the sheet to full MEDDIC — here's the MEDDIC playbook.

The key inversion: start from the sheet, not the framework. Reps memorize nine fields; the frameworks live invisibly in the design. For the broader landscape of when to use which framework across the sales cycle, see the sales frameworks guide.

---

Operating the Sheet: Habits and Failure Modes

Discovery sheets are easy to launch and hard to keep alive. Know the failure patterns before they happen.

Habit 1: Never fill the sheet during the meeting

The interrogation failure starts with trying to complete the form live. The working rhythm has three beats: before the meeting, scan the sheet and mark what is still unconfirmed; during, stay in the conversation and take free-form notes; immediately after (same day), transfer notes into the fields. The transfer step is the leak detector — whatever will not transfer is, by definition, your agenda for the next meeting.

Habit 2: Send the filled sheet back as meeting notes

Sending your discovery summary to the customer as "confirming what we discussed" does two things. It catches misunderstandings early — a budget or timeline misread discovered post-proposal is usually fatal. And it becomes the customer's internal briefing document: when your champion reports to their boss, your summary travels upward, meaning the decision-maker who never attends your meetings receives accurate information anyway.

Structure it from the sheet: ① current state and pain as heard, ② target outcome, ③ evaluation context (only what is appropriate to reflect back), ④ next actions on both sides with dates. Close with "please correct anything I got wrong" — that one line turns the notes into a verification loop. Send it the same day; accuracy decays with everyone's memory.

Habit 3: The sheet sets the floor; questioning skill sets the ceiling

A sheet determines what gets asked. How it gets asked — open vs. closed questions, follow-up probes, comfortable silence — is a skill layer the sheet cannot supply. Pair the sheet rollout with discovery-skill coaching and role-play: a useful drill is "cover all nine fields in a natural conversation," which trains the script into muscle memory and prevents interrogation mode in real meetings.

---

Why Spreadsheets Fail, and Centralizing Discovery in a Digital Sales Room

Once the sheet habit sticks, the next wall every team hits is scatter. If you read this far thinking "we'd build the sheet and it would still end up buried in someone's folder," this section is the structural fix.

The scatter problem is structural, not behavioral

• Files multiply per meeting. Deal A meeting 1, meeting 2, deal B... and soon nobody knows which file is current.
• Notes live in personal silos. Saved on reps' laptops and inboxes, findable only by the author. Every handoff or departure deletes institutional memory.
• The buyer never sees any of it. The sheet is internal, so the people on the buying side who never attend meetings — usually including the economic buyer — receive your story only through the champion's retelling, with all the distortion that implies.

A spreadsheet can record discovery, but it cannot operate a deal. How information flows — where it lives and who it reaches — deserves as much design as the fields themselves.

Centralizing discovery per deal with a DSR

A digital sales room (DSR) gives each deal a dedicated online space shared with the buyer, holding proposals, meeting notes, discovery summaries, and the mutual plan in one place (see what is a digital sales room for the concept).

Combining the discovery sheet with a DSR resolves the scatter problem directly:

• One room per deal — discovery notes accumulate in a single place that is always current; the "which file is latest" problem disappears.
• Meeting notes shared in the room — the "send the sheet back as notes" habit happens in the room instead of email attachments, and the buyer can revisit the full history anytime.
• Invite the decision-maker — stakeholders who never attend meetings can read the discovery summary, the proposal, and the deliberation trail firsthand, killing the telephone-game distortion.
• Deal history becomes a team asset — handoffs mean reading the room, not archaeology across inboxes. Discovery records from won deals become first-party data for win-pattern analysis.

DSRs also track engagement: you can see which materials the buyer opened, when, and for how long. When the customer who said "price is the concern" keeps re-reading your pricing page, the deal is moving. Pairing what buyers told you (discovery) with what they do (engagement) is a read no spreadsheet can give you.

Terasu is a digital sales room built for exactly this: discovery notes centralized per deal, shared with the buyer, with engagement tracking built in. If your discovery program keeps dying in spreadsheets, start with a single deal.

---

Frequently Asked Questions

---

Summary: Building the Sheet Is 10% — Running It Is 90%

• A discovery sheet exists to prevent missed questions, standardize quality, and turn conversations into team assets. Use the right variant: pre-meeting intake, discovery, or kickoff.
• Nine core fields plus two or three product-specific ones. More fields, worse meetings.
• Entry quality is the product: numbers, dates, proper nouns; facts vs. interpretation; written for the next action. "TBD" means "keep digging."
• Embed SPIN, BANT, and MEDDIC into the field design — reps memorize the sheet, not the frameworks.
• Fill the sheet after the meeting, send it back as notes, and centralize it per deal so it survives handoffs and reaches the people who never attend your meetings.

Paste the template into a spreadsheet and run it on one live deal this week. The fields you cannot fill are your team's discovery gaps — now visible, and fixable.

Terasu turns discovery notes from personal memos into a team asset: per-deal rooms shared with the buyer, decision-makers invited in, engagement tracked. Try it free.