Send a client the work on a private link, not a public URL.

See a real one first. Here is an actual client proposal, sanitised and hosted on Stacktree, password-protected exactly as described below. Open it with the password preview: view the example deliverable.

The handoff AI made harder, not easier

AI got very good at producing a finished, self-contained page: a discovery document, a status report, an interactive prototype, a dashboard, a pitch. The work is done in minutes. Then you hit the part nobody solved: getting it to the client cleanly.

The usual options all give something away. An HTML file attached to an email looks improvised and half the time renders wrong. A screenshot throws away the interactivity that made the work worth building. Standing up a Vercel or Netlify project is developer plumbing one page should not need. A Notion or Drive link is generic, unbranded, and often pushes your client into a sign-in wall. And a design-tool preview can expose your working file or demand an account from the viewer. None of these says: here is a private, professional link to the work.

The flow

• Publish the file. Drop the HTML in, or ask your AI to publish it directly. You get a private, unguessable link straight away.
• Gate it if you need to. Add a password, or restrict viewing to the client’s email domain. Set an expiry so the preview does not outlive the engagement.
• Put your name on it. Serve it from your own domain so it reads as your studio’s work, not a file on someone else’s host.
• Send the link. The client clicks and sees the real, interactive deliverable. No account, no app, no download.
• Know it landed. See when it was opened and how far they read, so you follow up informed instead of chasing.
• Collect the changes. Turn on the client feedback loop and comments come back on the page itself, anchored to the exact element, and the fix ships to the same URL.

Why a private link beats the alternatives

• vs emailing a file: renders perfectly every time, and you control access instead of letting an attachment travel.
• vs Notion / Google Drive: branded, on your domain, and no sign-in friction for the client.
• vs a full client portal: no setup. When you just need to send one deliverable, a portal is too much machinery.
• vs a design-tool preview: a password, no exposed working file, and no forced account on the viewer.

Private, professional, and under your control

The link is the credential, and you decide who gets in: passcode, email-domain gate, expiry, or a burn-after-read link for a contract, an offer letter, or a credentials handoff that should not outlive being read. For confidential client material you can encrypt the page end-to-end, so even the host cannot read it. And because you can replace the page in place, sending a revision never means sending a new URL: the client keeps the same link and always sees the latest version.