The Fractional Discovery Call Script: Questions That Close Without a Proposal
Most fractional executives lose deals not on the call, but in the week after it, while a proposal sits unread in someone's inbox. The fix is to run the call so well that the engagement is decided before you hang up.
This is a working script. It is built around a pain funnel: three layers of questions that move from what the buyer says they want, down to what is actually costing them money and sleep, and then to a close that asks for a decision instead of asking for permission to write a document. Use it on intro calls for fractional, advisory, interim, or consulting work. Adapt the wording to how you talk.
Why the proposal is usually the problem
A proposal is what you send when the call did not finish the job. It is an attempt to re-create momentum in writing, after the room has gone cold. The buyer is now reading on their own, comparing you to other tabs, and inventing objections you are not there to answer.
Strong discovery calls collapse that gap. By the end, the buyer has said out loud what is broken, what it costs, and what they want to see happen. You have confirmed scope and rate in the room. The follow-up is a one-paragraph email confirming what you both already agreed to, not a ten-page pitch hoping to earn a yes.
That only works if your fractional executive discovery call questions do real work. Generic questions get generic answers. The funnel below is designed to get past the polished version of the problem.
Before the call: set the frame in one line
Open by naming what this call is and is not. Something like: "I keep these to about 30 minutes. I want to understand what's going on, and by the end we'll both know if it makes sense to work together or not. Sound good?"
That sentence does three things. It gives the call a time box so the buyer relaxes. It signals that a "no" is an acceptable outcome, which lowers their guard. And it tells them a decision is expected today, not deferred to a document. You have quietly removed the proposal as the default next step.
Layer one: surface the stated problem
Start where the buyer is comfortable. These questions get them talking and give you the surface version of the situation. Do not solve anything yet. Just collect.
- "Walk me through what made you book this call. Why now?"
- "What does the team or function look like today?"
- "What have you already tried to fix this?"
- "In a perfect world, what changes six months from now?"
The "why now" question is the most important one here. Every engagement has a trigger: a board meeting, a missed quarter, a key person who left, a raise that did or did not happen. Find the trigger and you find the urgency. If there is no "why now," there is usually no deal, and it is better to learn that in minute four than in week three.
Layer two: quantify the cost
This is where most calls stop too early. The buyer has described a problem; now you make them attach a number and a consequence to it. You are not being aggressive. You are helping them do math they have been avoiding.
- "What is this costing you right now, in revenue, time, or headcount?"
- "If nothing changes for the next two quarters, what happens?"
- "Who else feels this problem? Whose number is it tied to?"
- "You said you tried hiring for this. What did that cost, and where did it land?"
Listen for the shift in their voice when the cost becomes concrete. "We're probably leaving a couple hundred thousand on the table" is a different conversation than "things are a bit messy." The first one justifies your rate without you ever defending it. The second one tells you to keep digging or politely wrap up.
If the buyer cannot name a cost, the problem is not yet expensive enough to pay you to fix. That is fine. You have just saved yourself an unpaid proposal.
Layer three: make the stakes personal
Companies do not buy. People with budgets and reputations buy. The third layer moves from the organization's cost to the individual's stake, because that is what actually moves money.
- "How does this land on you personally if it doesn't get solved?"
- "What are you telling your board or your boss about it right now?"
- "What does solving this free you up to do?"
These questions feel intimate, so earn them by listening hard through layers one and two. When a founder admits the cash crunch is keeping them up, or a VP admits this is the thing standing between them and a promotion, you are no longer selling a service. You are removing a specific weight from a specific person. That is what closes.
The close: "what do you need to see to move forward today?"
Now you transition from diagnosis to decision. Reflect back what you heard, propose a shape of work, and ask the closing question directly. Do not soften it into "let me put together a proposal."
It sounds like this: "Here's what I'm hearing. The lead pipeline is flat, it's costing you roughly X a quarter, and it's the thing your board is asking about. I'd come in two days a week, own the demand engine, and get you to a predictable pipeline inside 90 days. My rate for that is [your number]. What would you need to see to move forward today?"
That last question is the whole script in seven words. It assumes the deal is on. It surfaces the real objection while you are still in the room to handle it. And it puts the next move on the buyer instead of on a document you have to go write. The answers cluster into a handful of types:
| What they say | What it means | Your move |
|---|---|---|
| "Nothing, let's do it" | You are done. Confirm start date and rate. | Send a one-paragraph confirmation, not a proposal. |
| "I need to talk to my co-founder" | Real, but you are not in the room with the decider. | Offer to join that conversation. Do not let it go async. |
| "It's the budget" | Price or scope objection, now visible. | Adjust scope to fit the number, or hold your rate and trim deliverables. |
| "Send me something in writing" | Often a soft no, or a missing decider. | Ask: "Happy to. What specifically needs to be in it for you to say yes?" |
That last row is the trap the whole script exists to avoid. When someone asks for the proposal, do not just agree and hang up. Ask what needs to be in it for a yes. Either they tell you the real criteria, and your follow-up is a targeted confirmation, or they cannot, and you have learned this was never close. Both outcomes beat spending three hours on a document that was a polite brush-off.
What to send after a good call
When the call closes the way it should, your follow-up is short: the scope you agreed on, the rate, the start date, and how to book the first session. No cover letter, no deck. The persuasion already happened live. The email just makes it official and easy to say yes to twice.
That is the quiet advantage of running discovery this way. Your buyers self-qualify, your rate gets justified by their own numbers, and you stop subsidizing tire-kickers with free strategy documents.
When the conversation is ready to happen, it helps to control where it starts. On ExecRoster you publish a profile that says exactly what you fix and what you charge, so the people who book you already know your scope and your rate, keep about 90% of what they pay, and arrive on the call ready to run the script above, not to negotiate whether you belong on it.