# For prototyping

- URL: https://getroomi.com/use-cases/prototyping
- Built: 2026-10-26

Put the prototype in front of people. See what they did. Turn a prototype built with Claude into a hosted, private room in one sentence, without asking engineering for an environment. Then see which screens people used, where they stalled, and what they said, pinned to the screen.

## Learn what works before it is built for real

A product team’s job in a prototype round is to learn what works before engineering builds it for real. The outcome it wants is evidence: which screens people used, where they stalled and what they said. With Roomi, the prototype is live the day you build it, and every tester’s visit comes back to you.

- **A test the day you build**: Not a sprint later, after a ticket for an environment.
- **Behaviour, not politeness**: What testers did with it, screen by screen, beside what they said on the call.
- **Feedback you can find**: Every comment on the screen it is about, with a screenshot of what they saw.
- **The next round, sooner**: Redeploy after a round and send the same people back in.

## Feedback that arrives late, and vague

- “Getting a prototype hosted means a ticket and a wait.” — The test happens a sprint after the idea.
- “People say it looks great on the call, then never open it again.” — Polite feedback, and no evidence.
- “The feedback was “the second screen is confusing”. Which second screen?” — Hours spent working out what they meant.
- “A design file shows how it looks, not whether it works.” — You learn about the hard parts after the build.

## Prototype on Monday, evidence by Friday

A working prototype is live the day you build it, and every tester’s visit comes back as behaviour, not opinion.

- **Live without engineering**: Say “deploy it to roomi” in the chat you built it in. Claude rehearses the deploy and publishes when you say yes.
- **Each tester their own link**: So you know whose feedback is whose, and who never opened it at all.
- **Comments on the screen itself**: Pinned where they meant it, with a screenshot of what they were seeing.
- **Behaviour, not opinion**: Which screens held people, where they stopped, and who came back for a second look.

## How teams test a prototype today, and with Roomi

Today a prototype reaches testers as a design file, a booked session or a build engineering had to host. You learn what you noticed while you watched. A room gives each tester the working prototype on their own link, and records every visit, click and minute, screen by screen.

| Sharing | A design file or a booked session | Roomi |
|---|---|---|
| What they get | A clickable picture of the idea | The working prototype, with a tour through the flow you are testing |
| Who puts it live | A ticket to engineering, and a wait | You, by saying “deploy it to roomi” in the chat you built it in |
| What you know after sending | Whoever turned up to the session | Who opened their link, who came back, and who never did |
| What held their attention | What you noticed while watching | Minutes on each screen, for each tester |
| Their questions | Notes from the call | Comments pinned to the screen, with a screenshot |
| The next round | A new file and a new invitation | Redeploy, and it is still one project |
| What it costs to start | Engineering time for every round | Free to start. Pro is £4 a month for a private link per person and full analytics. |

How a product team tests a prototype today, compared with Roomi.

## A working prototype, live from the chat you built it in

The prototype runs on mock data, as a static build or in its own isolated container. Claude writes the guided tour with you, so testers try the flow you meant to test.

- No environment, domain or hosting to set up
- Hosted and private by default
- Redeploy after each round; it is still one project
- Ask Claude who tried it, and what they said

## See how the prototype was used, screen by screen

Every tester’s visit, every screen and every comment, in one place.

- **The round at a glance**: Who opened it, how long they stayed and how many finished the tour.
- **Each tester’s journey**: Every visit in order, where they stalled, and what they said on the screen they said it.
- **Which screens hold attention**: Where people spend their time, and where they leave, across the whole round.
- **Who to interview next**: The testers with the most to say, so your next conversation is the useful one.
- **Who has tried it**: Every tester moves from sent to opened to engaged on their own, so you can see who still needs a nudge.

## What to look at first, in order

What a room records about a prototype, ranked by what it teaches you.

1. **Screens where people stopped** (Look first): A long stop on a simple screen marks where the flow is unclear.
2. **Comments pinned to a screen** (Look first): Each one says what was wrong, on the screen where it went wrong.
3. **Testers who came back on their own** (Then): A second visit nobody asked for is a sign the idea is useful.
4. **Who to interview next** (Then): The testers who did the most have the most to tell you.
5. **Who never opened it** (Last): Swap them out for the next round, or send them a nudge.

## What product teams ask before the first round

### It is only a prototype.

That is what a room is for. It runs on mock data, and Claude writes a tour so testers try the flow you meant to test.

### Engineering looks after hosting.

There is nothing for them to host. Each demo runs in its own space on ours, apart from your production systems.

### Testers will not install anything.

They do not have to. It opens in their browser from their own link, with no account.

### We already have research tools.

Keep them for interviews and surveys. A room adds what testers did with the working prototype, screen by screen, and who to interview next.

## One round of testing

The people and the prototype are invented. The steps are what the product does.

1. **Built with Claude** (Monday, 10:00): The designer turns Thursday’s sketch into a working prototype on mock data.
2. **Live, with a tour** (Monday, 11:30): One sentence, “deploy it to roomi”, and it is hosted and private, with a tour through the flow under test.
3. **Twenty-four testers, twenty-four links** (Monday afternoon): Surveyors, site leads and office staff each get their own.
4. **The map step shows up** (Wednesday): Attention drops at the map for half the testers, and three pin the same question about signal.
5. **Round two** (Thursday): You redeploy the fix. The testers who come back show up in the same project, and you see whether it worked.

## Questions about prototyping

### How do I share a prototype built with Claude with testers?

Say “deploy it to roomi” in the chat you built it in. Claude checks the build, rehearses the deploy and publishes it when you say yes, with a tour through the flow you are testing. Then make a private link for each tester and send it. As you send it, tell them the room records their visit.

### Can I see which screens testers used?

Yes, on Pro and above. You see each tester’s visits in order, the minutes on each screen and where they stopped. Each comment they pinned comes with a screenshot of what they saw.

### Can I run a second round on the same project?

Yes. Redeploy after each round and it is still one project. Send the next round its own links, or send the same people back in.

### What does it cost?

Free costs nothing and puts a static prototype live. Pro is £4 a month before VAT, with a private link per tester, container demos and full analytics.

## Read more

Guides that go further into the same question.

- [How do you share a prototype you built with Claude with a client?](https://getroomi.com/guides/how-to-share-a-claude-prototype-with-a-client): Say “deploy it to roomi” in the chat you built it in. Claude rehearses, you approve, and each client gets their own link. Step by step, with what you see.
- [I built a prototype with AI. How do I make it real?](https://getroomi.com/guides/i-built-a-prototype-with-ai-how-do-i-make-it-real): You built it with Claude, Lovable, Bolt or v0. Make it real for a client first, then decide whether to harden it, rebuild it or drop it.
- [Prototype vs MVP vs proof of concept: what is the difference?](https://getroomi.com/guides/prototype-vs-mvp-vs-proof-of-concept): A proof of concept shows it can work, a prototype shows what using it is like, and an MVP is used by real customers. When you need each, and how to share it.

## Test the next idea while it is still an idea

Start free with private drafts. A link per tester and full analytics come with Pro.

[Get started free](https://app.getroomi.com/start)
