Airtable as a Lightweight CRM: Structure, Views and Limits
Many small and mid-sized businesses track leads in a chat app, a spreadsheet and somebody's memory. A full CRM feels heavy; a spreadsheet is fragile. Airtable sits between the two: it looks like a spreadsheet but behaves like a small database.
This article shows how to structure it for lead tracking, which views to build, and where it stops being the right answer. It is a guide for the person deciding, not a product pitch.
Why a flat sheet breaks
A single sheet with one row per lead works until the first repeat customer. Then you copy their details into a second row, and now two rows disagree. Notes pile up in one cell. Nobody can see which leads belong to which campaign or owner.
The cause is that a lead, a company, an interaction and a deal are different things squeezed into one table. A database keeps them apart and links them.
A four-table structure
- ContactsOne row per person
- CompaniesOne row per organisation
- InteractionsEach call, message or meeting
Links run both ways. A contact sees its deals; a deal sees its contact.
In Airtable, you connect tables with a linked-record field, which creates a matching field in the other table. Lookup and rollup fields then show values from linked records without copying them. Check the support documentation on linked records for the exact options.
Resist the urge to add every field you might one day need. Each extra field is something a person must fill in, and empty fields make views unreliable. Start with a few fields per table. A source field (which campaign or channel the lead came from) is the most valuable one, because it connects your CRM back to your advertising.
Views that do the work
A view is a saved filter, sort and layout over the same data. Build views for questions, not for decoration, and name each one after the question it answers.
Pipeline
Deals grouped by stage, so you see where they stall.
Follow-ups due
Records whose next-contact date is today or earlier.
By owner
Each person sees only their own work.
New this week
Leads waiting for a first reply.
Lost and why
A reason field makes losses countable.
If nobody opens a view weekly, delete it.
For people who should not see the whole base, Airtable's interface tools let you present a simplified layer over the data. Check the current documentation for which layouts and permissions your plan supports.
Illustrative example, not real results
Assume 40 new leads a day for 30 days: 40 x 30 = 1,200 contacts a month. If each lead gets about three logged interactions, that adds 3,600 records, so about 4,800 records a month in total. After 12 months at that pace: 4,800 x 12 = 57,600.
Airtable limits the number of records per base, and the limit depends on the plan; at the time of writing the support documentation lists a cap that grows with plan tier. Check the current figure for your plan. The point of the arithmetic is that interaction logs, not leads, fill a base fastest, so decide early what you log and what you archive elsewhere.
Limits and when to choose something else
- Record caps. As above, plan limits apply per base, across all tables.
- Scale and permissions. Complex role-based access, audit trails or thousands of daily users point to a dedicated CRM.
- Heavy reporting. Airtable can summarise, but deep analysis is better done in a reporting layer; see the executive dashboard guide.
- Data discipline. Airtable does not stop people entering messy data. Use single-select fields and required checks where you can.
- Personal data. Customer data may carry legal duties where you operate. Confirm them with a qualified adviser.
Implementation steps
- Write the questions you want the CRM to answer.
- Create the four tables and the links.
- Add only the fields needed for those questions.
- Build the five views.
- Feed it automatically from forms, ads or chat. See what n8n can automate and WhatsApp lead qualification.
- Review the structure after a month of real use.
Measurement and its limits
A CRM tells you what was recorded, not what happened. Source fields depend on people choosing them, or on tracking parameters passing through; see UTM naming. Conversion rates by source are only as reliable as the volume behind them.
Next step
Start with the questions and the four tables on paper. If you want the base built and connected to your lead sources, the Airtable CRM service covers it.