Every Airtable renewal conversation we get pulled into starts the same way: "the bill went up again and nobody can explain why." It is almost never one big thing. It is a workspace that accumulated seats for contractors who left, a base shared with a client at editor level because that was the fastest way to unblock them, an AI field that quietly reprocesses ten thousand records a month, and a plan upgrade bought to unlock one feature that a different design would not have needed.
This tutorial is the audit we run for clients. It takes an afternoon, it needs no scripting, and on a mid-sized workspace it usually finds double-digit percentage savings without taking anything away from anyone who is actually working.
How Airtable charges you (the mental model)
Three things drive the invoice:
- Billable collaborators. You pay per person who can create or edit content, per workspace or organisation depending on your plan. Read-only and comment-only collaborators are generally not billed the same way as editors, and people who only ever open a shared view link or submit a form are not collaborators at all.
- Plan tier. Feature gates (sync sources, extensions, admin controls, advanced permissions, retention windows) live on the tier, and the tier multiplies the per-seat price across everyone.
- Consumption. AI credits and, on some plans, automation run allowances are pools that get drawn down. These are the line items that move without anyone making a purchasing decision.
The audit works through them in that order, because seats are the biggest number and the easiest to fix.
Airtable's plan names, limits, and credit allowances change. Treat the exact numbers in your billing settings as the source of truth and use this playbook for the method, not the figures.
Step 1: inventory every human
Open the workspace (or, on enterprise plans, the admin panel) and export or copy the collaborator list. Build a scratch Airtable base — Seat Audit — with one record per person and these fields:
| Field | Type | Notes |
|---|---|---|
Person | Single line text | Name |
Email | Watch for personal-domain addresses | |
Current access | Single select | Owner / Creator / Editor / Commenter / Read-only |
Last active | Date | From the admin panel if you have it |
What they actually do | Long text | One sentence, filled in by their manager |
Proposed access | Single select | Same options, plus Remove and Link only |
Annual delta | Currency | Seat price × change |
Doing this in a base rather than a spreadsheet is not showing off: you will want to link people to the bases they touch, and you will want a rollup of the savings at the end to justify the work.
If you are on a plan with an admin panel, pull last-activity dates straight from it. If you are not, approximate: check each base's collaborator list and the record revision history on your two or three busiest tables. Someone who has not appeared in revision history in ninety days is a candidate.
Step 2: sort people into the four access patterns
Most workspaces have four kinds of user, and only the first genuinely needs a paid editing seat.
Builders and editors. They create fields, edit records, build automations. Keep them. This is the seat you are happy to pay for.
Record updaters. They change a status, add a note, upload a file — always in the same handful of views. Many of these people do not need base access at all: an Interface with a restricted set of elements, or a form, covers the job with far less risk of someone deleting a field by accident. Whether that removes the billing depends on your plan's access model, so check your own tier before promising a saving — but even where the seat still counts, the drop in blast radius is worth the change.
Readers and reporters. They open the base to look at a dashboard once a week. Downgrade to read-only or comment-only, or send them a shared view link (optionally password-protected and with download disabled). Viewers of a shared link are not collaborators.
Externals: clients, contractors, agencies. The default instinct is to add them as editors on the whole base. Do not. Use a shared view scoped to their records, an interface with row-level filtering, or a form plus a portal pattern. See our guide to Airtable client portals for the mechanics.
Fill in Proposed access for everyone before you change anything. Changing access field-by-field as you go is how you lock out the finance director on a Friday afternoon.
Step 3: find the seats nobody is defending
Run these five checks. In our experience they account for most of the waste.
- Leavers. Cross-reference the collaborator list against your HR list or shared drive. Offboarding processes routinely miss Airtable.
- Contractors past end-of-engagement. Any project-based collaborator whose project closed. Put a
Remove ondate on future ones and an automation to remind you. - Personal email domains. Often ex-contractors or people who signed up with a personal account and got invited twice. Two accounts, two seats, one human.
- Duplicate workspaces. Seats are counted per workspace on non-enterprise plans, so the same person in three workspaces can cost three times. Consolidating bases into fewer workspaces is frequently the single largest saving available.
- Service accounts. An integration authenticated as a departed employee is both a billing and a continuity problem. Move integrations onto a dedicated account with a personal access token that has narrow scopes — see our API quickstart.
Step 4: challenge the plan tier, not just the headcount
Upgrades are usually bought to unlock one capability. Write down, for each tier-only feature you rely on, what you would do without it:
- Sync from more sources — could the same data arrive via a scheduled automation or a script that upserts rows?
- Extensions on a dashboard — is that chart now buildable in Interface Designer, which is available more widely?
- Longer revision and snapshot history — is the real requirement a compliance retention period, in which case an automated export to your own storage is a better answer than paying per seat for retention?
- Advanced permissions — is the need field-level control, or would splitting one over-shared base into two bases with a sync between them do it?
Sometimes the honest answer is that the tier is worth it. But multiply the delta by every seat in the workspace before you decide; a feature that costs one person's licence is cheap, and the same feature across 120 people is a project budget.
Also check the reverse direction: annual billing versus monthly, and whether seats bought during a busy quarter are still needed at renewal. Seat counts on annual plans are easiest to reduce at the renewal date, so run this audit sixty days before renewal, not the week after.
Step 5: get AI credits and automation runs under control
Consumption is the line item that grows on its own. Three habits keep it flat:
Know what is running. List every AI field, AI-powered automation step, and agent in the workspace, with the table it sits on and roughly how many records a month it touches. Anything pointed at a high-volume table deserves a second look.
Stop accidental backfills. Creating an AI field over a table with 40,000 historical records can process all of them. Add the field against a filtered view, or with the trigger set to manual, then backfill deliberately in batches.
Do not pay a model to do arithmetic. If the logic can be expressed as a formula or a conditional rollup, it should be. Reserve AI for the parts that require reading prose. Our post on AI field agents covers the prompt and QA side of the same trade-off.
For automations, the equivalent waste is a scheduled run that fires every fifteen minutes to find nothing. Switch polling schedules to record-triggered or webhook-driven patterns where the platform supports it, and widen the interval where it does not.
Step 6: apply the changes safely
Work through Proposed access in one sitting, in this order:
- Remove leavers and duplicate accounts.
- Downgrade readers to read-only or comment-only, and tell them the same day, with the shared-view link that replaces their old access.
- Move externals onto interfaces or shared views.
- Consolidate workspaces last — it is the highest-value and highest-disruption change, so do it with a plan and a comms note.
- Recheck ownership: every base should have at least two people who can administer it. Cost-cutting that leaves one person holding every owner seat is a continuity risk, not a saving.
Then record the new baseline: seat count, tier, credit allowance, monthly cost. Put the numbers in the Seat Audit base so next quarter's audit starts from evidence instead of memory.
Step 7: make it stick
The bill creeps back within two quarters unless something owns it. The lightweight version of governance:
- A named owner for Airtable licensing, usually whoever owns the ops stack.
- A request path. A small Airtable form: who needs access, to which base, to do what, until when. Ironically, this is the easiest thing in the world to build in Airtable, and almost nobody does it.
- An offboarding checklist item that names Airtable explicitly.
- A quarterly fifteen-minute review of the collaborator list and the AI usage screen, scheduled sixty days before renewal so there is time to act.
A worked example
A 90-person operations team came to us at £/seat pricing on a mid tier across four workspaces. The audit found 14 leavers and ex-contractors still active, 9 people duplicated across two workspaces, 22 read-only consumers of a single dashboard who were on editing seats, and one AI field on a 60,000-record table that had been enabled "to try it out" six months earlier. Removing the leavers, consolidating three workspaces into one, moving the dashboard consumers to a shared interface, and scoping the AI field to a filtered view cut the annual spend by roughly a third — and, incidentally, reduced the number of people who could accidentally delete a table from 87 to 11.
The savings are nice. The permission tightening is the part that stops you needing our project rescue team later.
BaseBrainers runs seat and architecture audits for Airtable workspaces of every size, and builds the interface and portal patterns that let you cut editing seats without cutting anyone's access to the work. If your renewal is coming up, get in touch.