The Airtable that runs your studio has one author, and they're on a plane to a shoot in Queenstown
A custom internal tool for a Wellington studio or government team runs NZD 40,000 to 160,000 over 2 to 6 months. Build custom when a spreadsheet or Airtable base has become load-bearing infrastructure that breaks under permissions, audit, or concurrent edits. Retool and Airtable are brilliant for the first version. They become a liability the moment that base coordinates crew, gear, and budget for real money and only one person understands it.
Your studio's operations run on an Airtable base that a producer built two years ago. It schedules crew, tracks gear, and holds the production budget. It works, until a runner edits the wrong row mid-shoot, two coordinators overwrite each other, and the only person who understands the formulas is unreachable on location. Retool dashboards papered over some of it, but the data model underneath is still a spreadsheet pretending to be a database.
Government teams have the same problem with a different face: a shared spreadsheet that became the system of record, with no audit trail, no proper permissions, and a privacy obligation the moment it holds anything personal. The tool is doing a job it was never built to do safely.
What breaks first in Wellington
- One Airtable base coordinates crew, gear, and budget, and only its author truly understands it
- Concurrent edits during a busy production overwrite each other with no audit trail
- No real permissions, so a runner can edit the same budget cell as a producer
- Government use adds a Privacy Act obligation that a shared spreadsheet can't honour
The fix: internal tools built for Wellington, not rented
A purpose-built internal tool gives the same workflow a real database, proper roles, validation, and an audit trail, so a busy shoot day doesn't corrupt the production schedule. It stops being one person's fragile artefact and becomes infrastructure the whole studio can rely on, with the concurrency and permissions a creative-and-civic operation actually needs.
What internal tools costs in Wellington
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single workflow internal app | $40k to $70k | 2 to 3 months |
| Multi-role tool with audit and permissions | $70k to $120k | 3 to 5 months |
| Full operations hub with integrations | $120k to $160k | 4 to 6 months |
The capability list that earns its budget
Wellington internal tools: the full scope
Everything an internal tools build here can cover: workflow automation, back-office software, operations tooling, approval workflows, internal portal, business process automation and data-entry tools.
Exactly what you get
The same workflow your studio already trusts, rebuilt on a real database with roles, validation, and an audit trail. Shoot-day concurrent edits stop corrupting the schedule, the knowledge leaves one person's head, and the tool connects to your ERP job codes and project management software so the same data isn't re-typed three times.
How to choose a developer in Wellington
Choose a team that respects how much business logic is buried in your Airtable before they rebuild it. Wellington studios value craft, so ask them to map your existing base and show where the concurrency and permission risks are. A good developer treats your fragile spreadsheet as a spec to honour, not a mess to discard.
- !They want to rebuild your Airtable one-for-one without questioning the data model. Ask how they'd fix the concurrency problem.
- !No mention of permissions or audit. Ask how a government team would meet Privacy Act obligations.
- !They skip migration planning. Ask how the tangled existing base gets moved cleanly.
- !They propose a heavy framework for a small workflow. Ask why Retool wouldn't do.
- !No plan for who owns it after launch. Ask about hosting, backups, and support.
Most Wellington 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 a real risk?
When it coordinates real money and real schedules, only one person understands it, and concurrent edits during busy periods overwrite each other. At that point a Wellington studio is running production on infrastructure that can fail silently with no audit trail.
Can we keep some of Airtable's flexibility?
Partly. A good build keeps the fields and views you change often configurable, while putting the load-bearing logic on a real database. You trade some instant click-to-edit freedom for concurrency safety, permissions, and an audit trail.
Does a government team need more than a studio?
Usually yes. Government use adds Privacy Act obligations and records requirements, so audit logging and proper role-based access stop being nice-to-have and become mandatory parts of the build.
What does an internal tool cost in Wellington?
NZD 40,000 to 160,000 depending on roles, audit needs, and integrations. A single workflow app is at the low end; a full operations hub that replaces several spreadsheets reaches the top.