The harvest is run on one workbook, and only Janelle understands the macros
Custom internal tools for a Mildura horticulture operation run $25k to $80k and 6 to 16 weeks, depending on how many workflows you replace. Retool, Airtable, and a heroic spreadsheet get you surprisingly far, until the spreadsheet that schedules crews and tracks water orders becomes a single point of failure that one person maintains. Custom tools turn those fragile workbooks into something the whole shed can use during a frantic harvest morning without breaking it.
Somewhere in your business is a spreadsheet that does too much. It rosters the picking crews, tracks which blocks have water orders in, totals the day's bins, and feeds the dispatch list, and it works right up until two people open it at once or a formula silently breaks during the busiest week of the year. Airtable cleaned up the contact list and Retool gave a couple of admins a nicer view, but the core harvest workflow is still held together by one person who knows where the bodies are buried.
The risk is not that the spreadsheet is ugly. The risk is that on a 40-degree dispatch morning, with a container booked and a crew short, the tool everyone depends on is fragile, undocumented, and editable by anyone who fat-fingers a cell. That is a bad place for the heart of a seasonal operation to live.
Where the off-the-shelf tools fall short
- The core harvest workbook does crew rostering, water-order tracking, and dispatch all at once and breaks under load
- Only one person truly understands it, so it is a single point of failure during peak season
- Multiple people cannot safely use it at the same time on a busy morning
- Retool and Airtable patched the edges but the fragile centre still runs the business
Custom internal tools: what Mildura teams actually get
The case for custom internal tools is reliability under harvest pressure. A purpose-built tool replaces the do-everything spreadsheet with focused screens for the jobs that actually run your season: roster the crew, log water orders, count bins, build the dispatch list. Multiple people use it at once without clobbering each other, the logic is documented rather than hidden in macros, and a wrong number cannot silently break the whole operation. For a seasonal business where the busiest week is also the highest-stakes, that resilience is the whole point.
- A single fragile spreadsheet runs your harvest and one person maintains it
- Multiple people need the same workflow at once and the current tool cannot handle it
- Errors in the workbook have already caused a real dispatch or roster problem
- You want a base to grow into a proper CRM (Customer Relationship Management) or ERP (Enterprise Resource Planning) rather than more spreadsheets
- Your workflow is genuinely simple and a clean Airtable base covers it
- Only one or two people ever touch the tool and load is never an issue
- You need something this week and a Retool app gets you there
- You are not ready to commit to maintaining custom software
- Reliable multi-user tools that hold up when the whole shed is using them at once during harvest
- The do-everything spreadsheet split into focused, validated screens that cannot silently break
- Logic documented and owned by the company, not trapped in one person's macros
- Faster data entry on the floor with mobile-friendly screens for crew counts and bin tallies
- A foundation you can extend into a CRM, dispatch board, or full ERP later without starting over
- Even good internal tools need maintenance and occasional fixes; that is now your responsibility
- Replacing a flexible spreadsheet means defining rules explicitly, which removes some on-the-fly hacking
- Done badly, custom tools can be just as opaque as the spreadsheet they replaced
- For genuinely simple needs, a tidied-up Airtable or Retool app may be the right answer and far cheaper
Feature priorities for Mildura teams
What we build under internal tools in Mildura
Digital Heroes builds the full internal tools stack for Mildura teams. Typical engagements cover data-entry tools, admin panel development, internal dashboards, Retool alternative, workflow automation and back-office software.
The honest cost picture for Mildura
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single critical tool (e.g. dispatch builder) | $25k to $40k | 6 to 9 weeks |
| Crew, water-order, and dispatch suite | $45k to $80k | 10 to 16 weeks |
| Hardened layer on top of Airtable/Retool | $15k to $30k | 4 to 7 weeks |
Timeline: what happens, and when
Exactly what you get
Focused, reliable tools that replace the fragile do-everything workbook. Crew rostering and attendance you can enter from a phone in the shed, water-order tracking by block, validated bin counts, and a dispatch list that builds itself from the day's pack-out instead of being re-typed. Multiple people use it at once without breaking it, the rules are documented, and an audit trail means a wrong number gets caught and fixed. It is designed to grow into a fuller CRM or ERP when you are ready.
How to choose a developer in Mildura
Look for a team that respects the spreadsheet rather than sneering at it; the workbook encodes years of hard-won harvest logic, and a good developer extracts that before replacing it. They should ask to watch a real dispatch morning and design for fast entry on the floor in tough conditions. Ask how the tool handles many users at once and how it grows later. Avoid anyone who just rebuilds the sheet pixel-for-pixel; that recreates the same single point of failure with a nicer skin.
- !They want to just rebuild your spreadsheet as-is; ask which parts they would redesign and why
- !No plan for concurrent users; ask how it holds up with the whole shed entering data at harvest
- !They skip mobile entry; ask how crew counts get logged on the floor, not at a desk
- !No audit trail; ask how a wrong bin count gets traced and corrected
- !They cannot say how the tool grows later; ask how it extends toward a CRM or ERP
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
Why not just keep improving the spreadsheet?
Spreadsheets are great until they run a seasonal business. The harvest workbook becomes a single point of failure that one person maintains, breaks under concurrent use, and silently absorbs errors. Custom internal tools give you the same flexibility with reliability, documentation, and safe multi-user access for a frantic Sunraysia dispatch morning.
Can the developer reuse the logic already in our workbook?
Yes, and they should. The spreadsheet encodes years of real harvest rules. A good build starts by extracting that logic, then rebuilds it as focused, validated screens rather than throwing the knowledge away.
Will crew enter data from the shed floor?
That is the point. Tools should be mobile-friendly so crew counts, bin tallies, and water orders are logged where the work happens, not re-keyed later at a desk, which is where most of the spreadsheet errors creep in.
How is this different from a Retool app?
Retool is great for quick admin screens over existing data and may be all you need. Custom tools go further when you need reliable concurrent use, floor-grade mobile entry, validation, and a path to grow into a CRM or ERP without rebuilding.
Can we start with just one tool?
Absolutely, and most Mildura operations should. Replace the single most fragile or highest-stakes workflow first, usually the dispatch builder or crew roster, for $25k to $40k, prove it over a season, then extend to the rest.