Business & Money
What Your Meetings Actually Cost, and Where the Automation Dividend Goes
By Jim Vernon, Editor, AI Intelligence International · Published 3 February 2026 · Reviewed against our editorial standards · About the author
Companies that deploy AI successfully often report no visible change in output. The saved time went somewhere, and in most organisations it went into meetings and internal coordination, which expand to fill available calendars.
Protecting the dividend requires measuring it. The simplest instrument available is the fully-loaded cost of a recurring meeting, and it tends to change behaviour immediately.
Key takeaways
- Calculating a real meeting cost: Take attendee salaries, add employment costs of roughly a quarter to a third, convert to a per-minute rate, multiply by duration and attendance, and add preparation and context-switching time, which typically adds a third again.
- Where the dividend leaks: Three leaks dominate: new coordination meetings created by the tooling itself, expanded review cycles as output volume rises, and simple absorption where nothing changes except a slightly gentler day.
- Redesigning the meeting stack: Convert status meetings to written updates with automated summaries; keep meetings for decisions, disagreement and relationship work, which are the three things text handles badly.
- Using summaries well: Automated notes are the most widely adopted business AI feature and the most misused.
Calculating a real meeting cost
Take attendee salaries, add employment costs of roughly a quarter to a third, convert to a per-minute rate, multiply by duration and attendance, and add preparation and context-switching time, which typically adds a third again.
A weekly hour-long meeting with ten mid-level staff is a meaningful annual line item — comparable to a substantial software contract that would require three approvals to sign.
Nobody approves the meeting. That asymmetry is the point of doing the calculation.
Where the dividend leaks
Three leaks dominate: new coordination meetings created by the tooling itself, expanded review cycles as output volume rises, and simple absorption where nothing changes except a slightly gentler day.
The second is the most insidious. Doubling draft volume doubles review load, and review is the expensive human step, so throughput gains can evaporate entirely at the checking stage.
Track review hours as a first-class metric during any adoption programme. It is the leading indicator of whether the gain is real.
Redesigning the meeting stack
Convert status meetings to written updates with automated summaries; keep meetings for decisions, disagreement and relationship work, which are the three things text handles badly.
Require a written purpose and desired decision in every invitation. Meetings that cannot state a decision usually should be a document.
Cancel every recurring meeting for one month and see which get reinstated by demand. Roughly a third typically never come back.
Using summaries well
Automated notes are the most widely adopted business AI feature and the most misused. A summary is only valuable if it captures decisions, owners and deadlines, which requires the meeting to actually produce them.
Establish a house format: decisions, actions with names and dates, open questions. Then the tool has a target and the output is directly usable.
Publish notes where people who were not present can read them. That is what allows you to shrink attendance, which is where the money is.
Directing the dividend on purpose
Decide in advance how saved time is allocated: a share to throughput, a share to quality and documentation, a share returned to people. Announce it, and report against it.
Unallocated dividends are always absorbed, and the team concludes the tooling changed nothing. That perception is much harder to fix than the underlying problem.
Reviewing the allocation quarterly also gives you an honest read on whether the programme is delivering, independent of vendor dashboards.
A one-hour exercise for any team
List every recurring meeting, run the cost calculator on each, and sort by annual cost. Then for the top three, write down what decision each produces.
Most teams find at least one expensive meeting that produces no decision at all. Removing it funds a year of tooling without touching headcount, and it is the easiest win available in any adoption programme.
A worked example: the recurring status meeting
A weekly status meeting with nine attendees at an average loaded cost of ninety pounds an hour costs roughly eight hundred pounds each week, or over forty thousand pounds a year before anyone counts the context-switching around it.
Replacing it with a written update plus an AI-compiled digest, and keeping a thirty-minute fortnightly session for actual decisions, cut attendance-hours by about seventy per cent. The digest took one person ten minutes to check before sending.
The saving only became real because the recovered hour was explicitly assigned — in this case to a support backlog with a measurable queue. Without that step, the hour would have quietly refilled with other meetings.
Which meetings survive automation
Meetings that exist to transfer information are the obvious candidates: status rounds, read-outs, and most recurring updates. A written summary is faster to consume and searchable afterwards.
Meetings that exist to make a contested decision, to negotiate, or to deliver difficult feedback should stay live. Notes tools help these by removing the scribe role, but the conversation itself is the product.
The awkward middle is the meeting that exists to create shared attention — planning, retrospectives, onboarding. Keep them, but shorten them: an AI-prepared brief circulated beforehand routinely takes fifteen minutes out of a sixty-minute session.
Frequently asked questions
Should attendee salaries be shared to do this?
No. Use band midpoints; the estimate is directional and precision adds nothing but sensitivity.
Do automated notes create legal risk?
They can, since recordings and transcripts are discoverable and consent rules vary. Set a retention policy and disclose recording before it starts.
How do we stop meetings creeping back?
Require an owner, a decision and an end date for every recurring meeting, and review the list quarterly with the cost attached.
Is asynchronous always better?
No. Disagreement, negotiation and relationship building are faster and kinder live. Use meetings for those and text for everything else.
What hourly cost should we use?
Fully loaded cost — salary plus employer taxes, benefits and overhead — which is typically 1.25 to 1.4 times base salary.
Do transcripts create a records risk?
They can. Set a retention period, say who can access recordings, and exclude sensitive meetings such as performance and HR discussions.