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.
What it is, and where it sits
Airtable is a relational database with a friendly interface. For a business process living in a shared spreadsheet that three people fight over, 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.
Per-seat cost grows with adoption, which is the opposite of what you want when a tool succeeds. Twenty occasional users is expensive; consider whether some of them need a read-only view or a form instead of a seat.
Record limits are real. High-volume operational data will hit them. Airtable is not the place for a transaction log.
When it is the right choice
- A process has outgrown a spreadsheet but does not justify building software
- Non-technical people need to see and edit the data directly, every day
- You need a review-queue interface for automation exceptions and want it to look decent
- Record volume is modest — thousands, not millions
- The structure is still evolving and you want to change it without a migration
Limits worth knowing before you commit
- It becomes load-bearing. The most common failure: a base grows into the system of record for something important, with no backups, no access control discipline and no schema history.
- Record limits and performance. Large bases slow down, and the ceiling arrives sooner than people expect.
- API rate limits constrain high-throughput automation against it.
- Per-seat pricing punishes success.
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 licences. 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.