File
SMF·ZOOM-PRO
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·ZOOM-PRO

Can a prompt replace Zoom Workplace Pro?

Video meetings & webinars — video meetings

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
€13.33/moSource: zoom.us · Checked on July 31, 2026
Per year
€159.96
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: global media infrastructure
Exhibit Q Questions

Verdict

Zoom is a global media network with a client on top, and the client is the cheap half. No personal build reaches the reliability that made it the default, and reliability is the entire proposition. So instead of pretending, the build here answers the question the subscription raises but never asks: what do your meetings actually cost, and which recurring one should be deleted?

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a meeting-cost analyser over your own calendar. It never joins a call.

Stack: a local command-line tool plus a static report, SQLite, no network beyond fetching a calendar feed.

Input: one or more `.ics` feeds — the export or subscription URL your calendar already offers. Parse recurrence rules properly, including exceptions and cancelled instances, because a recurring series with three cancellations is exactly where naive parsers over-count.

Classification, kept manual and honest: for each event you assign a type once — one-to-one, team recurring, external, interview, focus block — and the tool remembers the choice by series so you do it once per series, not once per instance.

The numbers:
1. **Hours in meetings per week**, split by type, with a four-week trend.
2. **Cost per recurring series**: attendee count times duration times a configurable hourly figure, per occurrence and annualised. Print the annual figure in money — a weekly one-hour meeting with eight people is a genuinely startling number and it is the point of the build.
3. **Fragmentation**: the longest uninterrupted free block per day, which is a better measure of whether the calendar is workable than total meeting hours.
4. **The candidates list**: recurring series with the worst cost-to-signal ratio, defined explicitly as no agenda in the description, no attached notes document, and an attendee count above a threshold. Name them and their annual cost, because a list of three specific meetings is actionable and a dashboard is not.

Privacy: this reads your colleagues' names and availability. Keep everything local, offer a redaction mode that replaces names with initials in the report, and make retention explicit.

Output: one static HTML file per week in a folder, so the archive is browsable and comparable.

Write tests for recurrence expansion with exceptions and cancellations, for cost arithmetic across a series with varying attendee counts, and for the free-block computation across all-day events.

Do not integrate with a meeting platform, and do not attempt to join, record or transcribe anything.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 the meetings themselves and the network behind them
  • B.2 recording, cloud storage and the AI companion
  • B.3 phone dial-in and the telephony behind it
  • B.4 the client that works on every device your participants own
  • B.5 anyone to call when a call fails

Exhibit C — Why people still pay: global media infrastructure

Because the default matters: everyone has it, everyone can join, and the call does not drop. That is bought capacity and universal client support, and no self-hosted room replaces it.

Questions

Why is calendar recurrence parsing the hard part?

Because `RRULE` with exception dates, modified instances and timezone shifts is genuinely fiddly, and getting it wrong silently inflates every number in the report. Use a well-tested library and write tests against a series with cancellations.

Is putting a money figure on a meeting not crude?

It is crude and it works. A weekly hour with eight people is several hundred hours a year, and seeing that as an annual number is what gets a standing meeting cancelled — where "we have too many meetings" never does.

Why classify by hand instead of guessing from the title?

Because title heuristics are wrong often enough to discredit the whole report, and the classification is per series rather than per event, so the real cost is a few minutes once.

Is any of Zoom rebuildable at all?

Small self-hosted rooms are, and the Whereby and Google Workspace entries cover that. What is not rebuildable is a call that works for a stranger on an unknown network in another country, which is precisely why Zoom became the default.

Receipt

Already built this yourself?