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

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

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.

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

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, which is coming soon.