Short Answer
Stay on Airtable while it is doing the job without workarounds. It is genuinely good: fast to change, visual, and cheap at small scale. Move to a custom system when you notice the workarounds have become the system: automations chained to patch missing logic, “do not touch this column” rules, per-seat pricing multiplying across a growing team, and processes that silently fail when a record does not look the way a formula expects. Airtable is a superb way to discover what system your business needs. It is rarely the right way to run that system forever.
Why Airtable Wins Early
In the early stage of formalising a process, nobody knows what the process actually is. Airtable forgives that. You add a column, drag a view, bolt on an automation, and the tool keeps up with your thinking. Compare that to commissioning software before you understand your own workflow, which produces expensive systems that model a guess.
This discovery value is real and we would never talk a small team out of it. The base you build in Airtable is, in effect, a working specification. When businesses come to us from Airtable, the base tells us more about their operations than any requirements document could.
Where It Starts to Hurt
The symptoms cluster in familiar ways.
Scale. Records-per-base limits, performance that degrades as bases grow, and the moment someone proposes splitting the data across bases, which is the moment reporting across it dies.
Logic. Airtable stores data well but enforces rules weakly. Nothing stops the wrong status being selected, the step being skipped, the record being created half-filled. Your process exists as team folklore rather than as something the system guarantees.
Permissions. Real businesses need people to see some things and not others, edit this but not that. Airtable’s permission model runs out well before most operational needs do, which is why so many teams end up trusting everyone with everything.
Cost shape. Per-seat pricing means the tool gets more expensive precisely as it becomes more embedded. Teams respond by sharing logins, which breaks accountability, or by keeping people out of the system who should be in it.
The client boundary. Sooner or later you want clients or suppliers to see a slice of the data. Shared views leak more than intended or show less than needed, and there is no real concept of an external user with their own space.
What a Custom System Changes
A custom build takes the process Airtable helped you discover and makes it load-bearing. Rules are enforced, not remembered. Permissions match reality. The cost stops scaling with headcount. Clients get a proper way in, through a portal rather than a shared link. And the system connects directly to the rest of your stack instead of through an automation platform’s monthly task allowance.
What you give up is the drag-and-drop malleability. Changing a custom system means asking a developer, not dragging a field. For a process still in flux, that trade is premature, which is exactly why the right moment matters.
Reading the Right Moment
The signal we trust most: the base has stopped changing. When your Airtable structure has been stable for months and the team’s complaints are about limits rather than about the process itself, discovery is over. You know what the system needs to be. At that point every month on Airtable is rent paid on a specification you have already finished writing.
How We Approach This
Migrating from Airtable is one of the most common starting points for our custom software work, because the hard thinking is already done: the base is the spec. Data migration brings your records across intact, and workflow software is usually the shape the replacement takes. Where only one piece hurts, we sometimes build just that piece and leave Airtable doing what it still does well; a full replacement is not always the honest recommendation. Talk to us if you want a read on which side of the line your base has crossed. Related reading: spreadsheets vs a database for the stage before Airtable, and custom software vs off the shelf for the general form of this decision.
