Prepare for a decision, not a performance
Discovery-call preparation should help you listen. If your notes are so dense that you spend the call searching for the next question, they are working against you.
A useful prep page answers four things:
- What does this organization appear to do?
- What is this person likely responsible for?
- What do I need to understand by the end of the call?
- What is the most reasonable next step if there is a fit?
Layer 1: company context
Start with the organization’s own website and any material the prospect has already shared. Capture only what is relevant to the conversation:
- the product or service in one sentence;
- the customers or users it serves;
- a recent change that may affect the problem you discuss;
- the language the organization uses for that problem; and
- any assumption that still needs to be confirmed.
Separate facts from hypotheses. “The company announced a new product” is a fact if you have the announcement. “The launch has created a reporting problem” is a hypothesis until the prospect confirms it.
Layer 2: participant context
Review the person’s role, prior emails, CRM notes, and any previous calls you are authorized to access. Look for continuity:
- What did they say mattered previously?
- What did your team promise?
- Which stakeholders have already appeared?
- What remains unclear?
Avoid turning public profile details into false familiarity. The goal is to understand the person’s likely perspective and remember prior context, not to demonstrate how much you found about them.
Layer 3: call objective
Write one sentence describing what you need to learn. Examples:
- “Understand the current process, the cost of its limitations, and whether change is planned.”
- “Map who will evaluate, approve, and use a solution.”
- “Confirm whether the technical requirement is mandatory or negotiable.”
Then write a small question set that supports that objective. A reliable sequence is:
- Current state: “How are you handling this today?”
- Friction: “Where does that process break down?”
- Impact: “What happens when it does?”
- Desired state: “What would a better process need to make possible?”
- Decision: “How would your team evaluate a change?”
Treat the sequence as a map. Follow what the person says instead of rushing to the next prepared question.
Layer 4: next-step design
Prepare a next step that matches what you still need to learn. It might be a technical review, a call with another stakeholder, a written answer, or no further action. A discovery call does not need to end in a demo to be useful.
Before joining, check that you can state:
- the purpose of the call;
- the assumptions you need to test;
- the decision process you need to understand; and
- what you will not claim without evidence.
When preparation is incomplete
Say so plainly. A sentence such as “I reviewed the context you sent, but I do not want to assume I understand your process” is more credible than improvising certainty. Ask the participant to describe the current state, then use the framework to stay oriented.
Preparing with Cinder
Meeting prep is available on Starter and up and can use authorized call history and context. During the call, On-Demand analysis is available on every plan; Continuous Coaching is available on Starter and up. Cinder does not add a participant bot, but you remain responsible for required notice and consent.