Discovery is not an interrogation

An SDR spends two weeks earning thirty minutes with a director who almost said no. Then the meeting opens and the AE runs a checklist: headcount, stack, budget, authority, timeline, twelve questions in a row, each answer typed into a field the prospect can practically hear. The director came expecting a conversation about a problem. They got an audit, and the second meeting quietly never happens.
Interrogation extracts. Discovery trades.
Roughly one held meeting in two advances, and the deciding factor is rarely the product. It is whether the buyer left the meeting with anything. An interrogation collects information and gives nothing back, which buyers experience as doing free labor for a vendor's forecast. Worse, most of the collected information already existed. The account passed a written qualification bar before it ever reached the calendar, and the SDR's notes carry the stated problem, the context, and the words the buyer used, handed off before the meeting. An AE who re-asks known answers is billing the buyer for an internal process failure.
A structure that trades
- Open on their words. Restate the problem the prospect named on the SDR call, verbatim, and let them correct it. Thirty seconds, and it signals that the organization has a memory, which is rarer than it should be.
- Give before you dig. Share one specific observation about how similar companies handle that problem. Not a pitch, an insight, concrete enough to be checked. It converts the meeting from an inspection into an exchange, and it earns the depth that follows.
- Go deep on one thread, not wide on twelve. Pick the stated problem and pull: what it costs, what has been tried, who else feels it, what happens if nothing changes. Depth produces candor. Breadth produces recitation.
- Close on a decision, not a reflex. Instead of defaulting to a demo, agree on what would need to be true for a next step to make sense, and name who should be in the room when it happens. The best second meetings are designed in the last five minutes of the first.
The upstream half of a good first meeting
Discovery quality is set before the AE says a word. A meeting booked against a loose bar cannot be saved by technique, because there is no real problem to go deep on. This is why the acceptance loop matters beyond scorekeeping: an AE-accepted rate, tracked weekly, is also a mirror held up to the first meeting itself. When accepted meetings stall after discovery, the calls are usually extracting instead of trading.
Our part of the handoff is built for this. A CommandVA meeting arrives with the stated problem in the buyer's own words, the signal that started the conversation, and the objections raised on the call, so the AE can open from the middle. What the closer does with those thirty minutes is the client's craft, but we would rather arm it than watch a hard-won meeting die by questionnaire. If your held meetings are not advancing at the rate they should, book a strategy call and bring two recordings. The pattern is usually audible in the first five minutes.
One dedicated, full-time SDR inside a complete outbound system. Written meeting SLA, weekly reporting, month-to-month. A 30-minute call tells you if it fits.
Book a strategy call