Deploy a Claude artifact to a live link buyers can talk back to

You built the page in Claude. Now you need it live at a link you can drop into an email, not a file the buyer has to download. Deploying an artifact to a live link is one move in how sellers use Claude to close deals. With Vista, one command does it — and the link that comes back does something a plain host cannot. It lets your buyer talk back.

What deploying an artifact means

An artifact is just a page you built in Claude — a pitch page, a pricing page, a demo, a one-pager. Until you deploy it, it lives inside your Claude session, where the buyer cannot reach it.

Deploying it means moving that page to a live link: a real web address you can send, that opens in any browser, on a laptop or a phone. No download, no attachment, no 'enable editing' banner. The buyer clicks the link and they are on your page, exactly as you built it. That is the whole job of a deploy — get the page from your screen to a link the buyer can open.

The one-command deploy

If you build pages in Claude Code or Claude Desktop (the command-line and desktop versions of Claude), you can deploy without leaving your editor. Vista connects through MCP, the standard way Claude runs outside tools on your behalf. Here, MCP hands your finished page to Vista and gets a link back. One command does it:

vista deploy pricing-page.html

The live link comes back in the reply, ready to paste into an email. There is no separate dashboard to open, no upload screen, no export step. You stay in Claude the whole time. And the same set of tools that deployed the page will later pull the reactions and search what buyers said, so you never leave the place you already work. For the full picture of what these tools do, see what MCP does for sellers.

Static hosts stop at 'it's live'

A plain host can put your page on the internet. For most of them, that is where the story ends. The better ones will log that the page was opened — a timestamp, maybe a rough location. That is useful, and it is still a guess about what happened on the page.

You know the buyer looked. You do not know what they thought, which line confused them, or what made them lean in. A view count is not a reaction. It is a prompt to invent a story about a silent buyer, and inventing stories is exactly what makes follow-up slow and wrong. Every static host stops at 'it's live.' None of them collect the one thing you actually need: what the buyer has to say.

The wedge: your buyer talks back

A Vista link is a room your buyer can talk back to. While they are reading your page, they hold ⌘ (or tap) and talk. They say what they actually think, out loud, on the exact thing in front of them. Live transcription shows their words as they speak, so they can see it working.

This is the difference no host closes. Not opens, but reactions. Not a chart you have to interpret three days later, but the buyer telling you, in their own voice, minutes after they read it. The page is the same page you built in Claude. The link is the same link you would have sent anyway. The only thing that changed is that it now listens.

Picture it on one deal. You deploy the pricing page the morning of a call and drop the link into your follow-up. By that afternoon a voice note is waiting: the buyer, on the middle tier, saying the number is close but they need it net of the discount before finance will sign off. You never had to ask what they thought. You read it and reply to the exact thing.

Buyer needs nothing. No login, no account, no install. It works on a laptop or a phone. And because invite links are built to be forwarded, when your champion sends the room to their CFO, the CFO's reaction comes back as its own attributed message. You can see what buyers see in a Vista room before you send your first one.

What comes back to you

You do not get a raw, rambly recording to slog through. The voice note comes back polished into a readable message, filed to the right deal, anchored to the exact page (or section of the page) the buyer was reacting to. Each one is tagged by what it is:

• Question — something they need answered before they can move.
• Objection — the thing quietly giving them pause.
• Buying signal — the moment they lean in.
• Stakeholder mention — a name you now know to bring in.
• Action item — the follow-up they are expecting from you.

The original audio is always kept, so you can go back and hear the tone if you want it. Most of the time, the clean message is all you need to know what to do next.

Update the link without resending

The link stays current. Edit the page in Claude, deploy again, and the same link shows the new version. Fix a price, tighten the pitch, add the slide the buyer asked for — the buyer always sees the latest, and you never re-send an attachment. One link, always the newest version.

If you want to hand that same link to more people, here is how to share the artifact with a client: each person who opens it can react, and every reaction comes back separately attributed, so a full buying committee never blurs into one anonymous view.

Build the page in Claude — or in Codex, OpenAI's coding agent; the deploy is the same. One command, and you send a link that talks back. Free while in beta. The link goes out, the reaction comes back, and that is the whole idea.