Back to the library

Workflow Library · Client Work

Discovery Call Follow-Up Workflow

Turn a strong discovery conversation into a clean recap, next-step recommendation, and proposal path before the buyer cools off.

Summary

A discovery-call follow-up workflow for consultants, agencies, and service businesses using AI to summarize the call, clarify the problem, frame the recommendation, and send the next-step message without generic sales fluff.

What this workflow gets you

Start with a call recording or rough notes. Leave with a problem summary, deal-relevant recap, proposal recommendation, and a follow-up email that makes the next commitment obvious.

Step by step

The workflow outline

Each step is designed to reduce ambiguity between the raw input and the final deliverable, which is usually where generic prompt packs break.

Step 1

Capture the decision-relevant notes

Pull the buyer's goals, pain points, urgency, stakeholders, and constraints out of the raw conversation before the key context fades.

Input

Discovery transcript, notes, and account context

Output

A clean call brief with problem, urgency, stakeholders, and constraints

Step 2

Clarify the real buying problem

Separate surface requests from the actual bottleneck so the follow-up reflects what matters commercially, not just what was said most often.

Input

Call brief plus service or offer context

Output

A concise problem statement and opportunity framing

Step 3

Recommend the next step

Prompt for the most appropriate follow-up: proposal, mini-audit, second call, or a lightweight decision memo depending on readiness and complexity.

Input

Problem statement, budget signal, and decision stage

Output

A next-step recommendation with rationale and required inputs

Step 4

Draft the recap and follow-up email

Write the message that mirrors the buyer's language, summarizes the call, confirms next steps, and removes ambiguity around timing.

Input

Call brief and next-step recommendation

Output

A personalized follow-up email with recap, CTA, and timeline

Step 5

Prepare the internal handoff

Package the call into the proposal or delivery workflow so no one has to reconstruct the opportunity later from calendar memory.

Input

Recap email, recommendation, and offer notes

Output

An internal handoff note for proposal drafting or account setup

Example inputs and outputs

What the workflow looks like in practice

Sample prompt

Input

Summarize this 35-minute discovery call with a consultant prospect. Pull the buyer's real pain points, budget signal, and likely scope, then write a follow-up email that proposes a mini-audit before a full engagement.

Output

A buyer-specific recap with a clear next-step recommendation and a follow-up email that feels consultative instead of canned.

Sample checklist

Input

Build a discovery follow-up checklist that covers call summary, problem framing, proposal readiness, open questions, proposal deadline, and what needs to be captured for the delivery team.

Output

A repeatable post-call checklist organized around recap quality, commercial clarity, and handoff readiness.

Workflow action

Input

Turn these rough notes into an internal handoff for a proposal writer. Include the buyer's goals, top blockers, likely deliverables, urgency, budget sensitivity, and what still needs clarification before sending scope.

Output

A clean internal brief that makes proposal drafting faster and keeps the final recommendation tied to the original conversation.

Before and after

The difference between vague prompting and a reusable workflow

Before

The call feels strong, but the follow-up takes too long, the recap gets generic, and the next step loses the precision the conversation earned.

After

The buyer gets a timely recap that reflects the real conversation, and the internal team gets enough structure to move into proposal or onboarding without guessing.

Related products

Use the workflow as the demo. Use the product when you need the full pack.

These pages are public by design. When you want the reusable prompts, examples, and deeper systems behind them, start here.

Why these pages convert better

They show the workflow, not just the promise.

Short promise and clear audience

Step-by-step input/output framing

Before/after proof plus product pathways