About

We’ve built together since 2017.

We’ve raised VC money, ran two startups that failed and then a Venture Studio where clients exited and raised Series A and more. Building and selling tech externally and internally is all we’ve known… and it’s often been a painful process – that’s why we built Roomi.

Kaz, Co-founder and CTO of Roomi
KazCo-founder & CTOKaz on LinkedIn
Tesh, Co-founder and CEO of Roomi
TeshCo-founder & CEOTesh on LinkedIn

Our mission

Selling and showcasing tech should be as impressive as the tech itself and for a fair price

Pricing

Why our prices are low

Pro is £4 a month and Team is £5 a seat a month. Here’s why.

  • No investors and no money raised

    So we are not obliged to chase a “unicorn” return that trades on our customers’ loyalty.

  • 100% Ours

    Roomi is owned 50/50 by Tesh and Kaz meaning we can focus on customer success and product development with no outside voices distracting us from the mission.

  • Fair price for fair work

    In our careers in tech, we believe most people overcharge, and that’s not fair.

  • All tech should be showcased to its fullest

    A number of great ideas don’t get traction because of how they are shown. We want to change that.

See pricing

Our story

We kept building things nobody could see.

For a long time, the hardest part of showing someone a thing we had made was not the making. It was getting it in front of them.

A working prototype is the most persuasive thing you can put in front of a person. It answers questions a description can’t. But a prototype on your own laptop persuades nobody but you, and every way we found of getting it off the laptop cost us something.

Everything we tried

We sent staging links, and they broke on the morning someone finally opened them, because somebody had deployed over the top. We recorded our screens, and the recordings were out of date by the next change, and nobody could click anything in them. We pasted screenshots into decks, which turned a working thing back into a drawing of one.

When none of that would do, we asked an engineer to put the demo somewhere. Then we waited, because they had real work to do, and a demo for someone outside the team was never anyone’s priority. When it did go up, it went up behind a password we sent in the same message as the link, and could never take back.

And then, nothing

The worst part came after we pressed send. We didn’t know whether it had been opened. We didn’t know by whom, or whether they got past the first screen, or which part made them lean in and which part lost them. If they passed it to a colleague, we never learned who that was. We found out how it had gone weeks later, in passing, or we never found out at all.

We were deciding what to build next on the strength of silence.

The building had become fast. The showing, and the hearing back, had not.

What changed

Then building got quick. With Claude, someone who isn’t an engineer can make a working prototype in an afternoon. That made the old problem worse, not better: far more things worth showing, and the same slow, blind way of showing them. The step after building had become the slowest one, and the one we knew least about.

Why we built Roomi

So we built the thing we kept wishing we had. You say one sentence to Claude, “deploy it to roomi”, and the demo you just made is live in a room: hosted, private, with a guided tour. Each person you send it to gets their own link, and you can expire or revoke any one of them on its own. Nobody technical has to put it anywhere.

Then you can see what happened. Who opened it, and the route each of them took through it. Where their attention went. The questions they asked, pinned to the screen they were on, with a picture of that screen. Who they passed it to, because a forwarded link asks the next person who they are. What they said when the room asked what happens next. Each person’s evidence sits beside their name, the pipeline moves on its own, and you can ask Claude about any of it.

The demos run on mock data, each in its own isolated container or as a static build, on a domain kept apart from ours. The people looking at them are real, though, and so is everything they tell you, and we treat it that way.

Build or buy

Could you build this yourself?

You could. Here is roughly what it takes, piece by piece, and what it adds up to over a first year.

See what it takes

Show it, then hear back.

Start free. One sentence in Claude takes the demo you built to a room you can send, and tells you what happened after.