Keep Airtable or Retool until you hit a hard limit: a record cap, a permission rule you can’t express, or seat fees that cost more each year than a build. Smplfy’s custom internal tools start at $4,000, so switching usually pays off once a team of 20 or more lives in the tool every day.
Should you build an internal admin tool or keep using Airtable or Retool?
The three things that decide it
Most teams don’t leave Airtable or Retool because they dislike it. They leave because they hit one of three limits, and the workarounds start costing more than the tool.
- Rows. Airtable caps records per base by plan. Once a base nears the cap, teams split data across bases and lose the links between records.
- Permissions. You need a rule like "account managers see only their own clients" or "finance can edit amounts, nobody else can." Low-code tools handle table- and field-level rules well and row-level rules poorly.
- Seat cost. Both tools charge per user. Ten users is cheap. Forty users who open the tool every day can cost more each year than building your own.
If none of the three is hurting yet, stay where you are. The rest of this page shows how to tell when one is.
Airtable vs Retool vs a custom internal tool
Vendor prices are list prices at the time of writing, billed annually. Check the pricing pages on Airtable’s and Retool’s own websites for current rates. Custom-build figures are Smplfy’s.
| Attribute | Airtable | Retool | Custom internal tool |
|---|---|---|---|
| Upfront cost | $0 | $0, plus builder time | From $4,000; systems of record from $15,000 |
| Monthly cost | Team $20, Business $45 per seat | Per-user fees; builders cost more than end users | Hosting, typically $20–$150 (general market range), plus maintenance hours |
| Row limit | 50,000 records per base on Team, 125,000 on Business | No cap of its own; data lives in your database or API | Your database’s limit; millions of rows in Postgres |
| Permissions | Table and field editing rules; no true row-level read restriction inside a base | Permission groups by app; row rules are queries you write | Any rule you can define, by role, team or client, with an audit log |
| Who maintains it | Whoever built the base | Someone who knows SQL and JavaScript | Your engineer or us, with a runbook |
| What breaks first | Record cap and the API limit of 5 requests per second per base | Queries when an upstream schema changes; seat cost as users grow | Dependency updates and upstream API changes |
The API limit matters more than people expect. Airtable’s developer documentation sets a limit of 5 requests per second per base, so a Zapier or Make flow that pushes a few thousand records at once will start throwing 429 errors and need retry logic.
Worked example: when the seat fees pay for a build
Take an operations team of 25 on Airtable Business. That is 25 × $45 × 12 = $13,500 a year, or $1,125 a month.
A custom admin tool that covers the same workflow, scoped at $8,000–$12,000, then costs about $50 a month to host plus around 3 hours a month of maintenance at $85, or $305 a month in total. The monthly saving is about $820, so the build pays for itself in roughly 10 to 15 months.
Now take 8 people on Airtable Team: 8 × $20 = $160 a month. That is less than the custom tool’s running cost alone, so the build never pays for itself on cost. It would have to be justified by permissions or data volume, or not done at all.
What a custom admin tool actually is
It is usually smaller than people picture. A typical build is a Postgres database, a web app with list, detail and edit screens, login through your Google or Microsoft accounts, and roles that decide who sees which rows.
The work that costs money is in the edges. That means an audit log on every change, imports that reject duplicates instead of creating them, and integrations that retry when HubSpot or QuickBooks Online is down. It also means a runbook so the next engineer can operate it.
For Hoopes Vision we replaced manual monthly reports built from spreadsheets with a database pipeline and a reporting dashboard. The spreadsheets had outgrown what a shared file could do, the same point many Airtable bases reach.
What catches teams out during a migration
- Linked records have to become foreign keys, and broken links surface all at once.
- Attachment URLs from the Airtable API are temporary, so files must be downloaded and re-stored during the move.
- Formula and rollup fields become code. Each one needs a written definition, or the numbers change without anyone noticing.
- Automations that ran inside Airtable or Retool need a new home and new error alerts.
The decision rule
Low-code wins when
- Fewer than about 15 people use it, and the data fits comfortably under the record cap.
- The workflow is still changing every month. Rebuilding a base is faster than changing code.
- Everyone can see every row, or table-level permissions are enough.
- Retool sits on a database you already own, and someone on staff can maintain the queries.
A custom build wins when
- You need row-level access, for example by client, region or team, plus an audit trail.
- You are splitting bases to stay under the record cap.
- Seat fees exceed roughly $8,000 a year and the workflow is stable.
- The tool is becoming your system of record, and other systems sync to it.
Neither is worth doing yet when
The process is not settled, or nobody inside the firm will own decisions during the build. Clean up the base and write down the workflow first. That costs nothing, and it makes any later build cheaper.
Frequently asked questions
How much does a custom internal admin tool cost?
Smplfy’s internal tools and dashboards start at $4,000, and full systems of record start at $15,000. The price rises with the number of integrations, how detailed the permission rules are, and whether you need an audit log. Hourly work is billed at $85 an hour.
What is Airtable’s record limit per base?
At the time of writing, Airtable allows 50,000 records per base on the Team plan and 125,000 on Business, with higher limits on Enterprise Scale. Check Airtable’s pricing page for current figures. Teams that split data across bases to stay under the cap usually lose the links between records.
Can Retool restrict which rows a user sees?
Retool has permission groups that control which apps a user can open. Row-level restrictions are written into your queries, for example by filtering on the current user’s email. That works, but each query has to enforce the rule, so a single missed filter can expose data.
How long does it take to move from Airtable to a custom tool?
A single-workflow admin tool usually takes three to six weeks, including data migration. Most of the migration time goes on turning linked records and formula fields into a clean data model and on re-storing attachments. Running both systems side by side for a week or two before cutover is normal.
Should I use Retool on top of my own database instead of building?
Often, yes. If you already have a well-structured database and someone who writes SQL, Retool is a fast way to put screens on it. Build custom when end-user seat fees grow large, or when the permission and audit rules get complex enough that enforcing them in every query becomes risky.
Related answers
Want to know if your base has outgrown Airtable?
Send us a short description and we’ll reply with a free written scope, or we can do a free 20-minute call. It helps to have your user count, roughly how many records you hold, and the permission rule or workaround that hurts most today. Start a conversation.