What should the first follow-up email actually contain?

The written recap plus at most two supporting artifacts: the sourced answer to the buyer's stated question and one public page that carries your central claim. More than that tends to dilute the message, because it hands the buyer a prioritization job you should have done yourself.

How soon after the call should the follow-up go out?

The recap the same day, while commitments are fresh on both sides. The sourced answer as fast as accuracy allows — when speed and accuracy conflict, accuracy tends to matter more, because the buyer is checking your claims rather than waiting for your email.

Should pricing be included in the first follow-up?

Only if it was discussed on the call or explicitly requested. Sending unrequested commercial terms substitutes your agenda for the buyer's, and it changes the follow-up's character from verification aid to pitch.

What if there is no customer story that matches the prospect's situation?

Leave that slot empty rather than sending a near miss. A mismatched story tends to read as inventory-clearing and spends the credibility your sourced answer earned. The absence is also worth logging internally — it tells marketing which proof is missing for a segment you are actively selling into.

What to send a prospect after the first call

Guide · Sales · 4 min read · last verified 2026-07-27

Reviewed before publication Editorial board Independent commercial review

In shortThe follow-up as verification aid: buyers tend to fact-check after calls, so send artifacts that survive scrutiny — the sourced answer to their stated question, one public page, a matching named story, and the written record of the call.

A first-call follow-up is the small set of artifacts a seller sends after an initial conversation, and it has one job: to hold up under the verification the buyer is about to do without you in the room. What tends to happen after a good first call is not deciding but checking — the buyer retells what they heard to colleagues, searches the vendor's claims, and increasingly puts questions to an AI assistant and compares its answers with the seller's. That unsupervised stretch, mapped in What happens after the demo, is where first impressions are either confirmed or quietly reversed. The follow-up is your only contribution to it.

That framing settles most arguments about what to send. Anything chosen to persuade one more time competes with the buyer's checking; anything chosen to help the checking go well cooperates with it. Four artifacts, described below, consistently belong in the second group.

A verification aid, not a brochure

One caution before the list. What an AI assistant says about your category today is an observable example, not a fixed fact — the answers differ between systems and shift as sources and models are updated. You do not control that side of the buyer's checking; the only lever you hold is sending material that does well inside it: specific, sourced, and public wherever possible. Every artifact below is built to that standard.

First artifact: the sourced answer to their actual question

On the call, the buyer asked something specific — about an integration, a workflow, a security posture, a migration path. Answer that question in writing, precisely, with the source attached: the public documentation page, the named example, the dated reading. Not the adjacent question you would rather answer, and not a paragraph that gestures at the topic before pivoting to strengths.

This is where call preparation pays off twice. If you researched what answers your buyer would meet before the call — the discipline described in How to prep a sales call with AI answer research — you already know what your written answer will be compared against, and you can source it accordingly.

Second artifact: one public page that carries the claim

Send a live URL that supports the claim most central to their interest — a documentation page, a published methodology, a public customer page. Public pages can be forwarded, quoted, and checked by people who were not on the call. A gated PDF asks the buyer to trade contact details for the chance to verify you, which inverts the entire purpose of the exchange.

If no public page supports their use case, that is a finding worth reporting to marketing, not a reason to attach a deck in its place. The gap will be discovered either way; better that you discover it first.

Third artifact: the story that matches their situation

If a named customer in a comparable situation has a checkable outcome, send that story. The hierarchy in What is a proof point is the selection filter: a story the buyer can verify outranks a stronger-sounding story they must take on faith. And if nothing in the case file genuinely matches, send nothing in this slot — a mismatched story tends to read as inventory-clearing, and it spends credibility the first two artifacts just earned.

Fourth artifact: the written record of the call

A short recap: the buyer's problem in the buyer's own words, what each side committed to, and the next step with a date. It does two jobs at once. It demonstrates that you listened — the problem statement in their vocabulary is the proof — and it becomes the internal retelling artifact, because a champion who must summarize you to colleagues will often forward the recap rather than reconstruct it. Write it as the document you would want circulating without you.

What not to send

The all-purpose deck: built for every prospect, it answers none of this one's questions, and it signals that the follow-up was assembled by habit. The attachment pile: five documents ask the buyer to do your prioritization for you. Unrequested pricing: if commercial terms were not discussed on the call, sending them substitutes your agenda for the buyer's. Gated content of any kind: verification aids must not require a form. A wall of links: ten unranked URLs is the attachment pile with better formatting.

Each of these fails the same test — it serves the seller's need to feel thorough rather than the buyer's need to check.

Timing, and where the artifacts come from

The recap goes out the same day, while both sides' memory of commitments is fresh. The sourced answer follows as fast as accuracy allows — same day when the source is at hand, the next when it must be verified. Speed signals attention and accuracy signals competence, and when the two conflict, accuracy tends to win, because the buyer is checking rather than waiting.

Assembly speed is mostly determined before the call. Teams that maintain a proof library — every claim stored with its evidence, date, and owner — can pull the sourced answer and the matching story in minutes, because the claim-to-artifact pairing already exists. Teams without one rebuild that pairing under time pressure, per deal, and the follow-up quality shows it.