What to Send After a Discovery Call So the Next Step Is Clear

What to Send After a Discovery Call So the Next Step Is Clear

The call ends with “This was really helpful.” You close the laptop feeling good. Then you open a blank email and realize nobody agreed on what happens next.

Do you send a proposal? Your calendar link? A case study? A cheerful “Let me know if you have any questions,” which hands the entire project back to someone who already has a job?

A discovery-call follow-up should help both people make the next decision. It should capture what you understood, what remains uncertain, and the action each person agreed to take. The result may be a proposal, another conversation, a referral, or a decision not to proceed.

For an expert whose reputation brings people into the conversation, this small email matters. Your website promises clarity and judgment. The follow-up is an early chance to demonstrate both.

Write for the Decision, Not the Meeting Minutes

A prospect does not need a transcript of the last forty minutes. They need a useful record of the problem and the path forward.

Before writing, finish this sentence:

“The next decision we need to make is whether ______.”

Perhaps you need to determine whether a workshop fits the team’s problem. Perhaps a department head needs to involve the person who controls the budget. Perhaps neither of you knows enough to define a project yet.

If you cannot name that decision, sending a polished proposal may only make the uncertainty more expensive.

Your public offer should already give someone a reasonable sense of what you do. What to Put on a Consulting Services Page Before You Send Someone the Link covers that earlier step. The follow-up moves beyond the general offer into the prospect’s actual circumstances.

Include Five Things, Without Turning Them Into Five Pages

1. The Situation You Heard

Describe the problem in language the prospect would recognize. Avoid upgrading it into a grander problem that happens to match your most expensive service.

“Your managers are giving different answers about how new employees should handle customer complaints” is more useful than “Your organization needs transformational leadership alignment.”

The first describes something someone could check. The second sounds like a conference banner.

If your interpretation is uncertain, label it: “My understanding is…” Then invite a correction. You are confirming shared understanding, not announcing a diagnosis.

2. The Outcome They Want

Separate the problem from the desired result. “Managers disagree” describes the situation. “New employees can find one approved escalation process” describes a useful change.

Use the outcome discussed on the call. Do not add revenue targets, deadlines, or promises that nobody agreed to. If the prospect offered a broad ambition, identify what still needs defining.

For example: “We still need to decide what a successful first month would look like.” That is more honest than inventing a metric because the email feels incomplete without one.

3. The Boundaries and Open Questions

Include the few conditions that could change your recommendation: who needs to approve the work, what information is missing, what has already been tried, or which part of the problem falls outside your expertise.

Keep sensitive details out of a casually forwarded email. Confirm recipients and use an appropriate channel for private documents. The principles in How to Build a Personal Brand When Your Work Is Confidential apply here, too. Being thorough does not require repeating everything you heard.

4. The Most Useful Next Step

Choose a next step that reduces the uncertainty you actually have.

If the scope is clear and the right people are involved, that might be a proposal. If the scope depends on reviewing a process document, get that document first. If the person you spoke with cannot authorize the work, the next step may be a conversation with the decision-maker.

Avoid treating every call as permission to send a proposal. A proposal should not conceal unanswered questions under attractive headings.

5. An Owner and Agreed Timing

“Let’s reconnect soon” is not much of a plan. “You’ll send the current checklist, and I’ll review it before our Tuesday conversation” gives both people something concrete.

Distinguish proposed timing from an agreed date. A suggested meeting is not a booked meeting, and enthusiasm is not approval to begin work.

A Discovery-Call Follow-Up Example

Here is a hypothetical example for an operations consultant. The names, company situation, and commitments are illustrative.

Subject: Next step on your new-hire process

Hi Maya,

My understanding from today’s conversation is that new hires receive different guidance depending on which manager trains them. Your immediate goal is one usable checklist for the customer-support team, rather than a company-wide training overhaul.

Before I recommend a project, I need to see the current checklist and understand who approves changes. We also haven’t defined how you’ll judge whether the new process is working.

As discussed, you’ll send the checklist and introduce me to your support director by Thursday. I’ll review the material and come back Friday with either a proposed scope or the questions we still need to answer. I won’t prepare a full proposal until we have that scope clear.

If I’ve misunderstood the problem or the sequence, please correct me.

Thanks,
Devon

The email leaves out the biography, service menu, attachment pile, and claim that the consultant has already solved the problem.

Maya can forward it internally without translating a sales pitch. The work has boundaries, the missing information is visible, and the next action belongs to someone.

Change the Follow-Up When the Call Ends Differently

Your judgment should survive contact with your email software.

There Is a Fit, but No Decision Yet

Confirm what needs to happen before a decision. That might be an internal budget conversation, another stakeholder’s input, or a change in timing.

Ask what would make a follow-up useful rather than assigning yourself a permanent place in their inbox. If they agree to revisit the conversation next month, record that timing. Do not manufacture urgency to make your sales process feel active.

The Prospect Needs Work You Do Not Provide

Explain the mismatch without making the person defend their needs. If you know a suitable professional, offer to arrange an introduction with both people’s permission.

A graceful no protects your time and positioning. An expert does not have to accept every problem.

They Are Asking for the Solution Before Hiring You

A useful recap can clarify the issue without delivering an unpaid engagement. Distinguish a question you can answer briefly from analysis that requires meaningful work.

You might say, “Choosing between those systems would require reviewing your workflows and constraints. That assessment is a separate piece of work.” How to Handle “Can I Pick Your Brain?” Without Giving Away a Consulting Session offers more examples of that boundary.

Send Proof Only When It Helps This Decision

One relevant example can help a prospect assess your approach. A folder containing everything you have ever done usually creates another sorting task.

Choose evidence that addresses the specific uncertainty. If the prospect wonders whether your process works with a small team, share a relevant, permission-cleared example and explain its limits. Do not imply that a different client’s result predicts theirs.

Your Personal Brand Proof Folder: What to Collect Before You Need It can help you organize that material before you need to retrieve it. For longer examples, How to Turn Client Results Into a Personal Brand Case Study explains how to show the situation, your contribution, and the result without inflating your role.

For an author discussing speaking, consulting, or a launch partnership, the same rule applies to books. A relevant chapter can demonstrate how the author thinks; sending the entire book can distract from the immediate decision. Connecting the book’s promise to its audience is also part of the positioning work explored at Isla Lake.

Do a Two-Minute Check Before Sending

Read the email from the prospect’s side of the desk.

Can they recognize their problem? Can they correct your interpretation? Is it clear what has been agreed and what is only proposed? Does each next action have an owner? Have you included private information that does not belong in this recap?

Then delete anything included mainly to prove how impressive you are.

Send it within the timing you promised. Otherwise, send it while the conversation is fresh and the recap is accurate. No magic hour compensates for a vague message.

Your personal brand earns attention before the call. Afterward, clear thinking and reliable follow-through give that attention somewhere useful to go.

Frequently Asked Questions

Should I always send a proposal after a discovery call?

No. Send one when you understand enough about the problem, scope, decision process, and constraints to make a responsible offer. Otherwise, use the follow-up to confirm the missing information and the next decision.

How long should the follow-up email be?

Long enough to capture the decision and next actions, short enough to read without reconstructing the meeting. A short recap may be sufficient. A complex engagement may need a separate document, but the email should still make the next step obvious.

What if the prospect does not respond?

Follow the timing you agreed to. If no timing was set, one useful follow-up can ask whether the next step still makes sense. Avoid endless “just checking in” messages. A quiet inbox does not tell you why someone paused, and it does not authorize starting work.

Book a Free Brand Call to get a custom strategy for turning your expertise into opportunities. 👉 Schedule here.