What you stop paying when the meeting tool runs locally

The privacy story for keeping a meeting tool on your own machine is well-rehearsed. The cost-and-availability story is not. For procurement, finance, IT directors and ops teams looking at meeting AI tools as a recurring cost on the budget, the difference between a cloud tool and a local one shows up in places that the marketing pages do not put on the front.

This piece is for the role that has to defend the meeting tool spend to a finance director, justify the line item against alternatives, or produce the answer when the CEO asks “why are we paying for this every month”. It covers what cloud meeting tools actually cost over a typical multi-year horizon, what happens when one of them is unavailable on the day you need it, and how the bill changes when the tool runs on the user’s own computer.

What you pay for in a cloud meeting tool

The visible cost is the subscription. £15 to £30 per user per month is the standard band for mainstream meeting AI tools at the team and business tiers, with discounts at annual commitment and surcharges for the better summarisation models. For a team of 25, the published price comes out around £4,500 to £9,000 a year.

The cost that shows up later is in three other places.

Usage limits inside the tier. Most cloud meeting tools cap the amount of work each user can do per month. The cap is sometimes minutes of audio transcribed, sometimes meetings hosted, sometimes AI summaries generated. The limit is below what a heavy user would do without thinking about it. When the user hits the cap, the application either gates the feature until next month or asks the team to upgrade to a higher tier.

For a casual user this never matters. For a fee-earner running a busy month of client meetings, hitting the cap on the day a major matter is winding up is the worst possible outcome. The team’s response is usually to upgrade the whole tier, which costs more again.

Storage and retention. Recordings, transcripts and AI summaries take space. The base tier of a cloud meeting tool typically gives a few months of retention; longer retention costs more. For organisations with regulatory retention obligations (legal, clinical, regulated finance), the storage tier ends up larger than the messaging would suggest.

Integration and identity tax. SSO is usually a paid add-on on the entry tier. Calendar integrations, CRM connections and webhook delivery often require the business or enterprise tier even when the team can otherwise live with the cheaper one. Each of these is a cost the published pricing does not include.

The total over a three-year horizon for a 25-seat team in regulated work is rarely the £13,500 the simple multiplication suggests; it is usually 30-50 percent higher.

What happens when the tool is down

Cloud meeting tools have outages. Not catastrophic ones, mostly, but the kind that show up on a status page after the fact. A typical major SaaS quotes 99 to 99.5 percent uptime, which corresponds to several hours of downtime per month. The hours that matter are the ones during your meeting.

Two specific outage patterns worth knowing about:

The vendor’s own platform incident. The vendor’s API is degraded, transcription queues back up, the AI summary does not arrive after the meeting. Sometimes the application itself does not let users log in. Whether this happens during one of your important meetings is a matter of luck.

Third-party API dependency failures. Many meeting AI tools call out to external services for parts of their pipeline (the transcription model, the language model, the speaker identification). When one of those upstream services is having a bad day, the meeting tool’s quality drops or its features stop working entirely.

For meetings that do not have to happen at a specific time, this is mildly annoying. For client interviews, witness sessions, board meetings and regulator calls, the meeting cannot be rescheduled around a vendor’s incident. The meeting goes ahead. The recording either does not exist afterwards, or has to be remade by hand from notes.

The wider technical-evaluation framework for the same question is in what “on your own computer” actually means for a meeting tool.

Vendor lock-in and the slow upgrade

Two further costs do not appear on the bill but are worth budgeting for.

Price changes at renewal. Cloud SaaS pricing rarely goes down. The contract that started at £20 a seat per month is at £24 by the second renewal and £28 by the fourth. The increases compound. By year five the per-seat cost has typically risen 30-50 percent against the year-one price.

Feature deprecation and tier shuffling. Vendors restructure their tier lineups regularly. A feature that was in the standard tier moves to the business tier; a feature that was in business moves to enterprise. The team’s existing workflow continues, but the tier needed to keep using it is one notch higher than the team signed up for. Each of these is a small bill increase that adds up.

Account-level dependencies. SSO, identity provider, calendar integration, CRM. Each of these is a small step of integration that the team relies on. When the vendor decides to change the integration, deprecate the connector or move it to a higher tier, the team is locked into a renewal cycle to avoid breaking a workflow that already exists.

None of these are dishonest practices on the vendor’s part. They are the standard SaaS economics applied to the meeting tool category. The point is that the bill at year three is not the bill at year one, and the cost of leaving rises with each year that the team has built workflows on top of the tool.

What changes when the tool runs locally

A local meeting tool inverts every line above.

Single payment. Whistle Enterprise is sold per-seat per year, with one year of updates included. After the year, the version of the software the team received continues to run forever, on the same machine, with the same features. Renewing buys another year of updates. Letting the licence lapse does not switch the software off; it stops the team receiving new versions. The cost is whatever the team paid for the seats they bought, full stop. No tier shuffling.

No usage limits. There is no monthly cap on minutes transcribed, meetings hosted or summaries generated. The work runs on the user’s own CPU. The constraint is the user’s hardware, not a vendor’s billing system. A user who runs ten meetings of an hour each through Whistle Enterprise in a single day is paying nothing more than a user who runs one ten minute meeting in a year.

No vendor downtime. There is no service to be unavailable. The application installs locally, the models are bundled with the installer, and the processing runs on the user’s computer. Whistle Enterprise does not require an internet connection to record, transcribe or write the document. A meeting platform outage (Teams, Zoom, Meet, Webex) prevents the meeting itself, but does not affect Whistle Enterprise’s ability to record any other audio source.

No vendor lock-in. The recordings, transcripts and documents are local files. The application can be uninstalled and the files keep working. The exports (PDF, Word, Markdown) are standard formats that any other application can open. The team does not depend on the vendor’s continued availability to access the meetings the team has already documented.

The pricing detail for Whistle Enterprise is on the pricing page. The wider buyer’s view of the on-premise question is in on-premise alternatives to cloud meeting tools.

Where the trade does not pay back

Local meeting tools are not the right answer for every team. Three patterns where a cloud tool is genuinely a better fit:

Occasional, casual use. A team that runs one or two short meetings a week, where the document is a convenience rather than a requirement, is unlikely to recover the per-seat-per-year cost of a local tool against a free or cheap cloud tier. The cloud tool’s limits are above what the team is doing.

Real-time collaboration. Teams that want a transcript shared live across attendees during the meeting need a tool that streams the transcript through a server. Whistle Enterprise records and writes the document after the meeting; it is not a real-time collaboration surface.

Heavy integration with a CRM or sales workflow. If the meeting tool has to push the meeting summary into a CRM record automatically, surface customer history during the call, or provide a coach view to managers, that is a workflow the cloud tools are built for. Whistle Enterprise’s integration boundary is the file system, not an API.

For everyone else, the trade is real and the bill at year three is meaningfully smaller than the cloud equivalent. The free 30 day trial is the way to confirm the workflow fits before the cost question becomes interesting.

Back to all articles