Airtable CRM: how to build a custom CRM in 2026?

Is Airtable really suitable for building a CRM?

Airtable is not a traditional CRM. That is precisely what can make it interesting.

A classic CRM offers a structure already designed around contacts, companies, opportunities, and sales activities. Airtable lets you build your own data model, interfaces, and workflows.

This flexibility becomes particularly useful when sales need to be linked to the rest of the operations.

In a B2B service company, a won opportunity can, for example, trigger an onboarding, a project, or transfer certain information to the Ops teams.

Airtable then allows you to link:

Company → Contacts → Opportunities → Projects

without recreating the same customer data in multiple tools.

Conversely, if your need primarily consists of tracking accounts, contacts, opportunities, emails, and meetings, building this experience in Airtable is not necessarily the best option.

The real question is therefore:

Does your process justify a custom CRM rather than a specialized CRM?

What architecture for an Airtable CRM?

A frequent mistake is starting from a template and then adapting your process to the resulting structure.

It is better to do the opposite: start from real business objects and their relationships.

Companies, contacts, and opportunities: the most common foundation

For a B2B business, a simple model often starts with:

Companies ↔ Contacts ↔ Opportunities

The Companies table represents the accounts.

The Contacts table represents the associated interlocutors.

The Opportunities table represents potential sales.

This separation avoids repeating company information on each opportunity and allows for managing multiple contacts or multiple sales over time.

This model remains a starting point, not a universal rule.

A very simple business might need fewer objects. A company selling multiple offers, contracts, or subscriptions might need more.

The right model is not the one with the most tables. It is the one that correctly represents the activity without complicating input and maintenance.

Should you create a table for interactions?

Not necessarily.

An Interactions or Activities table becomes useful if calls, meetings, or sales actions need to be tracked as real objects: assignees, statuses, automations, structured history.

Otherwise, a few fields on the opportunity may suffice:

• last interaction;

• next action;

• date of next action;

• assignee;

• important notes.

The goal is not to rebuild HubSpot or Salesforce in Airtable. It is to keep the information necessary to move opportunities forward properly.

When the CRM must also be linked to operations

This is often where Airtable brings the most value.

An agency or consulting firm can use:

Company → Contacts → Opportunities

during the sale, then link the won opportunity to the corresponding project:

Company → Contacts → Opportunities → Projects

The sales team works on opportunities. The Ops team works on projects. Both use the same customer data.

This avoids manually recreating information after signature.

This continuity from sales → delivery is one of the cases where Airtable becomes particularly relevant compared to a more traditional CRM.

How to build your CRM in Airtable step by step?

The order we favor is simple:

process → data → pipeline → interfaces → automations

1. Start from the sales process

Before building the tables, describe how the sales actually work.

For example:

Incoming Lead → Qualification → Meeting → Proposal → Negotiation → Won / Lost

Each stage must correspond to an observable situation.

For each one, ask yourself:

• what allows entry?

• what allows exit?

• who is responsible for it?

• what information must be available?

• what action must follow?

A "Proposal Sent" stage is concrete. A "Warm" or "To Follow Up" stage is much more ambiguous.

A well-defined pipeline matters more than the Kanban view that will display it.

To delve deeper into this topic: how to build a B2B sales pipeline.

2. Model only the necessary data

Once the process is clarified, identify the necessary objects.

For a B2B SME:

• Companies;

• Contacts;

• Opportunities.

Then potentially:

• Offers;

• Contracts;

• Projects;

• Activities.

Each table and each field must meet a need.

Adding industry, region, revenue, multiple scores, and fifteen qualification fields from the start because they "might be useful" often ends up creating a CRM that nobody fills out.

Start with the data needed to:

1. move the opportunity forward;

2. make a decision;

3. transmit useful information;

4. manage the activity.

3. Build the sales pipeline

The Opportunities table generally contains:

• the company;

• the main contact;

• the owner;

• the stage;

• the amount;

• the estimated closing date;

• the next action;

• its date.

Depending on your cycle, you can add the relevant offer, source, or reason for loss.

The important thing is to avoid fields added solely for reporting.

If a piece of information helps neither the salesperson to act nor the manager to decide, its presence is worth questioning.

4. Create Interfaces adapted to users

An Airtable CRM should not force everyone to work directly in the tables.

Airtable Interfaces allow you to build an experience tailored to each role on top of the same data.

A salesperson can have:

• their opportunities;

• their next actions;

• a company profile;

• an opportunity profile;

• deals without recent follow-up.

A manager can have the complete pipeline, at-risk opportunities, planned closings, or reasons for loss.

