Has your business outgrown Airtable, and is it time to build your own app?

By Ranjit Bhinge, founder of Blur Studio · Updated · 6 min read

Short answer: Airtable, an online database that looks like a spreadsheet, is outgrown when you keep hitting its published limits on records, automation runs or seats, when per-seat cost climbs with every hire, or when customers need to log in to something it was not made for. Count those five things first. If only one is a problem, work around it. If three or more are, plan a staged move to a custom app, and keep Airtable for the parts it still does well.

Ranjit Bhinge

Airtable is getting slow, expensive or awkward for your team, and you want to know whether it is time to build your own app and how to move without breaking the business.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

The short answer

Airtable is a very good tool up to a point. It lets non-technical people build a database with forms, views and simple automations. Many businesses run happily on it for years.

You have outgrown it when the cost, the limits or the shape of what you need stops matching what it was built for. Do not decide on a feeling. Count five things, then use the rules in this article.

Five things to count before you decide

1. Records per base

A record is one row, such as one customer or one order. Airtable's help center lists record limits per base by plan: 1,000 on Free, 50,000 on Team and 125,000 on Business, as of November 2026. Enterprise Scale is quoted by Airtable's sales team. Count your largest base today and look at how fast it grows each month.

Trigger: you are above about 70 percent of your plan's limit and growing, and the next plan up costs a lot more.

One trap: Airtable's sync feature, which copies records from one base to another, counts synced records toward the destination base's limit. A setup that spreads data over many bases can still hit the cap.

2. Automation runs

An automation is a "when this happens, do that" rule. Airtable lists monthly run limits per workspace: 100 on Free, 25,000 on Team and 100,000 on Business. Check your usage page and see how many you used last month.

Trigger: you regularly use most of your monthly runs, or you have started deleting automations to stay under.

3. People and cost per seat

Airtable's pricing page shows Team at $20 per user per month and Business at $45 per user per month when billed annually (as of November 2026). Monthly billing is higher: $24 and $54. Airtable says Team bills anyone with Commenter permission or higher, while self-serve Business bills Editors and above, so check which of your people count as paid seats, since that changes the math.

Worked example (made-up business): A 25-person logistics firm has 15 people who edit data.

PlanSeatsPer yearOver 3 years
Team, billed annually15$3,600$10,800
Business, billed annually15$8,100$24,300
Business, 25 seats after hiring25$13,500$40,500

The figures are simple multiplication from the published per-seat prices and an invented headcount. Compare the 3-year total with a one-time build plus hosting. If you are not sure how to weigh that, my build or buy software guide shows the method.

Trigger: the per-seat bill grows faster than the value, or you want to give access to many occasional users.

4. Integrations and speed

If other software talks to Airtable through its API (the way programs exchange data), there are limits. Airtable's developer page lists 5 requests per second per base, and 50 requests per second per user token. When you go over, requests fail with a 429 error and you must wait 30 seconds.

Trigger: your integrations hit that wall, or a big base takes a long time to load and your team notices.

5. What you need it to be

Airtable is a database with simple screens. It is not meant to be a polished customer-facing product with logins, payments, custom rules and your own branding.

Trigger: you are bending Airtable into a customer portal, a marketplace or an app people pay for.

Score it

Triggers hitWhat I would do
0 or 1Stay. Fix the one problem: archive old records, trim automations, remove unused seats.
2Stay for now, but get a build estimate so you know your options.
3 or morePlan a staged move to a custom app.

Things that look like outgrown but are not

  • A messy base. Fifteen linked tables with duplicate fields run slowly and confuse people. Clean first.
  • Old records you never use. Archive them to a CSV file and the record count may drop below the limit.
  • Wrong plan. Sometimes one plan up is cheaper than a rebuild. Price it.
  • A missing view or interface. Often what you need is a better screen, not a new system.

For other tools in the same space, see Airtable alternatives. That covers ready-made options if you want a cheaper subscription instead of building.

Three ways to go

  1. Stay and tune. Cheapest, and often right.
  2. Move to a different ready-made tool. Fits when your needs are standard and cost is the main pain. Another no-code tool has its own limits, so read my no-code versus AI app builders comparison first.
  3. Build a custom app. Fits when per-seat fees, limits or the customer-facing need are the main pain, and the process is stable enough to write down.

