How each kind of professional hands finished work to a client — designers, freelancers, agencies, consultants, educators.
Start here
Designers, freelancers, agencies, consultants, in-house teams, and educators all hit the same wall — handing a finished HTML deliverable to the people who should see it. How the channel choice changes by role.
"Client portal" is one word covering two very different jobs. One of them needs software with logins and permissions. The other one is four links in an email, and buying the first when you needed the second is how a solo practice ends up administering a system nobody logs into.
You have one finished case study but the portfolio site isn't live yet. Here's how to send that single piece as a private link — without pushing a half-built site or flattening it into a doc.
Freebies, drafts, little tools — as a creator you keep needing a link that reaches specific people and nowhere else. A working guide to private share links for the three things creators send most.
Your freebie is the first thing a stranger ever taps in your bio — and a raw storage or design-tool URL gives you away before the page loads. Why a link-in-bio freebie should ride on a branded, own-domain link, and how to do it with no website and no server.
How analysts, freelancers, and agencies hand AI-built client work over as a private, branded link instead of a raw chat export — so the work reads as a finished decision, not a transcript of the model making it.
Materials trapped in the LMS disappear when the semester ends. The static HTML + private link shape lets a lesson live where the educator chooses, not where the institution provides.
Recurring reports break in a way one-off deliverables don't: every send produces another address, and the old ones keep working with old numbers in them. Here's the version where the report has one address for the whole engagement.
The writing got fast. The handover didn't. Here's why the last step of client work — getting the finished thing in front of the client — quietly became the slow part, and what a good version of it looks like.
A personal site updates twice a year. CMS subscriptions and full deploy pipelines are sized for sites that update twice a week. The middle ground: one HTML file at your own domain.
A pricing proposal is read more like a website than a document. Channel options for sending one, and where private-link HTML sits between a PDF attachment and an esignature tool.
Figma is designed for collaboration, so the share link shows comments, version history, and the frames you parked. Channel options for a client-facing preview, and where private-link hosting fits.
The format you pick for an internal review is a category-signaling choice. When the team starts shipping HTML links instead of .pptx attachments, the room reads it before the content opens.
Interactive dashboards lose their interactivity in PDF, screenshot, and screen recording. The trade-off, and where private-link hosting fits between handoff and full deployment.
Five channels agencies use for client previews — and what each accidentally reveals about the work in progress. Where private-link delivery sits, and when it's worth the swap.