# How do you share a prototype you built with Claude with a client?

- URL: https://getroomi.com/guides/how-to-share-a-claude-prototype-with-a-client
- Updated: 2026-10-12

Add the Roomi connector to Claude, then say “deploy it to roomi” in the chat where you built the prototype. Claude checks it, shows you a rehearsal, and publishes only when you say yes. On Pro, ask Claude for a private link for your client. They open it with no account, and you see what they did.

This guide takes you through it step by step. It covers what you need, the connector, the deploy and the link, then what you see and how to change it. If you have not built anything yet, the [quickstart](https://getroomi.com/docs/quickstart) starts from an empty chat.

## Ways to share a Claude prototype

There are four. Each one puts something different in front of the client, and tells you something different afterwards.

| Way | What your client gets | Needs a Claude account | What you learn afterwards |
|---|---|---|---|
| Share the artifact from Claude’s apps | The working prototype, once they sign in | Yes | What they tell you |
| A public link from Claude Code | The page, if you built it in Claude Code, for anyone with the link | No | What they tell you |
| Screen share or recording | A view of it, with you driving | No | What they say on the call |
| A Roomi room | The working prototype on their own link, with a guided tour | No | Who opened it, how far they got, what held them and what they said |

Anyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. In Claude’s apps, an artifact shared with “Anyone with the link” opens for anyone signed in to Claude who has the link, not for anyone at all. One that connects to your apps or uses Claude cannot be shared that way. That suits a colleague who already uses Claude. A client who does not has to make an account before they see any of your work. [Making a Claude artifact private](https://getroomi.com/guides/how-to-make-a-claude-artifact-private) covers Claude’s own settings in full, and [five ways to share an artifact](https://getroomi.com/guides/tools-to-share-a-claude-artifact-with-a-client) compares the routes.

Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. Claude Code’s artifacts page describes no record of who opened an artifact, no expiry date and no guided tour. For anyone outside your organisation, it describes a public link, not one for a named person. On Pro, a room gives each client a link in their name, which can expire or be revoked. It adds a guided tour, comments and next steps, and shows who opened it, for how long and who they passed it to.

## What do you need before you start?

You need three things. A Roomi account, which you make by signing in with GitHub or Google. Claude, on any plan that allows a custom connector. And a prototype that runs on mock data. For a private link per client, you also need Pro, at £4 a month before VAT.

- **A Roomi account.** Sign in at app.getroomi.com, and a Free workspace is made on the spot.
- **Claude, on any plan with room for a custom connector.** The first step below says what each plan allows.
- **A prototype on mock data.** Invented names, figures and records only. Every viewer gets a working copy, so nothing in it may be real.
- **Pro, for private links.** On Free, a project is a draft only you can open, or a public listing on the [community](https://getroomi.com/community).

## How do you add Roomi to Claude?

Add Roomi as a custom connector in Claude, paste its address, and sign in when Claude sends you to Roomi. You check what Claude is asking to do, and choose Allow. Nothing is installed on your machine, and it works the same on claude.ai and in the Claude app.

1. In Claude, add a custom connector. Custom connectors are on every Claude plan, and Free allows one. On Pro and Max you open `Customize`, then Connectors, and choose “+ Add”, then “Add custom connector”. On Team and Enterprise, an owner adds it for everyone first. You turn a connector on for a chat from the “+” button, then Connectors.
2. Name it **Roomi**, and paste the address. It is also in the Roomi app, under Settings, **Connect Claude**.

   ```text
   https://mcp.getroomi.com/mcp
   ```

3. Finish adding it. Claude sends you to Roomi: sign in, read what it asks to do, and choose **Allow**.
4. In the chat where you built the prototype, check the connector is turned on for that chat.

What you allow is listed on that page before you choose:

| Permission | What it lets Claude do |
|---|---|
| `pitch:read` | See your projects, builds, viewer links, visits and feedback |
| `pitch:write` | Deploy demos, make and revoke viewer links, and add pages to rooms |
| `offline_access` | Stay connected until you disconnect it |

## How do you deploy it?

Say “deploy it to roomi” in the chat. Claude reads Roomi’s guide, writes your prototype out as the files a browser runs, drafts a short tour and checks the lot. Then it rehearses and shows you exactly what would go live. Nothing is published until you read that and say yes.

1. Say “deploy it to roomi”, or be more particular: “Deploy this to Roomi as a new project called corner-demo, with a tour.”
2. Claude drafts a tour of three to six steps, one idea each, and shows it to you. Change any step you like.
3. Claude checks the files exactly as the deploy will, and fixes whatever the check names.
4. Claude rehearses the deploy and shows you the result: the project, the files, the apps and the tour. Nothing has been sent.
5. Say yes. Claude publishes it, and the room is live.

A chat carries a demo of at most 200 files and 3 MB that runs in the browser alone. If yours is bigger, or has a server of its own, Claude says so and offers the command line instead. [Deploying from Claude](https://getroomi.com/docs/claude) has every check and its fix, and [writing the tour](https://getroomi.com/docs/story) has the rules for a good one.

## How do you send it to your client?

Ask Claude to make a link for your client, named for them, with an expiry if you want one. Claude gives you the address in its reply. Copy it and send it yourself, by email or however you usually reach them: Roomi sends nothing. When they open it, the room greets them by name.

1. Ask: “Make a viewer link for Priya Shah, expiring in two weeks.”
2. Claude makes it and gives you the address in that reply. If it is lost later, ask Claude to show it again.
3. Send it to Priya with one line on what to try first.

Say in your message that the room shows you what they look at: Roomi’s [terms](https://getroomi.com/terms) ask you to tell each viewer that it logs what they do there.

If Priya forwards it, whoever opens it next is asked “Are you Priya Shah?”. Someone who says no gives their name, and appears under Priya’s link as forwarded, so you see everyone involved. You can switch one link off without touching the others. [Sharing a private link](https://getroomi.com/docs/sharing) covers every option.

## What will you see?

On Pro and up, you see everything each person did. When they opened their link, and the time they spent on each screen and page. How far through the tour they got, their comments and their next step. Roomi also tells you who to call first. On Free, you see total views.

| What happened | Where you see it |
|---|---|
| They opened it | An email, if you choose, and the link’s journey |
| They came back | A notice in the app, and the link’s journey |
| Where their time went | Their journey, screen by screen and page by page |
| How far through the tour they got | Their journey: “Took the tour to step 3 of 5” |
| A comment pinned to a screen | The Feedback tab, with a picture of what they saw |
| Their answer to “What happens next?” | Their pipeline card, which moves on by itself |
| Who is most worth a call today | Who to call first, on the project’s Overview |

You can ask Claude the same questions in the chat, such as “Who opened the corner demo this week?”

When a client comes back to the pricing screen with a colleague, that is the day to call. [How to follow up after a demo](https://getroomi.com/guides/how-to-follow-up-after-a-demo) says what to send for each thing a viewer did.

## How do you change it after sending?

Deploy again from the same chat. The new build goes live, and everyone opening a link gets it on their next page load. Nobody’s link changes, so you never have to send a new one. If you want to check a change before your client sees it, send it as a preview first.

- **Change it.** Ask Claude for the change, then say “deploy it to roomi” again. It rehearses and asks you again.
- **Check it first.** Ask Claude to send it as a preview. Only you and your team see it until you make it live.
- **Undo it.** On the project’s **Builds** tab, choose the earlier build and **Roll back to this**.

Every room tells its viewers the demo runs on mock data, and each demo runs apart from your account. [Prototyping](https://getroomi.com/use-cases/prototyping) shows how teams use this to test an idea with a client before anyone builds it properly.

## Questions people ask

### Do I need to know how to code?

No, not for a prototype you built in a chat. Claude writes the files, drafts the tour, checks everything and rehearses the deploy. Your part is to read what it would publish and say yes.

### Does my client need a Claude account?

No. They open their own link in a browser and the room opens. They need no Claude account and no Roomi account, and there is nothing for them to install.

### Can my prototype use real data?

No. Every demo runs on mock data, and every room tells its viewers so. The deploy stops if it finds something that looks like a live key, so a real system is never in reach.

### What if it is bigger than a chat can carry?

Then it goes through the Roomi command line on your own machine, which takes a much larger build and apps with their own server. In Claude Code, the Roomi plugin runs it for you when you say “deploy it to roomi”.

### Can my client comment on it?

Yes. They pin a comment to the exact spot on the screen, and you get it with a picture of what they were looking at. You reply in the app, and they read your reply in the room.

### Can they book a call from it?

Yes, on Pro and up. Book a meeting either books a time in the room from the weekly hours you set, or opens your own booking page, such as Cal.com or Calendly.

## Sources

- Anthropic: [support.claude.com/en/articles/9547008-publishing-and-sharing-artifacts](https://support.claude.com/en/articles/9547008-publishing-and-sharing-artifacts), checked 12 October 2026

- Anthropic: [code.claude.com/docs/en/artifacts](https://code.claude.com/docs/en/artifacts), checked 12 October 2026

- Anthropic: [support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), checked 12 October 2026

## About the author

**[Kaz Kato](https://getroomi.com/about)**, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit.

## Related guides

- [How can you share a Claude artifact with a client who doesn’t use Claude?](https://getroomi.com/guides/tools-to-share-a-claude-artifact-with-a-client)

- [How do you make a Claude artifact private, and send it to one client?](https://getroomi.com/guides/how-to-make-a-claude-artifact-private)

- [How do you follow up after a demo, using what they looked at?](https://getroomi.com/guides/how-to-follow-up-after-a-demo)

- [Can Claude run Roomi for you? Everything you can do without opening the app](https://getroomi.com/guides/can-claude-run-it-for-you)