Product

Know what happens after you share. Live without an engineer.

Roomi does two things nothing else does together: it puts what you built with Claude live in a sentence, with no technical person to deploy it, and it tells you everything that happens after you send it. Each is shown working below, drawn from the product’s own screens and words. Where something is still coming, it says so.

After you share

See who looked, what held them, and who they told

A deck tells you, at best, that it was opened. Every room tells you who came, how far they got, what they asked, who they brought in and whether they want to talk.

What you learn

Who looked, what held them, and who they told

Claude deploys it and hands you the link. From then on every visit comes back to you: who opened it and who came back, how far through the tour they got, which screen they stayed on, what they said, and who they passed it on to. Viewer by viewer on the paid plans, which are coming soon; Free shows total views.

  • Each visit in order, viewer by viewer
  • A link passed on shows up as a named person
  • An alert when someone opens a link: coming soon
The app’s Activity tab: three viewers who opened their links, Priya Shah’s return visit as she finishes the tour, comments, says yes and has passed the link to a colleague; then Analytics, its totals counting up, the tour, and her comment with its screenshot.

Deploying is one sentence to Claude with the Roomi connector, in Claude Desktop or claude.ai. Or from your terminal: pitch deploy rehearses and pitch deploy --commit publishes, and pitch dev shows the real room around your local build.

Links · paid plans

Every viewer their own link

Make a link for each person, in the app, with pitch link or from Claude. If it is passed on, whoever opens it next is asked who they are, so you see the whole buying group. On the paid plans, which are coming soon.

  • An expiry on each link; revoke one without touching the rest
  • A forwarded link becomes a named viewer under the same link
  • Shown once, with no copy kept to show again
The app’s Links tab: a link made for Priya Shah and shown once; then the room asking a second browser “Are you Priya Shah?”.

Feedback

Comments pinned where they happened

A viewer clicks the part of the demo they mean and says what they think. The room takes a picture of the screen with their pin on it, which they can take off before sending. You see it with the app and the page, reply from the app, and they read your answer in the room.

  • A screenshot of the screen, pin and all
  • Pinned to the app, the page and the place on the stage
  • Replies they read in the room, under Replies
A comment pinned on Columbus’s score screen and sent with a screenshot of the screen, then the comment in the app with its screenshot and a reply being written.

Next steps · paid plans

Every visit ends with a next step

“What happens next?” is one click away in every room: book a meeting, yes, later, a question, or not for me. You choose which the room offers, and the answer is on the viewer’s visit the moment they give it. On the paid plans, which are coming soon.

  • You choose which answers the room offers
  • Their answer arrives with everything else they did
  • A follow-up drafted from what they did: coming soon
In the room, Priya Shah answers “Yes — send the proposal”; in the app, her visit shows the answer beside the rest of what she did.

Live in a sentence

From the chat you built it in to a room you can send

No engineer, no hosting, no domain, no deck. Claude checks it, rehearses the deploy and publishes it when you say yes: the real, working thing, in a room of its own.

Deploy

One sentence, and it’s live

Say “deploy it to roomi” in the chat you built it in. Claude checks the build, rehearses the deploy, shows you what would go live and publishes only when you say yes. There is no hosting, domain, sign-in or analytics for you to set up, and nobody technical to wait for.

  • From Claude Desktop, claude.ai or Claude Code
  • Rehearsed first; nothing goes live until you say yes
  • A static build from the chat; an app with a server in its own container
A recording of Roomi at work: in a chat, Claude deploys the Columbus demo with the Roomi connector and makes Priya Shah her own link; Priya takes the tour, pins a comment with a screenshot and says yes; then the publisher sees what happened: everyone opened it, Priya came back, finished the tour, said yes and passed it to a colleague.

Columbus, Northgate Studio and everyone viewing it are invented, and so is everything they do here.

The room

The demo, with you walking them through it

Your demo runs live on a stage, in its device frame, beside your notes. Give it a story and the room offers a guided tour: each step opens the right screen and rings what to look at.

  • Phone, tablet, laptop or big-screen frames
  • Tour steps can open a page, change the frame and drive the demo
  • Every room says the demo runs on mock data
The room: the Columbus demo on a laptop stage, the tour offered, then its first two steps with what to look at ringed.

Community · Free

Free, and public when you choose

On Free a project is a draft only you can open, with Preview as viewer. List it on the community and it is public at one address, once Roomi has reviewed the card you wrote for it.

  • The card strangers see is yours to write, apart from your pitch
  • Up to five viewers at once, with total views
  • Suggested neutral wording for the card: coming soon
The project’s community listing: its card written, sent for review, then approved and listed with its card shown.

Branding · paid plans

Your room, in your brand

Your name, your accent colour and your logo on every room, in place of the “Made with Roomi” mark a Free room carries. On the paid plans, which are coming soon.

  • One brand for every project in the workspace
  • Set once in Settings; every room wears it
  • Your own domain: coming soon
A Free room with the Made with Roomi mark; the brand set in Settings; then the same room in the publisher’s colour and name.

Security and control

Private by design, from the first link

  • Private by default

    Nothing is public until you list it and it is approved. Until then a room opens for you, or through a private link you issued.

  • Isolated demos

    Every demo runs in its own container, never next to anyone else’s.

  • Your data stays yours

    What viewers do in your room is visible to you and nobody else.

  • Mock data only

    Demos run on mock data by design. Every room says so.

Your next deal is in someone’s inbox right now.

Start free. One sentence in Claude, from what you built to a room you can send, and every signal that comes back.