For organisations
Prototypes and pitches, with the controls your organisation expects.
Innovation teams prototype with Claude and show the work to a business unit in a sentence. Sales teams send every stakeholder their own room. Everyone sees what happened afterwards, and the enterprise controls come with the Enterprise plan, by arrangement.
The job
Turn prototypes into decisions
An innovation or sales team in a large organisation has to show its work to the people who decide. It has to do it in a way the organisation can answer for. The outcome is a decision made on evidence. With Roomi, the work is live in a sentence, and you see who engaged.
Ideas past the queue
A prototype in front of the business unit the week it is built.
Decisions on evidence
Who used it, what they asked and who said yes, before the committee meets.
A record of who saw what
Every visit against the viewer’s own link, for the people accountable for it.
One way to show work
Every team’s demos in one place, instead of hosted however each one chose.
The problem
Good ideas stall between the demo and the decision
The hackathon winner needs a hosting request, a security review and a quarter.
Ideas die in the queue between demo day and a decisionWe sent the prototype to the steering committee. Did anyone open it?
Budget decided by whoever spoke loudest in the meetingInfoSec will want to know where it is hosted before anyone outside sees it.
Every new tool starts with a questionnaireOur sales engineers each host demos their own way.
Nobody can say what was shown to whom
How Roomi helps
Fast for the people building. Answerable for the people responsible.
Speed to deploy for innovation, product and sales teams, and a record of who saw what for everyone accountable for it.
Live without a ticket to IT
A prototype built with Claude goes live when someone says “deploy it to roomi”. It runs on mock data in its own isolated container, apart from your production systems.
A link per stakeholder
Each member of a steering committee or buying group gets their own link, revocable at any time.
Evidence for the decision
Who opened it, how long they spent, what they asked, and their answer to “What happens next?”.
Private by default
Nothing is public unless someone lists it and it is approved. A room opens only for its publisher, or through a link they issued.
Today, and with Roomi
How organisations share a prototype today, and with Roomi
Today an internal prototype waits on a hosting request, then reaches the committee as slides or a demo in a meeting. You know who was in the room. A room gives each stakeholder the working prototype on their own link, apart from your systems, and records who engaged.
| Sharing | A hosting request and a slide | Roomi |
|---|---|---|
| What they get | Slides, or a demo in a meeting | The working prototype, on mock data, on their own link |
| Who puts it live | A ticket to IT, a review and a queue | The team that built it, by saying “deploy it to roomi” |
| What you know after sending | Whoever was in the meeting | Who opened it, across every function, and who came back |
| What held their attention | Rarely known | Minutes on each screen, for each stakeholder |
| Who else saw it | Rarely known | Every function it reached, by name |
| What they want next | Whoever spoke loudest | Their answer to “What happens next?”, such as “Bring in a colleague” |
| A record of who saw what | Scattered across inboxes | Every visit, against the viewer’s own link |
| A viewer’s data, on request | Found by hand, if at all | Exported or erased from the viewer’s record |
| What it costs to start | An internal build, or a new vendor review | Free to try. Enterprise by arrangement, invoiced. |
Speed to deploy
From demo day to the business unit in a sentence
Innovation teams, product teams and internal hackathons build with Claude and say one sentence to put the result live. The business unit opens a working prototype, not a slide about one.
- Mock data by design, and every room says so
- Each demo in its own isolated container, or a static build
- Claude rehearses the deploy and publishes only when you say yes
- Run it all by asking Claude: deploys, links and who looked
Tour · 2 of 5This is the claims triage queue, sorted by what the model flagged. Mock data throughout.
After you share it
See who engaged, across every function
Claims, Risk, Finance and IT each open their own link, and you see what each of them did.
Claims Assist · steering committee
Last 30 days- Shared with
- 12
- people
- Opened
- 11
- 92%
- Time inside
- 18m
- average
- Said yes
- 5
- so far
Minutes in the room, by day
| Day 1 | 0 |
|---|---|
| Day 2 | 14 |
| Day 3 | 30 |
| Day 4 | 26 |
| Day 5 | 18 |
| Day 6 | 4 |
| Day 7 | 2 |
| Day 8 | 22 |
| Day 9 | 41 |
| Day 10 | 37 |
| Day 11 | 29 |
| Day 12 | 8 |
| Day 13 | 5 |
| Day 14 | 33 |
From sent to yes
Helen Marsh · Head of Claims Operations
Said yes- Opened her link
- 10 minutes in Triage queue · the longest stop
- Pinned a question on Triage queue
Can this route by policy type as well as severity?
- Forwarded it to Raj Patel, Risk
- Raj said who he was and opened Audit view
- Helen chose “Bring in a colleague”
Where attention went
This weekClaims lives in the triage queue; Audit view lights up once Risk joins on Tuesday.
Who to brief next
This week- Helen · Claims Operations3 visits · said yesSaid yes
- Raj · Riskforwarded · 16 min in Audit viewEngaged
- Amira · Financewhole tour · 1 questionEngaged
- Owen · ITopened once · 5 minOpened
Raj spent most of his visit in Audit view. Bring the governance answer to the committee.
Steering committee · Claims Assist
Moves on what they didSent1
- Grace · Legal
Opened3
- Owen · IT
- + 2 more
Engaged3
- Raj · Risk
- Amira · Finance
- + 1 more
Said yes5
- Helen · Claims
- + 4 more
Who to brief next
The signals before a decision, strongest first
What a room records across a committee, ranked by how much it moves the decision.
- Brief today
They chose “Bring in a colleague”
Someone wants it seen more widely. Find out who, and send them their own link.
- Brief today
A new function joined
Risk, Finance or IT opened a forwarded link and said who they are. Their questions are coming.
- This week
One area held their visit
It tells you what that function cares about. Lead their briefing with it.
- This week
They asked a question in the room
Answer it in writing, where everyone who reads it later can see it.
- Before the meeting
They have not opened it
Better known now than in the meeting. Send a nudge, or brief them in person.
Objections, answered
What your review will ask, in plain words
- InfoSec will want a review.
- Send us your questionnaire and we will answer it in writing, including where the answer is no.
- Internal data cannot go into a third-party tool.
- It does not need to. Every demo runs on mock data, in its own container or as a static build, never beside anyone else’s.
- We need single sign-on.
- It is part of the Enterprise plan, by arrangement. Tell us your identity provider and we will tell you what we can support.
- A viewer may ask for their data.
- You can export what a viewer did, or erase it, from their record. The project’s history keeps a note that it was erased, naming nobody.
Security, procurement and governance
The questions your review will ask, answered plainly
What every plan does today, and what the Enterprise plan adds by arrangement. If something you need is not here, talk to us.
Security review
Built to the standard an InfoSec review expects. Send us your questionnaire and we will answer it in writing, including where the answer is no.
Isolated demos
Every demo runs on mock data, in its own container or as a static build: never inside the platform, and never beside anyone else’s.
Private links
Each viewer has their own link, revocable at any time. Nothing is public unless it is listed and approved.
Who saw what
On paid plans every visit is recorded against the viewer’s own link. A fuller audit history is part of the Enterprise plan, by arrangement.
Single sign-on
On the Enterprise plan, by arrangement. Tell us your identity provider and we will tell you what we can support.
Data residency
Part of the Enterprise conversation. Tell us where your records must be held and we will say plainly whether we can meet it.
CRM integration
By arrangement on the Enterprise plan. Talk to us about the system your sales team works in.
Procurement
Enterprise is for more than five people: invoiced rather than paid by card, with limits set to fit your team.
An example
From internal hackathon to an approved pilot
The people and the organisation are invented. The steps are what the product does.
- Hackathon, day 2
Built with Claude
The claims team builds a triage prototype on mock data in an afternoon.
- Day 2, 16:00
Live in a sentence
Someone says “deploy it to roomi”. No hosting request: it is live in a room, with a tour.
- Day 3
Twelve links
The steering committee, across Claims, Risk, Finance and IT, each gets their own.
- Week 2
Risk joins by name
Helen forwards it. Raj says who he is and spends his visit in Audit view.
- Week 3
A decision on evidence
The committee meets knowing who used it, what they asked and who said yes. The pilot goes ahead.
Questions from organisations
- How can a large organisation share an internal prototype safely?
- Build it on mock data with Claude and say “deploy it to roomi”. It runs in its own isolated container or as a static build, apart from your production systems. Each stakeholder gets their own private link, revocable at any time, and every visit is recorded against it. As you send it, tell them the room records their visit.
- Who can open a demo?
- Only the people you send a link to, and whoever they forward it to, who is asked who they are first. Nothing is public unless someone lists it and it is approved.
- What does the Enterprise plan add?
- Enterprise is by arrangement: as many people as you need, limits set to fit and invoiced billing. Single sign-on, data residency, a fuller audit history and CRM integration are part of that conversation.
Read more
Guides that go further into the same question.
- Is it safe to send a client a link to an app you built with AI? A checklist: Eleven checks before an app built with Claude, Lovable or Bolt goes to a client: data, keys, backends, links, and what to tell them.
- How do you host an app you built with Claude Code?: Claude Code builds the app on your machine. Where to host it for free, what each host allows, and how to send it to a client on a private link instead.
- How can you tell if a client has actually looked at your proposal?: Read receipts are unreliable. How tracked links work, what they can and cannot tell you, and how to see which parts a client spent time on.
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 agenciesPrototyping
Get a prototype in front of testers the day you build it, and see which screens they used and what they said, pinned to the screen.
For prototypingFounders
Show the product to customers, design partners and early users, and find out who actually wants it.
For foundersConsultants
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