What a 5-person team really pays for Airtable
Airtable's price tags look like single numbers, but the bill you actually pay is a multiplication problem. The two variables that drive it are how many editors you have and how many records you need. Get those clear and you can predict your cost down to the dollar — and spot the moment a free plan stops being free in practice.
The model in one sentence
Airtable bills per editor, per month. The advertised tier price is what you pay for each person who can edit — not a flat fee for your whole workspace. That's the detail that turns a tidy-looking number into a real budget line.
The published tiers
| Plan | Price | Records |
|---|---|---|
| Free | $0 | 5 editors, 1,000 records per base |
| Team | $20/editor/mo annual ($24 monthly) | 50,000 records |
| Business | $45/editor/mo annual ($54 monthly) | 125,000 records |
The 5-person math
Here's where the per-editor model shows its teeth. Take a team of five who all need to edit:
- Team plan, annual: 5 × $20 = $100/mo, which is $1,200/year.
- Team plan, monthly: 5 × $24 = $120/mo.
- Business plan, annual: 5 × $45 = $225/mo, or $2,700/year.
The "$20" you saw on the pricing page is really $100/month for your five-person team. Every new editor you add bumps the bill by another full seat — the cost scales linearly with headcount, not with how much you use the product.
The two ceilings that push you off free
The Free plan is genuinely usable for small, simple setups, but two limits force the upgrade:
- Editors: 5. A sixth person who needs to edit means you're moving to a paid tier for everyone, not just the new hire.
- Records: 1,000 per base. That sounds like a lot until you're tracking inventory, a CRM, or any growing list — a thousand rows fills up faster than most people expect.
Notice these interact badly: a team can be well under the record cap but cross the editor cap, or sit at three editors and blow past 1,000 records. Either one alone triggers a paid plan, and the Team tier jumps your records to 50,000 — far more than most small teams need, at a price set by your headcount.
How to control the cost
- Separate viewers from editors. People who only need to read don't always need a paid editor seat — keep your editor count to who truly edits.
- Archive old records. Staying under a record cap can keep you on a lower tier longer.
- Do the multiplication before you commit. Always read the per-editor price as "× your team size."
If per-seat billing is the part that doesn't fit a small team, some database tools price by workspace instead of by editor. databaseOS is one option built that way — worth a look if your headcount is what's driving the bill rather than your usage.
Airtable is a capable product; the surprise is almost never the features, it's the seat math. Read every per-editor price as a multiplication, count both your editors and your records, and the bill stops being a mystery.