Your Airtable base runs the whole port operation until two people edit it at once
Custom internal tools for a Bunbury operation typically cost $25k to $90k over 2 to 6 months. The trigger is when an Airtable base or a stack of spreadsheets has quietly become the system running your weighbridge logs, casual rosters or tour manifests, and it breaks the moment two people edit at once or the row count climbs past what Airtable handles smoothly. Custom internal tools give you that control with real permissions, validation and audit.
Someone clever in your office built an Airtable base to track export parcels or casual shifts, and now the whole operation depends on it. That's a sign it solved a real need, and a warning. Airtable slows once you pass tens of thousands of records, has no real role-based permissions for casual staff, and offers no proper audit trail when a weighbridge figure gets quietly overwritten the night before a vessel loads.
The spreadsheet version is worse: your dairy intake or tour roster lives in a shared sheet where one bad paste corrupts a formula and nobody notices until payroll is wrong. Retool can dress up a database but you still need that database and the back-end logic built properly. At some point the duct tape costs more in errors and rework than a real tool would.
Budgeting a internal tools build in Bunbury
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single tool replacing one fragile Airtable base | $25k to $45k | 2 to 3 months |
| Suite of connected internal tools across operations | $55k to $90k | 4 to 6 months |
| Hardened back-end behind a Retool or low-code front end | $30k to $55k | 2 to 4 months |
The case for owning your internal tools
A custom internal tool puts your real workflow on a proper database with validation, role-based permissions and a full audit trail. Casuals see only what they should; supervisors approve changes; and a weighbridge or payroll figure can't be silently overwritten. You keep the speed of the Airtable that everyone loved, without the fragility that's now scaring you.
- An Airtable base or spreadsheet has become load-bearing for a core process and breaks under real use
- You need audit and permissions Airtable can't give you for a financially sensitive workflow
- Record volumes have grown past where Airtable stays fast
- Multiple staff need to edit concurrently without corrupting each other's work
- The process is small, stable and edited by one or two trusted people
- Airtable or Retool genuinely covers it and you don't need deep audit or permissions
- You expect the workflow to keep changing weekly and want no-code flexibility
- Speed to set up matters more than long-term robustness
What your build should include
Internal Tools services we deliver in Bunbury
The engagements Bunbury teams bring us most often: data-entry tools, admin panel development, internal dashboards, Retool alternative and workflow automation.
Delivery, week by week
Exactly what you get
The tool your team already relies on, rebuilt so it can't betray you. Casual staff at the wharf or front desk capture data on their phones; supervisors approve; every change is logged; and a critical weighbridge or roster number can't be silently overwritten. It migrates your existing Airtable or spreadsheet cleanly and connects into payroll, accounting and the ERP rather than living as an island.
How to choose a developer in Bunbury
Choose a developer who will sit with your staff and watch the real workflow before quoting, because the value is in the messy details Airtable hid. Ask how they handle permissions, audit and data migration specifically. South West operators appreciate plain talk, so favour a team that says outright when Airtable or Retool is still the right tool for a given job. Internal tools usually feed into inventory management software, project management software and business intelligence dashboards, so check the developer can connect those rather than leaving you a fresh silo.
- Proper role-based permissions, so casual staff capture data without being able to edit locked supervisor fields
- A full audit trail on every change, so an overwritten weighbridge or payroll figure is traceable
- Validation that rejects bad data at entry instead of corrupting a downstream formula
- Performance that holds up as record counts grow, unlike Airtable past tens of thousands of rows
- A tool shaped exactly to your South West workflow rather than bent around Airtable's grid
- You lose Airtable's instant no-code editing; changing the schema now needs a developer
- A custom tool needs hosting, backups and security you must maintain or pay someone to
- If the underlying process is still changing weekly, building too early locks in a moving target
- Small, genuinely simple tracking jobs may not justify the cost over a well-governed spreadsheet
- !Vendor proposes another no-code tool with the same audit gaps; ask how they handle a locked-field permission
- !No mention of migrating your existing Airtable data; ask for their import plan
- !Skips validation; ask how they stop a bad tonnage or shift time from being saved
- !Can't show an audit trail; ask to see one in a past project
- !Builds without watching your staff work; ask to shadow a wharf or reception shift first
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 enough for us?
When a base becomes load-bearing for a process with money or compliance attached, needs real permissions and audit, or slows as records climb past tens of thousands. At that point the cost of errors and rework usually exceeds the cost of a proper tool.
Can we keep Airtable for some things and build others?
Yes, and you often should. Keep Airtable for genuinely simple, low-stakes tracking and build custom only where audit, permissions or volume demand it. A good developer will tell you which is which.
How do you migrate our existing base without losing data?
A bulk import maps your Airtable fields into the new schema, with a validation pass to catch the bad data the old grid let through. You run both in parallel briefly before cutting over.