LaunchVault Field Guide
A Consultant Discovery-Call Framework That Keeps the Conversation Useful
A practical sales-call template for independent B2B consultants: prepare with context, diagnose before recommending, qualify the path forward, and leave every conversation with a clear next step.
In this guide
- 1. Prepare with a working hypothesis
- 2. Follow the five-part call flow
- 3. Capture notes that lead to action
- 4. Close with a useful next step
Treat discovery as diagnosis, not a performance
A good discovery call helps a buyer name the problem in their own terms. It does not depend on a clever script or a promised outcome. Your job is to understand the current situation, the practical cost of leaving it alone, and whether your work is an appropriate next step.
That approach makes the call easier to run. You do not need to explain every capability, improvise a full proposal, or turn every conversation into a sale. You need enough shared clarity to make a sound decision: continue, pause, refer elsewhere, or close the loop.
Prepare in ten focused minutes
- Review the prospect’s site, relevant public material, and the original reason for the conversation.
- Write one working hypothesis about the problem. Treat it as a question to test, not a conclusion to sell.
- Choose the one service or engagement type you can credibly discuss if the fit is there.
- Open a note with sections for context, problem, impact, decision process, and next step.
- Decide what a respectful no looks like. A clear non-fit protects both sides’ time.
The five-part discovery-call flow
Use the sequence as a guide rather than a word-for-word script. Stay with the buyer's answer when it matters; the purpose of each section is more important than getting through every prompt.
01
Set the frame
Make the conversation useful without forcing a sales pitch.
- Thanks for making the time. I’d like to understand what is changing, what is getting in the way, and whether I can be useful.
- I’ll ask a few questions, share back what I hear, and then we can decide whether a next step makes sense. Does that work for you?
02
Understand the current situation
Establish a factual baseline before discussing a solution.
- What prompted you to look at this now?
- How are you handling this today, and where does that process become difficult?
- Who is affected when this stays unresolved?
03
Clarify the problem and impact
Separate a surface symptom from the work that actually needs attention.
- What does the issue cost in time, attention, quality, or missed opportunity?
- What have you already tried, and what did you learn from it?
- If this were working better in three months, what would be noticeably different?
04
Qualify the path forward
Check whether the work, timing, and decision process are real—not merely interesting.
- What would need to be true for this to become a priority?
- Who else needs to weigh in before a decision can be made?
- Is there a date, event, or constraint shaping the timeline?
05
Recommend only the next step
End with a proportionate commitment and a named owner.
- Based on what you shared, I see [brief observation]. The useful next step may be [specific action].
- Would it be helpful if I sent a short outline of that approach by [date]?
- Before we close, what should we each do next and when should we reconnect?
Use notes that make follow-through easier
Do not rely on a vague recap after the call. Capture enough detail to write an accurate follow-up, advance a qualified opportunity, or close a non-fit without revisiting the entire conversation.
| Section | Prompt | Your notes |
|---|---|---|
| Context | What changed or made this conversation timely? | |
| Current approach | How is the work handled today? | |
| Problem | Where is the friction, risk, or missed opportunity? | |
| Impact | What happens if nothing changes? | |
| Decision path | Who decides, what matters, and by when? | |
| Next step | What will happen next, who owns it, and when? |
Copy the structure into the note tool you already use. The blank column is intentional: use it for facts, not assumptions.
A clear non-fit is a successful outcome
Say no when the problem is outside your expertise, the buyer cannot name a meaningful need, the timing is not real, or the decision process cannot support the work. A respectful close is better than a proposal built on uncertainty.
When there is fit, send a brief recap while the context is fresh: the problem you heard, the agreed next step, the owner, and the date. Then record it in your pipeline immediately.
Keep the system connected
Run better calls inside a repeatable acquisition rhythm
Use the 30-day client acquisition plan to create the conditions for relevant conversations, then record outcomes and next actions in a practical pipeline tracker. For editable worksheets, follow-up templates, and the complete operating system, see the AI Client Acquisition OS.