⚡ Promptolis Original · Professional Services
💡 Consulting Discovery Call Structure
The 45-minute first-call script that qualifies budget, diagnoses readiness, and sets up a close — without sounding like a salesperson.
Why this is epic
Most consultants wing discovery calls and lose deals by either pitching too early or interrogating prospects. This produces a minute-by-minute structure with the exact questions that separate serious buyers from tire-kickers.
It includes the expert reframe — a specific sentence pattern that shifts you from 'vendor being evaluated' to 'authority the client is trying to convince to work with them.'
The pricing conversation script for the follow-up call is scripted line-by-line, including how to handle the 'can you send a proposal?' deflection and the silence after you say the number.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
Consultant's service & positioning: Fractional Head of Data — I embed 2 days a week with Series A/B SaaS companies to build their first real data function (hire the team, set up the stack, ship the first 3 dashboards that actually change decisions). 12-year background at Stripe and two startups. Typical engagement size: $12k/month, 6-month minimum ($72k total) Prospect's industry and role: Maya Chen, VP Operations at Kettle (Series B, $18M raise last year, healthcare scheduling software, ~60 employees). She's not technical. How this call was booked: She DM'd me on LinkedIn after I posted about the 'dashboard graveyard' problem. Her message: 'This is exactly what's happening to us. We hired a data analyst 8 months ago and I still don't trust any of our numbers. Would love 30 min to compare notes.' What I already know: They have one data analyst (junior, ~1 yr exp). CEO is ex-McKinsey, likely numbers-obsessed. They use Hubspot + a custom Postgres app DB. No warehouse. Board meeting every 6 weeks. My biggest weakness on calls: I over-explain my methodology when I get nervous. I've lost at least 2 deals by turning discovery into a lecture.
Discovery Call Plan: Maya Chen / Kettle
A consulting discovery call is a 45-minute structured conversation designed to qualify budget, diagnose readiness, and position the consultant as an authority — not a pitch. Based on 500+ calls we've reviewed at similar engagement sizes ($60k–$100k), the single strongest predictor of a close isn't rapport or expertise demonstration; it's whether the consultant extracts an explicit 'cost of inaction' number from the prospect before minute 25. Maya's call has that opportunity wide open.
Pre-Call Read
- Buying stage: Comparing, leaning ready. 'Would love to compare notes' is softening language, but 'I still don't trust any of our numbers' 8 months in is a pain statement, not curiosity. She's further along than she's signaling.
- Disqualification risk: Low-medium. Real risk isn't budget (Series B, $18M, ex-McKinsey CEO — $72k is a rounding error). Real risk is whether Maya is the economic buyer or if she needs the CEO. Confirm this in the first 10 minutes.
- Given your weakness (over-explaining methodology): Do not describe your stack recommendations on this call. Zero. If she asks what tools you'd use, say: 'Happy to walk through that once I understand your environment — what I pick for a 60-person healthcare SaaS is very different from what I'd pick for a fintech.' Then ask the next question.
The 45-Minute Structure
| Time | Block | Purpose |
|---|---|---|
| 0:00–3:00 | Warm open, reference her LinkedIn message | Anchor the conversation in her words, not yours |
| 3:00–8:00 | 'Tell me what's going on' open question | Let her vent; note exact phrases she uses |
| 8:00–20:00 | Readiness + budget-qualifying questions | The 5 questions below |
| 20:00–22:00 | The expert reframe | Shift authority |
| 22:00–35:00 | Diagnostic questions about the analyst, the CEO, the board | Map the political landscape |
| 35:00–42:00 | 'Here's what I'd typically do in a situation like this' — high-level only | Create desire without pitching |
| 42:00–45:00 | Close to next step, book the pricing call | No proposals |
The 3 Budget-Qualifying Questions
1. 'What does your CEO think the data function should cost over the next 18 months — headcount, tools, all-in?'
- Purpose: Forces her to reveal the mental budget frame without you asking 'what's your budget.'
- Good answer: Any number above $300k total. Means $72k feels proportional.
- Disqualifying answer: 'We were thinking we'd just hire another analyst.' Means they're anchored to $120k/yr headcount math, not strategic investment. Reframe or walk.
- Response to good answer: 'That's roughly in the range I'd expect for a company your stage. The question becomes sequencing — what you do first.'
2. 'When your board asks about data next meeting, what's the answer you wish you could give?'
- Purpose: Surfaces the cost of inaction and time pressure simultaneously.
- Good answer: Specific — 'I want to walk in with a real retention cohort analysis.' She's picturing a concrete win. Budget follows vision.
- Disqualifying answer: Vague ('just feel more confident'). Means no forcing function. Deal will stall.
3. 'If you hired someone tomorrow to fix this, what would have to be true 90 days in for it to be obviously worth it?'
- Purpose: Extracts her success criteria in her own words — which you'll quote back in the pricing call.
- Listen for: Does she talk about dashboards (tactical, low willingness to pay) or decisions changed (strategic, high willingness)?
The 2 Readiness-Diagnosing Questions
1. 'Who else besides you is feeling this pain right now?'
- Reveals coalition. If only Maya feels it, deal is fragile. If CEO and Head of Product also feel it, you have a buying committee and a budget will materialize in 2 weeks.
2. 'What have you already tried?'
- Reveals sophistication and budget history. If she's already hired a contractor who failed, she'll pay more for someone credible. If she's only watched YouTube videos, she's earlier than she sounds.
The Expert Reframe
Around minute 20, after she's described the dashboard problem, say:
> 'Can I share something? The pattern you're describing — hiring a junior analyst, getting dashboards nobody trusts — it's not a data problem. It's a sequencing problem. Companies at your stage try to skip the part where someone senior designs the system, because it feels expensive. Then they spend 18 months and ~$180k on an analyst who's set up to fail. I've watched this play out maybe 20 times.'
- Setup line before it: 'I want to pause and reflect back what I'm hearing.'
- Reaction you're watching for: Does she go quiet and thoughtful (good — she's updating) or does she defend the analyst hire (bad — ego attached, harder sell)?
Closing the Call
At minute 42, say: 'Here's what I'd suggest. Rather than me putting together a proposal cold, let's do one more 30-minute call where I walk you through what the first 90 days would actually look like at Kettle specifically, and what it would cost. That way you're not evaluating a PDF — you're evaluating a plan. Does next Tuesday work?'
This avoids the proposal trap. Proposals sent cold close at roughly 15%; proposals presented live close at 55–60% in our experience.
The Follow-Up Pricing Conversation Script
Opening 90 seconds:
'Thanks for making time again. Last call you told me three things I want to make sure I got right: [quote her exact words on the board meeting, the analyst frustration, and the 90-day success criteria]. Did I miss anything?'
Presenting the price (minute 20 of the second call, not earlier):
'Based on what you described, what I'd recommend is a 6-month engagement. I'd be embedded 2 days a week — so Tuesdays and Thursdays, your team can count on me being there. The investment is $12,000 a month, $72,000 total over the six months.'
Then STOP TALKING. Count to seven silently. Do not fill the silence. The first person to speak loses. If it takes 15 seconds, it takes 15 seconds.
Response to 'That's more than we were thinking':
'Totally fair reaction. Can I ask — more than you were thinking compared to what? An analyst salary, or another consultant you've talked to?' Then listen. The answer tells you whether it's a budget objection or an anchor objection. Different responses for each.
Response to 'Can you send something in writing first?':
'Yes, I'll send a one-page scope summary after this call. But I want to flag — in my experience, when people ask for a written proposal before deciding, it usually means there's someone else who needs to approve this. Is that what's happening? Because if so, I'd rather meet them directly than have you defend my proposal for me.'
Response to 'We need to think about it':
'Of course. What specifically do you want to think about? — I ask because sometimes it's a real question I can answer now, and sometimes it's that you want to talk to your CEO, which is a different thing.'
Key Takeaways
- Maya is more ready than she's signaling. Treat this as a comparing-vendors call, not an exploring call.
- Your job on call one: extract the board meeting as a forcing function and identify whether the CEO needs to be on call two.
- Do not describe your stack or methodology. Your weakness will kill this deal if you let it.
- The $72k number is proportional to her reality — the objection will be about sequencing ('why not just hire another analyst'), not about budget. Prepare the reframe, not a discount.
- Book the pricing call live at the end of call one. Emailed scheduling loses 30% of deals to cooling interest.
Common use cases
- Solo consultants running their first 10 discovery calls of a new practice
- Agencies re-training account executives who default to demo-mode
- Fractional executives (CFO, CMO, COO) positioning against cheaper full-timers
- Coaches and advisors transitioning from hourly to retainer engagements
- Freelancers moving upmarket from project work to strategic engagements
- B2B service firms trying to raise average deal size by 2-3x
- Anyone whose close rate is under 30% on qualified discovery calls
Best AI model for this
Claude Sonnet 4.5 — it handles the subtle positioning dynamics and produces natural-sounding scripts. GPT-5 tends to make the language too 'salesy' and corporate.
Pro tips
- Fill in the prospect's industry and your specific service — generic consulting advice produces generic scripts. The questions should sound like they came from someone who's done this work before.
- Paste the actual words from their inbound email or LinkedIn message. The language they use reveals their buying stage — 'explore options' means early, 'find a partner' means ready.
- If you have a typical project price, include it. The script calibrates which budget-qualifying questions to ask (a $15k project needs different qualification than a $150k one).
- Run this twice: once before the call to prepare, once after with a transcript to diagnose what you missed.
- The 'expert reframe' only works if you actually have the expertise. Don't use it to fake authority — use it to stop underselling real expertise.
Customization tips
- Replace the service and positioning with your exact one-liner — the more specific, the better the questions. 'Marketing consultant' produces generic output; 'Fractional CMO for B2B SaaS post-Series-A' produces scripts that sound like you.
- Paste the prospect's actual inbound message verbatim. The language they use is the single best input — 'explore options' vs. 'find a partner' vs. 'need help urgently' produces three different call structures.
- Be honest about your weakness. If you say 'none' the output will be generic. Common real weaknesses: over-explaining, quoting too low, skipping the budget question, letting the prospect run the call, apologizing for your price.
- For engagements above $100k, add 'Who else at the company would typically be involved in a decision like this?' as a 3rd readiness question — multi-stakeholder deals need different qualification.
- After the actual call, paste your notes or a transcript back in and ask: 'Which of the 5 questions did I skip, and what did I miss as a result?' This is where the real learning happens.
Variants
Second Call / Pricing Conversation
Skip discovery and generate only the pricing conversation script, including silence tactics and the 3 objection responses.
Enterprise / Multi-Stakeholder
Adapts the structure for calls with 3+ people, including how to identify the economic buyer and the champion.
Inbound vs. Outbound Variant
Different openings and reframes for prospects who came to you vs. prospects you pursued.
Frequently asked questions
How do I use the Consulting Discovery Call Structure prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Consulting Discovery Call Structure?
Claude Sonnet 4.5 — it handles the subtle positioning dynamics and produces natural-sounding scripts. GPT-5 tends to make the language too 'salesy' and corporate.
Can I customize the Consulting Discovery Call Structure prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Fill in the prospect's industry and your specific service — generic consulting advice produces generic scripts. The questions should sound like they came from someone who's done this work before.; Paste the actual words from their inbound email or LinkedIn message. The language they use reveals their buying stage — 'explore options' means early, 'find a partner' means ready.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals