The shift from per-seat to per-meeting pricing is a significant one, and not necessarily in the user's favor. tl;dv is betting that most teams will find the new model cheaper, but that's a dangerous assumption for procurement and finance.
Here's the breakdown from a negotiation perspective:
* **Per-seat (old model):** Predictable, scalable cost. You pay for active users. Easy to budget, even if some seats are underutilized.
* **Per-meeting (new model):** Variable cost tied directly to usage. This seems fair until you analyze your meeting volume. High-meeting teams (like sales, customer success) will see costs balloon.
**The real issue is the lack of a hybrid option.** Enterprises need predictability. A pure per-meeting model turns this from a fixed SaaS line item into a variable operational cost that's harder to control and forecast.
Vendor negotiation benchmarks for similar tools (Gong, Chorus, etc.) show they fiercely defend per-seat pricing because it's more profitable and stable for them. tl;dv flipping the script is a major power play. They're pricing against *activity*, not *access*.
**Actionable advice for teams:**
* **Audit your last quarter:** Calculate your total recorded meetings under the new pricing tier. Compare it directly to what you would have paid under a per-seat model for the users who actually recorded.
* **Push for an annual cap:** If you proceed, negotiate a hard ceiling on your annual spend based on the per-meeting model. Protect yourself from unexpected spikes.
* **Question the "unlimited" seats claim:** Unlimited seats with a meeting cap is just a different form of licensing. It's a feature wrapper. Evaluate if you actually need that many editors, or if it's a marketing gimmick.
For small teams with low meeting volume, this might be a win. For any company with consistent recording needs across departments, this introduces financial uncertainty. I'd be preparing a cost-benefit analysis and exploring alternatives before my next renewal.
List price is for suckers
I'm a platform engineering lead at a 550-person SaaS company, and my team directly manages the procurement and integration of internal tooling like meeting recorders, which we use for sales enablement and engineering syncs across our global teams.
* **Predictability vs. Operational Variance:** Per-seat is a fixed cost; at my last shop, we budgeted $25/user/month for a similar tool. Per-meeting turns it into a variable utility bill. A single enterprise sales team can generate 300+ recorded meetings in a month; at a hypothetical $0.50 per meeting, that's $150 for that team alone, which can quickly surpass the flat per-seat cost and is subject to seasonal spikes.
* **True Cost Driver Alignment:** Per-seat aligns cost with headcount growth, which is relatively linear. Per-meeting aligns cost with meeting culture, which is exponential and often a policy issue. If you launch a company-wide initiative to "record all customer syncs," your finance department will need to model that as a direct cost increase, which changes the procurement conversation entirely.
* **Audit and Control Overhead:** With per-seat, I can sync our IdP (Okta) and deprovision seats monthly. With per-meeting, I now need to monitor a usage dashboard and potentially implement governance gates (e.g., "tag this meeting as billable") to control spend, adding operational toil. We saw a 20% admin overhead increase when we switched a different service to a usage model.
* **Vendor Incentive Structure:** A per-seat vendor is incentivized to improve user adoption broadly. A per-meeting vendor is incentivized to encourage more recording behavior, which can lead to feature development that prioritizes volume over quality. I've seen this manifest in "record by default" settings becoming harder to disable.
Given our need for predictable quarterly budgets and the fact we have a stable, growing employee base, I'd recommend sticking with a per-seat model if you can still negotiate it. If you're forced into per-meeting, your two most critical questions should be: what is your historical monthly meeting volume across all teams, and do you have the internal policy controls to prevent unbounded growth in that number?
infrastructure is code