Start with the sales question the base should answer
For an illustrative small consultancy, the immediate question is which open opportunities need a follow-up this week. Start with the fields needed to answer that question: a company, contact, deal stage, responsible person, and next action date. Leave elaborate forecasting formulas until the team agrees what each stage means.
Choose a few sample deals that expose different relationships. One company may have two contacts and several opportunities. One contact may leave a company. A repeated company name in a spreadsheet is not enough to establish how those changes should propagate through the CRM.
Create companies, contacts, and deals as linked records
Airtable linked-record fields connect records across tables and create a reciprocal relationship. Lookup fields can display information from linked records. This supports keeping a company's main details in one place while referring to that company from contacts and deals.
Create the three tables, then link actual sample records. Adding a linked-record field does not by itself identify which old rows refer to the same business. Decide how to reconcile inconsistent company names during an import rather than creating several nearly identical company records.
| Table | One record represents | Useful relationships |
|---|---|---|
| Companies | A customer organization | Contacts and deals |
| Contacts | A person the consultancy communicates with | Current company and relevant deals |
| Deals | One specific opportunity | Company, main contact, and owner |
Define stages and next actions separately
Give each stage an observable meaning. For example, Proposal sent should mean the proposal was actually delivered, not that someone intends to write it. Keep next action and next action date separate from stage so a deal can remain in negotiation while its owner schedules a concrete follow-up.
Use the sample records to walk through a postponed call, a lost deal, and two active opportunities at the same company. The company record should remain useful after one opportunity closes. If every update requires editing several copies of a company address, revisit the linked model before adding automation.
Add one follow-up automation with an explicit boundary
Airtable automations combine a trigger and one or more actions. Its documentation explains that newly enabled automations do not automatically process all matching existing records, and that records leaving and re-entering a triggering view may run again. Both successful and failed triggered runs count toward applicable usage limits.
For the consultancy, start with an internal follow-up reminder rather than an automatic customer email. Define who receives it, what makes a deal eligible, and how repeated reminders should behave. Test an overdue deal, a closed deal, and a deal whose date changes. Plan an explicit backfill if imported opportunities also need an initial action.
Check permissions separately from filtered views
An interface can present a focused workflow, but interface permissions and base permissions need separate review. Airtable documents different sharing capabilities and plan requirements for interfaces. A filtered record picker or a cleaner screen should not be treated as proof that someone lacks access to the underlying records.
Write a simple sharing requirement for the sales assistant, the consultancy owner, and any external collaborator. Test with the actual access type each person will receive. Confirm whether they can open the base, edit linked records, or see unrelated opportunities before sharing a CRM populated with real contacts.
Use a small operating routine to keep the CRM accurate
Have the deal owner review missing next actions and stale opportunities at a regular interval. Add a short description to fields that people interpret differently. Keep automation ownership visible so someone can inspect failures or update a reminder when the sales process changes.
Airtable is worth evaluating when the team benefits from flexible records and can maintain a shared structure. The first useful milestone is a trustworthy list of deals needing action, backed by clear relationships and appropriate sharing. More fields and automations are valuable only when they help the team answer that question consistently.
Sources and editorial method
Official sources linked in this guide were checked on October 27, 2026. Features, interfaces, and commercial limits can change. The examples are proposed workflows and illustrative calculations, not customer results or a hands-on product benchmark. Confirm the current documentation before implementing the workflow.