Solutions Engineering

The Discovery Playbook

A field guide for Solutions Engineers who want to ask better questions and hear what buyers actually mean.

Most discovery calls produce information but not insight. The questions are asked, the boxes are ticked, and the SE leaves with a list of requirements that could apply to any account in the pipeline. The problem is rarely curiosity. It is structure. Good discovery is not about asking more questions; it is about knowing which questions reveal real pain, when to stay in a conversation rather than moving on, and what a buyer is actually signalling when their language suddenly sharpens. This guide is for Solutions Engineers who already run discovery and want to understand why it sometimes produces less than it should.

Structure

The Anatomy of a Discovery Call

A well-run discovery call doesn't happen by accident. Every call that produces genuine insight follows the same five-stage arc, regardless of product, deal size, or audience. Miss a stage and what follows is built on incomplete intelligence.

1
Anchor

Before your first question, establish mutual purpose. Name the goal of the call and ask the buyer what they want to get out of it. This single move shifts the dynamic from interview to conversation.

Mistake: diving into a pre-built question list the moment pleasantries end
Fix: open with a 60-second contract: "my goal is to understand your situation. What would make this useful for you?"
2
Surface

Use broad, open questions to give the buyer room to name their own pains in their own language. Your role at this stage is to listen, not to steer.

Mistake: asking leading questions that suggest the answer: "are you struggling with approval delays?"
Fix: ask one question, wait five full seconds after the buyer stops talking before asking the next
3
Deepen

When the buyer names a pain, stay there. Ask pressure questions that move from symptom to root cause and from problem to cost. The first answer is rarely the whole story.

Mistake: accepting "we have some inefficiencies" and moving to the next topic
Fix: ask at least one cost question before leaving any pain: "what does that cost you in time or revenue?"
4
Map

Build a picture of the environment where a solution will need to survive: the systems, the stakeholders, the constraints, and the decision process. Technical environment is half the map.

Mistake: mapping the tech stack and ignoring the buying committee entirely
Fix: for every technical question asked, ask at least one question about the person or team affected
5
Confirm

Close the call by reflecting back the buyer's top pains in their exact language and proposing explicit success criteria. This is the bridge between discovery and demo.

Mistake: ending with "great, I'll put something together" with no documented agreement
Fix: read back the two top pains, propose two success criteria, ask the buyer to confirm or correct
Framework

The Five Discovery Dimensions

Complete discovery covers five distinct dimensions. Most SEs map one or two well and leave the others as assumptions. The dimensions you skip are the ones that surface as objections in the late stages of the deal.

Dimension 01: Pain

Pain

The pain dimension captures what the buyer is experiencing in their current state: the friction, inefficiency, or risk they live with every day. Pain named by the buyer in their own words carries more weight than pain suggested by the SE. Your job is to create the space for it to surface, not to predict it.

"Walk me through what currently happens when [process] breaks down. What does that look like for the team?"
Dimension 02: Cost

Cost

A pain without a quantified cost stays at the sympathy level. The cost dimension turns "we have a problem" into "this problem is worth solving now." Cost can be measured in time, money, headcount, delayed revenue, or increased risk. What matters is that the buyer has named a number, not that you've estimated one.

"If you had to put a number on how much that costs you, in hours, in deals, or in risk, what would it be?"
Dimension 03: Environment

Environment

The environment dimension covers the technical, organisational, and workflow context in which any solution will have to operate. It prevents you from proposing something that can't survive contact with the buyer's reality, whether the constraint is a legacy system, a procurement process, or a department that owns the decision.

"What does the current stack look like, and who owns the decision to change any part of it?"
Dimension 04: Power

Power

The power dimension maps who is involved in the decision, who influences it without being visible, and who has the authority to block it. A deal that advances without a clear power map is a deal that stalls in committee. The goal is to understand the decision structure before you are already navigating it.

"When a decision like this moves forward, who else typically gets pulled in, and what are they usually focused on?"
Dimension 05: Timeline

Timeline

Timeline reveals whether urgency is real or implied. A pain without a deadline is a pain that can be deferred. Understanding what would happen if the buyer did nothing for six more months separates genuine urgency from polite interest in your product. Timeline also surfaces dependencies: the initiatives, renewals, or milestones that make a decision more or less likely to move at a given point in time.

"Is there something driving a decision before a specific date: a project milestone, a contract renewal, or an internal deadline?"
Technique

Question Architecture

