Airtable gets described as “a spreadsheet that thinks it’s a database,” which is close enough to be useful and wrong in the way that matters. It is a relational database with a spreadsheet interface, and the word doing the work is relational.
That single property is why teams love it and why some of them end up trapped in it. This review is based on Airtable’s documented capabilities rather than independent testing, and it is direct about where the product has moved away from the people who originally adopted it.
What Makes It Different
In a spreadsheet, a cell holds a value. In Airtable, a cell can hold a link to a record in another table, and that link is live in both directions.
So a Projects table can link to a Clients table. Open a client, and every project they own is listed there automatically — no lookup formula, no VLOOKUP breaking when someone inserts a column. Change the client’s name once and it updates everywhere.
Add to that typed fields — attachment, checkbox, single select, date, formula, rollup, user — and you get something spreadsheets genuinely cannot do without becoming fragile.
If you have ever maintained a spreadsheet where one tab referenced another and it broke when someone sorted it, that is the problem Airtable solves.
Core Features
Views
The same underlying data presented as grid, kanban, calendar, gallery, timeline or form. Each view has its own filters, sorts and hidden fields, and each person can have their own without disturbing anyone else’s.
This is the feature that gets teams to adopt it. The person running delivery sees a kanban; the person doing invoicing sees a filtered grid; both are looking at one dataset with no copies in circulation.
Interfaces
Airtable’s app-building layer — you assemble pages with charts, filtered lists and forms, and give people access to those instead of the raw base.
This matters more than it sounds. Handing a non-technical colleague a base with fourteen tables invites accidental damage. Handing them an Interface with three buttons does not.
Automations
Trigger on record created, updated, or on a schedule; then send email or Slack, update records, or run a script. Adequate for internal workflows, and less capable than a dedicated automation tool once conditions get complicated.
Formulas, rollups and lookups
Formulas work per-record. Rollups aggregate linked records — total value of all projects for this client, count of open tasks, latest delivery date. This is where the relational model pays off in reporting.
Sync and integrations
Bases can sync from other bases or external sources, so one team’s table can appear read-only in another’s. Useful; also a common source of confusion about which base is authoritative.
Where Airtable Is Genuinely Good
Structured operational data. Content calendars, applicant tracking, inventory, client rosters, event planning, product catalogues. Anything that is a list of things with attributes and relationships.
Replacing a spreadsheet that outgrew itself. The classic entry point, and the strongest use case.
Giving different people different views. No other tool in this space does it as cleanly.
Prototyping an internal tool. You can build something in a day that would take a developer weeks, and find out whether the process is right before anyone writes code.
Where It Struggles
It is not a project management tool. No native dependencies worth the name, no workload view, no personal cross-project task list. Teams that adopt it for project management usually add another tool within a year.
It is not a document tool. Long-form text in a cell is unpleasant. Notion is better if your work is mostly writing.
Record limits arrive faster than expected. Every plan caps records per base, and the caps are lower than people assume when they start logging events or line items rather than entities. Check the current limit against your realistic volume, not your starting volume.
Reporting is shallow. Charts exist; genuine BI does not. Teams needing real analysis export to a spreadsheet or connect a BI tool.
Permissions are coarse at the lower tiers. Field-level and record-level permissions sit on higher plans. Below that, someone with edit access can edit anything.
Pricing and the Direction of Travel
Priced per user per month across free, team, business and enterprise tiers, with record limits, automation run limits, attachment storage and permission granularity all scaling by tier.
Two structural things to understand.
Per-editor pricing shapes behaviour. Read-only access is cheaper or free depending on tier, but everyone who edits is a seat. Teams often discover the bill scales with adoption, which is exactly when they least want to restrict it.
Airtable has moved upmarket. Over recent years the product and its messaging have shifted toward larger organisations and app-building, and pricing and plan structure have changed more than once, generally not in favour of small teams. Several features that small businesses want now sit on higher tiers than they once did.
That is not a reason to avoid it, but it is a reason to check current pricing and limits directly rather than relying on anything written more than a few months ago — including this review, which quotes no figures deliberately.
The Lock-In Question
Worth thinking about before you build your business on it.
Your data exports cleanly to CSV. Your structure does not. Linked records, rollups, views, interfaces and automations have no portable format — moving to another tool means rebuilding all of it by hand.
The more Airtable does for you, the more expensive leaving becomes. That is true of most software, and it is more true here because the value is concentrated in structure rather than content.
Practical mitigation: keep a scheduled CSV export, and do not put anything in Airtable that you would be unable to reconstruct.
Who It Suits
Small teams with structured operational data currently living in a spreadsheet that keeps breaking.
Agencies and studios tracking clients, projects and deliverables with real relationships between them.
Content and marketing teams running editorial calendars where one piece links to a campaign, an owner and a channel.
Anyone prototyping an internal tool before committing engineering time.
Who Should Look Elsewhere
Teams wanting project management. Asana or monday.com. Airtable will frustrate you on dependencies and workload.
Teams whose work is writing. Notion.
Anyone needing a real CRM. You can build one in Airtable, and it will lack email integration, sequences and pipeline reporting. Use a CRM.
Very high record volumes. Check the limits before committing. Logging data will hit them.
Common Mistakes to Avoid
- Building it like a spreadsheet. If you are copying the same client name into forty rows, you have missed the point. Make a second table and link to it.
- Ignoring record limits until you hit them. They are per base and lower than most people expect. Plan your structure around them.
- Giving everyone edit access to the raw base. Build an Interface. Raw base access to non-technical users causes avoidable damage.
- Using it as project management. The absence of real dependencies and workload views will surface within months.
- No owner for base structure. Without one, you get fourteen near-duplicate views and three tables that should be one.
- Assuming you can export and move. Data exports; structure does not. Know what rebuilding would cost before you depend on it.
- Storing large attachments. Storage counts against your plan and gets expensive. Link to files in cloud storage instead.
FAQs
Is Airtable better than Excel or Google Sheets?
For relational data, yes — linked records and rollups do things spreadsheets cannot do reliably. For calculation, analysis and pivot tables, spreadsheets remain better. They are different tools that look similar.
Can Airtable replace a project management tool?
Not well. It lacks genuine dependency handling, workload views and a personal cross-project task list. Teams that try usually add a project tool within a year.
Is the free plan usable?
For a single person or a small base, yes. Record limits, automation runs, attachment storage and permissions are all constrained. Check the current caps against realistic volume before building anything important on it.
Is Airtable a real database?
It is a relational database with a friendly interface and an API. It is not a replacement for a production database behind an application — different performance characteristics, different guarantees, and record limits a real database does not have.
How hard is it to leave Airtable?
Data exports to CSV easily. Structure — links, rollups, views, interfaces, automations — has no portable format and is rebuilt by hand. Budget accordingly before you depend on it heavily.
Is Airtable or Notion better?
Airtable if your work is structured records with relationships. Notion if your work is documents and notes with some structure attached. Notion’s databases are weaker; its writing experience is much better.
Verdict
Airtable is the best tool available for structured operational data that has outgrown a spreadsheet, and linked records plus per-person views are a genuine capability that competitors do not match.
The honest reservations are record limits that arrive sooner than expected, a pricing and product direction that has moved toward larger customers, and structural lock-in that grows with how much value you get from it.
Adopt it for the thing it is good at. Do not let it quietly become your project manager, your CRM and your document store, because it is worse than dedicated tools at all three and harder to leave than any of them.
Key Takeaways
- Linked records are the whole product — if you are not using them, use a spreadsheet.
- Build Interfaces for non-technical users rather than exposing the raw base.
- Record limits are per base and lower than most people expect. Check before committing.
- Data exports cleanly; structure does not. Lock-in grows with usefulness.
- It is not a project management tool, a CRM or a document editor.
For the jobs Airtable is not built for, see our project management software guide and our Asana vs monday.com comparison.