How the read works

Three minutes, three steps, one thing to try.

No recorder, no bot, no setup call. You bring a transcript you already have and we read it the way a colleague would if they'd been taking notes for you.

01

Sign in and name your meeting.

A code by email, no password. Your workspace is yours: the meetings, the people in them, the moves you've tried. Nobody on your team gets access unless you invite them.

What we ask for

Your email. The meeting's name and date. Who was in the room, so we can use their real names back to you.

02

Paste the transcript, or drop the file.

Plain text works. So does the .vtt or .srt your call tool exports, a copied Google Meet transcript, or notes you cleaned up yourself. You see the text before we read it, and you can edit it.

Works with

Plain textZoom .vtt.srtGoogle MeetYour own notes
03

Read it, try one thing, come back.

You get one insight, one risk, one recommendation — each tied to a line and a timestamp you can check. Next time you upload, the read opens with the move you tried and what the room did with it. That's where it starts compounding.

Go deeper if it warrants it

The fuller analysis — influence map, every commitment, the full transcript walk — stays one click away on the same meeting.

What we look at

Four ways of reading the same transcript. The engine works from observable signals — who spoke when, whose framing got adopted, which questions went unanswered, what closed without a name — and organizes them into readings you can argue with.

Power and influence

Who shaped the decision, and whether that matched who was supposed to. Airtime, framing adoption, direction of influence.

Power DynamicsAttribution

Group dynamics

What the team did as a system: deferring, clustering, closing early, going quiet after a particular person spoke.

Group Dynamics

What stayed unsaid

Concessions that weren't agreement. Questions answered with a different question. Topics that quietly disappeared.

Subtext

Who owns what now

Every commitment made in the room, and whether it left with a name attached to it.

Decision Ownership

What this isn't

—

Not a score. No team health number, no risk percentage, nothing out of 100.

—

Not a verdict on a person. We describe what a room did, in one meeting, and we say when we're guessing.

—

Not a transcription tool. We don't join calls or record anything. Bring the transcript.

—

Not a surveillance tool for your reports. The read is written to you, about the room you run.

—

Not a meeting summary. If you want to know what was said, you already have the transcript.

Privacy, plainly

Transcripts are encrypted at rest and never used to train models. You can delete a meeting, and everything derived from it, at any time. Your team's names stay inside your workspace. No bot ever joins your calls.

Encrypted at rest · never used to train models · deletable any time

Start with the meeting you ran this week.