For product teams and designers
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.
The job
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.
The problem
Feedback that arrives late, and vague
Getting a prototype hosted means a ticket and a wait.
The test happens a sprint after the ideaPeople say it looks great on the call, then never open it again.
Polite feedback, and no evidenceThe feedback was “the second screen is confusing”. Which second screen?
Hours spent working out what they meantA design file shows how it looks, not whether it works.
You learn about the hard parts after the build
How Roomi helps
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.
Today, and with Roomi
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. |
Speed to deploy
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
Tour · 3 of 6Try logging a site visit without the map. Tell us where you got stuck.
After you share it
See how the prototype was used, screen by screen
Every tester’s visit, every screen and every comment, in one place.
Field Notes · round 2
This round- Testers
- 24
- people
- Opened
- 21
- 88%
- Time inside
- 14m
- average
- Comments
- 37
- pinned
Minutes in the prototype, by day
| Day 1 | 0 |
|---|---|
| Day 2 | 34 |
| Day 3 | 61 |
| Day 4 | 52 |
| Day 5 | 40 |
| Day 6 | 18 |
| Day 7 | 9 |
| Day 8 | 6 |
| Day 9 | 22 |
| Day 10 | 48 |
| Day 11 | 57 |
| Day 12 | 44 |
| Day 13 | 30 |
| Day 14 | 26 |
From invited to feedback
Kemi Adeyemi · site surveyor
Came back- Opened her link
- 6 minutes in Visit log · the longest stop
- Left at the map step · after 40 seconds
- Pinned a comment on Map
I never have signal on site. Can it save offline?
- Came back for the second round
Where attention went
Round 2Photos holds people longest; the map loses them from the first day.
Who to interview next
Round 2- Kemi · site surveyor2 visits · 4 comments on Map4 comments
- Callum · site leadwhole tour · 3 comments3 comments
- Aisha · office managerwhole tour · 1 comment1 comment
- Rob · surveyoropened once · 2 minOpened
Kemi left four comments on the map step. Ask her for twenty minutes.
Testers · round 2
Moves on what they didSent3
- Rob · surveyor
- + 2 more
Opened6
- Lena · surveyor
- + 5 more
Engaged9
- Kemi · surveyor
- Callum · site lead
- + 7 more
Said yes6
- Aisha · office
- + 5 more
After a round
What to look at first, in order
What a room records about a prototype, ranked by what it teaches you.
- Look first
Screens where people stopped
A long stop on a simple screen marks where the flow is unclear.
- Look first
Comments pinned to a screen
Each one says what was wrong, on the screen where it went wrong.
- Then
Testers who came back on their own
A second visit nobody asked for is a sign the idea is useful.
- Then
Who to interview next
The testers who did the most have the most to tell you.
- Last
Who never opened it
Swap them out for the next round, or send them a nudge.
Objections, answered
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.
An example
One round of testing
The people and the prototype are invented. The steps are what the product does.
- Monday, 10:00
Built with Claude
The designer turns Thursday’s sketch into a working prototype on mock data.
- Monday, 11:30
Live, with a tour
One sentence, “deploy it to roomi”, and it is hosted and private, with a tour through the flow under test.
- Monday afternoon
Twenty-four testers, twenty-four links
Surveyors, site leads and office staff each get their own.
- Wednesday
The map step shows up
Attention drops at the map for half the testers, and three pin the same question about signal.
- Thursday
Round two
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?: 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?: 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?: 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.
More use cases
See how other teams use it
Tech sales
Send every prospect a working demo with their own link, see who leaned in and who it was forwarded to, and call the right person first.
For tech salesTech agencies
Win the pitch with the build. Put the client’s idea live before the meeting and see which stakeholders used it.
For agenciesFounders
Show the product to customers, design partners and early users, and find out who actually wants it.
For foundersOrganisations
Internal prototypes and sales pitches, without a ticket to IT, with the controls a large organisation expects by arrangement.
For organisationsConsultants
Send the client the working model instead of the final deck, and see who read the recommendation before the steering meeting.
For consultantsProduct teams
Show the next release to stakeholders and customers before it ships, and see who tried it and what they asked.
For product teams