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 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

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.

How a product team tests a prototype today, compared with Roomi
SharingA design file or a booked sessionRoomi
What they getA clickable picture of the ideaThe working prototype, with a tour through the flow you are testing
Who puts it liveA ticket to engineering, and a waitYou, by saying “deploy it to roomi” in the chat you built it in
What you know after sendingWhoever turned up to the sessionWho opened their link, who came back, and who never did
What held their attentionWhat you noticed while watchingMinutes on each screen, for each tester
Their questionsNotes from the callComments pinned to the screen, with a screenshot
The next roundA new file and a new invitationRedeploy, and it is still one project
What it costs to startEngineering time for every roundFree 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
fieldnotes.getroomi.app

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

Minutes in the prototype, by day
Day 10
Day 234
Day 361
Day 452
Day 540
Day 618
Day 79
Day 86
Day 922
Day 1048
Day 1157
Day 1244
Day 1330
Day 1426

From invited to feedback

  1. Invited24
  2. Opened21
  3. Finished the tour15
  4. Left feedback12

After a round

What to look at first, in order

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

  1. Look first

    Screens where people stopped

    A long stop on a simple screen marks where the flow is unclear.

  2. Look first

    Comments pinned to a screen

    Each one says what was wrong, on the screen where it went wrong.

  3. Then

    Testers who came back on their own

    A second visit nobody asked for is a sign the idea is useful.

  4. Then

    Who to interview next

    The testers who did the most have the most to tell you.

  5. 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.

  1. Monday, 10:00

    Built with Claude

    The designer turns Thursday’s sketch into a working prototype on mock data.

  2. 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.

  3. Monday afternoon

    Twenty-four testers, twenty-four links

    Surveyors, site leads and office staff each get their own.

  4. Wednesday

    The map step shows up

    Attention drops at the map for half the testers, and three pin the same question about signal.

  5. 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.

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 sales
  • Tech agencies

    Win the pitch with the build. Put the client’s idea live before the meeting and see which stakeholders used it.

    For agencies
  • Founders

    Show the product to customers, design partners and early users, and find out who actually wants it.

    For founders
  • Organisations

    Internal prototypes and sales pitches, without a ticket to IT, with the controls a large organisation expects by arrangement.

    For organisations
  • Consultants

    Send the client the working model instead of the final deck, and see who read the recommendation before the steering meeting.

    For consultants
  • Product teams

    Show the next release to stakeholders and customers before it ships, and see who tried it and what they asked.

    For product teams

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.