How to Share a Claude Design Deck (And Track Per-Slide Engagement)

HummingDeck Team
··読了時間8分
How to Share a Claude Design Deck (And Track Per-Slide Engagement)

Claude Design will write you a twelve-slide pitch deck while you make coffee. Describe an investor narrative, ask for the deck, and a few minutes later it's done: on-brand, interactive, polished. The hard part isn't building the deck anymore. It's everything that comes after.

You want to send it to an investor, a sales prospect, or a stakeholder. You want to know whether they actually read it, which slides they spent time on, and whether they forwarded it. The defaults are all bad:

  • Email attachment. Most email clients block HTML attachments. The ones that don't tend to flatten or sandbox the file until the interactivity breaks.
  • Google Drive. Drive won't render the file. Your investor opens the link and sees raw HTML source or a broken preview, not a pitch.
  • PDF export. Strips the interactivity, animations, and any embedded behavior. You've taken a polished interactive deck and turned it into a static document.
  • Deploying to Vercel or Netlify. Works, but you've just turned a five-minute send into a thirty-minute deployment exercise. And you still have no engagement tracking, no access controls, and no way to revoke the link.

Claude Design makes the deck in minutes. The distribution layer hasn't kept up. That's the gap this guide is about.

What Claude Design is, in one paragraph

Claude Design is Anthropic Labs' visual prototyping product, launched on April 17, 2026. It sits at claude.ai/design and pairs Claude Opus 4.7 with an HTML canvas. An admin wires your design system in once, and every new project picks it up automatically. After that anyone on the team can describe a pitch deck, mockup, or landing page in plain English and shape it through chat, inline comments, or direct edits. Output is on-brand and interactive. The target user is the founder, AE, PM, or marketer who doesn't have a designer to call. Anthropic covers the launch in Introducing Claude Design and the workflow in Get started with Claude Design.

There are two ways out of a finished Claude Design project, both built in:

  • Handoff to Claude Code when the project is a prototype you want turned into real shipping code.
  • Export and share externally when the project is a deck, one-pager, or landing page you want a prospect, investor, or customer to read.

This guide is about the second path. Claude Design's built-in share link is scoped to your organization, so colleagues with org access can view or edit. It doesn't give you a link you can hand to someone outside the company with access controls and engagement tracking. HummingDeck is that layer.

Step 1: Export from Claude Design as standalone HTML

Open the deck in Claude Design and click Export in the upper right of the canvas. The menu lists six options: Download as .zip, Export as PDF, Export as PPTX, Send to Canva, Export as standalone HTML, and Handoff to Claude Code. Pick Export as standalone HTML.

You get a single .html file with everything inlined: fonts, images, brand assets. No external dependencies, nothing breaks when you move the file.

Save it somewhere you'll find it.

A quick word on the other exports. PPTX is fine for handing the deck to a colleague who'll keep editing in PowerPoint, but the HTML-to-PPTX conversion is lossy: brand kit drifts, layouts shift, animations get stripped. PDF preserves the look but loses everything interactive. The .zip is a multi-file bundle, mostly paired with the Claude Code handoff. For an external send where you also want to see what the recipient does, standalone HTML is what you want.

Step 2: Upload to HummingDeck

Drag the .html into your HummingDeck deck library. There's no API call to Anthropic, no OAuth, no "connect your Claude account" step. You export the file, you upload it. That's the whole integration.

HummingDeck unwraps Claude Design's bundler on upload, so slide structure comes through correctly. The deck lands in your library with the right section count.

It's served from a sandboxed viewer, so the HTML, CSS, and JavaScript inside the export run in isolation. The recipient still gets the interactivity. Your account stays protected.

The standard share-link controls apply:

  • Email gate so only specific recipients can view.
  • Link expiration so the deck stops working after a date.
  • Revoke access at any time, even after the recipient has the URL.
  • Custom domain so the share URL sits on your brand, not ours.
  • Viewer notifications so you get pinged the moment someone opens it.

Tune them to the use case. Investors: email gate, expiry at the close of the round, custom domain. Sales prospects: domain gate, longer expiry, notifications on every view. Internal stakeholders: no gate, short expiry, notifications off.

Generate the link. Done.

Email the link. The recipient clicks it, lands on the HummingDeck viewer, and reads (or doesn't read) the slides.

Tracking runs inside the viewer and watches what they actually do: which slide they're on, how long they spend there, how far through the deck they get, and which links and buttons they click. It's tuned for the shape of Claude Design output, so per-slide breakdown is accurate.

In your dashboard:

  • Per-slide time-on-page. Which slides they spent four minutes on, which ones they skimmed in fifteen seconds.
  • Completion percentage. Did they reach the ask slide, or bail at the problem slide?
  • Clicks. Every link or button inside the deck, including any interactive prototype Claude Design embedded.
  • Forwarding inference. When a second viewer fingerprint opens the deck in the same window and the network or geography don't match the first viewer, HummingDeck flags it as likely forwarded. A champion is selling for you internally.
  • Return visits. When someone comes back weeks later, you get notified. Usually it's a budget cycle, board prep, or a stalled deal moving again.

In a sales motion, those five signals decide your next move. A prospect who lingers on the pricing slide for two minutes gets a different follow-up than one who bounces on slide two. A prospect who forwards the deck to three colleagues gets a different follow-up than one who opens it alone at 11pm.

Why this signal is more honest than open rates

Cold email open rates barely measure anything in 2026. Apple Mail Privacy Protection, corporate security scanners, and AI inbox agents pre-load every tracking pixel before a human sees the message. Plenty of SDR teams see open rates in the high-40s on campaigns where real human readership is in the single digits. We covered the full mechanics in Cold Email Open Rates Are Dead and the broader pixel-and-receipt failure mode in Do Email Read Receipts Actually Work?.

Engagement on a deck you shared is a different category. Bots don't read for four minutes. Scanners don't come back to the pricing slide three weeks later. AI inbox agents don't forward the deck to a CFO. When you see those signals on a Claude Design deck behind a tracked link, you're seeing real human behavior. That's the kind of signal you can actually forecast on.

The shift is structural. Claude Design lets you ship a deck in minutes. The number of decks in flight per rep is climbing fast. The question for revenue teams isn't "how do I make more decks" anymore. It's "how do I tell which of the decks I'm sending actually landed." Per-slide engagement, tied to a specific recipient, is the signal that survives the bot layer.

Beyond Claude Design: the same flow for other AI tools

The same upload path takes anything that exports self-contained HTML. ChatGPT canvas, v0 demos, Lovable apps, Bolt projects, Manus artifacts, Cursor previews. Same tracked link, same sandboxed viewer, same per-section engagement. Claude Design was the forcing function because of how fast it ships polished pitch decks, but the capability is broader.

If you're running multiple AI tools and need a single distribution layer for everything they produce, that's what HummingDeck is. One library, one analytics view, one set of share controls for every deck and prototype your team ships.


Related: