A BETTER WAY TO SHARE THE WORK
Write a sales follow-up buyers can use to make a decision
Give your buyer something useful to forward, not another list of everything your product does.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
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.
01 / SEE THE DIFFERENCE
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.
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.
02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
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.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
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.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- 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.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
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.