From meetings to board, instantly.
Capture with the Noot bot, or with the browser extension for teams that will not put a bot in a call. Either way the same thing happens next: the meeting is written up, and the work lands on the board with an owner and a date.
Sprint sync
24 min · 6 attendees · speaker-labelled
Summary
Onboarding ships next sprint. Pricing is held for design review. The migration and the QA pass were both given owners in the room.
On the board, with owners
- Migrate the onboarding flowMayaFri
- Run the QA pass on checkoutSamTue
- Draft the pricing copyOps leadThu
A bot in the call, or nothing in the call.
Two routes, one pipeline. Whichever you use, the write-up, the transcript and the board update are produced by exactly the same code — so the choice is about the room, not about what you get afterwards.
The Noot bot
Send it to a Zoom, Meet or Teams link and it joins, records and hands the recording to the pipeline. On a Noots voice or video call the in-house bot does the same thing without leaving the app.
- Joins from a pasted link, or from a meeting already on the calendar
- Records Noots' own calls too, not just the third-party ones
- Live notes during a Noots call — opt-in, and off until an admin turns it on
- A meeting stuck mid-processing is swept and finished, not left hanging
The browser extension
Some rooms go quiet the moment a bot appears in the participant list. The extension records the tab in your browser and transcribes there, and nothing reaches Noots until you have read the transcript and pressed Save.
- Nothing joins the call and no one is notified
- You review the transcript before any of it is sent
- Chrome, Edge and Brave
- Installed from a downloaded zip in developer mode, not the Web Store
Six panels, one writer.
Every capture route ends in the same function, so every meeting carries the same six panels — and a field added to one of them appears on all of them at once.
Topics and concepts are questions rather than labels: click one and it is explained from this meeting's own transcript, generated at the moment you ask and kept for the next reader.
What the meeting was for and where it landed, in plain language.
The substance — what was actually discussed, not a list of headings.
Kept apart from the key points, because a decision is a different fact.
Every commitment, with the person who made it and the date they gave.
Chips you can click. Each one is explained from this meeting's own transcript.
Who spoke and how much — derived from the transcript, never from the invite list.
- Dana07:12
Can we still hit the 28th?
- Theo07:19
Yes, if scope holds at one page.
- Dana07:26
Then I'll take the migration.
Talk share · measured in seconds
- Dana44%
- Theo31%
- Four others25%
Turns, timestamps, and one person per speaker.
A transcript is a sequence of turns, not a wall of text. Each one carries who said it and when, so the reader can be searched, jumped through and quoted.
- Speaker-labelled turns with timestamps, searchable inside the meeting
- Talk share measured in seconds when the capture is timed and in words when it is not — and the panel tells you which
- Two labels for one colleague are merged, so a rejoin does not split someone's talk share in half
- Where the labels genuinely are not reliable, it renders as prose rather than inventing speakers
And then the project moves.
The write-up is the halfway point. What makes it worth having is that six other surfaces update from it without anybody re-typing a word.
Tasks on the right board
Action items become real tasks with an owner, a due date and a link back to the meeting they came from. The owner is matched against your actual roster, and an unmatched name is left as text rather than guessed at.
Notes filed as a document
The write-up is filed on the project as a document, so the record lives with the work instead of in someone's inbox.
Dates on the calendar
A deadline agreed out loud lands on the project's calendar. Grounded only — nothing invents a date that nobody said.
Risks in the RAID log
A risk raised in the room is logged against the project, and where it threatens a task we already created, it is tied to that task rather than matched by name later.
Spend, proposed — never posted
A figure someone said in a call is a claim, not a ledger entry. It arrives on the Budget tab as a proposed line for a human to confirm.
Shared with the people who were there
Colleagues who attended get the meeting in their own vault. People outside the organisation do not.
The four people ask first.
Do I have to put a bot in the call?
Which platforms does the bot join?
What happens to a meeting that was recorded before all this existed?
Can it write to a project nobody meant it to touch?
What we don't claim
- No cross-meeting search yet — you search inside a transcript, and the vault list filters by title.
- Nothing is written from a meeting Noots did not capture.
- Amounts and dates heard in a call are proposed, never posted.
- AI features that read what you typed are opt-in, and the consent is enforced on the server.
Stop writing up the meeting you just sat through.
Free to start, eight recorded meetings a month, and no credit card. Bring a bot or don't.
Set up in minutes · no credit card required