A business case for async meetings, with the calculation and a one-page template
Steffen Rosenögger, Founder of CapmePublished October 18, 2026
One status meeting moved to a recorded agenda: the saving with its method, the alternatives that cost nothing, a 14-day pilot and a one-page template.
In short
- A weekly one-hour status meeting with 8 people, moved to a recorded agenda, frees about 188 hours a year in our example, worth about €8,500 at the Destatis average.
- Cutting it to 30 minutes frees about 184 hours with no licence.
| Figure | Value | Where it comes from |
|---|---|---|
| Labour cost per hour worked, Germany, 2025 | €45 | Destatis, 29 April 2026 (industry and services) |
| Freed by a recorded agenda | about 188 h, about €8,500 | Our calculation, method below |
| Licence for 3 speakers, per year | €432 billed monthly, €360 billed yearly | Capme Meetings, Team: €12/speaker/month or €120/year, min. 3, plus VAT; viewers free |
| Break-even | 9.6 h a year, about 13 min a week | Monthly-billed licence ÷ Destatis rate |
| Advantage over cutting to 30 min | about 3.8 h a year, about €170 | Our calculation; less than the licence |
What does finance need to see in the request?
A business case for an async meeting tool sets the hours one recurring meeting takes from everyone in it against the licence for the few who would record instead. The licence is one invoice line; the benefit is an estimate, so finance checks the method. Print every assumption next to the euro figure. The hours side fits in one spreadsheet row with the meeting cost formula.
Ask for one meeting. "Reduce meetings" across a department has no baseline and no owner; moving the Monday status meeting for two weeks has both. Check which meetings can go async first: one that mostly informs is a candidate, one that must reach agreement is not.
Meeting hours calculator
A typical team lead spends 9 of 42 working weeks a year in meetings
That is about 370 hours, from six standing meetings and three hours of one-off meetings a week. Tick your own and the squares become your year.
Work out your yearIs a shorter meeting cheaper than an async tool?
Cutting a weekly 60-minute status meeting of 8 people to 30 minutes frees 4 person-hours a week at no cost, against 4.08 for a recorded agenda. We think a request should show that comparison openly: a controller can do the sum in their head, and a case without it loses credibility on every other figure.
| Option | Hours freed a week | Licence | Where it falls short |
|---|---|---|---|
| Cut to 30 minutes | 4 | None | Everyone still meets at one time; an hour's agenda gets rushed or cut |
| AI notetaker in the meeting | 0 (all still attend) | Extra licence | Saves the minutes; transcripts raise their own works council questions |
| Written update | n/a | Usually none | Hard to show a screen or demo; easy to skim |
| Recorded agenda (async tool) | 4.08 | €432 a year | Open points still need a short call; fails if speakers do not record; per-person watch data concerns the works council |
The recorded agenda beats the free cut only while setup, recording, watching and the call stay under 4 person-hours a week. The example needs 3.92. Against the free 30-minute cut, the recorded agenda gains about 3.8 hours a year, worth about €170, which is less than its €432 licence. It earns the licence where 30 minutes is no option: the content needs more, or part of the team works in another time zone. Then the 4.08 person-hours freed each week, worth €184, cover the year's licence in week 3. If your status meeting is mostly discussion, shorten it and skip the tool. On notetakers, see AI notetaker or async meeting.
How much does moving one status meeting to async save?
In the example, a recorded agenda gives back 4.08 of the meeting's 8 person-hours a week. The rate is from the Federal Statistical Office, whose press release of 29 April 2026 is headed "Eine Arbeitsstunde kostete im Jahr 2025 durchschnittlich 45,00 Euro" ("An hour of work cost an average of 45.00 euros in 2025", translated); it covers industry and services, non-wage costs included. For a mostly senior team, meeting cost in Germany by role gives a better rate; the meeting cost calculator runs your own numbers.
The 3 who report become speakers, the team lead among them organising; the other 5 watch. We assume: 10 minutes a week to set up the agenda, since meetings cannot be copied; 20 minutes per speaker to prepare and record a 5-minute topic; all 8 people watch the whole 15-minute agenda once; 3 of them still need a 15-minute call; 46 weeks a year. We leave out preparation for the live meeting, which favours the live meeting.
| Item | Per week | Per year |
|---|---|---|
| Live meeting | 8 × 60 min = 8 h | 368 h |
| Agenda setup | 1 × 10 min = 0.17 h | 7.7 h |
| Recording | 3 × 20 min = 1 h | 46 h |
| Watching | 8 × 15 min = 2 h | 92 h |
| Follow-up call | 3 × 15 min = 0.75 h | 34.5 h |
| Hours freed | 4.08 h | 187.8 h |
| Value at the hourly cost | €184 | about €8,500 |
At half the saving, the hours are still worth about €4,200. If all 8 people report, the licence rises to €1,152 net a year.
As checked in Capme's code in October 2026, the in-app "Time saved" card subtracts no recording or watching time, so it reads higher. It treats the rate as gross pay and adds employer costs: to match Destatis, enter €37.50, not €45.00.
Are saved meeting hours a real cost saving?
Saved meeting hours turn into a cost saving only when someone decides what the time is for; until then they are capacity. Nobody's salary falls when a status meeting ends.
Name the line that will move, for example the 188 hours set against an overtime budget. Without one, claim less.
How does the example meeting run in Capme?
In Capme Meetings, organising needs a speaker seat, so the team lead takes one of the 3 seats; viewers are never counted. Step by step:
- An admin sets watch progress to Totals only before inviting anyone: organisers see how many finished, not who.
- The team lead sets the deadline to Monday 09:00, the old slot.
- The first agenda row, the organiser's intro, takes the team lead's report; two more rows get the other speakers, each with a Target length of 5 minutes and the hint "A target, not a limit, so running over is fine."
- Add the 5 viewers as attendees. Saving asks Send emails? and invites only the speakers. Mid-week, Remind everyone reaches speakers who have not recorded; Capme never does this by itself.
- On Monday, Publish meeting emails everyone; a missing video shows as a placeholder. The same dialog can switch on one reminder for viewers who have not finished.
Put Capme's limits in the request too. It holds no live calls, so the follow-up call stays in Teams or Zoom. Recordings take no comments, and questions go to chat. There are no transcripts, captions, summaries or mobile app; speakers record in a desktop browser, best in Chrome or Edge.
How do you prove the savings in a pilot?
Run the real meeting async for 2 weekly rounds in Capme's trial. It lasts 14 days (as of October 2026), needs no card and does not count speakers. Before round one, write down the baseline (length, attendees, required output) and the success criteria; finance will not accept a criterion written after the results. The pilot plan runs it day by day and ends in a go or no-go memo.
Set the criteria as numbers. For the example: all videos in before the old slot, 6 of 8 people finished each round, follow-up call within 15 minutes. Have the 3 speakers log their setup and recording time. For watching, use the calculation's assumption: 15 minutes for each person the admin Overview tab shows as finished. Capme counts a topic as watched once 75 % of it has played (code checked October 2026). With the call, the total must stay under 4 person-hours a week. After round two, ask everyone whether they missed anything and want the live meeting back.
Owners and admins can forward the one-page Trial summary to forward from the Overview tab; in the October 2026 code it lists usage, price and DPA acceptance but no time saved, so attach your calculation.
What will the works council and IT ask?
The works council will ask about monitoring. § 87 (1) no. 6 BetrVG gives it a say on "Einführung und Anwendung von technischen Einrichtungen, die dazu bestimmt sind, das Verhalten oder die Leistung der Arbeitnehmer zu überwachen" ("the introduction and use of technical devices designed to monitor the behaviour or performance of employees", translated). The Federal Labour Court reads "designed to" as objectively suited to monitoring, whatever the employer intends (1 ABR 7/15, 13 December 2016), and a tool that shows who watched what is suited to it. Totals only (step one above) takes the names out. Talk to it before the pilot; what the works council co-determines in a video tool helps prepare.
IT and data protection will ask where the video lives and on what contract. The tool processes employee data on your behalf, so it needs a DPA under Art. 28 GDPR; Capme's DPA is public. On Business and Enterprise, recordings can stay in your own S3 bucket instead of Capme's EU hosting; they are never transcribed or used for training.
Procurement will ask about the exit. After cancelling, the plan runs to the end of its month or year, then stays readable without new recordings; the hosted videos go after 30 days, and recordings are exported as MP4 on request before then. On a monthly plan the risk is one month.
What does a one-page business case look like?
Copy the seven rows and fill the right-hand column with your meeting.
| Section | What to write | From the example |
|---|---|---|
| Problem | The meeting, length, attendees, cost | Weekly status meeting, 60 min, 8 people, 368 person-hours a year |
| Option | What replaces it; alternatives compared; why 30 minutes is not enough | Recorded agenda, 3 speakers incl. organiser; vs. 30-min meeting (184 h, no licence), notetaker, written update; 30 min too short: 3 reports plus demo, 2 members in another time zone |
| Cost | Licence per year, net; who pays | €432 monthly or €360 yearly billing, plus VAT |
| Benefit | Hours returned, assumptions, value, where the time goes | About 188 h a year, about €8,500; at half effect €4,200 |
| Risks | Adoption, works council, data protection, exit, limits | Totals only agreed with works council; DPA accepted; call stays in Teams; 30 days to export videos after cancelling |
| Pilot | Length, measures, success criteria (fixed in advance) | 14-day trial, 2 rounds; videos in before the old slot, 6+ of 8 finished, call within 15 min; effort logged |
| Decision | What you ask for, from whom, by when | Approve 3 speakers on the Team plan for one year if the pilot meets its criteria |
Send the request with the pilot dates filled in; a controller signs a 14-day test more readily than a year's licence.
Frequently asked questions
- Can a team lead pay for it without a purchase order?
- Monthly plans are paid by card or SEPA direct debit; yearly plans also by invoice, due 14 days after issue. Whether a card purchase needs one is your company's rule.
- What if part of the team works outside Germany?
- Use each country's own labour cost; the Destatis figure covers Germany only. The BetrVG applies to establishments in Germany; elsewhere, check local rules on employee representation.