Beam

Meetings that write themselves into the record.

The call ends. The record updates.

The problem with a standalone meeting tool

You meet in one app. You take notes in another. You paste action items into a third.

By Friday, the decision is a memory and the transcript is a file nobody opens.

Vernais closes the loop.

The meeting happens where the work lives, so the conversation doesn’t evaporate into a separate notes app. It becomes a Signal, a summary page, and evidence on the Initiative it’s about.

One connected surface beats four disconnected ones.

01 · One-click video

Schedule from the Calendar. Start the room with one click.

The Calendar you already use for month, week, and day views is the same place you spin up a video room, no second app, no meeting-link roulette.

  • Schedule anywhere: book on the Calendar in month, week, or day view.
  • Invite guests: add teammates, track RSVPs, see who’s in.
  • Reminders & recurrence: one-off or repeating, with reminders that fire on time.
  • One click to live: start a LiveKit video room straight from the event. No install, no dial-in.

02 · Live transcription

It transcribes itself.

Captured as it’s spoken, labeled by speaker. No bot to invite, no upload to wait on. By the time you say goodbye, the transcript already exists.

  • Speaker-labeled: every line attributed, so the record reads like the conversation happened.
  • In-browser: nothing leaves the room to a third-party transcription service.
  • Ready at “end call”: the transcript is finished the moment the meeting is.

03 · From transcript to evidence

It becomes evidence.

Link the meeting to an Initiative. When it ends, the transcript does the paperwork.

This is the difference. A standalone tool gives you a transcript. Vernais gives you a filed piece of evidence: correlated to the problem, classified by what it is, and dropped into the right phase.

What happens when the call ends

Flow: a meeting transcript becomes a correlated and classified Signal (kind=transcript), then lands in the Initiative’s Validate phase, tagged Built.

And a summary page writes itself

Every recorded meeting also produces a page in Codex, an AI summary you didn’t have to write.

  • Decisions: what the room actually decided.
  • Action items: who owns what.
  • Topics: what the conversation was about.
  • Live dashboard: the summary page shows the Initiative’s signal counts by category, updating as the initiative moves.

The transcript page has restricted visibility: meeting content stays with the people who were in the room and on the initiative.

04 · The right cast

The right people in the room.

Tag a meeting to an Initiative and Vernais surfaces the people the work belongs to, its reporter and owner, plus attendees, so you bring the right people in instead of guessing.

  • Reporter & owner surfaced: the Initiative’s IN-n reporter and owner appear on the meeting.
  • One-click add: pull them into the guest list in a tap.
  • No more “who should be here?”: the meeting inherits the initiative’s cast.

Today Vernais surfaces the reporter, owner, and attendees; adding them is a one-tap manual step, not automatic yet.

Why it beats a standalone meeting tool

The conversation is the most evidence-dense thing your team produces. It shouldn’t die in a separate app.

The transcript doesn’t sit in a folder

It becomes a Signal on the initiative it’s about.

The decision doesn’t get lost

It’s written into a summary page, with action items and topics.

The evidence doesn’t need re-entry

Correlation and classification happen automatically at “end call.”

The record stays connected

The meeting, the page, and the Signal all point back to the same Initiative IN-n.

You meet. Vernais files it. The work moves forward.