How to share a Claude artifact with a client (no login for them)

You built something good in Claude — a pricing page, a one-pager, a live demo — and now you need it in front of a client. An artifact is just that: a page you made in Claude. The hard part is getting it to someone outside your company without making them sign in, install anything, or hit a wall because your plan won't let the page go public. Here is how to send it as a link they can just open, and hear what they actually think of it.

The usual ways to share, and where they fall short

There are a few obvious ways to hand a Claude page to someone. Each one leaks when the someone is a client.

You can use Claude's own Publish button to make the page public. It works when it works. But the published page lives inside Claude, it can read as a shared document rather than a page from you, and on some plans the button is switched off entirely.

You can copy the code out and drop it on a hosting service yourself. That is a detour. You are now babysitting a host, a URL, and a file, for one page you just wanted to send.

You can paste it into an email or a doc. The layout breaks, the interactive parts stop working, and it no longer looks like the thing you built.

Every one of these gets the page in front of the client. None of them tells you what the client thought. You send it Tuesday, and by Thursday you are refreshing your inbox, guessing whether it landed. And the first one stops working the moment your plan blocks Publish.

When the Publish button is blocked on a Team plan

This is the wall a lot of sellers hit. You are on a Team or Enterprise plan, you go to publish your artifact, and the option is greyed out or gone. An admin turned off public sharing for the whole workspace, usually for good security reasons, and it is not getting switched back on before your follow-up is due.

Vista is a way around that wall, not a replacement for it. Vista takes the same artifact and gives it its own public link — one that lives with Vista, not inside Claude's sharing settings. Your workspace's Publish policy stays exactly as your admin set it. You just get a client-ready link by another path.

Share it as a room instead

Instead of publishing the page, you deploy it as a Vista room. A room is one page at one public link, built to be sent to a buyer. Your artifact becomes the page inside it.

From Claude Code — the command-line version of Claude that AI-native sellers already keep open — one command sends the artifact up and hands back the live link:

vista deploy pricing-page.html

The link comes back ready to paste into an email. For the full walkthrough of that step, see how to deploy a Claude artifact for sales. The short version: one page in, one link out. It does not even have to be a Claude page — a one-pager built in Codex, OpenAI's coding agent, ships the same way.

A room can hold more than the one page, too. Drop the artifact in next to the PDF you were already sending, or the pricing sheet the client asked for, so everything they need sits behind the same link instead of scattered across three emails.

The client needs nothing to open it

Buyer needs nothing. Your client opens the link and the page is just there. No login, no account, no install, no Claude access of their own. It works in any browser, on a laptop or a phone.

The person you most want to reach — the CFO, the VP who got cc'd — is the least likely to create an account just to look at your page. With a room, there is nothing between them and the thing you sent. For the full picture of the buyer's side, see what your client sees in a Vista room.

The client is not going to file a support ticket to see your one-pager. If opening it needs an account, a password, or an app, a good share of the people you send it to simply will not bother. Zero friction is the whole point.

And they can talk back

Here is the part no other way of sharing gives you. Every method above ends the same way: the page goes out, and you wait to find out if anyone cared.

A Vista room is a room your buyer can talk back to. While your client is looking at the page, they hold ⌘ (or tap) and talk. They say what they actually think — the question, the objection, the part they liked — right on the page they are reacting to.

It comes back to you as a clean, readable message, filed to the deal and tagged for what it is: a question, an objection, a buying signal, a name to bring in, or a follow-up they expect. You are not guessing whether the page landed. You are reading what they said about it.

And when your client forwards the room to a colleague — the way a champion sends it up the chain — each person's reaction comes back on its own, attributed to them. You can tell the CFO's objection from the champion's question, across a full buying committee, without asking anyone to sign in or say who they are.

Keep the link current

You will change the page after you send it. The pricing shifts, the client asks for one more slide, you catch a typo. Update the room and the client's link shows the new version. Same link, always the latest.

No "ignore my last email." No re-sending a fresh file and hoping they open the right one. The link you sent on Monday is still the right link on Friday.

That is the whole move: build the page in Claude, deploy it as a room, send one link, and hear back. Free while in beta, no credit card at signup. For the bigger picture of selling this way, see how salespeople use Claude.