Sales Layer · Client Acquisition · Brief 43
Discovery Call OS for Solo Consultants:
Scripts, Frameworks, and Tools.
You're not losing deals on the call. You're losing them in the system around it. The discovery call is a diagnostic session, not a sales pitch — and the consultant who positions as a diagnostician closes more deals at higher prices. Six-layer OS with the pre-call system, four-phase call structure, diagnostic question bank, investment conversation scripts, and post-call follow-up templates. Updated May 2026.
Updated: May 2026 · Pricing verifiedThe failure mode
You're not losing deals on the call. You're losing them in the system around it.
A great call, clear interest, no close. The "I'll be in touch" that turns into silence. The ghosting problem almost never traces back to the call itself — it traces back to a broken post-call system. No same-day follow-up. No clear next step stated at the end of the call. No proposal timing commitment. The call converted; the system lost the deal.
The discovery call is not a sales pitch. It is a diagnostic session. The consultant who positions as a diagnostician — not a persuader — closes more deals at higher prices. When a prospect feels genuinely understood — when they hear their problem reflected back with precision — they move toward engagement without needing to be persuaded. System beats personality. The goal is to remove as many variables from the call as possible so the only remaining variable is genuine fit.
Six layers of the Discovery Call OS
Each layer is a designed component, not a tip in isolation.
Layer 1 — The Pre-Call System
The discovery call begins before the call. Two inputs determine call quality more than anything that happens during it: the information you have about the prospect and the information they have provided you.
Intake form design: A well-designed intake form does three things — pre-qualifies the prospect, signals you run a serious process, and hands you the diagnostic foundation. Key fields: current situation (in the prospect's own words), what they've already tried, desired outcome, timeline, and budget range. An open-text "describe your situation" field outperforms a multiple-choice dropdown for prep value.
Pre-call research (20 minutes): LinkedIn profile (recent activity, not just role), company website (current positioning, recent news), any referral context, and intake form responses cross-referenced with their public presence. Arrive with a hypothesis about their actual problem before they describe it. Confirming or refining a hypothesis is far more powerful than arriving blank.
Pre-call framing email (24 hours before): "This is a working session, not a sales call — come with your real numbers and real constraints." This framing shifts the prospect's mental posture before the call begins. One of the highest-leverage, lowest-effort improvements in the Discovery Call OS.
Layer 2 — Four-Phase Call Structure
| Phase | 45-min call | Purpose |
|---|---|---|
| 1 — Frame-setting | 5–8 min | Establish structure; explain three possible outcomes ("agreement on path forward / not my specialty / need more info") |
| 2 — Diagnosis | 20–25 min | Situation → complication → implication → previous attempts → success definition. You speak <30% of the time. |
| 3 — Reflection | 5–8 min | Precise verbal summary of their situation, cost of the problem, and definition of success. If they say "yes, exactly" — proceed. |
| 4 — Investment | 10–12 min | Only begin after reflection lands. Scope + price + cost of inaction. State the number. Stop talking. |
Layer 3 — The Diagnostic Question Bank
These are frameworks to internalise and adapt, not scripts to read. Organised by diagnostic goal.
Current situation
"Walk me through what's happening right now — give me the version with the real numbers, not the polished one." / "How long has this been the case?"
Urgency and timeline
"What's made this a priority right now, as opposed to six months ago?" / "What happens if this is still the situation in six months?"
Previous attempts (skip at your peril)
"What have you already tried? What worked, what didn't?" / "Have you worked with a consultant on this before?" — prevents recommending something they've already failed at; surfaces political context.
Budget and authority (skip and pay for it later)
"Have you set a budget, or are you still figuring out the right investment?" / "Who else is involved in making this decision?" / "On a scale of 1–10, how committed are you to solving this in the next 90 days?"
Success definition
"How will you know, six months from now, whether this engagement was successful?" / "What would make you say 'that was worth every dollar' after this is done?"
Layer 4 — The Investment Conversation
Moving to pricing before the prospect feels understood is the single most common cause of price resistance. The investment conversation only begins after the reflection lands.
Transition phrase: "Based on what you've described — [one-sentence problem summary] — here's how I typically approach this." The word "typically" signals you've done this before and have a process.
Investment summary frame: Scope + price + cost of inaction. "This engagement is priced at $18,000. Based on our conversation, a successful outcome is conservatively worth $150,000 — that's an 8× return." Only viable if the implication questions surfaced a real cost.
After you state the number: stop talking. Solo consultants almost universally fill silence after stating a price. Silence is consideration, not rejection. The first person to speak after the price is stated loses negotiating position.
"I need to think about it" response: "That's completely fair. Can we schedule a 20-minute follow-up call for [specific date] so I can answer any questions that come up?" This transforms a polite brush-off into a committed next step. If they decline to schedule, you have important new information.
Layer 5 — The Post-Call System
The "they ghosted" problem that consultants diagnose as "they weren't serious" is almost always a post-call system failure.
Same-day follow-up email template (within 2 hours)
- Opening: One sentence naming the most important thing you heard (demonstrates listening)
- Mirror: Brief restatement of the problem in their language
- Path forward: What happens next with a specific date
- Closing question: "Does this match how you're thinking about it?" — keeps the conversation open
Proposal timing: Proposals sent more than 48 hours after the call convert at dramatically lower rates. Send within 24 hours for straightforward engagements; for complex proposals, send a "proposal preview" email within 24 hours confirming you're working on it.
CRM update immediately: Decision criteria stated, timeline and decision deadline, budget confirmed or inferred, decision-makers involved, specific language the prospect used to describe their problem (quote verbatim — this language is gold for proposal writing).
Layer 6 — Tools Layer
Booking: SavvyCal or Calendly with a dedicated discovery call page that includes qualifying copy — not a generic "book a call" link. AI notes: Fathom or Fireflies for automated transcription and summary — use AI notes as a first draft for the CRM update and follow-up email, then edit. AI captures words; consultants capture meaning. CRM pipeline stage update immediately post-call.
Self-diagnostic
Where does your discovery call actually break down?
Pre-call gaps
No intake form. Read answers but didn't research. Confirmation email confirms logistics but doesn't set the frame.
During-call gaps
Spoke more than 30% of the time during diagnosis. Moved to investment before the reflection landed. Skipped the budget and authority questions because they felt intrusive.
Post-call gaps (where most deals are actually lost)
Follow-up email sent the next day (or not at all). Proposal took more than 48 hours. No explicit next step committed to before ending the call. CRM not updated.
The lowest-friction first step
Implement the post-call follow-up template today. This single change will improve conversion before anything else changes. The call system is important; the post-call system is where most deals are actually lost.
Get the Solo Consultant OS Blueprint
Five-layer OS architecture, tool selection by practice stage, and automation wiring — free for subscribers.
- Five-layer OS framework
- Tool selection by practice stage
- Make automation scenarios
- Weekly OS Review template
Free for subscribers
No spam. Unsubscribe any time.
Related reading