Guides

The sales leave-behind that reports back

The best follow-up after a real meeting is not a deck attached to a thank-you email. It is a small live page built from what was actually discussed — an ROI calculator with the prospect's numbers in it, a one-pager mapping their stack, a comparison of the options you walked through — published at a stable URL, gated to the prospect's company, and instrumented. You send one link. From then on you know who opened it, when, for how long, and, most usefully, when someone new from their domain opens it — because that means your champion forwarded it internally.

There is plenty of advice about how to make sales collateral. Almost none of it answers the only question you actually have after hitting send: did they read it? This guide is built around that answer.

What do you send after the meeting?

Something the prospect could not mistake for a template. You were in the room; your notes or the transcript carry their team size, their current tooling, the objection the VP raised at minute forty. An agent can turn that into a leave-behind in the time it takes you to write the recap email — and the strongest format is interactive, not static.

This is already standard advice for sellers working with Claude. SalesGear's guide to Claude for sales puts it directly: "Ask Claude to build an interactive ROI calculator as an Artifact: deal-specific inputs (team size, current costs, time savings), live outputs, shareable with your champion" (SalesGear). Their reasoning for why it works is the part to internalize: the champion re-runs the calculator with colleagues, "which means they are selling for you."

Three shapes that consistently earn a read:

• An ROI calculator with their numbers pre-loaded. Sliders for the inputs they pushed back on. The default state shows their case, not a generic one.
• A one-pager mapping their stack. Where you sit, what you replace, what you touch — concrete system names from the call, not category boxes.
• An option comparison. The two or three paths you discussed, with the trade-offs you conceded as well as the ones you won. Conceding one earns more trust than a wall of green checkmarks.

Interactive client-facing pages are displacing decks in adjacent work too: ad agency Adspirer cut client reporting from "1.5 to 2 hours per client" to "5 minutes per client" by moving to Claude-built interactive reports (Masset). The economics that make a bespoke report viable per client are the same economics that make a bespoke leave-behind viable per deal.

Why not a PDF attachment or a public link?

A PDF goes dark the moment you send it. You will never know whether it was opened, skimmed, or forwarded, and when the deal shifts you send "v2_FINAL" while the old file keeps circulating in their inbox.

Publishing from the AI lab's own share button has the opposite problem: the link stays live, but it tells you nothing back — no view counts, no notifications, no names. You sent the follow-up into a void and the void does not report.

There is also a privacy wall the native options cannot get around. A real leave-behind names the prospect and carries their numbers — costs, headcount, stack. That cannot sit on a public-or-nothing URL. Lab-native sharing is coarse: private to you, visible inside your own organization, or fully public. Your organization's boundary, by definition, does not include the prospect. There is no tier that means "the people at Acme, and nobody else."

To be fair to the alternatives: hosting is free everywhere. GitHub Pages, Netlify, an S3 bucket, the lab's publish button — any of them will serve your HTML at no cost. Hosting was never the hard part. What you need starts after the link leaves your outbox: who can open it, who did, and what they did with it.

How do you gate it so the forward still works?

Send Artifact publishes a self-contained HTML file or folder to a stable URL — sendartifact.com/you/acme-followup — and every publish starts private until you widen it. Readers never create accounts; at most they verify their email with a one-time code, once per browser.

For a leave-behind, three settings make sense:

Gate to the domain, not just the attendees. The moment your champion forwards the link to a colleague you have never met, that colleague can still open it — they verify their own @acme.com address and they are in. And because guest access always verifies, you see a new, verified reader from the account in your analytics. That is the buying-committee signal every seller wants and almost never gets: evidence the deal is being socialized internally, with names attached. Grant only the attendees' individual emails and the same forward dead-ends at an access screen — right for genuinely confidential material, but it silences the one signal you most want to hear.

One more setting worth deciding on: readers can pin comments on an artifact, and comments are on by default. For a leave-behind, where the reader is an audience rather than a reviewer, turn them off at publish (--comments off). If you leave them on — say your champion's technical counterpart likes to ask questions inline — the comments simply queue for you. You read them, and when you decide something should change, you point your agent at the thread. Nothing about the artifact changes because a reader typed into it.

How do you know when to follow up?

Because the artifact reports back. Each artifact shows views by day and by version, distinct readers, each reader's identity where they verified or entered an email, active read time — time the page was actually in front of them, not merely open in a tab — and how far down the page they got. Link-preview fetches and other bot hits are filtered out, so a view means a person rendered the page.

That turns follow-up from a guessed cadence into a reaction:

• Opened Wednesday 9:04, read six minutes, scrolled to the end — call Thursday, and reference the section they clearly spent time in.
• Opened, thirty seconds, a fifth of the page — the framing did not land. Fix the page before you send another word.
• Not opened by Friday — your nudge can be honest: "resending in case it got buried," instead of the "any thoughts?" you'd otherwise send into the void.
• A second reader from their domain — the forward. Ask your champion who else should be in the next meeting; you may already know the name.

None of this is a novel theory of selling. Gated links plus read receipts for static slide decks was DocSend's entire early product, and Dropbox paid about $165M for it in 2021 (TechCrunch). The same mechanics now apply to something better than a deck: an interactive page your agent built from this meeting, for this deal.

What happens when the deal changes?

You republish. Same slug, same URL — the link in the prospect's inbox, in the forwarded thread, and pasted in your CRM now serves the new version. Every version is retained, immutable, with one-step rollback, so "what did we show them in July" is a lookup, not an argument. And because views attribute to versions, you can see whether anyone has read the revised pricing you shipped Tuesday — worth knowing before the Thursday call where you plan to defend it.

This matters more than it sounds. Deals move: procurement gets added, a competitor cuts price, your packaging changes. A PDF forks, and stale copies keep circulating with old numbers. A republished artifact converges: one URL, always current, history intact.

The workflow, end to end

1. Meet. Take notes or capture the transcript as usual.
2. Draft. Point your agent at the notes: "build a one-page leave-behind for Acme — the ROI calculator with the numbers Maya gave us, plus the two rollout options we discussed." Self-contained HTML, up to 25 MB.
3. Publish and gate.

npx @sendartifact/cli login you@yourcompany.com
npx @sendartifact/cli publish ./acme-followup --slug acme-followup
npx @sendartifact/cli access acme-followup --visibility guests --grant acme.com

The publish is private until the access line runs, so nothing is exposed in between.

1. Send one link in your recap email.
2. Watch the readers, not the calendar. Follow up on the read, the stall, or the forward — each with different words.
3. Republish as the deal moves. The URL never changes.

If your agent has the Send Artifact skill installed, steps 3 and 6 become things you say rather than commands you type — "publish this for the Acme team" resolves to a domain-gated artifact on its own. The read signal comes back the same way: ask "has anyone at Acme read the follow-up?" and get names and read times instead of opening a dashboard.

The leave-behind used to be the piece of collateral you knew the least about: you put the most deal-specific thinking into it, then handed it to the void. Reverse that and follow-up stops being a cadence problem. You are no longer guessing whether Tuesday's meeting is moving. The page you left behind is telling you.

Published 2026-08-27 · markdown twin at /guides/sales-leave-behind.md · questions: support@sendartifact.com.