Structure your discovery framework

Cover four topics in every first call: pain, impact, timeline and budget. They answer four plain questions: what is wrong, what it costs, when it has to change and whether money exists to change it.

Add a fifth, the decision process, if your deals involve more than one person. The way to find the other people is in Multi-thread, because the person on the call rarely signs alone. Keep the list short. Five topics is the most a person can hold in a live conversation.

An anchor question is the one you ask if you remember nothing else. Write it in your own words so it sounds like you. These are examples to adapt:

• Pain: "What made you take this call now?"
• Impact: "What does that cost you in a normal month, in time or money?"
• Timeline: "What happens if nothing changes by the end of the quarter?"
• Budget: "How have you planned to pay for fixing this?"

Open questions work best. If the answer is a single word, you asked the wrong kind of question. A fuller bank of questions is in Prepare qualifying questions.

The anchor starts the topic. The follow-ups go deeper. Write two per topic, and make them short: "Tell me more about that." "How long has that been going on?" "Who else feels it?" "What have you tried already?"

Follow-ups beat clever questions. They show you are listening, and they take the buyer from a symptom to the cause. The skill behind this is in Find the pain, then sit in it.

This is the step most frameworks miss. Write one line per topic describing what you must know before you move on:

• Pain: you can repeat it back in the buyer's words and they agree.
• Impact: you have a number or a clear consequence, even a rough one.
• Timeline: you have a date or an event that forces the decision.
• Budget: you know whether money exists, who holds it and what range they expect.

Without a finish line, you either leave too early or keep digging after you have the answer. Write down the minimum you need to qualify. How to turn the answers into a clear yes or no is in Qualify hard, because a clean no beats a slow maybe.

The four topics do not have to come in a fixed order. If the buyer starts with the deadline, follow the deadline. Tick the topics off in your notes and bring the missing ones in near the end: "Before we finish, I want to check two things."

The call itself, from opening to next step, is laid out in Design the call flow. The framework is what you gather. The flow is how you run the hour.

Set up a note template in your CRM, with one block for each topic and one line for the next step. In HubSpot or Pipedrive you can add the fields to the deal record, so the data is searchable later.

If you record calls, a tool such as Fireflies or Fathom can write the first draft of the notes. Check the draft against your four topics, and correct anything that is not what was said. This also feeds the monthly habit in Review call recordings monthly.

Role-play the framework with a colleague, a friend or an AI assistant. Run three short calls, then adjust any question that feels forced. Rewrite it until you would say it to a friend.

A framework that is too neat gets read from the page. The page is a safety net, not a script.

• Treating the framework as a form to fill in during the call.
• Asking about budget in the first two minutes, before there is any pain.
• Skipping impact, then wondering why nothing closes.
• Writing questions so long that nobody can remember them.
• Letting every salesperson use a different framework.
• Never changing the framework after you see what the won deals have in common.

• Every call ends with all four topics covered or a note on why one is missing.
• The buyer talks for most of the call.
• Notes look the same across calls and across people.
• Fewer deals stall because of a surprise about budget or timing.
• You can say yes or no to a prospect within a day of the call.