About

Every other meeting AI is a guest in the room.

It dials in like a person, hears the call mixed down to a single stream, and works out who was speaking from the sound of their voice. Everything it tells you afterwards rests on that guess.

We built the room. So we do not have to guess.

Two architectures compared A guest bot receives one mixed audio stream and must infer speakers, producing uncertain labels. Team Meet receives one transcribed stream per person, so each line already carries a name. A bot in someone else's call one mixed stream diarize Speaker 1  “we should ship Friday” Speaker 2  “Friday looks tight” Speaker 1?  “fine, Friday” 88–90% right in a clean 1:1. ~75% once five people are on. A meeting held here Jack Roger Priya one stream per person, transcribed on their own machine Jack  “we should ship Friday” Roger  “Friday looks tight” Jack  “fine, Friday” Right every time, at any size, because it was never a guess.
The speaker on a line here is the connection the words arrived on. Not an inference from timbre.

A wrong word is noise. A wrong name is a record.

A transcript that misspells your product name is annoying and you fix it without thinking. A transcript that puts a sentence in the wrong person's mouth reads perfectly — it is grammatical, it is specific, and it has a name in it. Then someone forwards it to a person who was not in the room, and a machine's guess becomes your commitment.

“The worst is when someone uses these, blindly trusts the output, and then sends out an email after the meeting with a list of hallucinations that everyone supposedly ‘agreed to’.”

Hacker News, 386 comments

That is the failure we built around, and it is why the room came first. Own the room and speaker attribution stops being a modelling problem. Everything downstream inherits the certainty.

Four rules everything is built to.

Not values. Constraints, in the code, with tests that fail when they are broken.

  1. Every claim carries the words it came from.

    When the notes say a decision was made, they carry the sentence that made it, and that sentence is checked as a literal substring of the transcript. A claim that fails the check renders as unverified. It never renders as fact.

    A note that invents a constraint is worse than one that is merely wrong, because a group will plan around it.

  2. The number people act on is arithmetic, never a model call.

    When a group decides something, the count comes from counting. Nothing that can be persuaded is anywhere near it.

    The one figure a room acts on cannot come from something that can be talked into an answer.

  3. A program in the room is always visible, and anyone can remove it.

    An agent joins under its own name, its arrival is written into the chat, and any person present can throw it out. Not the host. Anyone. One switch turns agents off for the whole meeting and disconnects the ones already connected.

    Every complaint about meeting bots comes back to not being able to see one, remove one, or having agreed to one.

  4. We say what we cannot do, in the place you would find out.

    The developer docs carry their own limits section. The privacy page names every third party by name, including the one most products quietly omit: in Chrome and Edge, speech recognition is Google's, and your audio goes there.

    You will find out eventually. Finding out from us is the whole difference.

And five things we will not build.

Each of these is shipping somewhere else right now.

A meeting score.Nobody wants their conversation graded, and a graded room is a room where people perform for the machine.
A live sentiment read-out.Same reason, and it is mostly wrong. A confident number about how someone feels is a weapon.
An AI that talks unprompted.A second interrupting voice would spend every bit of credit the first one earned.
Guessed owners on action items.Work nobody took is listed as unowned. Guessing is how a recap becomes something people argue with instead of act on.
A summary that does not quote.The whole product rests on a line being real because you can see the words behind it. One unquoted feature would undo every quoted one.

You can check all of this in about a minute.

No account, no download, no card, and nothing to book.

Start a meeting A name and a click. The link is yours to send, and it works in any browser on any device. Read why the guess fails The measured numbers, the conference-room case nothing can solve, and what we do instead. Every claim sourced. Get an API key One unauthenticated POST. Free, no minimum, and your agent joins with a socket instead of a browser. Or read the teardown of how meeting bots actually work, with every claim sourced, including the parts that are fair to our competitors. The whole argument →

Who is behind it.

Team Meet is built by Jack Jay, founder of Persist Ventures, a studio that builds and staffs companies rather than only funding them. It started as an alignment protocol for a single hard conversation and became a meeting platform because the protocol needed a room that could be trusted about who said what.

It is free while we build it. There is no upgrade path being dangled at you, no feature held hostage behind a tier, and no salesperson attached to this page.

Start one now.

It takes a name and a click.

Start a meeting