Question 1

When is Airtable the right choice — and when is it the wrong one?

Accepted Answer

Airtable shines for internal operations: CRM for small sales teams, project and content tracking, inventory, intake workflows — anywhere you need structured data plus flexibility, fast. It is the wrong choice for high-volume transactional systems, customer-facing products with thousands of concurrent users, or anything needing complex row-level permissions. We will tell you honestly when custom software is the better investment.

Question 2

What are Airtable's limits that I should know about before committing?

Accepted Answer

The biggest ones are record caps per base — 50,000 on the Team plan, 125,000 on Business, 500,000 on Enterprise — an API rate limit of 5 requests per second, and permissions that work at base and table level rather than per row. None of these are dealbreakers for typical operations workloads, but they must shape the architecture from day one, which is exactly what we design for.

Question 3

How long does a typical Airtable project take?

Accepted Answer

A focused single-base build like a CRM or project tracker usually takes 1–2 weeks. A multi-base operations platform with automations, integrations, and a client portal typically runs 4–6 weeks including data migration and parallel testing. Compare that with 3–6 months for equivalent custom software.

Question 4

Can external clients use the system without us paying for Airtable seats?

Accepted Answer

Yes — that is usually the main cost question. Anyone who edits inside Airtable needs a paid seat, but external users can submit data through forms and view or update their records through a Softr portal that authenticates them separately. For a client-facing workflow this routinely saves hundreds of dollars per month in seat costs.

Question 5

Can Airtable replace our CRM or ERP?

Accepted Answer

For a small-to-mid-size sales team, an Airtable CRM tailored to your exact pipeline often beats a generic CRM you only use 20% of. A full ERP is a different story: payroll, double-entry accounting, and regulatory reporting belong in dedicated systems. The sweet spot is Airtable as the operations layer, integrated with your accounting tool rather than replacing it.

Question 6

How do Airtable automations work, and where do they fall short?

Accepted Answer

Native automations are trigger-action rules — record updated, send email, create record — with a quota of automation runs per month that depends on your plan, and a cap of 50 automations per base. For multi-step logic, branching, or talking to external APIs reliably, we move that work to Make or n8n, which also gives you execution logs and retry handling that native automations lack.

Question 7

Is our data safe in Airtable? What about compliance?

Accepted Answer

Airtable is SOC 2 Type II certified, encrypts data in transit and at rest, and offers SSO and admin controls on higher plans. The practical caveats are data residency — hosting is US-based — and the coarse permission model, which we work around with synced bases and portal-level access control. For strict regulatory environments we will flag early whether Airtable fits.

Question 8

What happens if we outgrow Airtable?

Accepted Answer

That is a feature of how we build, not a crisis. Because we design proper relational schemas, exporting to PostgreSQL and rebuilding as a custom app later is a structured migration, not an archaeology project. Many clients run on Airtable for two or three years, validate their processes cheaply, and migrate only the parts that hit real limits.

Airtable Solutions
FAQ

Helpful
information

Getting Started

Timeline

Pricing

Support

Still have questions?

Airtable SolutionsFAQ

Helpfulinformation