Your Glasgow ops run on a spreadsheet only Margaret understands, and Margaret retires in March
A custom internal tool for a Glasgow engineering, events, or financial-services operation runs £25,000 to £85,000 over 2 to 6 months. Retool, Airtable, and spreadsheets get you started fast, then become the risk: the job tracker, the resource planner, or the bid log grows into a sprawling workbook one person maintains, with formulas nobody else dares touch. A custom internal tool turns that fragile spreadsheet into a real application with validation, permissions, and an audit trail, so your operation doesn't stop the day its keeper is off sick.
Every Glasgow firm has the spreadsheet. It started as a quick job list and now drives quoting, scheduling, and resource allocation, with macros, hidden tabs, and one colour-coding system only its author can read. It works right up until someone fat-fingers a formula, two people edit at once, or the person who built it leaves, and then a key part of the business is suddenly unsteerable.
Retool and Airtable are a real step up and worth trying first. But they hit a ceiling when the logic gets specific: estimating rules that depend on weldment type, event resourcing that flexes by crew and venue, or compliance checks that have to be enforced not suggested. When the no-code tool can't hold your actual rules, you're back to exporting to a spreadsheet for the hard part, and the fragility returns.
Where the off-the-shelf tools fall short
- A business-critical spreadsheet is maintained by one person, so the operation stalls when they're off or they leave
- Concurrent edits and accidental formula changes silently corrupt the data everyone is making decisions on
- Retool and Airtable can't enforce your real estimating or resourcing rules, so the hard logic falls back to Excel
- No audit trail or permissions, so for financial-services or compliance work you can't prove who changed what
Custom internal tools: what Glasgow teams actually get
You build a real internal tool when a spreadsheet has quietly become core infrastructure and its fragility is now a business risk. A Glasgow build replaces the workbook with a proper application: enforced validation, role-based permissions, an audit trail, and your actual estimating or resourcing logic baked in so it can't be bypassed. For an engineering or events firm where that spreadsheet decides quotes and crew, the case is simply that you can't afford a single point of failure on the thing that runs the business. These tools often feed your ERP and project management systems and share data with business intelligence dashboards.
- A single spreadsheet runs a core process and only one person truly understands it
- You've hit Retool or Airtable's ceiling on your real business rules and keep falling back to Excel
- Compliance or financial-services work needs an audit trail the spreadsheet can't give
- Concurrent edits or accidental formula changes have already caused a costly mistake
- The need is simple and Airtable or Retool genuinely covers it without constant Excel workarounds
- The process is still changing weekly and you want to prototype before committing
- Few people use it and a spreadsheet's fragility is an acceptable risk for now
- You lack the budget to own and host a custom tool for the long term
- The business-critical process becomes a robust app with validation, so it survives a key person leaving
- Role-based permissions and an audit trail, so financial-services and compliance work can prove who changed what
- Your real estimating or resourcing rules enforced in software, not relegated to a fragile Excel fallback
- Multiple people work safely at once without corrupting each other's data
- Clean data that feeds your ERP, project management, and reporting instead of being rekeyed
- A custom tool needs maintenance and hosting; a spreadsheet is free and needs neither
- Building takes weeks where a Retool screen takes hours, so it's overkill for genuinely simple needs
- You take on a small ongoing support burden the spreadsheet never had
- Over-scoping is easy; a tool can grow features that recreate the very sprawl you were escaping
Feature priorities for Glasgow teams
Glasgow internal tools: the full scope
The engagements Glasgow teams bring us most often:
The honest cost picture for Glasgow
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single internal tool replacing one critical spreadsheet | £25k to £45k | 2 to 4 months |
| Multi-process internal platform with permissions and audit | £50k to £85k | 4 to 6 months |
| Custom logic layer extending an existing Retool app | £20k to £40k | 2 to 3 months |
Timeline: what happens, and when
Exactly what you get
A real application that replaces the fragile spreadsheet at the heart of your operation: enforced validation, role-based permissions, a full audit trail, and your actual business rules baked in so they can't be bypassed. You get safe multi-user editing, change history, and clean data that feeds the rest of your stack. Most Glasgow internal tools connect to the ERP for costing, the CRM for client data, and a project management or business intelligence layer downstream, so the tool stops being an island.
How to choose a developer in Glasgow
Pick a developer who asks to see the spreadsheet before quoting and is honest about whether you even need custom. The best ones will tell you to try Retool or Airtable first if that genuinely fits, then build only the logic those tools can't hold. Glasgow's plain-spoken culture rewards that candour. Ask for examples where they replaced a critical spreadsheet, confirm they'll handle migration of your existing data, and make sure permissions and audit are in scope if you do any compliance work.
- !They quote without seeing the spreadsheet that runs the process; ask them to walk through your real workbook first
- !They push a full platform when one tool would do; ask what the minimum viable replacement looks like
- !No mention of permissions or audit for your compliance work; ask how change history is captured
- !They can't articulate when Retool would be enough; a good developer tells you when not to build
- !No data-migration plan from your existing spreadsheets; ask how years of data come across cleanly
Teams investing in internal tools in Glasgow usually scope it next to custom software, wordpress, accounting, since these systems share data and budgets.
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
Should we just use Retool or Airtable instead?
Often yes, and a good developer will say so. You move to custom when those tools can't enforce your real rules and you keep exporting to Excel for the hard part, or when a critical process depends on one person's spreadsheet. That fragility, not the tooling, is what justifies a build.
How risky is the spreadsheet we're on now?
If a core process stops the day its author is off sick, that's a single point of failure on your business. A custom tool removes that risk by encoding the logic in software with permissions and an audit trail, so the knowledge lives in the system, not one head.
Can it extend our existing Retool app?
Yes. A custom logic layer over an existing Retool app runs £20k to £40k in 2 to 3 months, adding the rules and audit Retool can't express while keeping the screens you already built.
Will our years of spreadsheet data come across?
A proper build includes migration. Your historic data is cleaned, validated, and loaded into the new model so you don't start from zero, and the import surfaces the inconsistencies the spreadsheet was hiding.