Your ops team runs the Edinburgh Fringe on a Retool dashboard that times out every August
Custom internal tools in Edinburgh typically cost £25,000 to £85,000 over two to five months. Build when Retool or Airtable has become the operational backbone of your festival, fintech, or finance ops and it stalls under August load or hard permission needs. Keep the low-code tools for genuinely internal, low-stakes admin.
Retool and Airtable are brilliant until they're load-bearing. An Edinburgh festival operator starts with an Airtable base to track venues and casual staff, and by August it's the system 200 temporary workers depend on, querying tens of thousands of rows while it grinds and rate-limits. Airtable's record caps and Retool's query latency were never meant to carry your busiest three weeks of the year, but that's exactly when they fail.
For fintech and finance ops, the wall is governance rather than scale. Spreadsheets and shared low-code apps can't give you the role-based access, audit trail, and data-handling controls that a regulated Edinburgh firm needs. The tool that let one person move fast becomes the thing that fails a compliance review, and there's no clean way to retrofit proper permissions onto an Airtable base everyone already shares.
- A Retool or Airtable tool has quietly become operational infrastructure and stalls at peak
- You need role-based access and audit trails the low-code tool can't provide
- Your automation chains between Airtable and other systems break under August load
- Critical logic depends on one person's undocumented formulas
- The tool is genuinely internal, low-stakes, and low-volume
- No regulated data or hard permission requirement is involved
- Your team can keep iterating in Airtable faster than a developer could
- The workflow is likely to change weekly and doesn't need to scale
- A data layer that handles tens of thousands of records and concurrent August users without stalling
- Role-based access and audit logging that satisfy a regulated fintech's compliance review
- Direct integrations to ticketing, payroll, and finance instead of fragile Zapier chains
- Operational logic captured in code and documentation, not one person's Airtable formulas
- A faster ops workflow during the three weeks of the year that actually matter
- You lose the instant editability of Airtable; changes now go through a developer
- Build cost is real where a low-code base felt free, so the ROI case has to hold
- Over-building a simple admin tool wastes money; not everything deserves a custom app
- You take on hosting and maintenance that the low-code vendor previously handled
The honest cost picture for Edinburgh
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single operational tool replacing an overloaded Airtable base | £25,000 to £45,000 | 2 to 3 months |
| Integrated ops suite with permissions and live integrations | £45,000 to £85,000 | 3 to 5 months |
| Hosting, support, and enhancements | £6,000 to £18,000/year | ongoing |
Feature priorities for Edinburgh teams
What we build under internal tools in Edinburgh
Digital Heroes builds the full internal tools stack for Edinburgh teams. Typical engagements span:
Exactly what you get
An internal tool that does what Retool promised but holds up under load: a real data layer, role-based permissions, audit logging, and direct integrations to ticketing, payroll, and finance. You get the operational dashboards your team runs the festival on, built to survive concurrent August use. It complements your CRM, accounting software, and booking system rather than duplicating them, and it stops one person's spreadsheet from being a single point of failure.
How to choose a developer in Edinburgh
Choose a team that asks where the tool breaks before they ask what it should do. Ask for a build where peak concurrency was a design constraint and where they replaced brittle automation with proper integrations. Edinburgh's fintech scene means many developers understand regulated access control, so favour one who treats audit trails as standard. Confirm they'll document the logic well enough that you're not held hostage by the original developer.
Timeline: what happens, and when
- !They suggest scaling Airtable further; ask what its record cap does to you in August
- !No audit or access-control plan; ask how a regulated fintech passes review on this tool
- !They rely on Zapier for core integrations; ask what happens when a chain breaks at peak
- !They can't quantify load; ask how the tool behaves at 200 concurrent users
- !No documentation commitment; ask how the logic survives your seasonal staff leaving
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 does Airtable stop being good enough?
When it becomes operational infrastructure that other people and systems depend on. The moment record caps, query latency, or missing permissions create risk during your busiest period, you've outgrown it, and Edinburgh's August festival load tends to expose that fast.
Can a custom tool handle 200 concurrent festival staff?
Yes, that's exactly the case for building. A purpose-built data layer and backend can handle the August concurrency and record volume that make Airtable stall, which is the whole point of moving off low-code at peak.
How do we add proper permissions for a regulated fintech?
By building role-based access control and audit logging into the tool from the start. Retrofitting real permissions onto a shared Airtable base is rarely clean, which is usually what pushes a regulated firm to a custom build.