Using Airtable as a CRM: When It Works and When You Need a Real CRM
Airtable is a very good database with a very good interface. That's most of what a CRM is, which is why using it as one works better than people expect.
It also isn't a CRM, and the gap shows up in specific, predictable places — usually around the time a business starts depending on it.
Here's where the line falls.
What Airtable genuinely does well
You design the structure. A CRM imposes a model of how sales works. If your business doesn't match it, you spend a year fighting the software. In Airtable you build what you actually need.
Views are excellent. Different people seeing different slices of the same data, without duplicating anything, is worth more day to day than most CRM features.
Linked records. Companies to contacts to projects to invoices, properly related rather than bolted together. Many entry-level CRMs handle this worse.
It's fast to change. Add a field, reshape a view, try a different structure. A CRM makes this a project.
People will actually use it. It looks like a spreadsheet, which is the interface most small businesses are already fluent in.
For a business with an unusual process, Airtable-as-CRM is often the right answer — and sometimes the right answer permanently.
Where it works well
You have a non-standard process. Project-based work, long custom cycles, something that isn't lead-to-deal. The flexibility is the point.
The team is small. Under about five people actively using it, the coordination problems stay manageable.
Volume is low to moderate. Hundreds of records, not tens of thousands.
Communication happens elsewhere, and that's fine. You're comfortable with email in your email client and the record in Airtable.
You need it to be more than a CRM. Inventory, projects and customers in one related structure is something Airtable does naturally and a CRM doesn't.
Where it stops working
1 · Communication history
This is the big one, and it's the one people discover late.
A CRM logs the emails, the calls, the messages, against the record. You open a contact and see the conversation.
In Airtable, that history lives in whoever's inbox. Two consequences, both expensive:
You can't see what was said. Picking up someone else's client means asking them, or searching your own email and finding only your side.
You can't tell when someone last heard from you. The most important question about any open opportunity, and the structure can't answer it.
You can log it manually. Nobody does, consistently, for more than a few weeks.
2 · Sending from the system
Replying from inside the record, from templates, with the reply logged automatically — that's core CRM behaviour and it isn't what Airtable is for.
For a business where most of the work is conversation, this is the point where the workarounds start costing more than a migration would.
3 · Automated follow-up sequences
Timed sequences — reminders, nurture, re-engagement — are standard in a CRM. Airtable can trigger things, and combined with an automation tool it can do a lot. But you're assembling what a CRM gives you configured, and you own every piece of it afterwards.
4 · Permissions at scale
Airtable's permission model works for a small team. Once you need per-record visibility — this person sees only their accounts — you're working against the design.
5 · Telephony and messaging
If your business runs on phone calls or WhatsApp, a CRM that captures them is a different category of tool. Nothing in Airtable closes that gap.
6 · Volume
Airtable has per-base record limits that vary by plan, and large bases get slow before they hit them. If you're heading for tens of thousands of records, check the current limits for your plan before committing — the figures change, and a base that grows past them is a disruptive migration rather than an upgrade.
The honest decision test
Five questions. Answer them about your actual business, not your intentions.
| Question | Airtable | CRM |
|---|---|---|
| Is most of your work conversation? | no | yes |
| Do several people need to see the same conversation history? | no | yes |
| Is your process unusual enough that standard CRMs don't fit? | yes | no |
| Do you need timed automated sequences? | no | yes |
| Is your record count heading past several thousand? | no | yes |
Mostly left: Airtable, and stop worrying about it.
Mostly right: a CRM, and the longer you wait the more history you'll fail to migrate.
Split: usually Airtable now with a known trigger for revisiting — "when we hire the third person," "when we pass five hundred open records."
If you're using Airtable as a CRM, do these
The same structural decisions a CRM would force on you. Airtable won't, which is the trade-off.
Define your stages as states, not tasks. A single-select field: Enquiry, Qualifying, Proposed, Negotiating, Won, Lost. Not "Send proposal."
Add a "last contact date" field and maintain it. This is the one that compensates most for the missing communication history. A view sorted by it tells you who's gone quiet.
Add "next action" and "next action date." With a view showing everything overdue. This is your actual to-do list.
Make lost reason a required single-select. The most valuable field in any CRM, and in Airtable you have to remember to add it.
Set up deduplication deliberately. Airtable won't stop you creating the same contact twice. Decide what makes two records the same and check periodically.
Use single-select, not text, for anything you'll report on. Source, status, type. Free text is unreportable and unfixable afterwards.
Build a "needs attention" view. No next action, or next action overdue, or no contact in X days. If the base only takes input and never tells you anything, people stop maintaining it.
The migration question
If you outgrow it, moving is real work — but less painful than people fear, with one exception.
The data moves fine. Contacts, companies, opportunities, all structured and exportable.
The history doesn't exist to move. Which is the point: if you'd had it, you probably wouldn't be migrating.
The automations rebuild. Whatever you assembled around Airtable doesn't transfer.
If you suspect you'll migrate eventually, two things make it cheaper: keep your structure close to standard CRM concepts, and avoid elaborate automation you'll have to rebuild.
The thing worth saying plainly
Using Airtable as a CRM isn't a compromise or a stopgap. For a lot of small businesses it's a better fit than an entry-level CRM they'd half-use.
The failure isn't choosing Airtable. It's choosing it, never making the structural decisions a CRM would have forced, and ending up with a flexible database that nobody maintains.
The tool was never the deciding factor. The decisions were.
Airtable is an excellent CRM for a business whose work isn't mostly conversation. Past that line, you're rebuilding a CRM by hand.
Not sure which side of the line you're on?
A free systems audit covers your current setup and whether the tool is actually the constraint.