Not all discovery questions do the same job. The three types below form a sequence, not a script. Use them in the right order and the buyer does the work of revealing both their pain and its cost without feeling interrogated.

1

Opener Questions

Opener questions are designed to produce a long, unstructured response from the buyer. Their purpose is to let the buyer name their own pain in their own language without any steering from the SE. The best opener questions cannot be answered in one sentence, they require the buyer to think, choose, and describe. This is where you listen for the phrases you will use in the demo.

"Tell me about how your team handles [process] today."  ·  "Walk me through a recent time when [situation] became a problem for you."  ·  "What does a difficult week look like for the team that owns this?"
2

Pressure Questions

Pressure questions are asked after the buyer has named a pain. Their purpose is to move the conversation from symptom to root cause and from problem to cost. Never accept the first answer as the whole story. Buyers understate their pain in early conversations because they don't yet know whether they are talking to someone who can do something about it. Pressure questions earn the right to deeper honesty.

"When that happens, what's the downstream effect on the team?"  ·  "How often does this occur, and what does it cost when it does?"  ·  "If this didn't get resolved in the next six months, what would that mean?"
3

Confirmation Questions

Confirmation questions close discovery loops. They reflect back what the buyer said and ask them to validate, refine, or correct the summary. They protect against the most common discovery failure: the gap between what the buyer meant and what the SE heard. A confirmation question at the end of each topic costs 30 seconds. Misreading a priority costs a deal.

"Let me make sure I've got this right, you said [X]. Is that an accurate picture?"  ·  "If we could solve [X] specifically, would that address the core issue you described?"  ·  "Before we move on, is there anything you'd add to what we've covered?"
Awareness

Listening for Signals

Discovery is not just what you ask, it is what you notice. The four signal types below don't announce themselves. They surface in patterns of language, silence, and behaviour that pass by unnoticed if you are focused on the next question rather than the current answer.

Signal Type 01

Language Intensity Signals

When a buyer's language becomes more specific, more urgent, or more personal, they are crossing from general territory into real pain. "We have some inefficiencies" is general. "Last month we lost a deal because of the delay" is a signal. When dates, names, and consequences appear, slow down. Ask one more question before moving on. This is where the real discovery happens.

Listen for: specificity, urgency, named consequences: any shift from "we sometimes" to "last week we…"
Signal Type 02

The Unsaid

What the buyer doesn't say is as informative as what they do. Silence after a sensitive question, a subject changed too quickly, an answer deflected to someone else in the room, these are signals that the real pain lives somewhere the buyer hasn't yet chosen to take you. Notice the pattern and name it without forcing it: "I notice we haven't talked much about [X]. Is that relevant here?"

Listen for: topic changes, deflections, unusually brief answers after specific questions
Signal Type 03

Stakeholder Reference Signals

When a buyer mentions another person by name during discovery, they are almost always signalling something about the decision structure or the real risk. "Legal will want to see that" or "our CTO would push back on the pricing model" are pieces of intelligence that buyers rarely offer as stakeholder maps. Catch every name dropped and follow up: "You mentioned [name], what's their role in a decision like this?"

Listen for: any mention of another person's view, reaction, or concern about the topic at hand
Signal Type 04

Constraint Signals

Constraints, including budget limits, timeline pressures, legacy system locks, and procurement processes, are rarely stated directly. They surface in hedge language: "probably", "we'd need to check", "in theory", "assuming everything aligns." These are signals that a constraint exists but hasn't been disclosed. Constraints discovered in the demo are expensive. Constraints discovered in procurement are fatal.

Listen for: hedge language, conditional framing, mentions of process steps that would need to happen first
What to Avoid

Discovery Anti-Patterns

Most discovery failures are predictable. They follow one of five patterns, each with a recognisable shape, a specific cost, and a direct fix.

Anti-Pattern 01

The Interrogator

Asking a rapid sequence of short, tactical questions without giving the buyer room to develop a thought. The discovery call becomes a form fill.

The buyer gives short answers because they've been trained to by the pace of the conversation. You collect data points, not insight. Discovery that produces data points builds a generic demo, not a personalised one.
Ask one question, then hold silence for at least five seconds after the buyer finishes speaking. If they have more to say, they will say it. The pauses are where the real answers live.
Anti-Pattern 02

The Solution Jumper

Moving to product positioning or technical architecture before the buyer has finished describing their problem. Usually triggered by a keyword the SE recognises as a match for their product.

