The Napier harvest spreadsheet has fourteen tabs, one author and no version history, and it is quietly running your business
Custom internal tools for a Napier operation typically cost NZ$25,000 to NZ$90,000 over 5 to 14 weeks, and they are the highest-return software most Hawke's Bay businesses can buy. You are replacing the spreadsheet one person maintains, the paper docket that gets wet in the rain, and the group chat where pick decisions actually get made.
There is a workbook on someone's laptop called something like Harvest 2026 Final v4. A tab per block, conditional formatting nobody dares touch, and a formula that broke three seasons ago and now gets corrected by hand. During vintage four people open it, two of them on a phone in a vineyard with one bar of signal. It is the most important system in your business and it has no backup, no audit trail and no owner.
Retool and Airtable get you further than most people expect, and for a while they are the right answer. The wall arrives at three predictable places: when a tool must work offline in a Bridge Pa block with no coverage, when permissions get serious enough that a casual worker must not see grower pricing, and when per-seat pricing scales faster than the value at peak headcount. At that point you are paying subscription fees for something you have already outgrown and cannot take with you.
Where the off-the-shelf tools fall short
- Critical harvest and packing logic lives in one spreadsheet with no version history and one person who understands it
- Field staff cannot record anything reliably in blocks with poor coverage, so data arrives hours late and half remembered
- Airtable and Retool permissions are too coarse to hide grower pricing or wage rates from seasonal staff
- Every year someone rebuilds last season's spreadsheet from scratch because nobody trusts the old one
Custom internal tools: what Napier teams actually get
Internal tools have the shortest path to payback in custom software, because you are automating a task you can already measure in hours. A purpose-built intake app that a weighbridge operator uses in gloves, in the rain, in ten seconds, saves more per vintage than most enterprise licences cost. Build offline-first, sync when signal returns, put role permissions in from day one. The scope is small enough to ship in weeks and specific enough that no vendor will ever build it for you.
- A spreadsheet failure during vintage would materially cost you money and it has already come close
- Field staff work where coverage is unreliable and current tools assume connectivity
- Airtable or Retool seat costs climb faster than the value they deliver at peak headcount
- You need permission boundaries that no-code platforms cannot enforce properly
- The process is still changing weekly and you have not settled on how it should work
- Fewer than about ten people use the tool and all of them sit in the office with wifi
- You are testing a new operating model and expect to discard the first version
- A packaged product already covers 80 percent and the remaining 20 percent is preference, not necessity
- Field data captured once, where it happens, instead of reconstructed from memory at the end of a shift
- Offline-first operation that works in Gimblett Gravels and Bridge Pa blocks where coverage drops out
- Role permissions granular enough that a seasonal picker sees their own tally and nothing else
- No per-seat subscription that punishes you for hiring 120 people for six weeks
- Institutional knowledge moves out of one person's spreadsheet into a system with an audit trail
- Small tools multiply. Without an owner you end up with eleven internal apps and eleven logins
- Airtable ships a change in an afternoon. Custom takes a sprint, and impatient teams route around it
- Offline sync is genuinely hard engineering and adds real cost to what looks like a simple form
- You are now responsible for uptime during the six weeks of the year when downtime is unacceptable
Feature priorities for Napier teams
Internal Tools services we deliver in Napier
Everything an internal tools build here can cover: approval workflows, internal portal, business process automation, data-entry tools and admin panel development.
The honest cost picture for Napier
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single tool, for example offline harvest intake capture | NZ$25,000 to NZ$40,000 | 5 to 8 weeks |
| Two or three connected tools with shared login and permissions | NZ$40,000 to NZ$65,000 | 8 to 11 weeks |
| Internal platform with sync, audit trail and accounting integration | NZ$65,000 to NZ$90,000 | 11 to 14 weeks |
Timeline: what happens, and when
Exactly what you get
Usually three things: a mobile capture app that works without signal, a web console where the office sees the same data live, and an export feeding your existing systems. The capture app is deliberately plain and fast. Big targets, few fields, no scrolling, readable in direct Hawke's Bay sun. The console is where supervisors correct tallies, approve piece-rate counts and watch block progress against plan.
The third piece matters most and gets skipped most often: the sync engine resolving conflicts when two devices record against the same bin from opposite ends of a block. Get that wrong and the tool loses trust in week two. These builds usually feed onward into payroll and crew management, stock tracking and eventually a wider operations system.
How to choose a developer in Napier
Pick the agency that asks to come to the weighbridge. Internal tools live or die on ergonomics, and ergonomics cannot be gathered over a call. Someone who has stood beside an intake queue at 6am understands why a two-tap flow beats a beautiful form. Ask for the offline story in technical detail, including what happens on a device that has been out of range for six hours.
Be suspicious of anyone who wants to build everything at once. The right first project is one tool, in production, used by real people, inside eight weeks. If that lands, appetite for the next one appears on its own. If it does not, you have spent NZ$30,000 learning something important rather than NZ$150,000 learning the same thing. Insist on a rollback plan too, because during vintage the fallback has to be paper and it has to be practised.
- !They treat offline as a checkbox. Ask what happens when two people edit the same bin record with no signal
- !No interest in watching someone use the current spreadsheet. Ask them to spend half a day on site before quoting
- !They propose a heavyweight framework for a four-screen tool. Ask why, and what maintenance looks like
- !Permissions discussed as an afterthought. Ask how they stop a casual worker seeing grower rates on day one
If internal tools is on the roadmap, custom software, wordpress, accounting usually follow within the year. Budget them as one conversation. Weighing options across the region? We publish the same internal tools guide for Hastings. 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.
- In a February 2026 survey of 517 small-business employers, 82% had adopted at least one AI tool (typical firm uses five), 66% reported revenue increases linked to AI (22% reported gains exceeding 10%), and 74% said digital platforms make it easier to compete with larger firms; owners saved a median of 5 hours per week and businesses saved a median 11.5 employee-hours weekly. Source: Small Business & Entrepreneurship Council (SBE Council) (2026) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
- Acquiring a new customer is five to 25 times more expensive than retaining an existing one, and research by Frederick Reichheld of Bain & Company found that increasing customer retention rates by 5% increases profits by 25% to 95% - underscoring the ROI of support that keeps customers. Source: Harvard Business Review / Bain & Company (2014) →
Charlie writes the words inside and around the products the team builds: interface copy, onboarding, product pages and the explanations that stop support tickets. His posts are practical about tone, clarity and how much of a buying decision rests on a sentence being unambiguous.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does an offline harvest data app cost to build in Hawke's Bay?
NZ$25,000 to NZ$40,000 for a single well-built tool covering bin counts, pick tallies and block observations with offline sync. Offline capability is the main cost driver, often around 40 percent of the build, because conflict resolution is real engineering. A connected-only version would be cheaper and would fail in exactly the blocks where you need it.
When should we move off Airtable for our Napier operation?
Move when one of three things is true: seat costs at peak headcount exceed what a build would amortise to, permissions are too coarse to hide wage or grower pricing, or field staff need it to work without signal. Until then Airtable is a good answer, and switching early wastes money you could spend on the tool that actually matters.
Can internal tools work in vineyard blocks with no mobile coverage?
Yes, if they are built offline-first from the start rather than retrofitted. The app stores records locally, queues them, and syncs on reaching coverage, with a defined rule for what wins when two devices conflict. Retrofitting offline into a connected app later usually costs more than building it correctly at the outset.
How do we stop seasonal pickers seeing grower pricing?
Role-based permissions enforced on the server, not hidden in the interface. A picker account sees their own tally and nothing else, a supervisor sees the block, the office sees rates. This is a common reason Napier operators outgrow no-code tools, where permissions are typically per table rather than per row.
Do we own the code for internal tools built by an agency?
You should own it outright, with the repository transferred and third-party licences in your name. Internal tools are the ones most likely to need small changes years later, often by someone else, so a clean handover with documentation matters more here than on a large system. Put it in the contract before the first sprint.
How long does it take to replace our harvest spreadsheet?
Five to eight weeks for a first production version, assuming access to the spreadsheet and half a day at the weighbridge. We would run it in parallel with the spreadsheet for the first fortnight of vintage, then retire the sheet once the numbers match. Do not attempt the cutover mid-harvest without a parallel run.
Will custom internal tools handle piece rates that must meet minimum wage?
They can, and this is a strong reason to build. Under New Zealand law a piece-rate worker still has to earn at least the minimum wage for hours worked, so the tool records both the tally and the hours and flags any shortfall for top-up. Spreadsheets miss this until an audit or a complaint surfaces it.
What does maintenance cost for a set of internal tools?
Budget roughly NZ$500 to NZ$1,500 a month per active tool for hosting, monitoring, security updates and small changes. That figure rises during vintage when response times matter and falls in winter. The alternative, an unmaintained tool that breaks in February, has a much higher effective cost.
Should we build one big tool or several small ones?
Several small ones sharing a login and a permission model. Small tools ship faster, earn trust faster and can be retired independently when a process changes. The failure mode is eleven disconnected apps with eleven logins, which is why the shared authentication layer belongs in the first project rather than the fourth.
How do I calculate the ROI of a custom internal tool?
When does a company outgrow Airtable?
How do I vet a development agency for an internal tools project?
How long does it take to build a custom web or mobile app from scratch?
What should I prepare before contacting an agency about an internal tool?
How many developers does it take to build an internal tool?
What does it cost to keep custom software running after launch?
Can we start on Airtable or Retool now and move to custom software later?
Who can build custom internal tools for a business in Napier?
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 Napier 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.
