Your Dundee studio's ops live in eleven Airtable bases and one very tired producer
If your Dundee studio's producer spends Friday afternoons stitching together a build tracker, a contractor invoice sheet, and a milestone calendar by hand, you've hit the ceiling of Airtable and spreadsheets. Custom internal tools cost £25,000 to £90,000 over 2 to 5 months and pay back fastest where the same data gets re-keyed across docs that don't talk to each other.
Dundee runs on small, fast teams: indie studios, design houses, lab groups, all coordinating contractors, milestones, and deliverables. The default reflex is Airtable plus a stack of Google Sheets, and it works until it doesn't. The build tracker says one thing, the invoice sheet another, and the publisher milestone calendar a third, and nobody notices the conflict until a payment is late or a build ships against the wrong spec.
Retool and Airtable are genuinely good, but they have edges. They struggle to reach into a CI pipeline, a perforce or git build server, or a lab instrument's output. So the moment your internal process touches the technical reality of how games get built or experiments get run, the no-code tool becomes a manual copy-paste bridge, and the bridge is a person.
Budgeting a internal tools build in Dundee
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single ops dashboard + 2 integrations | £25k to £45k | 2 to 3 months |
| Multi-tool suite + build pipeline integration | £45k to £70k | 3 to 4 months |
| Full internal platform + approvals + sync | £70k to £90k | 4 to 5 months |
The case for owning your internal tools
Custom internal tools connect the systems your no-code stack can't reach: your build pipeline, your contractor ledger, your milestone calendar, all in one tool your producer actually trusts. Instead of a person reconciling Airtable bases, you get a dashboard that pulls live build status, flags a slipping milestone before payment day, and ties every contractor to the project they bill. You build only the screens you need, on top of the data you already have.
- The same data is re-keyed across multiple Airtable bases or sheets daily
- Your process touches a build server, CI, or lab instrument no-code can't reach
- A slipped milestone surfaces only by manually cross-referencing documents
- Producers spend hours each week reconciling tools instead of producing
- Your process is genuinely simple and Airtable or Retool covers it
- Your workflow changes weekly and you need to tweak it without a developer
- You have no system integrations to make and just need shared structured data
- Budget is tight and the manual reconciliation is still a few minutes a day
What your build should include
Internal Tools services we deliver in Dundee
The engagements Dundee teams bring us most often:
Delivery, week by week
Exactly what you get
You get the operational glue your no-code stack couldn't reach: a dashboard pulling live build status from CI, a milestone tracker that flags a slip before payment day, and a contractor register linked to real project budgets. Your producer stops being the integration layer between Airtable bases, and the data your accounting and project management software needs flows automatically instead of by Friday copy-paste.
How to choose a developer in Dundee
Find a team that respects the line between what should stay in Airtable and what needs custom code. The best partners for Dundee's lean studios scope a tight first phase, integrate with your build pipeline rather than reinventing it, and leave you a tool simple enough that small process tweaks don't always need them. Ask them to point at the one workflow that hurts most and fix that first.
- One internal dashboard pulling live build status, milestone dates, and contractor billing instead of three reconciled docs
- Direct integration with CI, git, or build servers that Retool and Airtable can't reach
- Contractor onboarding and approvals linked to the actual projects and budgets they affect
- Early warning on slipping milestones so a late payment never surprises you
- Cheaper and faster than a full ERP when you only need to fix the operational glue
- Custom tools need maintenance as your process changes; Airtable lets a non-developer tweak a view instantly
- You lose the instant-prototype speed of no-code for genuinely simple internal needs
- Scope creep is the classic trap: an internal tool quietly grows into an unplanned ERP
- If your process is still changing weekly, hard-coding it early can lock in the wrong workflow
- !They propose rebuilding everything as custom when Airtable handles half of it. Ask what they'd leave in no-code
- !No plan to integrate your build server or CI. Ask how live status gets in without copy-paste
- !They can't scope tightly and the tool keeps growing. Ask for a fixed first phase
- !No thought to who maintains it when your process changes. Ask about hand-off
- !They ignore your existing accounting and project tools. Ask how the new tool syncs
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 should a Dundee studio replace Airtable with custom internal tools?
When the same data is re-keyed across multiple bases daily, or when your process needs to reach a build server or CI that Airtable can't. Until then, Airtable's instant editing usually beats a custom build.
Can custom internal tools pull live build status from our CI?
Yes. That integration is exactly what no-code tools struggle with and where custom earns its keep, pulling git or CI status into one ops dashboard instead of someone copying it in and watching it go stale.
How do we stop an internal tool turning into an accidental ERP?
Scope a tight first phase around the single most painful workflow, ship it, then decide. Disciplined partners fix the milestone-to-payment gap first rather than building everything at once.
How much do custom internal tools cost in Dundee?
A single ops dashboard with a couple of integrations starts around £25k. A multi-tool suite with build-pipeline integration runs £45k to £70k, depending mostly on how many systems it must connect.
Will the internal tool replace our project management software?
Not usually. It typically sits alongside and syncs with your project management and accounting tools, filling the gaps they leave rather than replacing systems that already work.