The buyer stops being honest about their situation once they sense they're in a pitch. The remaining discovery produces answers shaped by politeness, not reality, and the demo is built on incomplete intelligence.
Note the match internally, keep asking discovery questions for at least two more minutes. Acknowledge nothing about product fit during discovery. That is the demo's job.
Anti-Pattern 03

The Scripted Tourist

Following a fixed discovery script regardless of what the buyer says. Moving through pre-written questions in sequence even when the buyer's answers signal a different conversation should happen.

You produce complete coverage of the script and zero coverage of what was actually important to this buyer. Every question was answered, but the call revealed nothing that couldn't be found on their website.
Use a discovery framework as a map, not a script. Know where you need to end up, but let the buyer's answers determine the route.
Anti-Pattern 04

The Early Qualifier

Using discovery time to qualify the deal, probing budget, authority, and timeline, before any pain has been meaningfully explored.

Qualification signals to the buyer that the SE is more interested in the deal than the problem. It closes them down. Deals stall because the SE never understood what was actually at stake, only whether it was big enough to pursue.
Earn the right to qualification by demonstrating genuine curiosity about the buyer's situation first. Let qualification surface naturally from the conversation, not from a checklist.
Anti-Pattern 05

The Passive Listener

Nodding and taking notes while the buyer talks, without reflecting, probing, or surfacing subtext. Mistaking polite attention for active discovery.

The buyer leaves the call feeling heard but not understood. The SE leaves with a list of statements that could have been gathered from a form. No insight, no signal, no differentiation from every other vendor who asked the same questions.
After every substantive answer, either reflect it back to confirm understanding or ask a pressure question to deepen it. A pain statement that passes without one of those two responses is a missed signal.
Self-Assessment

Score Your Last Discovery Call

Rate each dimension of your most recent discovery call on a 1–5 scale. 1 = this didn't happen. 5 = executed precisely. Be honest, the score only helps if it's accurate.

1. Did you open the call by establishing mutual purpose and asking what the buyer wanted to get out of the conversation?
Dived straight into questionsAlways contract the call at the start
2. Did you ask at least one opener question that required the buyer to talk for two or more minutes without interruption?
Questions were mostly short-answerConsistently used broad, open openers
3. When the buyer named a pain, did you ask at least one pressure question to surface the cost before moving on?
Accepted first answers at face valueAlways pressed into the cost behind each pain
4. Did you cover all five discovery dimensions: pain, cost, environment, power, and timeline, by the end of the call?
Covered two or three at mostDeliberately mapped all five
5. Did you listen for language intensity signals, moments where the buyer's language became more specific or urgent, and slow down at those moments?
Followed the script regardless of buyer signalsConsistently noticed and followed intensity signals
6. Did you ask at least one question about stakeholders other than the person you were speaking with?
Did not map the buying committeeBuilt a clear picture of the decision-making structure
7. Did you end the call by reading back the buyer's pain in their own language and proposing specific success criteria?
Ended vaguely with "I'll send something over"Confirmed pain, criteria, and a specific named next step
8. Did you leave the call with enough material to build a personalised demo that uses the buyer's vocabulary and maps to their top two ranked pains?
Notes are generic, could apply to any accountNotes are specific enough to build a demo for this account only
Context

What Shaped This Playbook

The frameworks here are original, but they didn't emerge in a vacuum. These four books are the deepest reading in the SE and negotiation canon, all available in the SE Resources books section.

Doing Discovery
Peter E. Cohan

The most practical field guide to what should happen before the demo begins. Cohan's framework for separating symptoms from situations from impacts is the closest thing the SE field has to a universal discovery method.
Mastering Technical Sales: The Sales Engineer's Handbook
John Care

The most comprehensive treatment of the SE role end-to-end. Care's chapters on discovery preparation and stakeholder mapping are essential reading before you attempt to systematise your approach at scale.
The Challenger Sale
Matthew Dixon & Brent Adamson

The research behind commercial teaching: the idea that the best sellers don't just discover pain, they reframe it. The Challenger model is the theoretical grounding for the insight dimension of discovery: bringing buyers something they hadn't yet articulated themselves.
Never Split the Difference
Chris Voss

Voss's techniques for tactical empathy, mirroring, and labelling emotions are directly applicable to discovery. The listening framework in this playbook, particularly the treatment of the unsaid and language intensity signals, draws heavily on his negotiation practice.
Back to SE Resources