How Sales Teams Share AI-Generated Proposals Without the Attachment Mess

The deal cycle breaks your file, not the other way around

You generate a proposal in Claude or ChatGPT. The narrative is sharp, the research is specific to the account, and the HTML looks good. Then the delivery layer undoes all of it.

You export to PDF because "that's what clients expect." You attach it to an email. The prospect's inbox flags it, or their IT strips the attachment, or they forward it to a colleague who never gets the file. You update the pricing after a call, export again, and send a second email with "updated proposal attached." Now two versions exist in the wild and nobody is sure which one matters.

This is not an AI problem. It is a distribution problem. The generation step got better; the sharing step stayed broken.

One URL in the CRM, not a trail of attachments

The fix is structural: give the proposal a permanent address.

When you publish HTML to unfurl, you get a single URL. Paste it into your CRM, drop it in a follow-up email, or pin it in a Slack channel. When the proposal changes after the next discovery call, publish again. The URL stays the same. Your prospect opens the link tomorrow and sees the version you published today.

This eliminates the re-send loop. It also eliminates the "which version did they see?" conversation with your manager before the forecast call. The dashboard shows a timestamped version history, so you can see exactly what was live on any given date.

Sensitive pricing stays behind a password

Not every proposal should be visible to anyone with the link. If your pricing is account-specific or your proposal includes competitive positioning you would rather not have forwarded freely, add a passphrase to the share link. The prospect enters the password once; the page loads in their browser. No PDF to save, forward, or screenshot by accident.

This matters most for enterprise deals where a proposal circulates through procurement. You control the access layer instead of hoping the email stays in the right thread.

Your brand on the page, not a generic file share

When a VP of Procurement opens a proposal link, the page should look like it came from your company. On the Pro plan, your logo and brand name appear on the shared page. The experience reads as "we built this for you," not "here's a link from some tool."

Combine that with a clean URL and no download friction, and the first impression lands the way you intended.

What this looks like in practice

1. Generate the proposal in Claude, ChatGPT, or your team's internal tooling. Focus on the narrative and the account research.
2. Publish to unfurl by dragging the HTML file into the dashboard. If your team has a pipeline that produces proposals programmatically, use the API instead.
3. Paste the link into your CRM record and your outbound email. One link, one source of truth.
4. Iterate after every call. Pricing changed? Scope expanded? Publish the updated HTML. The link your prospect already has shows the new version.
5. Check the history before your next internal review. The version trail shows what was live when, so you can reconstruct the conversation accurately.

A habit worth building early

Most reps try this workflow with one deal and stop resending attachments after that. The moment a prospect says "I just opened the link and saw the update" without a new email is when the old process stops making sense.

If your team is already producing proposals with AI, the generation step is solved. The gap is the last mile: getting that output to the prospect in a form that survives the deal cycle. That is the part worth fixing first.

For a deeper look at the hosting and versioning model, see Host AI-generated HTML documents. If you are using Claude specifically, How to share Claude artifacts professionally covers the end-to-end workflow.