The underlying system is the same, but each user only sees what they need.

This is essential for adoption.

A CRM can be very well designed technically and still be bad if it forces users to navigate through useless tables, fields, and views.

The Airtable documentation details how Interface Designer works.

5. Add only useful automations

Once the process is stabilized, certain actions can be automated:

• create a task after a new opportunity;

• flag an opportunity with no next action;

• record a stage change date;

• create a project after a sale;

• transfer useful information to delivery.

Not all automations require the same architecture.

The rule is simple:

use the simplest layer capable of executing the workflow correctly.

If Airtable is enough, adding Make, n8n, or another layer does not automatically make the architecture better.

To go deeper:

• Airtable Automations

• Airtable API

• Airtable Webhooks

The same logic applies to AI: it becomes interesting when it handles a truly probabilistic task — summarizing, qualifying unstructured data, preparing research — and not just because you absolutely must "add AI" to the CRM.

Example: an Airtable CRM for a B2B service company

Let's take a consulting firm with four main objects:

Companies
Clients and prospects.

Contacts
Associated interlocutors.

Opportunities
Ongoing sales deals.

Projects
Missions carried out once the sale is signed.

A company can have multiple contacts, opportunities, and projects over time.

The sold offer can simply be carried by the opportunity if it does not justify a dedicated table.

When an opportunity moves to Won, Airtable can create the corresponding project.

The project remains linked to the original company and opportunity. The delivery team thus directly finds the contacts, the sold offer, and the information necessary for launch.

The salesperson works in their CRM interface. The Ops team uses their Delivery interface.

The value of the system comes less from the customizable pipeline than from the continuity:

sales → project → delivery

What are the limitations of Airtable as a CRM?

Airtable's flexibility is its main advantage, but also its main risk.

The email and calendar experience is less CRM-first

A specialized CRM can naturally integrate emails, meetings, and interactions into a contact's profile.

Attio, for example, allows you to sync Gmail, Google Calendar, or Microsoft 365 and link these interactions to the relevant people and companies. The official Attio documentation details this functionality.

With Airtable, this type of experience requires more design or integration.

If salespeople's daily activity relies heavily on their inbox, calendar, and relationship management, this gap can be decisive.

Customization can become difficult to maintain

Being able to quickly add a table, field, or automation does not mean you should do it.

A base can progressively accumulate:

• unused fields;

• hard-to-understand automations;

• duplicated data;

• overloaded interfaces;

• complex dependencies.

The CRM must therefore remain governed over time.

Your sales process evolves, certain data becomes useless, and new offers appear. A simple architecture is easier to evolve than a system that is over-built from the start.

Limits depend on the plan and volume

The number of records, automations, API usage, and certain governance features vary depending on the Airtable plan.

Before building a central CRM, estimate in particular:

• the number of users;

• the data volume;

• its growth;

• automations;

• integrations;

• permission needs.

Since limits and pricing are subject to change, we maintain them in our guide on Airtable plans and pricing.

Airtable or Attio: which one to choose for your CRM?

Airtable and Attio can both manage relational data and a pipeline, but their center of gravity is different.

Attio is primarily designed as a CRM and a Revenue platform.

Airtable is a more general platform for building business tools and operational systems.

A hybrid architecture can therefore use Attio for CRM / Revenue and Airtable for Delivery / Ops, with only the necessary data synchronized between the two.

But it should not become a default reflex. If a single tool properly covers the need, adding an extra layer mostly creates maintenance.

To compare the options more broadly: which CRM to choose for an SME in 2026?.

How much does an Airtable CRM cost?

The cost of an Airtable CRM is not limited to the license.

You need to consider:

• the Airtable plan and billable collaborators;

• the initial design;

• potential migration;

• automations and integrations;

• system maintenance.

Building a few tables is quick. Properly designing the data model, Interfaces, and workflows represents the real implementation work.

The more specific logic the system contains, the more its evolution must be anticipated.

Up-to-date Airtable rates are detailed in our article dedicated to Airtable pricing.

Should you build your CRM in Airtable?

Yes, if your process is specific, if the CRM needs to adapt heavily to your activity, or if sales need to be linked directly to operations.

Probably not, if you are primarily looking for a native CRM experience around contacts, opportunities, emails, calendar, and relationship history.

To define before choosing, if multiple teams need to share the same data or if the CRM must become a central piece of your information system.

In this case, start with:

process → objects → relations → responsibilities → interfaces → automations

then decide only what should live in Airtable.

This is also the approach used at HyperOps for CRM implementation or redesign projects: build the simplest system capable of properly covering real operations.

Frequently asked questions about Airtable CRMs