Why Roomi
Pitch the product, not the deck
Why this exists, what it does, and what it doesn’t.
With AI, a working demo takes an afternoon: the phone app, the dashboard, the screen your customer would really use, built on mock data before the meeting is even booked.
Showing it is still stuck in the last decade. Screenshots in a deck, a recording, a shared password, a screen share where you drive and they watch. The thing you built rarely reaches the person you built it for.
Roomi sends a demo the way you would send a document: a link per person, the story beside it, and their own copy to click through. Then you see what landed — who opened it, where they spent their time, and what they said back.
Here’s to the demo doing the talking,
— Kaz
Properties
What you get.
Deploy from Claude
Say “deploy it to roomi” in Claude Code, or ask Claude in chat once the connector is added. It checks the build, rehearses the deploy, and publishes only when you say yes.
Real software, with a guided tour
Viewers click through your live demo, not a recording, and the tour you write walks them through it step by step. A multi-app build runs in its own container; on the paid plans, each viewer link gets a fresh copy.
Feedback pinned where it happened
A viewer’s comment arrives on the screen they were looking at, with a screenshot of it, and you can reply in the same thread.
Limitations
What it doesn’t do. Better you hear it from us.
Free is small, on purpose
A Free room holds 5 viewers at once and shows totals. A private link per viewer, and what each of them did, come with the paid plans.
Mock data only
Demos run on mock data, never connected to real systems or anyone’s real records. Every room says so to its viewers.
Web demos only
A demo runs in the viewer’s browser: one app, or several over one mock API, each framed as the device it is for. Something that only runs once installed cannot be shown.
Benefits
What it’s for. The full picture comes with the paid plans; on Free you see the totals.
See who looked at what
Which apps and screens each viewer opened, for how long, and where they stopped. The part that didn’t land is the most useful thing to know.
Hear what they said
Their comments, their answer to the next step you offered, and your replies, kept with the viewer who wrote them.
Know who it was passed on to
When a link is opened somewhere new, the pipeline shows it, so a pitch that was forwarded doesn’t go unseen.