Three Leeds departments run on shared spreadsheets nobody dares change
Replacing the spreadsheet-and-Retool layer that runs a Leeds back office costs £30,000 to £90,000 over 3 to 6 months, depending on how many processes you consolidate. Retool, Airtable, and shared spreadsheets are brilliant for getting started and dangerous once a real operation depends on them. Build a proper internal tool when a broken formula or a deleted row would actually cost you money or breach a regulation.
Somewhere in your Leeds firm there is a spreadsheet that three departments depend on, that one person understands, and that everyone is afraid to touch. It started as a quick fix for tracking client onboarding or stock or case allocation, and it grew tendrils. Now it is load-bearing, has no validation, no audit trail, and one wrong paste corrupts a week of work.
Retool and Airtable felt like the upgrade, and for a while they were. But Retool apps multiply until nobody knows which one is current, and Airtable's row limits and permission model start fighting you the moment a process gets serious. These tools are scaffolding. The problem is when scaffolding becomes the building, and you are running regulated client work or stock-controlled distribution on something that was never meant to bear that weight.
What breaks first in Leeds
- A critical spreadsheet has no validation, so a mistyped cell silently corrupts client or stock data
- One person holds all the knowledge of how the Retool app or master sheet actually works
- No audit trail, so when a number is wrong nobody can see who changed it or when
- Permissions are all-or-nothing, so juniors can edit fields they should never touch
The fix: internal tools built for Leeds, not rented
A purpose-built internal tool gives you validation, role-based permissions, and an audit trail that a spreadsheet never will, while fitting your exact process instead of forcing your process into Airtable's grid. For a Leeds operation where the spreadsheet is now genuinely load-bearing, the value is removing single-point-of-failure risk and the quiet daily cost of errors nobody catches until month-end.
What internal tools costs in Leeds
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single process replacing one critical spreadsheet | £18k to £35k | 2 to 3 months |
| Multi-process internal tool with roles and audit | £40k to £65k | 3 to 5 months |
| Department-wide back-office platform | £65k to £90k | 5 to 6 months |
The capability list that earns its budget
What we build under internal tools in Leeds
The engagements Leeds teams bring us most often:
Exactly what you get
A web tool that replaces your most dangerous spreadsheet with structured forms, validation that rejects bad data at the door, role-based permissions, and a full audit trail. It fits the process you actually run instead of forcing it into a grid. The single-person knowledge dependency is documented and designed out. Data the old sheet buried in a hidden tab surfaces as a dashboard your managers can actually use.
How to choose a developer in Leeds
Find a team that will tell you when not to build. The honest answer for some processes is that Airtable is fine, and a good Leeds developer will say so. For the load-bearing ones, ask how they handle validation, permissions, and the migration of years of spreadsheet history. They should connect the tool to your CRM, ERP, and internal tools layer so nobody enters the same data twice. Pragmatic Yorkshire buyers should pin down exactly which risk or hour the tool removes.
- !They want to rebuild the spreadsheet exactly as-is. Ask which process steps they would simplify
- !No mention of validation or audit. Ask how they prevent the same errors the sheet allows
- !They cannot name who owns the tool after launch. Ask about the maintenance handover
- !They over-engineer a simple need. Ask honestly whether Airtable would do the job for less
- !Vague on permissions. Ask how a junior is stopped from editing a sealed record
If internal tools is on the roadmap, custom software, wordpress, accounting usually follow within the year. Budget them as one conversation.
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 is a spreadsheet too risky to keep using?
When it is load-bearing, has no validation or audit trail, and one person understands it. At that point a mistyped cell can silently corrupt client or stock data, and a deleted row can cost a week. If a wrong paste in that sheet would breach a regulation or lose money, it has outgrown being a spreadsheet.
Is Retool not already a custom tool?
Retool is excellent for fast internal apps, but it has limits: apps proliferate until nobody knows which is current, you pay per user as you scale, and complex logic gets awkward. For a stable, audited, mission-critical process it is often worth moving from Retool to owned code. For experiments and low-stakes tools, stay on Retool.
Will we lose the flexibility of spreadsheets?
Yes, deliberately. The flexibility that lets anyone edit anything is exactly what makes a load-bearing spreadsheet dangerous. A custom tool trades instant editability for validation, permissions, and an audit trail. If your process genuinely changes weekly, that trade is premature, and a no-code tool is the better fit for now.