Your whole ops desk runs on one Airtable base, and the person who built it just handed in their notice
Build a proper internal tool when an Airtable base or Retool app has quietly become business-critical and fragile. For a Liverpool operations team that is usually £25k to £80k and 6 to 16 weeks per tool. Below that threshold, keep using Airtable; the trigger to build is when an outage or one person leaving would stop work.
Your operations desk started with a clever Airtable base to track containers, shifts or stock, and it grew. Now it holds the rota for a waterfront hotel, the gate schedule for a freight team, or the sample log for a Knowledge Quarter lab, and it bends under the weight. Formulas break when a row count climbs, two people overwrite each other on a match-day Saturday, and nobody fully understands the automations the original builder bolted on.
Retool got you further, but you have hit its limits too: row caps, slow loads on big tables, and permissioning that cannot stop a part-time staffer seeing every customer's deposit. The tool that was a smart shortcut is now a single point of failure, and it lives in one person's account.
Where the off-the-shelf tools fall short
- An Airtable base that runs daily ops slows or errors as records pass the tens of thousands
- Two staff editing the same rota or gate schedule on a busy Saturday overwrite each other's work
- Permissions are all-or-nothing, so a part-timer can see deposits, salaries or patient-adjacent data they should not
- The original builder is the only person who understands the automations, and they are leaving
Custom internal tools: what Liverpool teams actually get
A purpose-built internal tool replaces the fragile base with a real application: a proper database that does not buckle at scale, row-level permissions, an audit trail, and a UI built for the actual job rather than a grid pretending to be one. For a Liverpool ops team that means the rota, gate schedule or sample log keeps working through a festival weekend without one person babysitting it.
- An Airtable or Retool app has become business-critical and would stop work if it failed
- Performance degrades as your record count grows past Airtable's comfortable range
- You need real permissions and an audit trail the no-code tool cannot give you
- Knowledge of the tool sits with one person who could leave
- The tool is genuinely simple, low-volume and used by a handful of people
- No-code permissioning is good enough for the data involved
- You want to keep editing it yourself without a developer in the loop
- It is a short-lived or experimental workflow not worth hardening yet
- A real database underneath means the tool stays fast whether you hold ten thousand records or a million
- Row-level permissions keep deposits, pay and sensitive data visible only to those who should see it
- An audit trail shows who changed what, which Airtable hides and which matters for compliance
- Concurrent editing is handled properly, so a busy match-day shift does not overwrite itself
- The tool no longer lives in one departing employee's account; your business owns it
- You give up the instant, no-code editability that made Airtable feel free; changes now go through a dev
- A custom tool needs hosting, monitoring and occasional maintenance that Airtable handled for you
- Upfront cost and a few weeks of build replace a base you could spin up in an afternoon
- If the tool is genuinely simple and low-volume, you may be over-engineering what Airtable did fine
Feature priorities for Liverpool teams
What we build under internal tools in Liverpool
Digital Heroes builds the full internal tools stack for Liverpool teams. Typical engagements cover operations tooling, approval workflows, internal portal, business process automation, data-entry tools and admin panel development.
The honest cost picture for Liverpool
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single internal tool (rota, tracker, log) | £25k to £45k | 6 to 9 weeks |
| Multi-tool ops console with integrations | £50k to £80k | 10 to 14 weeks |
| Platform replacing several Airtable bases | £75k to £130k | 14 to 20 weeks |
Timeline: what happens, and when
Exactly what you get
A hardened version of the tool your team already relies on, rebuilt on a real database with proper permissions, an audit trail, and a UI shaped to the job. For a waterfront hotel that is a robust rota and booking console; for a freight team, a gate and container tracker that does not buckle on a busy Saturday. You get the code, the data, hosting set up, and documentation so the tool no longer lives or dies with one employee.
How to choose a developer in Liverpool
Look for a team that respects the work your Airtable base already does and rebuilds it without losing the cleverness, not one that sneers at no-code. Ask them to point at which of your tools genuinely need hardening and which should stay as they are. Liverpool teams value a developer who is honest about scope. Confirm they will migrate your data cleanly, integrate with your booking or lab systems, and leave you owning the result, with documentation a non-technical manager can follow.
- !They want to rebuild everything as custom code: ask which tools should stay in Airtable
- !No audit trail or permission plan: ask how they separate finance from floor staff
- !They ignore migration: ask how your existing base data moves over without loss
- !No monitoring or hosting plan: ask who keeps it running after launch
- !They cannot show a comparable internal tool: ask for a reference still in daily use
Most Liverpool teams pricing internal tools end up comparing notes on custom software, wordpress, accounting too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
When does an Airtable base become risky enough to rebuild?
When it runs daily operations, when an outage or the original builder leaving would stop work, or when record counts and concurrent edits cause errors. For a Liverpool ops team that point usually arrives once the base holds the live rota, gate schedule or sample log that the business cannot run without.
Can we keep some tools in Airtable and harden only the critical ones?
Yes, and you should. The right move is to identify the two or three tools that are genuinely business-critical, rebuild those properly, and leave low-volume, low-risk bases in Airtable where editing them yourself is an advantage. A good developer will tell you which is which.
How is a custom internal tool different from Retool?
Retool is a faster way to build an internal UI on top of a database, and it is a fine middle step. The custom case is when you outgrow Retool's row limits, need permissioning or audit trails it cannot give you, or want a UI and workflow Retool's component model cannot express cleanly at the scale you run.