Internal tools development in Blenheim, for the spreadsheets running your winery that nobody is allowed to touch
Replacing the critical spreadsheets in a Blenheim operation with proper internal tools typically costs NZ$25,000 to NZ$90,000 and takes four to fourteen weeks, which makes it the highest return software spend most Marlborough businesses can make. You are not buying a platform. You are buying the end of the situation where one person's laptop holds the tank sheet, the pruning gang hours and the harvest forecast, and everyone else waits for them to be back from lunch.
There is a workbook somewhere in your business that decides real money. Maybe it is the tank and blend sheet, maybe it is the pruning contractor hours by block, maybe it is the mussel line seeding and harvest planner. It has forty tabs, six of them hidden, and a formula written in 2019 by someone who left. During vintage it gets emailed around and three versions exist by Friday.
Retool and Airtable are genuinely good and worth trying first. They fall down in two predictable places here. The first is offline: Airtable does not work in a shed at the back of a Rapaura block or on a barge in Kenepuru Sound, and that is where the data is created. The second is rules. Once your logic includes piece rate top-ups to minimum wage, tonnage bands per grower, or a growing area status that invalidates a planned harvest, you are writing an application inside a low-code tool and paying per seat for the privilege.
The problems nobody warns you about
- One spreadsheet holds operational truth and one person holds the spreadsheet, so their annual leave is an actual business risk during a season you cannot pause.
- Vintage produces three simultaneous versions of the same sheet, and reconciling them afterwards takes days you should have spent on the wine.
- Contractor and gang hours are recorded on paper in the block, keyed in later, and the transcription errors only surface when someone disputes an invoice.
- Nobody can safely change the workbook, so obvious improvements go unmade for years and workarounds accumulate around the outside.
The case for owning your internal tools
Internal tools are where custom software has the shortest path to value, because the scope is small and the users are your own staff. A purpose-built tool encodes the rules once, records who changed what, works on a phone with no signal, and lets three people work at the same time without emailing files. Most importantly it is boring and cheap relative to an ERP (Enterprise Resource Planning), so you can build the two tools that hurt most this year and decide about the rest later, having learned something.
Budgeting a internal tools build in Blenheim
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single tool replacing one critical spreadsheet | NZ$25,000 to NZ$45,000 | 4 to 8 weeks |
| Two or three connected tools on a shared data model | NZ$50,000 to NZ$75,000 | 8 to 12 weeks |
| Tool suite with offline mobile capture and Xero integration | NZ$70,000 to NZ$90,000 | 10 to 14 weeks |
| Support and small changes after launch | NZ$900 to NZ$3,000 per month | ongoing |
What your build should include
What we build under internal tools in Blenheim
Everything an internal tools build here can cover: admin panel development, internal dashboards, Retool alternative, workflow automation, back-office software and operations tooling.
Exactly what you get
A web application your team logs into, a mobile capture experience that works offline, and the data behind it in a real database you own. For a first tool the scope should be uncomfortably narrow: one process, done properly, live in weeks.
The deliverables that matter beyond the screens are a documented data model, a tested restore, and an export path so nothing is trapped. Ask for the migration of your historical spreadsheet data as part of the build rather than as a later project, because a tool that starts empty gets used half-heartedly and a tool that already contains three seasons of history gets used immediately.
How to choose a developer in Blenheim
For internal tools, seniority beats team size. You want one experienced developer who will spend a morning watching your cellar hand record tank movements, not a team of five running a discovery workshop in a boardroom. Ask who specifically will write the code and whether you can meet them.
Pin down the offline requirement in writing, including what happens when two people record against the same record while disconnected. That single question separates developers who have shipped field software from those who have only built dashboards.
Agree a fixed scope and a fixed price for the first tool. It is small enough to estimate honestly, and it gives you a low risk way to test whether you want to work with this team on anything larger, such as inventory or a full custom platform.
- !They propose rebuilding every spreadsheet at once. Ask which single tool they would build first and why, then judge the reasoning.
- !They have not asked where the data is created. Ask directly whether the tool works with no signal at a block or on a barge.
- !They quote a platform licence plus development. Ask what happens to your tools if you stop paying the platform.
- !They skip the audit trail because it is not in the brief. Ask how you would settle a disputed contractor invoice six months later.
- !They will not commit to a working version in under eight weeks. For a single internal tool, that timeline is a warning sign about their process.
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.
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Salesforce research indicates sales reps spend only about 30% of their time actively selling, with much of the rest lost to administrative work including manual CRM data entry and updates. Source: Salesforce (2024) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
Lila builds email and lifecycle programs: welcome flows, abandoned cart sequences, segmentation and the deliverability work that decides whether any of it arrives. Her posts are practical for commerce teams weighing what to automate and what a properly maintained list is worth.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
How much does it cost to replace a critical spreadsheet in a Blenheim winery?
A single well scoped internal tool replacing one business-critical spreadsheet runs NZ$25,000 to NZ$45,000 and takes four to eight weeks. Adding offline mobile capture for block or barge work pushes it toward the upper end. Ongoing support afterwards is usually NZ$900 to NZ$3,000 a month depending on how often you want changes.
Can we just use Airtable or Retool instead of building something custom?
Often yes, and you should try. They stop working when your data is created offline in a Rapaura shed or in Kenepuru Sound, when your logic includes real rules like piece rate top-ups or tonnage bands, or when per-seat pricing across a seasonal workforce starts costing more than a build. Try the cheap option first and let it fail honestly.
Will an internal tool work at a vineyard block with no mobile coverage?
It will if it is built offline first, meaning the app stores records locally, queues them, and syncs when signal returns with explicit conflict handling. This is a design decision made at the start, not a feature added later. Ask any developer to describe their conflict resolution approach before you sign.
How do we stop internal tools turning into the same mess as our spreadsheets?
Agree one shared data model before you build the second tool, so blocks, tanks, growers and staff are defined once and referenced everywhere. Sprawl happens when each tool invents its own version of a grower. A half day of data modelling at the start prevents a year of reconciliation later.
Can internal tools handle contractor hours and piece rates for pruning gangs?
Yes, and this is one of the strongest use cases in Marlborough. The tool records hours or piece counts per person per block, applies the top-up arithmetic required to meet minimum wage obligations, and produces a payable summary the contractor and your payroll both accept. It also gives you a defensible record if the calculation is ever questioned.
How long before staff actually adopt a new internal tool?
In our delivery experience adoption is decided in the first two weeks, and it hinges on whether the new tool is faster than the spreadsheet for the person doing the work. Migrate historical data before launch so the tool is useful on day one, and have the developer present on site during the first busy period rather than available by email.
Should we build internal tools before an ERP?
Almost always yes. Two or three internal tools cost a fraction of an ERP, deliver value in weeks, and teach you what your real requirements are. Many Blenheim operations find that once the three worst spreadsheets are fixed, the ERP case is much smaller than they thought.
Who owns internal tools built by an agency?
You do, including source code, database and hosting accounts, with everything transferred to your own organisation. This matters more for small tools than people expect, because they are the ones most likely to be handed to a different developer for a quick change in two years.
What happens to our internal tools during vintage when nobody has time?
Nothing should need to happen, which is the point of scoping them properly. Agree a change freeze from before first pick until after the last ferment, and have your support arrangement guarantee response times during that window. Any developer who wants to deploy changes in the middle of your crush has not understood the operation.
What tech stack should an internal tool be built with?
At what point does Retool cost more than building a custom tool?
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Who owns the code when an agency builds our internal tool?
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
When does a company outgrow Airtable?
Who owns the code when an agency builds my software?
Should I hire a freelancer or an agency for my software project?
How much should a small business budget for its first custom app or website?
What are the most common mistakes companies make when building internal tools?
What should I prepare before contacting an agency about an internal tool?
Who can build custom internal tools for a business in Blenheim?
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 Blenheim 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.
