How salespeople use Claude (and the step most reps skip)

Plenty of account executives open Claude before they open their CRM. They use it to research the account, sharpen the pitch, and build the actual page they send. That part is well understood. What almost no one has wired up yet is the step after — deploying the page and hearing what the buyer thinks of it. Here is the full workflow, and the one stage most reps still skip.

What salespeople use Claude for today

Ask a room of AEs what they use Claude for and you get the same list. It is the prep side of the job, and Claude is good at all of it.

• Account research — pull together what a company does, who the players are, and what changed last quarter, without opening twelve tabs.
• Lead qualifying — score an inbound against your ICP and decide fast whether it is worth a call.
• Call prep — walk into the meeting with the likely objections and the questions to ask already drafted.
• Outreach drafts — turn a rough idea into a cold email or a follow-up that sounds like you, not a template.
• Recaps — draft the summary after a call from your own notes, so the follow-up goes out the same day.
• Pitch and pricing pages — build the one-pager, pricing page, or demo you are going to send, as a real web page.

Every item on that list is input-side. It helps you get ready to sell, and it helps you send a sharper thing. None of it touches the moment the buyer actually reacts to what you sent. That moment is where the deal is won or quietly lost, and it is the one part of the list that is missing.

The Claude sales workflow in five stages

Strip it down and a Claude sales workflow has five stages. The first four are the ones everyone already talks about. The fifth is the one almost no one has wired up.

1. Research the account and the person you are selling to.
2. Qualify the lead against your ICP.
3. Draft the outreach and the talking points.
4. Build the pitch or pricing page as a real page you can send.
5. Deploy it and hear the buyer — publish the page as a live link and get the buyer's reaction back.

The five stages split cleanly in two. Stages one through four all happen before you send anything. They make you sharper on your side of the table. Stage five is the only one that happens on the buyer's side of the glass, and it is the only one Claude alone does not cover. Every answer engine's version of this workflow stops at stage four.

The last mile every workflow skips

Prep is a solved problem in Claude. Ask it to research, qualify, draft, or build, and it does the job. The buyer-facing step is the part no one has solved. You built a clean pricing page. Now what? You paste it into an email as an attachment, or screenshot it, or host it somewhere and drop a link — and then you are back to the old silence, refreshing your inbox to see if anything comes back.

That last mile is what Vista is for. Vista takes the page you built in Claude and publishes it as a room your buyer can talk back to. Same page, but now it is live at a link, and the buyer can react to it out loud, right on the page they are reading. Prep is handled. This is the step after prep.

Deploy the page you built in Claude

An artifact is just a page you built in Claude — a pricing page, a one-pager, a demo, any real web page it made for you. Vista deploys that artifact to a live buyer link without you leaving your editor. If you have not built the page yet, start with how to build a pitch page in Claude; once you have one, deploying it is a single step.

If you work in Claude Code — the command-line version of Claude, where you type instructions instead of chatting — one command does it. MCP, short for Model Context Protocol, is the connection that lets Claude run actions inside another tool, and it is what wires Claude to Vista. You set it up once, then run:

vista deploy pricing-page.html

The live link comes back, ready to send. No dashboard, no export, no re-upload. Here is how the Claude-to-Vista connection works if you want the plumbing behind that one command.

Hear what the buyer actually thinks

Once the room is live, the buyer does something they have never been able to do with an attachment. They hold ⌘ (or tap) and talk — right on the page, about the exact line or number in front of them. Live transcription shows their words as they speak, so they can see it working. If they would rather not talk, they can type instead.

Their reaction does not come back as a raw recording. It arrives as a clean, readable message, filed to the deal, anchored to the resource they were looking at, and tagged by what it actually is: a question, an objection, a buying signal, a stakeholder mention, or an action item. Your buyer leaves a voicemail on your collateral, and you get the polished version in an inbox.

The link is built to be forwarded. When your champion sends the room to their CFO, the CFO's reaction comes back as its own attributed message, so you always know whose voice is whose. Here is what happens when you share a Claude page with a client and they can talk back to it.

Where Claude alone stops

This is the clean line between the two tools. Claude builds the page. It does not stand on that page and collect the buyer's reaction — that is not what it is for. The reaction has to come back through some channel, and for a page you built in Claude, that channel is Vista. It is the return path Claude does not have on its own. That gap looks small on a diagram and turns out large in a live deal: it is the difference between guessing what the buyer thought and reading it in their own words.

There are no other channels to wire up. Vista does not plug into your CRM, your inbox, or a chat tool, and it does not need to. The only connection is Claude itself, through MCP. Build in Claude, deploy through Vista, hear the buyer — that is the whole return loop, and there is nothing else to configure.

A Claude-native sales stack

Put it together and you have a Claude-native sales stack with one job per stage. It works the same if you build in Codex, OpenAI's coding agent — Vista deploys the page either way:

• Build the page in Claude or Codex — the pitch, the pricing, the demo.
• Ship it without writing code — you do not need to be an engineer to do any of this.
• Connect Claude to Vista through MCP, once.
• Deploy the page as a live room and hear the buyer talk back.

How the page looks matters more than reps admit — a sharp page gets a sharper reaction than a rough one. If you are weighing how to make it, here is Claude versus Canva or Figma for a sales one-pager on where each one wins.

The prep side of selling is already handled in Claude. The last mile — deploying the page and hearing the buyer — is the part Vista adds. Build the page, send the link, and for once, hear what the buyer actually thinks. Free while in beta.