Having evaluated numerous SaaS analytics platforms, I find MeetGeek's pricing model, like many others, employs a tiered "per seat" structure that isn't immediately transparent. The core confusion stems from what constitutes a "seat" versus a "license," and how features are gated across tiers (Starter, Pro, Business). Based on my team's procurement process and a detailed review of their current pricing page, here is a breakdown.
The fundamental unit is the **host seat**. Anyone who needs to *schedule* meetings where MeetGeek will be the designated recorder requires a paid seat. However, the model is not strictly 1:1 for consumption. Key nuances include:
* **Attendee Access vs. Editor Roles:** Guests or regular attendees who simply receive summaries or recordings do **not** count as seats. The cost escalates when you require team members to have editing capabilities—for example, to highlight key moments, edit transcripts, or manage the knowledge base. These are often termed "editor seats" or "contributor seats" in higher tiers.
* **Tiered Feature Allocation:** The per-seat monthly cost unlocks different ceilings of usage and features **per seat**, not per account. For example:
* **Starter:** A seat might include AI summaries and transcripts, but with a monthly cap on total recording minutes *per user*.
* **Pro/Business:** The cap increases or is removed, and features like video recording, custom branding, and advanced integrations (e.g., Slack, Notion) become available. Crucially, some tiers grant access to "Shared Libraries," but editing rights for that library may require the more expensive seat type.
* **The "Team" vs. "Company" Distinction:** Lower tiers are often limited to a single "team" (a defined group of hosts). Scaling to multiple teams across the organization typically forces an upgrade to a "Business" or "Enterprise" plan, which carries a significantly higher per-seat cost but enables cross-team knowledge management.
From a data pipeline perspective, consider the cost implications for exporting data. While basic CSV export might be included, automated webhook integrations or direct API access for piping meeting metadata, transcripts, and analytics into a data warehouse (like BigQuery or Snowflake) are typically locked behind the highest tiers. This is a critical consideration for building reliable data products from meeting intelligence.
A practical example of cost calculation:
Let’s assume a 10-person engineering team needs meeting intelligence.
- Scenario A: Only 3 people schedule meetings requiring recording. They need basic summaries and transcripts. → You likely need **3 Pro seats**.
- Scenario B: Those same 3 schedulers, but now 5 other team members need to actively highlight and tag key moments across all recordings for a knowledge base. → You now need **8 Pro seats**, as the editors consume a seat.
- Scenario C: The above, plus you need to send all raw transcript data to your data lake for NLP analysis. → You now require **8 Business seats**, a substantial cost jump.
The salient point is that "per seat" is better understood as **"per privileged user,"** where privileges are defined by the need to schedule *or* edit/curate. Always map your anticipated user roles (Scheduler, Editor, Consumer) directly to the feature matrix of each tier before estimating costs. The headline per-seat price is rarely the final landed cost for a functional team deployment.
--DC
data is the product
You're right about the host seat being the trigger. The real cost isn't just the number of seats, it's the multiplier from the features you need per seat.
For example, the AI action items and video highlights are often feature-gated per seat on the Pro tier. If you need those, every host seat jumps to the higher price. Your "editor roles" point is spot on, that's usually the Business tier unlock.
Always check the recording hour limits per seat per month too. It's not unlimited.
Prove it with a benchmark.
Yeah, that feature-gating per seat is what caught our team too. It's not just about bumping everyone to Pro for one feature. You have to check if the feature you need is even available as an add-on in Starter, or if it's locked entirely behind the higher plan. That's the real seat multiplier.
So if you have a team of ten hosts, and just two need AI action items, do you still have to upgrade all ten seats to Pro? Or can you mix and match seat types within a team? The pricing page isn't super clear on that.
Great breakdown on the host seat being the core unit. Your note about **editor seats** is crucial, that's where the math gets tricky. On their Business tier, adding those editing permissions for just a few people can feel like you're paying for a second, invisible seat on top of the host license.
We got tripped up by the per-seat video storage limit. It's not pooled across the team, so if one person records a lot of long workshops, they can hit their cap while others have tons left unused. You can't reallocate those minutes.
Wait, the video storage isn't pooled? That's a big detail I missed. So if one team member hits their cap, they just can't record more that month, even if the team overall has spare minutes? That seems really inefficient.
And the editor seat thing is confusing. Does that mean on the Business plan, a host who also needs to edit meeting notes is essentially taking up two "slots" from a cost perspective, even though it's one person?
Spot on about the host seat being the trigger for pricing. Your breakdown of editor roles is exactly where teams get surprised. I'd add that the "license" term often gets used for the overall account subscription, while "seat" is the individual user slot inside it. That's why you can't mix Starter and Pro seats in one account - the license tier sets the features available for all seats. So if one host needs a Pro feature, the license jumps, and all seats get priced at that tier. It's a bundle.
ship it
You've hit the nail on the head about the "per seat, not per account" feature allocation, but I think the bigger trap is in the practical application. Let's say your Starter tier seat gives you 300 recording minutes per month. That sounds fine until you realize a single two-hour customer discovery call burns through 40% of that allotment. One intense week of back-to-backs and that seat is useless, while the sales rep next door, with a lighter schedule, has a surplus that evaporates.
The whole model banks on uneven consumption, but prevents you from smoothing it out. It's not just inefficient, it's designed to create friction that pushes you to buy more buffer seats you don't technically need. So you're not just paying for the host, you're paying for the peak usage of each host, independently.
Exactly, that's the core of the consumption trap. It mirrors the problem with some old-school data pipeline pricing where credits aren't pooled. You're provisioning for individual peaks, not team capacity.
I'd be curious if the unused minutes roll over. My guess is they don't, which makes the inefficiency even worse. You're incentivized to over-provision seats just to cover a few people's busy months, leaving a ton of wasted capacity on the table.
Makes you wonder if they'll ever offer a true team-wide pool of minutes as an enterprise add-on.
Yeah, the lack of rollover is a confirmed pain point. I asked their support directly last month, and they confirmed minutes are "use it or lose it" per seat each month.
That's what pushes you into buying a whole extra seat just as a buffer for your heavy recorders. It feels like you're buying insurance, not productivity.
I doubt we'll see a pooled minutes add-on anytime soon. That consumption trap is likely a core part of their revenue model, not an oversight.