How Many Seats Do We Need Software? A Guide

The short answer to "how many seats do we need software" for a meeting notetaker is: fewer than it looks like on paper. Count the people who own or start a meeting the tool has to join, not everyone who happens to sit in on one. In most teams that number is well under the full headcount, because attendees can read a shared summary afterward without ever logging into the tool themselves. The rest of this guide walks through which roles actually need a seat, which don't, and how to size a plan on real usage instead of a department list that is already out of date.

What "Seat" Actually Means in Meeting Software

Before you count anyone, it helps to know what you are counting. Most AI notetakers sell access one of three ways: per-seat (one license per named person, whether or not they use it that week), per-meeting (the tool is billed by meetings recorded rather than people invited), or a mixed model where a small number of full seats can invite unlimited free viewers into a shared workspace. These are not interchangeable, and picking the wrong one is how teams end up either overpaying for logins nobody opens or hitting a wall the first month someone new needs access.

A "seat" in this category almost always means the ability to connect the notetaker to your calendar, send it into a meeting as a bot, and manage your own recording settings. Reading a transcript someone else generated is a different, usually free, kind of access. That distinction does most of the work in the rest of this guide, so it is worth confirming in whichever plan you are actually looking at rather than assuming it works the way the last tool you used did.

How Many Seats Do We Need Software For, and Who Actually Uses One

Three questions sort almost every person on a roster into "needs a seat" or "doesn't":

1. Do they start or own meetings the tool needs to join, or do they only attend ones someone else scheduled? Owners need seats. Regular attendees usually don't, because they can read the output without one.
2. How often do they show up in a recorded meeting? Someone in three recorded meetings a week is a different case from someone who drops into one a quarter. Occasional attendees are the group most teams over-provision by default.
3. Do they need account-level features such as connecting a calendar, setting their own retention rules, or exporting to a CRM? If the answer is no, a shared or read-only view usually covers them, and what that view looks like from the attendee's side is covered in what participants see when an AI notetaker joins a meeting.

Run every name on your team roster through those three questions before you open a pricing page. It is a slower first step than just buying one seat per employee, but it is the step that keeps the bill matched to actual use six months in.

A Simple Headcount Method You Can Run in Ten Minutes

You don't need a formula for this, just a short audit:

1. List the recurring meetings the tool would actually touch (standups, client calls, planning sessions, one-to-ones you plan to record).
2. Mark who owns or starts each one. That person is a seat candidate.
3. Mark who only attends. They are a viewer candidate, not a seat candidate, unless the plan you're considering has no free viewer tier at all.
4. Count the unique owners across your list. That is your baseline seat number, not your total headcount.
5. Add a small buffer for people about to start owning meetings (a new manager, a growing sales team), rather than sizing to today's org chart alone.

If you're still comparing tools rather than sizing an existing one, matching plan features to team size is part of a wider decision covered in how to choose an AI meeting note taker. And if this is a first rollout rather than an expansion, phase the seats in with the team the same way a phased team rollout works, which is walked through in rolling a notetaker out to a team of five to twenty. Seat count and rollout pace are usually the same decision, not two separate ones.

Seat-Based vs Per-Meeting Pricing: Which Fits a Small Team

If your team runs a handful of recorded meetings a week, per-seat pricing can cost more than it needs to, because you're paying for standing access rather than actual use. Per-meeting or credit-based pricing can work out cheaper here, at the cost of less predictable monthly billing.

Vendors also build in constraints worth checking before you assume a plan will fit your headcount at all. Fathom's own pricing page (read September 18, 2026) sets a two-user minimum on both of its team-level plans, which matters if your seat count is genuinely one or two people and you were hoping to start smaller. Fathom's pricing page is worth reading directly rather than assuming from a features comparison chart, since minimums like this are easy to miss until checkout. On the admin side, Otter.ai's own pricing page (read September 18, 2026) lists bulk user management as a feature of its team tier, which is the kind of control that makes adding and removing seats later a lot less painful than doing it one login at a time. Otter.ai's pricing page is the primary source for what that tier currently includes, and it's worth confirming directly since plan features change.

Neither model is universally cheaper. The right one depends on your ratio of owners to occasional attendees, which is exactly what the headcount audit above is for.

Common Seat-Counting Mistakes

A few patterns show up repeatedly:

• Buying a seat per department instead of per person. "Sales needs access" is not a seat count. Someone still has to name the actual owners.
• Treating occasional attendees like owners. Someone who shows up to a monthly all-hands and just wants the action items afterward doesn't need a seat; they need the summary, which is exactly what a good notetaker output is built to hand off, as covered in turning a transcript into action items people actually do.
• Sizing to the org chart instead of who actually starts meetings. Job titles are a poor proxy for who owns recorded meetings day to day.
• Forgetting to remove seats when people change roles or leave. Seats rarely get reclaimed automatically; someone has to go back and free them, and skipping that step is the most common reason a team's bill quietly outgrows its actual headcount.

A Worked Example: A Twelve-Person Team

Say a twelve-person team is adopting a notetaker. Three people run client calls and own those recordings. Two managers run their own one-to-ones and want their own retention settings. One person coordinates a weekly cross-team sync. The other six attend meetings regularly but never start one and are happy reading a shared summary afterward.

Run that group through the three questions above and the seat count is six, not twelve, plus however many free or viewer-level accounts the plan allows for the rest. That is an illustrative example to show the method, not a claim about what any specific team will need. Your own ratio of owners to attendees will differ, which is exactly why the audit matters more than any rule of thumb.

When to Revisit Your Seat Count

Seat counts drift, in both directions. Review the list at least once a quarter, and immediately after any team reorganization, a new hire who will own meetings, or a role change that moves someone from attendee to owner. The same review is a good moment to check that departed employees' seats were actually freed rather than left billing quietly in the background.

FAQ

Does every meeting attendee need their own seat?
No. Most notetaker plans separate the person who owns and starts a recording from the people who only attend and read the output afterward. Only owners typically need a full seat.

What's the difference between a seat and a license?
In practice they're usually the same thing: one seat equals one paid login tied to a person. Some vendors add a separate free or view-only tier that isn't counted as a seat at all.

Can someone without a seat still see the meeting notes?
Often yes, through a shared workspace or a link the owner sends, depending on the plan's workspace-visibility settings. Confirm this in the specific tool's settings rather than assuming, since it varies by vendor.

Should we buy per-seat or per-meeting pricing?
It depends on your ratio of meeting owners to occasional attendees and how many meetings you actually record in a typical week. Teams with few recorded meetings and infrequent use often do better on a per-meeting or credit model; teams with several people owning recordings daily usually do better on seats.

How often should we recheck our seat count?
At least quarterly, and right after any reorg, new hire, or role change. Seat counts drift upward mostly because nobody removes a seat when someone stops needing it, not because teams deliberately over-buy.