Airtable or custom, a guide
If Airtable does the job, keep it. I build custom apps for a living and I still tell people that. A custom app makes sense once your team spends more time working around the base than working in it, and that point is easy to spot.
The short answer
Airtable is a good tool. A small team can set up tables, forms and simple automations in an afternoon, change them the next day and pay a monthly fee instead of a build. For tracking work that a few people share, that's hard to beat.
The trouble starts as the business grows around the base. More people need to log in, customers want to see their own orders, the data has to follow rules, and the automations get long enough that nobody is sure what runs when. None of that happens on day one, which is why the question comes up a year or two in.
Which side you're on
Most teams can tell in a few minutes by going down these two lists.
Airtable is usually enough when
- A handful of people use it, mostly in the office
- Everyone may see most of the data
- Mistakes are easy to spot and cheap to fix
- The automations fit on one screen
- You're still changing how the work runs
Signs you've outgrown it
- You pay for seats so people can tick one box
- Customers or crews need their own login and view
- Someone fixes bad or duplicate records every week
- Data gets copied by hand between Airtable and other tools
- You're splitting the base because it's near the record cap
Where they differ
These are the places where a base and an app built for one business work differently.
Who logs in
Airtable's paid plans bill per person who can edit. That's fine for a small office. It adds up when every crew member or part-timer needs to update a record.
What each person sees
Airtable controls access by base, interface and view. When different people must see different rows and fields every time, like crews seeing their jobs without the prices, an app built for it enforces that in one place.
Rules the data must follow
In a base, many rules are habits people have to remember. A custom app can refuse a job without an address or stop an invoice going out twice, every time.
How much data
Each plan caps records per base. Years of orders, line items and notes can reach that cap, and splitting one business across several bases makes reporting harder.
Automations
Airtable's automations cover a lot, with a monthly run allowance per workspace. Work that branches, waits on people or touches several outside tools is easier to follow in code.
Who owns it
Airtable owns the product, the price and the roadmap. With a custom app the code sits in your repository and the hosting is in your name, so changes happen when you decide.
The limits
Airtable's free plan allows 1,000 records per base. The Team plan allows 50,000 records per base and 25,000 automation runs per workspace each month. The Business plan allows 125,000 records per base and 100,000 automation runs per month. On both paid plans, people who can edit are billed as collaborators, and read-only people aren't.
Checked on 3 November 2026 against Airtable's plans overview. Plans change, so read the current page before deciding anything on these numbers. Compare them with your own base and how fast it grows each month.
A middle path
Replacing Airtable isn't the only option. Because it has an API, a custom piece can sit on top of your base and leave the rest alone. A page where customers check their own orders, a phone screen for crews with three buttons, or a script that moves data to your accounting tool every night.
That costs less than a full app and tests whether custom work pays off for you. If it does, the rest can follow later, one part at a time.
Moving off
- Map the base. Every table, field, link between tables, view and automation, and who uses each one. Half of them are usually no longer used.
- Clean while you move. Duplicates, free text in number fields and three spellings of one customer get fixed in the import instead of carried across.
- Rebuild the automations as plain steps. Each one gets written down first, so you can see what it does before it runs in the new app.
- Run both for a short while. The team tries the new app on real work while the base stays as a backup, and the switch happens when the counts match.
How we'd start
I'm Rob, and I run Senova Systems, a small software studio in central New Jersey. I'd start by looking at your base and how your team uses it today, then tell you which of the three fits. Keep it as it is, build one piece on top, or move to a custom app. The quote is free, with one fixed price for the agreed scope.
The internal tools page has a live demo of a job board that replaces a shared spreadsheet. If cost is the next question, the guide to what custom software costs explains what moves the price, and there are case studies of what I've built too.
Your quote
Every project gets its own written quote before any work starts. If you're on Airtable now, sharing a read-only view of the base makes that quote much more accurate.
The scope
What we'll build, page by page or screen by screen, and what's out of scope, in plain words.
A fixed price
One price for the agreed scope. It only changes if the scope does, and only with your OK.
A dated timeline
When the first preview arrives, when each part lands and when you go live.
What you'll own
The code, the design and every account, in your name from day one.
Running costs, itemised
Hosting, email and any other services listed one by one, paid to each provider at cost.
Where projects usually start
Each card leads to the full service page, with a live demo you can try.
FAQ
If it does the job and your team isn't working around it, yes. A custom app costs more up front, and it only earns that back when it saves real time or fixes something Airtable can't. I'd rather tell you to keep it than build something you don't need.