A sales follow-up captures the buyer’s decision, relevant evidence, open questions, and next steps—so colleagues who missed the call can understand the evaluation.
You review the facts and access. Nothing is published without your approval.
The method behind the recapFrom a feature list to a buyer’s evaluation
How do you turn a sales call into a useful follow-up page?
Start with the decision the buyer needs to make. Use an agent to organize approved call notes into their priorities, relevant evidence, unresolved questions, and one agreed next step. Review the claims and sharing permissions, then share a short HTML recap that makes sense even to someone who missed the call.
What to give your agent
Approved discovery notes or a transcript you have permission to use, with the buyer’s priorities and objections preserved.
Current product documentation for the specific capabilities discussed, including limitations that affect the decision.
Approved pricing or proposal material, with its date, scope, and any conditions clearly attached.
The next step actually agreed on the call; keep a suggested next step separate from a confirmed commitment.
Name the buyer’s decision
Write one sentence describing what the buyer is evaluating and why now. Ask the agent to extract requirements from the notes, not infer them from a job title. If the notes do not establish budget, authority, or timing, leave those questions open. This sentence determines what belongs on the page.
Match evidence to priorities
For each important requirement, include the relevant capability, its supporting source, and any limitation. Leave unrelated features out. Distinguish something demonstrated during the call from something a product document describes. A helpful recap gives the buyer enough context to challenge a claim, not just repeat it internally.
Make uncertainty visible
Add a compact section for unanswered questions, who will resolve them, and the target date if one was agreed. Show proposed evaluation criteria separately from accepted criteria. Avoid turning an enthusiastic comment into purchase intent or a tentative date into a commitment. Those small distinctions protect the usefulness of the recap.
Review, then share the recap
Check the page against the source notes and approved commercial terms. Remove internal qualification scores, private comments, and information the recipient should not see. Apply your saved style if available, while keeping the buyer’s decision prominent. Share only after confirming the audience and access setting; changing a page later does not retract copies.
Using only the approved call notes and product material I provide, draft a buyer-facing sales follow-up as static HTML. Lead with the buyer’s decision, then show their priorities, evidence relevant to each priority, limitations, unresolved questions, and the agreed next step. Distinguish confirmed facts from proposals. Do not invent pricing, capabilities, commitments, quotations, or dates. Exclude internal qualification notes and confidential customer details. Apply my saved artifact style if available, with readable headings and restrained emphasis. Include source links only when supplied and appropriate for this audience. No scripts, forms, tracking, or live-data claims. Return a draft and a short list of claims I should verify. Wait for my review before publishing or changing access.
Check before you shareAccuracy, clarity, and permission
Can a colleague who missed the call understand the decision without reading the transcript?
Does every product and pricing claim match current approved material, including conditions?
Are tentative dates, suggested actions, and unverified requirements clearly identified?
Have you removed internal notes and confirmed who may open or forward the page?
When HTML fits
A concise recap that a buyer can read on a phone and forward to other decision-makers, with links to approved supporting material.
When another format fits better
A substitute for a signed proposal, contract, secure deal room, or automatically updated customer record. Keep those authoritative records in their existing systems.
What we started withThe same facts, as an email
Fictional project email
Northstar — recap of the shared-reporting evaluation
Hi Northstar team,
The decision is whether to evaluate a shared reporting tool for your three-person operations team. The priorities discussed were a readable weekly summary and an export the team can keep. Automated source updates were discussed but are not verified.
The call included a sample summary. That is something shown, not proof of fit for your workflow or measured results. Export requirements still need comparison with current product documentation. No documentation excerpt, link, format, plan, version or date has been supplied, so export is not a confirmed capability. Automated source updates also remain unverified.
The open question is whether the tool can support your access requirements. Seller to confirm before proposing a pilot. Exact access criteria, a named seller owner and a target date are not supplied.
Proposed next step: review a sample built from non-sensitive test data. This is not yet agreed. No pilot date or commercial commitment has been agreed. No pricing or proposal terms are supplied; budget, purchasing authority and timing are not established.
This fictional buyer-facing recap was prepared September 20, 2026, not a supplied call date or documentation verification date. It includes no internal qualification notes, private sales comments or confidential customer details. Sources are the accompanying fictional discovery notes; no evidence links are supplied. It is a static recap, not an automatically updated customer record, booking or purchase authorization.
Inspect the HTMLOne self-contained file
The example is sanitized and isolated from this site. No scripts, forms, or live data.
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Northstar · Buyer evaluation recap</title><style>
*{box-sizing:border-box}body{margin:0;background:#faf6ee;color:#293329;font:16px/1.55 system-ui,sans-serif}main{max-width:1080px;margin:auto;padding:clamp(22px,5vw,56px)}h1,h2,h3,p{margin:0}h1{font:500 clamp(36px,5.8vw,64px)/1.06 Georgia,serif;letter-spacing:-.035em;margin:22px 0}h2{font:500 clamp(26px,3.6vw,36px)/1.17 Georgia,serif;letter-spacing:-.02em}h3{font-size:18px;line-height:1.35}p{margin-top:12px}.eyebrow{font-size:11px;font-weight:750;letter-spacing:.11em;text-transform:uppercase}.masthead{display:flex;justify-content:space-between;gap:12px;flex-wrap:wrap;border-bottom:1px solid #bfc8b9;padding-bottom:16px}.intro{font-size:19px;max-width:740px}.decision{margin-top:26px;padding:24px;background:#e8eddf;border-left:4px solid #486047}.decision h2{margin-top:10px}.section{margin-top:34px}.section>h2{margin-bottom:20px}.priority{display:grid;grid-template-columns:190px 1fr;gap:26px;padding:23px 0;border-top:1px solid #bfc8b9}.priority:last-child{border-bottom:1px solid #bfc8b9}.priority h3{margin-top:10px}.tag{display:inline-block;font-size:12px;font-weight:700;padding:5px 9px;background:#e8eddf;color:#344d30}.open{background:#f4e6c8;color:#6a4c19}.label{font-size:11px;text-transform:uppercase;letter-spacing:.06em;font-weight:750;color:#586252}.priority p{font-size:15px}.priority .note{font-size:13px;color:#586252}.gate{display:grid;grid-template-columns:1.5fr 1fr;gap:26px;border:1px solid #c7bea7;background:#f3ecdc;padding:24px;margin-top:28px}.gate h2{margin-top:10px}.gate p{font-size:15px}.gate .owner{border-left:1px solid #c7bea7;padding-left:24px}.next{margin-top:28px;background:#2f493b;color:#fff;padding:26px}.next h2{margin-top:12px}.next p{color:#e3ebdf}.terms{display:flex;gap:14px;flex-wrap:wrap;margin-top:18px}.terms span{font-size:12px;border:1px solid #91a58e;padding:7px 10px}.footnotes{display:grid;grid-template-columns:1fr 1fr;gap:26px;margin-top:26px}.footnotes p{font-size:14px}footer{border-top:1px solid #bfc8b9;padding-top:20px;margin-top:30px;font-size:12px;color:#586252}footer p{margin-top:6px}@media(max-width:600px){.priority,.gate,.footnotes{grid-template-columns:1fr;gap:14px}.priority{padding:20px 0}.priority h3{margin-top:6px}.gate .owner{border-left:0;border-top:1px solid #c7bea7;padding:16px 0 0}.decision,.gate,.next{padding:22px}}@media print{body{background:white}main{max-width:none;padding:24px}.priority,.gate,.next{break-inside:avoid}.next{background:#e8eddf;color:#293329}.next p{color:#293329}.terms span{border-color:#586252}}
</style></head><body><main>
<header><div class="masthead"><span class="eyebrow">Northstar / Buyer recap</span><span class="eyebrow">Fictional evaluation · No commitment</span></div><h1>A clearer next conversation.</h1><p class="intro">For Northstar’s three-person operations team: what matters, what the call showed, and what still needs an answer.</p></header>
<section class="decision"><p class="eyebrow">The buyer’s decision</p><h2>Should Northstar evaluate a shared reporting tool?</h2><p>This recap supports that evaluation decision. It is not a proposal, purchase approval or agreed pilot.</p></section>
<section class="section"><h2>Your priorities, matched to evidence.</h2>
<article class="priority"><div><span class="tag">Shown on the call</span><h3>A readable weekly summary</h3></div><div><p>The call included a sample summary.</p><p class="note">A sample was shown—not validated against Northstar’s own workflow. No measured outcomes or buyer acceptance are established.</p></div></article>
<article class="priority"><div><span class="tag open">Needs verification</span><h3>An export the team can keep</h3></div><div><p>Export requirements still need comparison with current product documentation.</p><p class="note">No documentation excerpt, format, plan, version or date supplied. This is a requirement, not a confirmed capability.</p></div></article>
<article class="priority"><div><span class="tag open">Discussed · Not verified</span><h3>Automated source updates</h3></div><div><p>Discussed on the call, but not verified.</p><p class="note">No supported behavior or documentation has been established. This static recap does not refresh automatically.</p></div></article>
</section>
<section class="gate"><div><p class="eyebrow">Before a pilot is proposed</p><h2>Can the tool meet your access requirements?</h2><p>The exact access criteria still need to be specified and checked.</p></div><div class="owner"><h3>Seller to confirm</h3><p>Confirm support before proposing a pilot. A named owner and target date are not supplied.</p></div></section>
<section class="next"><p class="eyebrow">Proposed next step · Not yet agreed</p><h2>Review a sample built from non-sensitive test data.</h2><p>A possible next evaluation step—not a booked session or a promise of fit.</p><div class="terms"><span>No pilot date agreed</span><span>No commercial commitment agreed</span></div></section>
<section class="footnotes" aria-label="Evidence and commercial boundaries"><div><h3>Commercial terms remain open.</h3><p>No pricing or proposal terms supplied. Budget, purchasing authority and timing are not established.</p></div><div><h3>Keep claims traceable.</h3><p>Source: the accompanying fictional discovery notes. No product-documentation links or dated extracts supplied. Verify claims before relying on them.</p></div></section>
<footer><p>Fictional worked example by share/artifacts. Northstar and this scenario are illustrative, not customer evidence. Prepared September 20, 2026; call date not supplied.</p><p>Buyer-facing recap only. No internal qualification notes or confidential customer details. Static reading view; no tracking, forms or booking. Keep proposals, contracts and customer records in their authoritative systems.</p></footer>
</main></body></html>
The original follow-up, reframedThe same evaluation, without the feature dump
A follow-up built around an evaluation
A fictional software evaluation after a discovery call. Product names, requirements, and dates are invented to show the structure.
The original notes
Thanks for your time! Here are our twelve features, a brochure, and a link to book another demo.
Decision
Should Northstar evaluate a shared reporting tool for its three-person operations team?
What matters
A readable weekly summary and an export the team can keep. Automated source updates were discussed but are not yet verified.
Evidence
The call included a sample summary. Export requirements still need comparison with the current product documentation.
Open question
Can the tool support the buyer’s access requirements? Seller to confirm before proposing a pilot.
Next step
Proposed: review a sample built from non-sensitive test data. No pilot date or commercial commitment has been agreed.
A buyer can forward this page without having to translate a feature list into a business decision.
Questions, adaptations & sourcesGo deeper when you need to
Should the follow-up replace the email?
Usually the email introduces the recap: one sentence about the buyer’s goal, the link, and the agreed next step. Keep urgent questions directly in the message. The page holds the context someone else may need when the email is forwarded.
Can I make a different recap for each stakeholder?
Yes, but keep the underlying facts consistent. A technical evaluator may need limitations and evidence; a budget owner may need scope and tradeoffs. Ask the agent to adapt the emphasis, then verify it has not changed the claims or exposed restricted details.
What if the buyer corrects the recap?
Treat that correction as valuable input. Update the page after review, add an updated date, and tell affected recipients when the change matters. An HTML page is not automatically synchronized with your notes or customer system.