Meeting Bot API Pricing: Per-Seat vs Per-Minute vs Pay-As-You-Go

The three models

Meeting bot APIs price their services three ways. Understanding the model matters before you commit, because the right choice depends entirely on your usage pattern.

Per-seat pricing

You pay a flat monthly fee per user or per "seat" in your application. Typical: $15–50 per user per month. Works well if every user has a predictable number of meetings. Gets expensive fast if your active users vary month to month, or if you have many users who rarely use the feature.

Per-bot-minute with session minimums

You pay per minute of bot time, often with a minimum per session (e.g., 15 or 30 minutes regardless of actual meeting length). A five-minute standup costs the same as a 30-minute meeting. At high volume, session minimums add up significantly.

Pay-per-second captured

You pay only for audio actually captured, rounded to the second. No minimums, no monthly fees. A five-minute meeting costs five minutes. A two-hour board meeting costs two hours. Predictable, proportional costs.

Which model wins at different scales

Under 50 meetings/month: All models are cheap. Choose based on predictability — a flat fee is easier to budget.

50–500 meetings/month: Pay-per-second starts pulling ahead, especially if your meetings vary in length. Session minimums become a material cost at this scale.

500+ meetings/month: Pay-per-second is almost always cheapest unless you have near-identical meeting durations and no variability.

Gregnote's model

Gregnote charges £0.50 per hour of audio captured. No seat fees. No session minimums. No monthly commitment.

At 500 one-hour meetings per month: £250 total. At 500 meetings with a 30-minute minimum pricing model at $0.01/min: $150 minimum fee + actual time.

The gap widens at scale and with shorter meetings.