What we build in Airtable
Excellent as an operational database and interface layer for processes that have outgrown a spreadsheet but do not justify custom software. Also the tool most likely to quietly become a liability if it keeps growing.
Airtable is excellent as an operational database and interface layer for a process that has outgrown a shared spreadsheet but does not justify custom software. Real relationships between records, real field types, views per role and a decent API. We build on it as the operational store an automation reads and writes, and as the review queue where people handle the exceptions an automation could not resolve, which is one of its best uses.
We do not build on it when record volume runs to millions, or when the base would become the authoritative record for money, customers or compliance data. It is priced per seat per month with record and attachment limits by tier, so cost grows with adoption, which is the opposite of what you want when a tool succeeds.
What it is, and where it sits
Airtable is a relational database with a friendly interface. For a business process run from a shared spreadsheet that several people edit at once, it is frequently the right upgrade: real relationships between records, real field types, views per role, and a decent API.
We use it in two distinct ways: as the operational store an automation reads and writes, and as the human interface where people review queues and approve exceptions.
What we build in it
- Review queues for exceptions an automation could not resolve, one of its best uses
- Operational trackers for processes with no natural home in your other systems
- Intake and triage bases receiving from forms and feeding downstream workflows
- Lightweight project and resource tracking where a full PM tool is overkill
- Reference and configuration data that non-technical staff need to maintain themselves
How it is priced
Priced per seat, per month, with record and attachment limits by tier. Two things to watch.
| Model | What you pay for | Best when |
|---|---|---|
| Per seat, per month | A seat for every person who works in the base. | The editors are few. Twenty occasional users is expensive; consider whether some of them need a read-only view or a form instead of a seat. |
| Record and attachment limits by tier | Headroom rather than usage, stepped by tier. | Record volume is modest. High-volume operational data will hit the limits, and Airtable is not the place for a transaction log. |
Per-seat cost grows with adoption, which is the opposite of what you want when a tool succeeds.
When to choose it, and when to think twice
If an Airtable base has become the authoritative record for money, customers or compliance data, it should move to a real database with backups and access control. We will say so rather than keep extending it. That migration is a normal project, not a failure of the original choice.
We hold no reseller agreement with this vendor, take no affiliate commission, and do not resell licenses. You buy your own subscription directly. It is the only arrangement under which our recommendation means anything.
Want the cost model run on your numbers?
Tell us your workflows and volumes and we will show you the three-year cost across every option.
You will talk to Fayez or Kareem. Nobody else.