For agencies
Send clients a clean link to generated work instead of a zip file, with expiry when the engagement ends and a project link when the deliverable has several parts.
The situation
You produce visual deliverables for clients who are not technical and will not run a local file, clone a repository, or create an account on a tool they have never heard of. The work is often generated or assembled with AI assistance, it changes across review rounds, and it should stop being available when the engagement closes.
What you are publishing
- Client-facing reports
- Audits, performance summaries, competitive analyses, and research write-ups rendered as one browsable document.
- Design and prototype previews
- A working HTML prototype the client can click through without a staging environment or a design tool login.
- Multi-part deliverables
- A strategy document, an appendix, and a data view that belong together behind one project link.
What matters most here
The client opens a link, nothing else
No account, no download, no unzipping. The share URL opens in the browser they already have, on the phone they are reading email on.
Expiry when the engagement ends
Set a retention window so deliverables stop being reachable after the contract closes, without you having to remember to remove anything.
Revision rounds keep one URL
Round two publishes as a new version of the same artifact. The client keeps the link from round one and sees the current work.
One link for a bundle
Project links index several artifacts at once, which is closer to how a real deliverable is shaped than a single file.
How the workflow runs
- 01Generate the deliverable as a self-contained HTML document.
- 02Publish it into a project named for the client engagement.
- 03Send the artifact link, or the project link if the deliverable has several parts.
- 04Publish new versions as review rounds land, without reissuing URLs.
- 05Set or shorten the expiry when the engagement closes, or revoke the link outright.
The questions this team asks first
Can I put this on our own domain?
No. BinHTML does not offer custom domains, so links are always on binhtml.com. If white-labelled delivery is a hard requirement, a deployment platform with a client subdomain is the better tool.
Is an unlisted link private enough for client work?
Unlisted means anyone with the URL can open it, and the page is noindex so it will not surface in search. For work that must not be forwardable, use private visibility on Pro, which restricts viewing to your account. Neither is a substitute for redacting content that should not be published at all.
What happens if a client loses the link?
The artifact stays in your dashboard, so you can resend the same URL. Revoking is a deliberate action; losing the email does not revoke anything.