ZAM

We replaced Zoom and Google Meet with our own room

It records, it transcribes, it writes the summary, and it costs nothing per month. Here is exactly how it is built, what it does badly, and where we would still pay someone else.

Video calling is one of those bills nobody argues with. You need to talk to clients, so you pay per host, every month, forever. The moment a second person needs to run their own calls, you pay twice.

What finally bothered me was not the price. It was that the recording, the transcript and the notes from a client call all lived somewhere else, in a vendor account, disconnected from the client record those calls were about.

So we built the meeting room into our own system. It runs at no ongoing cost. Here is the whole thing, including the parts that are worse than what we left.

What we actually needed

Not "a Zoom clone". Writing a video platform from scratch would be a terrible use of anyone's time. We wrote down the four things we actually used:

  • A link a client can click with no app install and no account.
  • A recording of what was said.
  • A text transcript we can search later.
  • A summary with decisions and action items, so nobody writes up notes by hand.

Only the first one is genuinely hard. The other three are things a browser can already do and most people do not realise it.

Piece one: the room

We did not build the video layer. We use Jitsi, an open-source meeting platform with a free public server, and embed the room in our own page so the call runs inside our system rather than sending the client somewhere else.

Every appointment generates its own room name from the booking itself, so the link is stable and specific to that meeting. No host account, no dial-in PIN, no timer cutting you off mid-sentence.

This is the honest shortcut in the whole build. We are using someone else's infrastructure. The difference is that it is free, open source, and swappable, rather than rented per seat.

Piece two: the recording

Your browser can already record audio. There is a built-in recorder that most people never touch, and it needs no server and no service. We start it when you press record and it produces an audio file at the end that you can play back in the page and download.

That file never leaves the machine. We deliberately do not upload it anywhere. More on why that cuts both ways below.

Piece three: the transcript

Browsers also ship a speech recognition engine. It listens continuously and returns text as you speak, including a live preview of the words it is still deciding on.

One detail took a while to get right: the engine quietly times out every so often. If you only start it once, transcription dies partway through a long call and nothing tells you. So it restarts itself for as long as the recorder is still running.

Piece four: the summary

When the call ends, the transcript goes to our own AI endpoint and comes back as a structured summary: the gist, the key decisions, the action items with an owner and a deadline where one was stated, and the next steps.

That summary is written straight back onto the appointment record. Which is the actual point. The transcript, the decisions and the follow-ups now sit on the same record as the client, the quote and the invoice, instead of in a separate meetings product.

The trade-offs, honestly

This is the part most build-it-yourself posts skip. Four real limitations:

  • Recording and live transcription only work in Chromium browsers, so Chrome or Edge. In Safari or Firefox the call is fine but the recorder is not, and the page says so and offers manual notes instead of failing silently.
  • It records your microphone, not the call's mixed audio. Your side is clean; the other side is captured as it comes out of your speakers. On a laptop one-to-one that is fine. In a conference room with bad speakers it is not.
  • The audio stays in the browser until you download it. That is a privacy decision we are happy with, but it means closing the tab loses the audio. The transcript and the summary are already saved, so what you lose is the recording, not the record.
  • Transcription is good, not exact. Names and industry jargon come out wrong. It is a searchable memory of a conversation, not a legal transcript.

What we would still pay for

If you run webinars, need guaranteed uptime for high-stakes external calls, or need compliance-grade recording with a retention policy behind it, keep paying. A free public server has no support line and no promises, and you should not learn that during a board meeting.

For internal calls, client check-ins, discovery conversations and anything where losing a call means rescheduling rather than losing money, owning it has been strictly better.

What it actually took

One page, one endpoint, and a handful of browser features that were already sitting there. The reason it is not a big build is that we stopped trying to replace the product and only replaced the four things we used.

That is the pattern under nearly every subscription we have killed. You are rarely using the product. You are using four things inside it, and those four things are usually much smaller than the bill.