7–15%
of payroll goes on meetings
With little test of whether that spend returns anything.
Rogelberg et al., via SHRM
For organisations that run on meetings
Standups that could be a page. Syncs with no stated outcome. Catch-up calls for everyone who wasn’t there. Pyris removes the meetings that don’t need to happen, shortens the ones that do, and keeps a record so nobody asks twice.
Tuesday 30 September
Your day
Day ahead
2 h 15 min in meetings of 8 h 30 min
Transcribed on the device · No audio stored · Text stays in your tenancy · Entra sign-in
The tax
Nobody approves a coordination budget. It accrues one invite at a time: a standing meeting that outlived its reason, a sync with no stated outcome, a catch-up because the notes never arrived, a decision made twice because nobody wrote down who owns it. It shows up as a full calendar and a slow quarter.
One team, one week
What’s left is the meeting that needed a room.
7–15%
With little test of whether that spend returns anything.
Rogelberg et al., via SHRM
22 min
And the stop-start around it cost more than the meeting itself.
Stray et al., IEEE Software, 2020
62%
And 54% often leave without a next step or an owner, so it gets held again.
Atlassian, 2024
30%
If people trusted they’d be kept in the loop. Attendance is insurance.
Rogelberg for Otter.ai, 2022
Public research on knowledge workers, not Pyris customer results. Pyris doesn’t promise these numbers as savings. It measures yours.
How it works
Not another place to keep notes. A discipline applied before the invite goes out, on the morning of every standing meeting, and after the room empties.
1 · Before the invite
Pyris asks what must be true when the hour ends. “Discuss the rollout” is an activity. “The rollout date is chosen and one person owns it” is an outcome. While you plan, the last meeting’s summary and open actions sit beside you.
For each outcome, Pyris suggests live or async. Async ones become pre-work, and Pyris drafts the email. The meeting that remains is shorter because the writing already happened.
Cuts meetings with no point, and the time spent finding one.
Live or async
2 · The morning of
On the morning of a recurring meeting, its owner gets one question: is a meeting a good use of time today? Meet, go async, or cancel. No answer, and the meeting goes ahead. Silence is never a cancellation.
Async turns the occurrence into a status report: everyone’s own words, blockers, cross-dependencies, and who hasn’t answered. Guests from outside the company reply from a personal link, without signing in.
Cuts status meetings that exist because they existed last week.
Is a meeting a good use of time today?
Async: seven people keep the fifteen minutes. The report lists blockers and who hasn’t answered.
No answer by 09:00 and the meeting goes ahead.
3 · After the room
The room gets a note that sets each stated outcome against the record. The boxes start unchecked; only a person’s tick confirms one.
Anyone who stayed away opens a brief written for their role: the headline, the decisions that touch them, their actions, and whether it was safe to skip. People decline with confidence once they trust the brief will arrive.
Cuts attendance as insurance, and the catch-up call afterwards.
Brief for me
Rollout moves to 14 October. Your budget sign-off is needed by Friday.
Decisions that touch you
Your actions
Decision log
The most expensive meeting is the one that re-opens a decision nobody can find.
Confirmed decisions leave the meeting note and enter the organisation’s decision log: what was decided, why, the alternatives, who made it, and the one person accountable. Each is scoped to the meeting, the team, or the whole organisation.
When minds change, a decision is superseded, not overwritten. It stays in the log, linked to what replaced it. The next person to ask gets an answer, not another meeting.
Ship the rollout on 14 October, behind a staged flag.
Metrics
Pyris keeps your organisation’s own counts, meeting by meeting, instead of borrowing someone else’s percentages. When the sample is too small, it says there isn’t enough data yet.
Active time on the agenda before the hour.
How long it ran, against the time booked.
Time on the note, not waiting for the draft.
Who was needed, asked of the people invited.
Outcome hit rate
Security
Transcription happens on the device. Audio is held in memory for that work. It’s never written to disk or uploaded.
Only text reaches the organisation. People sign in with Entra, the draft is written in your own cloud, and transcript text is purged after 30 days. The note stays because a person reviewed it. The model never approves its own sentences.
Captured for the meeting. Processed in memory on the device.
The transcript, segment by segment. Nothing else from the recording.
Written in your cloud tenancy, in the shape chosen before the hour.
A person’s acknowledgement that they inspected it. Edits never create one.
Who it’s for
See the outcome before you accept. Stay away and still open a brief written for your role. When the morning question turns a standup into a page, the time you get back is yours.
Name the outcome before the invite goes wide. Move what you can into pre-work. Ask each morning whether the room is needed. Afterwards, see which outcomes were hit and which decisions entered the log.
The payroll already spent on rooms becomes something you can see, meeting by meeting, instead of a feeling that every week is full. Decisions have an owner and a scope. Audio never rests on a disk.
Start with one team and one standing meeting. The counts are yours from the first occurrence: which ones needed a room, which outcomes were hit, and what everyone got back.