The Dubbo depot morning run sheet is a spreadsheet one person rebuilds by hand
Custom internal tools for a Dubbo operation run $25,000 to $75,000 and take six to fourteen weeks. Build them when the spreadsheet that allocates trucks, tracks saleyard consignments, or rosters regional service crews has become the single most important and most fragile thing in the business. Retool and Airtable get you partway, but they buckle once the allocator needs to juggle distances, fuel, and saleyard timings live.
Somewhere in your business there's a workbook with twelve tabs, colour-coded by someone who left two years ago, that decides which truck runs where each morning. The allocator opens it at 5am, drags jobs around, and the entire depot's day depends on it. It works because of the person, not the tool. When they take leave, the run falls apart, and when a formula breaks, nobody can fix it.
Airtable and Retool are the obvious upgrade, and for a while they help. But the moment you need the tool to know that this run is 380km, that the truck can't legally do both jobs in a day, or that a saleyard consignment has to be on the deck before the draft, the no-code ceiling hits. You end up with the same fragility, just in a nicer interface, and still dependent on one person who understands the wiring.
Where the off-the-shelf tools fall short
- The depot's daily allocation lives in a spreadsheet only one person can run
- Saleyard consignment tracking is manual and breaks under sale-day pressure
- Retool and Airtable can't enforce distance, fuel, and driver-hours rules for Orana runs
- When the spreadsheet owner is on leave, the operation slows to a crawl
Custom internal tools: what Dubbo teams actually get
A custom internal tool encodes the rules the spreadsheet only holds in someone's head: legal driver hours, run distances across western NSW, saleyard cut-off times, fuel and backload logic. It becomes a tool anyone on the desk can run, not just the one person who built the workbook. You're not buying a prettier spreadsheet, you're turning tribal knowledge into software the whole depot can rely on, with proper validation and an audit trail.
- A single spreadsheet is the most critical and most fragile asset you own
- You've outgrown Airtable or Retool because they can't enforce real-world rules
- Onboarding a new allocator takes months because it's all tribal knowledge
- Airtable still comfortably handles your volume and rules
- Your process changes weekly and you need spreadsheet-level flexibility
- The tool only needs to be used by one person who's happy with it
- Daily allocation can be run by anyone on the desk, not just the spreadsheet owner
- Distance, fuel, and driver-hours rules are enforced, not remembered
- Saleyard consignments tracked reliably through sale day
- Changes are logged, so a wrong allocation can be traced and fixed
- Slots cleanly between your CRM (Customer Relationship Management), booking software, and ERP (Enterprise Resource Planning) instead of re-keying
- Internal tools feel cheap to start but accrete features and maintenance over years
- If the underlying process is genuinely chaotic, software just exposes the chaos
- You lose the spreadsheet's infinite flexibility, some edge cases need code changes
- Replacing a tool the team trusts means a real change-management effort
Feature priorities for Dubbo teams
Internal Tools services we deliver in Dubbo
Everything an internal tools build here can cover: data-entry tools, admin panel development, internal dashboards, Retool alternative and workflow automation.
The honest cost picture for Dubbo
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single tool replacing one critical spreadsheet | $25k to $40k | 6 to 8 weeks |
| Allocation plus saleyard board | $40k to $60k | 8 to 11 weeks |
| Connected suite across depot and yard | $60k to $75k | 11 to 14 weeks |
Timeline: what happens, and when
Exactly what you get
A purpose-built allocation and consignment tool that anyone on the desk can run, with the driver-hours, distance, and saleyard cut-off rules baked in. It links to your custom CRM development for account jobs, your booking software for incoming work, and your ERP for costing, so a job allocated in the morning flows straight to invoicing instead of being typed in three times.
How to choose a developer in Dubbo
Find a developer who'll sit with your allocator at 5am, or near enough, and learn the spreadsheet before replacing it. Half the value is the undocumented rules in that workbook, and a developer who skips that step will build something that's prettier but just as wrong. Ask them how they'll capture the rules nobody wrote down, and how they'll get the desk to trust the new tool over the old sheet.
- !Wants to rebuild the spreadsheet feature-for-feature instead of fixing the process
- !Can't enforce driver-hours or distance rules, that's the whole point
- !Pitches pure Retool when you've already hit Retool's ceiling
- !Ignores the audit trail, you need to trace a bad allocation
- !No plan for getting the team off the trusted spreadsheet
Most Dubbo 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
Isn't this just a better Airtable?
No. Airtable stores and filters data well but can't enforce that a run is too long for one driver's legal hours or that a saleyard consignment missed cut-off. A custom tool encodes those rules so the allocation is correct, not just tidy.
What happens to our existing spreadsheet?
It becomes the spec. A good developer reverse-engineers the logic in it, the rules nobody wrote down, then rebuilds that as validated software, so you keep the knowledge without the fragility.
Can it handle our black-spot drivers?
Yes. The allocation runs in the office, but any field component captures offline and syncs later, which matters for long runs west of Dubbo with no reception.