The Tauranga allocation spreadsheet that four people edit at once
Replacing the spreadsheets that actually run a Tauranga operation costs NZ$25,000 to NZ$85,000 and takes 6 to 16 weeks for a focused tool. The right first target is almost never the biggest spreadsheet, it is the one four people edit at the same time during peak, because that is where the errors turn into money. Retool and Airtable get you 70 percent of the way and then stall on offline use, printing, and the permission rules a packhouse floor actually needs.
Somewhere on your shared drive is a file with a name like ALLOCATION_final_v7_USE_THIS.xlsx. It decides which grower lot goes into which coolstore row, which pallets are picked for which container, and who gets told when a booking moves. During autumn, three supervisors and a dispatch coordinator have it open simultaneously, and the version that wins is whoever saves last. Nobody built this deliberately. It grew, one column at a time, because the ERP (Enterprise Resource Planning) could not do it and buying another system for one process felt absurd.
Airtable and Retool are the obvious escape and they genuinely help, until you hit the specific things. Airtable has no real concept of a locked record that a shift supervisor can read but not change. Retool needs an internal developer to maintain the queries and breaks when the underlying schema shifts. Neither of them prints a legible pick sheet that survives a wet coolstore, and neither works when the wifi in the far end of the store drops out for ten minutes. So the spreadsheet stays, quietly running your season.
Where the off-the-shelf tools fall short
- The allocation file is edited concurrently by three or four people during peak and the last save silently overwrites the others
- Nobody can tell you who changed a coolstore row assignment or when, because the spreadsheet has no audit trail
- Dispatch reprints pick sheets by hand because Airtable views do not produce something usable on a forklift
- Retool dashboards break whenever the ERP schema changes and only one person in the business can fix them
- Wifi dead zones deep in the coolstore mean any browser-only tool loses ten minutes of work
Custom internal tools: what Tauranga teams actually get
Internal tools are the cheapest custom software you will ever buy and the fastest to prove value, which makes them the right entry point for a Tauranga operator who is nervous about a six-figure ERP. You pick one process, usually coolstore allocation or dispatch sequencing, and you build exactly that with real record locking, a change log, printable output and offline tolerance. Because the scope is narrow, discovery takes days not weeks, and the tool is in supervisors hands inside two months. It also does something strategic: it produces clean structured data about a process that previously existed only as a spreadsheet, which is what makes a later ERP or BI project affordable instead of speculative.
- A single spreadsheet is edited by three or more people during your busiest weeks
- Errors in one file cost real money, such as a missed container or a double-allocated room
- You want to prove custom software works before committing to a larger ERP programme
- Your Retool or Airtable setup depends on one person who has become a bottleneck
- The process is stable, single-user and low stakes, in which case Airtable is genuinely fine
- You need something this week and can tolerate manual workarounds
- You have an internal developer who enjoys maintaining Retool and will still be there next season
- The workflow is a standard one, like leave requests, where a cheap SaaS product already fits
- Concurrent editing stops destroying work, because the tool locks a record while someone is changing it and shows who holds it
- Every change carries a name and a timestamp, so the Monday morning argument about who moved the pallets ends in ten seconds
- Printable pick and load sheets are designed for a cold, damp, gloved environment rather than a laptop screen
- The tool keeps working through a wifi dropout in the store and reconciles when the connection returns
- You get structured historical data on a process that had none, which makes later reporting and forecasting genuinely possible
- Small tools multiply. Without an owner you end up with nine of them and no consistent login, which is its own mess
- You give up the instant self-service change that Airtable offers, so small tweaks now go through a developer
- Cheap tools attract scope creep from every department, and the second and third request are rarely as valuable as the first
- If the underlying process is genuinely broken, software makes the broken process faster rather than fixing it
Feature priorities for Tauranga teams
What we build under internal tools in Tauranga
Digital Heroes builds the full internal tools stack for Tauranga teams. Typical engagements cover internal portal, business process automation, data-entry tools, admin panel development, internal dashboards and Retool alternative.
The honest cost picture for Tauranga
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single focused tool, for example coolstore allocation or dispatch sequencing | NZ$25,000 to NZ$45,000 | 6 to 9 weeks |
| Connected suite of three to four tools with shared login and permissions | NZ$55,000 to NZ$110,000 | 3 to 5 months |
| Replacing an unstable Retool or Airtable setup with a maintained application | NZ$30,000 to NZ$60,000 | 6 to 10 weeks |
| Support and small change retainer | NZ$1,500 to NZ$4,000 per month | ongoing |
Timeline: what happens, and when
Exactly what you get
One process, done properly. For most Bay of Plenty operators the first build is coolstore and dispatch allocation: a live board of rooms and rows, drag-and-drop assignment with hard locking, automatic release when a lot ships, and a printable load sheet that a driver can hold. Underneath it sits an audit trail on every field, role permissions so quality can flag a lot without moving it, and a sync into your accounting or ERP data so the numbers stop being retyped. It runs on a tablet, and it keeps accepting input when the store wifi drops.
The second and third tools usually follow the same shape: a maintenance request log for packing line breakdowns, a grower advice generator, or a container loading planner. Once two or three exist, they should share one login and one permission model. Teams that skip that step end up with a folder of bookmarks. If reporting is the real goal, pair this with business intelligence dashboards, and if the process touches stock movement, look at inventory management software and a warehouse management system (WMS) before you build a third overlapping tool.
How to choose a developer in Tauranga
Judge them on how they choose scope. A good team will ask to watch a shift rather than read your requirements, and they will come back arguing for a smaller first build than you proposed. That instinct is worth paying for, because internal tool projects fail by growing, not by being too small. Ask them to name the one screen that must work perfectly on day one. If they cannot pick one, they have not understood the process.
Practical checks for a Tauranga build: ask how the tool behaves at the far end of a coolstore with no signal, ask what the printed output looks like, and ask who supports it in April when your supervisor rings at 6am. Confirm the code and hosting are in your name, and that a handover pack exists. If you already run Xero, ask specifically how they will push data across without a nightly CSV, because the CSV always becomes someone's job.
- !They want to build all six tools at once. Ask which single spreadsheet they would replace first and why
- !No question about who edits the file simultaneously. Ask how they will handle two supervisors saving at the same moment
- !They ignore printing. Ask to see a pick sheet they have designed for a coolstore, not a screen mockup
- !They propose Retool as the answer without asking who will maintain it. Ask what happens when the schema changes
- !They cannot show you a tool still in daily use two years after launch. Ask for one and call the client
Most Tauranga teams pricing internal tools end up comparing notes on custom software, wordpress, accounting too; the systems share one data spine. Weighing options across the region? We publish the same internal tools guide for Rotorua. Prefer to talk to the team that builds these? Digital Heroes handles custom software development end to end.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
Mahira leads UI and UX design, which at an agency means moving from a vague client request to wireframes, then to screens engineers can build without guessing. She works on dashboards, storefronts and internal tools where usability decides whether staff adopt the software. Her posts focus on design decisions that survive contact with users.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does it cost to replace our packhouse allocation spreadsheet?
A single focused tool covering coolstore allocation, locking, audit history and printable sheets runs NZ$25,000 to NZ$45,000 over 6 to 9 weeks. Dispatch sequencing and grower advices typically add NZ$15,000 to NZ$25,000 each. In our delivery experience this is the cheapest way for a Bay of Plenty operator to test whether custom software is worth it.
Is Airtable good enough for a Tauranga packhouse?
For stable, single-user, low-stakes processes it is genuinely fine and much cheaper. It falls over when several supervisors edit the same records during peak, when you need real permission separation, or when output has to be printed and used on a forklift. If any of those apply, a purpose-built tool costs less than the errors.
Will the tool work in the coolstore where wifi drops out?
It should be designed to. The pattern is a local store on the tablet that queues changes and syncs when signal returns, with clear indicators so a supervisor knows what has and has not been saved. Ask for this explicitly, because a browser-only build in a metal-clad coolstore will lose work.
How fast can we get the first tool live before harvest?
Six to nine weeks from a signed start for a single process, which means starting in December or January to be comfortable for an autumn peak. Starting in March is possible but you will be training supervisors during the busiest fortnight of their year, which rarely goes well.
Can it push data into Xero without someone exporting a CSV?
Yes. A direct API connection into Xero handles invoices, bills and tracking categories, and it removes the recurring export job that always lands on one person. Get this into scope at the start, because bolting it on later usually means reworking how the tool records transactions.
Do we still need an ERP if we build internal tools?
Often not for another year or two. Well-scoped tools solve the acute pain and, more usefully, they produce structured data about processes that previously lived in spreadsheets. That data makes a later ERP decision evidence-based rather than a guess, and it usually shrinks the ERP scope.
Who maintains it after launch?
Either a retainer at NZ$1,500 to NZ$4,000 per month or an internal owner with agency backup. What does not work is assuming nobody needs to maintain it. Small tools accumulate change requests, and without a named owner they drift out of use within a season.
Can it handle piece-rate picking records for payroll?
It can capture picker output by block and by bin and feed that into payroll, but treat the minimum wage top-up calculation carefully. New Zealand law requires piece-rate workers to still reach at least the applicable minimum wage for hours worked, so the tool needs hours as well as counts. Build that check in rather than doing it in a spreadsheet afterwards.
Do we own the tool, or are we renting it?
You own it, including source code and hosting accounts, and that should be written down before the first invoice. Some agencies host internal tools on their own infrastructure and quietly make you dependent. Ask for a handover pack and confirm you could move it to another developer without their cooperation.
How do I calculate whether custom software will pay for itself?
Should we build our internal tool in Retool instead of hiring developers?
Does it matter which tech stack the agency wants to use?
What do developers charge for internal tools work in Tauranga?
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
At what point does Retool cost more than building a custom tool?
How many people should be working on my software project?
Can we start on Airtable or Retool now and move to custom software later?
Is custom software more secure than off-the-shelf SaaS?
Will a custom internal tool scale as our company grows?
Who can build custom internal tools for a business in Tauranga?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, so an operator in Tauranga gets an assigned senior team rather than a local account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
