You built something good in Claude. A live dashboard, a pricing calculator, a polished one pager. Now you need to get it in front of a client, and the only obvious option is the share button that spits out a claude.ai link.
Stop for a second before you paste that into an email. That link does three things you probably do not want. It puts Claude's name on your work. It can expire, which means the link you sent last month may be dead when your client clicks it. And it drops your client onto a page that clearly is not yours, which quietly undercuts the fee you just charged.
There is a better way to do this, and it takes about two minutes to set up the first time.
Why the default share link is a problem
Native Claude sharing was built for showing something to a colleague, not for delivering paid work to a paying client. The gap shows up in a few places.
- The URL says claude.ai. Your client sees the tool, not your studio.
- Published links can be public. Anyone who gets the URL can open it, and it can end up indexed.
- Links are not permanent. When they lapse, you are the one fielding the 'this link is broken' message.
- There is no structure. One link is one thing. A real client relationship has ten things across three months.
What clients actually expect when they receive work
Think about the last deliverable you were proud of. The value was not only in the content. It was in how it arrived. A clean address, your logo at the top, everything in one place, nothing that felt like a workaround. That is the standard your work is being measured against, whether or not anyone says it out loud.
The handoff is part of the deliverable. A brilliant analysis sent through a broken link reads as careless, not brilliant.
The approach that works: re-host it under your own brand
Instead of forwarding Claude's link, you re-host the artifact at an address you control. The artifact stays live and interactive. The wrapper around it becomes yours: your name, your colors, your domain. Your client never sees claude.ai and never needs to know which tool you used.
Here is the workflow we recommend, and the one 1hub is built around.
- Copy the artifact link from Claude as usual.
- Paste it into a portal for that specific client. The artifact is re-hosted, not screenshotted, so anything interactive stays interactive.
- Set who can see it. Invite only, a password, or a plain private link, depending on the client.
- Send one address, like yourstudio.com/acme. When you update the artifact, the same address shows the new version. The link never changes.
Keep it interactive when the interactivity is the point
A finished chart can be flattened to an image and nobody loses anything. A model where the client is supposed to change an input cannot. If you built a calculator or a live dashboard, sending a PDF of it defeats the purpose. Re-hosting keeps the thing alive so your client can actually use it, which is usually the reason you built it in Claude in the first place.
When you want feedback on the page itself
Sometimes the point of sharing an artifact is to get notes back. Instead of a client emailing you 'the second chart looks off,' it is far cleaner when they can leave a comment right on the thing. For that, a tool worth knowing is commentable. You publish your HTML as a private, commentable page and the client can drop feedback directly on it, no account or setup on their side. It pairs nicely with a Claude artifact when you are still in the review stage and want reactions in context.
We like it enough to recommend it outright. When you are collecting feedback, use something like commentable. When you are delivering the finished work, put it in a branded portal on your own domain. Different jobs, different tools.
A quick word on privacy
Client work is often confidential. Before you publish anything, make sure the delivery method matches the sensitivity. A private, access controlled portal is a very different thing from a public link that anyone can open. If the content includes numbers a competitor would love to see, the difference matters.
The short version
Do not hand clients a claude.ai link and hope it holds up. Re-host the artifact on your own address, keep it interactive, control who gets in, and send one link that never breaks. Your work looks like what it is, which is yours.
That is exactly what 1hub does. Paste a Claude artifact, get a branded portal on your own domain, and send a single link per client. You can set one up free and see how it feels before your next handoff.