You export a Dunedin-built machine to a plant in Nebraska, then fly a technician fourteen thousand kilometres to read a fault log
Custom software for a Dunedin engineering or manufacturing exporter runs NZ$70,000 to NZ$220,000 over 5 to 10 months. Generic SaaS covers your email, your books, and your CRM (Customer Relationship Management). It does not cover the thing that makes you money, which is a machine you designed in Otago running in a plant on the other side of the planet, generating data nobody can see, on a service contract nobody can evidence. That software does not exist to buy because nobody else builds your machine.
The engineering is world class and the software around it is a folder of spreadsheets. Commissioning notes live in the installer's notebook. Spare parts get quoted from a price list someone updates when they remember. A fault at a customer site becomes a phone call at 3am New Zealand time, then a screenshot on WhatsApp, then a flight. You are running a global service business with the tooling of a local workshop, and every year the fleet gets bigger and the gap widens.
There is no product to buy for this. Off-the-shelf SaaS assumes your product is a subscription, not a physical asset with a serial number, a firmware version, a warranty clock, and a customer who bought it in 2019 and will still expect support in 2031. The moment you want fleet visibility, remote diagnostics, parts tied to configuration, and a service contract that can be proven met, you are building. The alternative is to keep paying for it in airfares and in the discount you give when a customer complains.
The problems nobody warns you about
- You cannot see the installed fleet, so a fault is reported by the customer rather than detected by you
- Machine configuration and firmware version live in commissioning notes, so spare parts get quoted wrong and shipped twice
- Service contract obligations are tracked in a spreadsheet, which makes renewal conversations weak and renewals cheap
- Every serious diagnostic starts with a time zone problem and often ends with a technician on a plane
The case for owning your custom software
Build when the software is inseparable from the product. A Dunedin machine builder's system holds an asset register keyed to serial number, telemetry pulled from the controller, a parts catalogue that resolves against the actual configuration on site, remote diagnostics that let an engineer in Dunedin see a fault at 9am local rather than 3am, and service contract tracking that produces evidence at renewal. That is a product decision, not an IT decision, and it changes what you can charge. Machines with proven uptime and remote support sell at a different price than machines with a phone number.
Budgeting a custom software build in Dunedin
| Project scope | Typical cost | Timeline |
|---|---|---|
| Asset register, parts, and service contract tracking | NZ$70,000 to NZ$110,000 | 5 to 6 months |
| Full platform with telemetry, diagnostics, and customer portal | NZ$155,000 to NZ$220,000 | 8 to 10 months |
| Telemetry and alerting added to existing systems | NZ$45,000 to NZ$85,000 | 3 to 5 months |
What your build should include
Custom Software services we deliver in Dunedin
The engagements Dunedin teams bring us most often: cloud software, MVP development, legacy modernization, systems integration and microservices.
Exactly what you get
A platform that turns your installed base into something you can see and sell against. Concretely: an asset register keyed to serial number, telemetry from the controller with alerting before failure, a parts catalogue that knows the exact configuration on site, remote diagnostic tooling with an access audit trail, contract evidence for renewals, and a customer portal that works in their working hours. You own the code, the data, and the deployment. Around the edges it meets custom ERP (Enterprise Resource Planning) software for production and costs, inventory management software for the spares holding, and supply chain software once parts start moving through Port Chalmers on a schedule.
How to choose a developer in Dunedin
The right team will ask to see the machine before they ask about your budget. Watch whether they talk to your service engineers or only to management, because the service engineers know which faults recur and which ones cost a flight. Ask what they would build first; if the answer is not the asset register, they have not thought it through. Check they can hold a serious conversation about network security with a customer's IT department, since that conversation will happen and you do not want to be translating it. And confirm who supports this in year seven, because your machines will still be running.
- !They have never integrated with industrial controllers; ask which protocols they have shipped against and where
- !Security is discussed only as a login screen; ask how a customer IT team will assess your connectivity request
- !No plan for machines that cannot connect; ask how a manual data path works for a customer who blocks outbound traffic
- !They propose starting with the customer portal; ask why, because the asset register has to exist first
- !Discovery is quoted at under two weeks; ask how they will understand your machine in that time
Teams investing in custom software in Dunedin usually scope it next to website, inventory management, warehouse management, since these systems share data and budgets. Weighing options across the region? We publish the same custom software guide for Queenstown. Want it built, not just budgeted? That is our custom software development practice.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- 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) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
Tom leads people operations for North America: hiring, onboarding, and keeping the day to day of employment running while teams work across five offices and several time zones. He writes about how staffing decisions shape delivery, which clients feel long before they hear about them.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does custom software cost for a Dunedin machine builder or exporter?
An asset register with parts and service contract tracking runs NZ$70,000 to NZ$110,000 over 5 to 6 months. A full platform with telemetry, remote diagnostics, and a customer portal is NZ$155,000 to NZ$220,000 over 8 to 10 months. Adding telemetry and alerting to systems you already run costs NZ$45,000 to NZ$85,000.
Can we monitor machines already installed overseas, or only new ones?
Both, but retrofitting is harder and should be priced separately. Older units often run different controllers and firmware, so each generation needs its own integration work and sometimes a hardware gateway on site. Start with new builds, prove the value, then retrofit the generations that represent the most service cost.
What happens when a customer's IT department refuses outbound connectivity?
Design for it from the start with a manual export path: the site pulls a diagnostic file locally and sends it to you, and the platform ingests it exactly like live telemetry. Perhaps a quarter of industrial customers will impose some restriction, and having an answer ready keeps the sale moving. Treat it as a required feature rather than an exception.
Does this actually reduce how often we fly a technician out?
In our delivery experience, the biggest saving is not eliminating travel but arriving prepared: the engineer already knows the fault, the configuration, and which parts to carry. Some faults resolve fully over a remote session, and those are pure saving. Model the business case on both effects rather than assuming remote fixes everything.
Who owns the machine data, us or our customer?
Settle this contractually before you build, because it becomes contentious later. The common position is that the customer owns operational data about their production while you retain machine health and diagnostic data needed to support the asset. Write it into your sale and service agreements, and make the platform enforce whatever you agree.
How long does a build like this take from first meeting to production?
Five to ten months depending on scope, with discovery alone taking three to four weeks because someone has to genuinely understand the machine. Expect the controller integration to be the least predictable part of the schedule. Plan a pilot on two or three friendly customer sites before any wide rollout.
Can we hire the developers for this in Dunedin?
Dunedin has strong engineering and software talent, and people here tend to stay, which matters for a system with a fifteen year life. Finding developers with industrial protocol experience specifically is harder and you may need to look to Christchurch or bring the capability in through an agency. Plan for a hybrid: agency depth plus one or two internal owners.
How does GST work when we sell software support to overseas customers?
Services supplied to non-resident customers who are outside New Zealand are generally zero-rated for GST, while domestic customers attract the standard 15 percent. The system needs to tag the customer's status and apply the right treatment on every invoice rather than leaving it to a bookkeeper. Get your accountant to confirm the treatment for your specific contracts before it is coded.
What should we budget for maintenance and hosting after go-live?
Plan 15 to 20 percent of build cost annually, plus telemetry hosting that scales with fleet size and data frequency. For a NZ$180,000 platform that is roughly NZ$27,000 to NZ$36,000 a year before hosting. Reducing telemetry sampling frequency is the easiest lever if hosting costs run ahead of expectations.
How long does it take from first call to software my team can actually use?
Does it matter which tech stack the agency wants to use?
Can I build my product on a no-code tool like Bubble instead of hiring developers?
How do I vet a software agency before I sign anything?
If an agency builds my software, who actually owns the code?
Will custom software work with the tools we already use, like QuickBooks and Stripe?
How do I calculate whether custom software will pay for itself?
Who owns the code when an agency builds my software?
Our developer disappeared mid-project. Can another team pick up the code?
How do I vet a software development agency before signing a contract?
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
Who can build custom software for a business in Dunedin?
Digital Heroes builds custom software 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 Dunedin 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 software 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.
