Share AI-generated work with clients

sendhey turns whatever your AI just finished — a report, an audit, a prototype, a proposal — into one link you control: gated with a password or a verified email if the client needs it, tracked if you want to know it was opened, and built to survive a client's inbox instead of dying in a chat export. Connect Claude, ChatGPT, Cursor, or Codex to sendhey once, then have the agent publish there instead of pasting raw files, screenshots, or a wall of markdown.

The workflow

Connect your AI client at /connect — one browser OAuth approval, done once. From then on, tell the agent to deliver finished work through sendhey instead of dropping it in the chat: it calls publish_page with the HTML or files, picks an access gate, and gets back a share URL to send the client plus, for a hosted page, a separate owner-only edit link that stays with you. Manage, re-gate, or turn any link off later from your dashboard.

What you're actually sharing decides the details

Gates and tracking, honestly

Every link defaults to open, with no tracking beyond a delivery record. From there you choose a shared password, an email address (optionally verified with a one-time code), or a restriction to named people or company domains. Analytics is a separate, explicit choice — off, anonymous aggregate counts, email-verified identified opens, or consent-based behavioral events — never bundled silently into the access gate. If a client needs to formally acknowledge the exact document version they were shown, turn on document approval: sendhey records a one-time-email-verified acknowledgement of that specific content. That is a recorded acknowledgement, not an electronic signature, and we make no claim about its legal effect.

Where this fits a consultancy

If you run client delivery for a small AI studio or solo practice, the pattern repeats every week: an agent produces something, a human decides who can see it, and a client opens a link that just works with no account of their own. See client delivery for AI consultancies for the weekly-delivery version of this workflow, or the MCP reference if you're wiring this up from code rather than a chat.

For your role

The same "gate it, track it, revoke it" job shows up under different names depending on who's sending the link and what their agent built: founders sharing a pitch deck or investor update, product teams sharing a prototype, PRD, or spec, agencies and studios delivering built creative work through revision rounds, sales teams sharing an AI-drafted proposal, investors sharing a deal memo or LP update, and customer success teams sharing a QBR or renewal case.

Honest limits

sendhey doesn't rewrite or improve what your AI produced — it's a delivery layer, not an editor. Identified "who opened this" tracking needs an email gate; a fully open link only ever gives you counts. Document approval is a recorded acknowledgement, not a signature with legal weight. And a client still needs the link in hand — sendhey doesn't discover or notify recipients on its own.

Try it free

Free 14-day Pro trial starts when you publish your first link. No card.

Connect your AI · Create a workspace instead

See pricing for exact plan limits, or read who builds sendhey.

Written by Marcel Seibold, founder of sendhey.

About · Privacy · Legal notice · Report illegal content · Terms · DSA