Consulting Growth

The Follow-Up Email After an AI Discovery Call Should Confirm the Unknowns

After an AI discovery call, confirm the observed problem, unanswered questions and next step without turning tentative ideas into a sales promise.

A discovery conversation can produce enthusiasm before it produces a defined project. Your follow-up should help the owner confirm what you understood, not imply that every idea discussed is already feasible.

Lead with the business problem

Use the owner's description in plain language. “Your team copies incoming requests into a shared tracker” is clearer than “We identified an agentic transformation opportunity.” If you did not observe the process directly, say that the description came from the conversation.

Separate known facts from open questions

Here is an illustrative follow-up you can adapt:

Thanks for walking me through how requests reach the team. My understanding is that staff currently copy them into the tracker and decide who should respond.
Before recommending a pilot, I need to confirm which system holds the current record, who can approve access and how the team handles incomplete requests. We have not yet agreed on automatic sending or changes to customer records.
If that summary is accurate, the next step is a short walkthrough using fictional or appropriately sanitized examples. After that, I can propose a bounded scope and explain what would still require staff review.

The example intentionally makes no price, timing or savings promise. Add those only when you have a defined basis for them.

Ask for one response

Give the recipient a simple action: correct the summary, identify the process owner or agree to a walkthrough. Do not attach a large questionnaire and ask them to design the project for you.

If there is no fit, close that loop politely. An honest discovery process can end with a recommendation to simplify the existing process or postpone the work.

Keep the message proportional

You do not need a proposal disguised as a thank-you note. Keep the discovery record short enough that the owner can notice and correct a wrong assumption. Store the correction with your project notes before drafting scope.

AI Consultant Launchpad provides a starting point for practical consulting work. The first useful deliverable may be an accurate shared understanding of what you still need to learn.