The Packhouse Grade Out Spreadsheet Has 41 Tabs and One Person Who Understands It
Purpose built internal tools for a Nelson packhouse, processing floor or tour operation typically cost NZ$25,000 to NZ$70,000 over six to fourteen weeks, which is the cheapest serious software you will ever buy. The trigger is almost always the same artefact: a spreadsheet that started as a grade out sheet, grew macros, now runs a shift, and lives on the laptop of one person who is about to take annual leave. Retool and Airtable get you a long way, and Digital Heroes recommends them regularly, but they hit real ceilings on offline use, print and label output, and anything a seasonal worker needs to operate with gloves on.
Every Nelson operation of any size has one. It might be the bin reconciliation workbook that ties orchard blocks in Riwaka to pallets on the dock. It might be the run sheet that assigns crew to processing lines. It might be the tide and departure planner that a water taxi operator rebuilds every Sunday night. It works, mostly, until it is copied, emailed, opened on a phone, or edited by two people at once during the busiest week of the year.
Retool is a good answer when the data already sits in a proper database and your users are office staff on decent connections. Airtable is excellent for structured lists until the record count and the automation limits bite, or until you need it to work in a chiller where the wifi does not reach. The gap in Nelson is specific: the people who need to enter data are on a line, on a wharf, in an orchard block or on a boat, and the output is often a label, a run sheet or a docket that has to print reliably.
Why the usual tools struggle in Nelson
- A critical spreadsheet with no version control, no audit trail and one person who knows the formulas
- Double entry between the operational spreadsheet and the accounting or stock system, with the two never agreeing
- Seasonal staff trained on a tool that is hostile to anyone who has not used it for three seasons
- Automations in Airtable or Zapier that fail silently, so nobody notices a missed dispatch until the customer calls
What a custom internal tools build changes
Internal tools are where custom software has the best return, because scope is small and the pain is precise. You are not replacing an ERP (Enterprise Resource Planning). You are taking one workflow that costs somebody four hours a week and thirty minutes of panic a day, and giving it a screen designed for the person doing it. In Nelson the highest value builds we see are grade out capture, crew and line scheduling, bin and lot reconciliation, and dispatch run sheets. These often become the first module of something larger, feeding inventory, warehouse and reporting systems later.
- The spreadsheet has become an operational dependency and only one person can maintain it
- Users are in the field or on a line, and connectivity or gloves make a browser form unworkable
- You need printed output such as labels, dockets or run sheets as part of the workflow
- Two systems disagree and someone reconciles them manually every week
- Your users are office based with reliable connectivity and the data already lives in a database
- The workflow is a form, a table and an approval, which Retool will handle in days
- Under a few thousand records with light automation, where Airtable is genuinely fit for purpose
- The process is still changing weekly and needs to settle before anyone codes it
- One workflow fixed properly in six to fourteen weeks rather than a two year platform programme
- Screens designed for the actual environment, whether that is a chiller, a wharf or the back of a shuttle van
- An audit trail, so you know who recorded a grade or changed a schedule and when
- No key person risk, because the logic sits in documented software rather than in someone's macros
- A working proof of value that makes the case for a larger build far easier to fund
- Small tools multiply. Five separate internal apps with five separate logins is its own problem
- You still need hosting, backups and someone to call when it breaks, even for a NZ$30,000 tool
- If the underlying process is broken, software makes it faster and does not make it better
- Retool or Airtable might genuinely be enough, and a good consultant will tell you so before quoting a build
The features that matter for Nelson
Internal Tools services we deliver in Nelson
Digital Heroes builds the full internal tools stack for Nelson teams. Typical engagements cover business process automation, data-entry tools, admin panel development, internal dashboards and Retool alternative.
Internal Tools pricing in Nelson: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single workflow tool, for example grade out capture | NZ$25,000 to NZ$40,000 | 6 to 9 weeks |
| Multi screen tool with printing and offline capture | NZ$40,000 to NZ$70,000 | 9 to 14 weeks |
| Suite of connected tools with shared login and data | NZ$70,000 to NZ$130,000 | 4 to 6 months |
From kickoff to launch: the schedule
Exactly what you get
One workflow, done properly: the capture screens, the supervisor view, the printed output, the reports, and a clean export. Hosted somewhere you control, with backups and a documented restore. The scope is deliberately small so it can be delivered before your next busy period rather than after it.
The part people underestimate is training material for seasonal staff. If your crew turns over between seasons, you need a one page guide and a five minute video, not a manual. We build that into the delivery because a tool nobody can teach quickly is a tool that gets abandoned by week three of harvest.
How to choose a developer in Nelson
For internal tools, choose on responsiveness rather than reputation. You want someone who will make a change in days when the packhouse supervisor discovers the grade list is missing an option. Ask what a small change costs and how it gets requested, and get that in writing before you start.
Also ask what happens if you want to extend this into a bigger system in two years. The answer should involve a real database, an API and code you own, not a proprietary builder that traps your data. Nelson operations that started with a NZ$30,000 tool and grew it into an operational core did so because that first build was made on solid foundations.
- !They never suggest Retool or Airtable as an option. A consultant who only sells custom builds is not advising you
- !No site visit before quoting. Ask them to stand on the floor and watch the workflow for an hour
- !The plan ignores printing. Ask specifically how labels and dockets will come out of your existing printers
- !They quote a platform, not a tool. Ask what the smallest useful version is and what it costs
If internal tools is on the roadmap, custom software, wordpress, accounting usually follow within the year. Budget them as one conversation. Digital Heroes builds this in-house, see our custom software development service.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
Shaurya builds cross platform apps in React Native at Digital Heroes, sharing logic between iOS and Android and dropping into native code where the shared layer runs out. His posts are useful for teams estimating a cross platform build and wondering where the hidden work sits.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does an internal tool cost for a Motueka packhouse?
A single workflow such as grade out capture or bin reconciliation runs NZ$25,000 to NZ$40,000 over six to nine weeks. Add offline capture, label printing and a supervisor dashboard and you are at NZ$40,000 to NZ$70,000. This is the least risky software spend in your business because the scope is small enough to see the whole thing.
Is Retool good enough for our packhouse or should we build?
Retool is genuinely good when your data already sits in a database and users are on laptops with reliable wifi. It struggles when users are offline, when you need reliable label printing, or when the interface has to be usable by a seasonal worker in a cold store. If two or more of those apply to you, a purpose built tool is the better spend.
Can an internal tool work in an orchard block with no mobile coverage?
Yes, if it is built offline first. Records are written to the device and queued, then synced when the crew comes back into coverage at the shed. The important design decision is conflict handling, because two people editing the same bin record offline needs a defined rule rather than a silent overwrite.
Will it print labels on the printers we already own?
It should. Most Nelson packhouses and processors run thermal or Zebra label printers, and a properly built tool talks to them directly rather than generating a PDF someone has to open. Confirm your printer models during discovery, because label layout and printer language work is real effort that belongs in the quote.
How do we avoid ending up with five disconnected internal apps?
Insist on shared authentication and a shared database from the first build, even if you only need one tool today. The cost difference at the start is small and it saves an expensive consolidation later. If a supplier proposes a standalone app with its own login, ask what the plan is when you build the second one.
Can our own staff make changes after launch?
Some parts, yes. Reference data such as grades, blocks, crew and product codes should be editable by your supervisor through an admin screen without a developer. Logic changes need code. A good build draws that line deliberately so you are not paying for a developer to add a new apple grade.
How quickly can this be live before harvest?
Six to nine weeks for a focused tool, so a decision in November comfortably makes a February start. Leave less than eight weeks and you are testing during your busiest period, which is where internal tool projects usually fail. Digital Heroes will normally decline a go live inside a peak window and propose a parallel run instead.
What if the process changes next season?
Then you change the tool, which is the advantage of owning it. Budget a small change allowance each year, typically NZ$4,000 to NZ$10,000 for a tool of this size, and treat it as normal operating cost. Processes in a seasonal business always shift, and a tool that cannot move with them becomes the next spreadsheet.
Does an internal tool replace our accounting or stock system?
No, and it should not try. It fixes one workflow and hands data to the systems you already run, typically Xero for finance and whatever holds stock. If the tool starts absorbing stock control and invoicing, you have quietly started an ERP project and should scope it as one.
Will an app built for 10 users survive growing to 500?
What questions should I ask a development agency on the first call?
Can I build my product on a no-code tool like Bubble instead of hiring developers?
When does a company outgrow Airtable?
What does an internal tool cost for a small business with 20 to 50 employees?
What does it cost to keep an internal tool running after launch, and do we need to hire a developer?
Is a custom internal tool secure enough for HR records and financial data?
Can we migrate years of data out of our current system into new custom software?
Who can build custom internal tools for a business in Nelson?
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 Nelson 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.
