10 First-Meeting Discovery Questions

A first meeting is not a shortened demo and it is not an interrogation. It is a structured exchange that helps both sides decide whether a deeper conversation is worth the time. Your job is to earn relevance, understand context, and leave with a next step the buyer helped design.

Intent → priorities → current workflow → preserve value → gaps → priority → perspectives → learning agenda → fit risks → commitment

The VSM First-Meeting Arc sequences these questions for a first conversation. The diagnostic questioning underneath it builds on Neil Rackham’s SPIN research — full framework credits.

Reading the questions is the easy half. The interactive Sales Readiness Assessment drops you into 18 real call moments across six competencies and scores what you’d actually say — without telling you the answer as you go, so the later questions still measure something. You finish with a Sales Readiness Score, a profile of all six competencies, and the one habit to fix first.

Take the assessment →

About ten minutes. Your score and full competency profile are free, need no email, and are worked out in your browser.

01“What prompted you to take this conversation?”

Intent · permission to explore

Why ask it: This reveals the buyer’s original motivation and expectations, and whether a trigger, referral or active problem earned the meeting. It also hands them permission to define what would make the time useful.

Follow-ups: Was there a specific event? What caught your attention? What would make this worthwhile?

Listen for: They accepted only to be polite, can’t recall why, or expect a product pitch with no relevant problem.

02“What are you responsible for improving this year?”

Priority · personal relevance

Why ask it: People engage when a conversation connects to an outcome they own. This surfaces the targets and pressures that shape what the buyer will notice — and tells you whether your value proposition belongs in this conversation at all.

Follow-ups: Which target is hardest? Why does it matter to your team? How is progress measured?

Listen for: No meaningful overlap with the problem you solve, or priorities too broad to guide a next step.

03“How does your team handle this today?”

Current workflow · reality

Why ask it: A workflow narrative reveals more than a list of tools, because it shows where time, information and accountability actually move. It also gives you a factual baseline for any later value conversation.

Follow-ups: Walk me through the last time this happened. Where does it slow down? Who owns each step?

Listen for: Vague generalities, no ownership, or answers limited to tool names. Listen for work happening outside the official process.

04“What is working well that you would not want to lose?”

Preserve value · reduce defensiveness

Why ask it: Buyers open up when you respect what already works. This identifies the strengths a future solution has to protect — and it prevents the most common rookie error, which is exaggerating dysfunction to manufacture pain.

Follow-ups: Why is that important? Who benefits most? What would a change need to protect?

Listen for: You ignore existing strengths, or the buyer fears change will remove something valuable.

05“Where are you seeing gaps or missed opportunities?”

Friction · specific evidence

Why ask it: This lets the buyer define the gap in their own language instead of accepting your hypothesis. Specific examples reveal frequency, affected people and consequences that broad pain statements hide.

Follow-ups: Can you share a recent example? How often does that happen? What opportunity was lost?

Listen for: A hypothetical issue with no recent example, consequence or owner — or a gap too small to justify change.

06“How important is solving this compared with your other priorities?”

Priority test · honest qualification

Why ask it: A problem can be real without being important enough to act on. This exposes whether attention, budget or leadership support is likely, and protects both sides from pursuing a low-probability project.

Follow-ups: What would move it higher? What happens if it waits? Who considers it important?

Listen for: Low importance, no catalyst, or a problem owned by nobody. Don’t convert mild interest into false urgency.

07“Who else would have useful perspective on this?”

Perspectives · early multi-threading

Why ask it: This begins stakeholder discovery without making your contact feel bypassed. Other people may own the metric or see risks they can’t — and asking improves accuracy rather than demanding access.

Follow-ups: How are they affected? What might they see differently? Would their input improve the next discussion?

Listen for: The contact refuses broader perspective without explanation, or whole groups are expected to accept change without involvement.

08“What would you want to learn in a second conversation?”

Learning agenda · buyer-shaped next step

Why ask it: A second meeting should answer the buyer’s specific questions, not default to a generic demo. This tells you what evidence would make continued evaluation worthwhile, and gives them a sense of control over the process.

Follow-ups: Who should be included? What should we prepare? What decision should that meeting enable?

Listen for: The next step is only “see the demo,” with no learning objective, audience or decision attached.

09“Is there anything that would make this a poor fit?”

Fit risks · permission for truth

Why ask it: Inviting disqualification lowers defensiveness and surfaces constraints that otherwise stay hidden until late. A credible seller is willing to discover that an opportunity shouldn’t move forward.

Follow-ups: What concerns do you already have? What requirement might we not meet? What would stop a second conversation?

Listen for: Major constraints emerging only after commitment, or a buyer who names no concern at all despite obvious tradeoffs.

10“Can we agree on the next step, owner and date?”

Mutual commitment · momentum

Why ask it: A specific next step converts interest into coordinated action and tests whether the conversation created enough value to continue. Naming the owner and date makes responsibility mutual instead of putting every task on you.

Follow-ups: What should be completed before then? Who needs to participate? What outcome should it produce?

Listen for: No date, no owner, no objective — a generic promise to reconnect, or only seller-owned work.