The hybrid option, which many should pick

You do not have to move everything. A good split is:

  • Keep in Airtable: internal planning boards, small lists, one-off projects, content calendars, anything under a few thousand records that only staff touch.
  • Build custom: the busy core data, the customer-facing screens and anything that needs strict permissions or payments.

This keeps the cost of a build small, because you build only the parts that hurt. For more on small in-house systems, see internal tools. If all you need is reporting from a base, a dashboard without coding may be enough.

How to migrate in stages

A big-bang switch, where everyone changes on one Monday, is the riskiest way. Use stages.

  1. Inventory (days). List every table, every automation, every integration, every form and every person who uses each. Mark which ones matter.
  2. Clean (days to a week). Remove duplicates, fix blank fields, agree what each field means. Moving a mess just gives you a new mess.
  3. Export a copy. Check Airtable's help center for the export steps on your plan, and make sure attachments and linked records come across. Keep this copy as a safety net.
  4. Build the one painful workflow first. Pick the table or process that causes the most pain, not the easiest. It proves the approach.
  5. Run both in parallel (2 to 4 weeks). Staff enter data in the new app while Airtable stays as the backup. Compare totals each week. Fix differences.
  6. Cut over one group at a time. Move the office first, then field staff, then customers.
  7. Keep Airtable read-only for a while. Cancel the paid plan only after a full business cycle, such as one month-end, runs cleanly.

Write down a pass or fail check for each stage. For example: "All 12,400 customer records match, and 25 random ones are identical by hand." The same discipline applies to scoping any build, so see how to scope a small business software project.

What to ask a builder

  • Who owns the code, the data and the hosting account at the end?
  • How will my Airtable data, files and links be imported, and how will we check it?
  • What does hosting cost each month, and what happens if you stop working with me?
  • How are permissions handled, so each person sees only what they should? OWASP, a nonprofit that publishes software security guidance, ranks Broken Access Control first in its 2021 Top 10, so this question matters.
  • What does phase 1 include, and what is left for later?

Who should not build

  • Teams under a handful of people with a stable, small base.
  • Anyone whose process changes every month.
  • Anyone with no one available to answer questions during the build.

How I'd approach this

Do not leave Airtable because it feels limited. Count the five things above and put a price on each. Most of the time the right answer is smaller than a full rebuild: clean the data, trim the seats, and build only the screen or portal that Airtable cannot do.

When a move is right, I like to start with the single table that hurts most, run the new and old side by side for a few weeks, and keep Airtable read-only until month-end has passed once. Slow and boring beats clever, because your data is your business.

Come with your record counts, your seat count, last month's automation runs and a list of what annoys your team. That is enough for me to tell you whether to stay, hybrid or build.

Questions people ask

What is the Airtable record limit and what happens when I hit it?

Airtable lists 1,000 records per base on Free, 50,000 on Team and 125,000 on Business, as of November 2026. Check Airtable's plans page for the current numbers and for what happens at the cap. Archiving old data or splitting bases can help, but synced records still count toward the destination base.

Is Airtable too expensive for a growing team?

It can be, because it charges per seat. At the published annual prices of $20 (Team) and $45 (Business) per user per month, 15 editors on Business is $8,100 a year. Compare that with a one-time build in build or buy software.

Can I build a customer portal on top of Airtable?

You can, but it is the use that most often pushes people past what Airtable was designed for, mainly because of permissions, branding and API limits. A common fix is to keep Airtable for staff and build only the portal. See internal tools for how that split works.

How long does a move from Airtable to a custom app take?

It depends on how many tables and workflows you move. A staged plan with a 2 to 4 week parallel run is a good rule. A builder should give you a phase 1 timeline after seeing your base, as I describe in how to scope a software project.

Are there ready-made alternatives to Airtable instead of building?

Yes. See Airtable alternatives for the main ones and what each fits. A different tool has its own limits, so check them before you move.

Do I lose my data if I leave Airtable?

Not if you plan it. Export a full copy before you start, check that attachments and linked records came across, and keep Airtable read-only until the new app has run a full business cycle.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…