Three Variables Nobody Sells Software For: The Tide, The Forecast, and How Much You Are Allowed to Catch
Custom software for a Nelson operation typically costs NZ$60,000 to NZ$220,000 over four to nine months depending on how much of the business it covers. The reason generic SaaS keeps failing here is not quality, it is assumption. Almost every off the shelf product assumes a plan you set and then execute. Nelson businesses run on three inputs they do not control: the tide, the weather, and a regulated entitlement to harvest. Digital Heroes has delivered 2,000+ builds, and the pattern that works locally is to model those constraints explicitly rather than pretending the calendar is stable.
You have probably already run the trial. A promising platform, two weeks of enthusiasm, then the moment where you realise it cannot express something basic about your operation. That the departure time depends on high tide at Kaiteriteri, not on a fixed 9am slot. That a harvest area can be closed on a biotoxin result and every plan built on it evaporates. That you cannot sell what you cannot catch, and what you can catch is capped.
So you keep the platform for the bits it does well and you build the rest in Excel. Six months later there are four spreadsheets, two shared inboxes and a WhatsApp group doing the actual coordination, and the software you pay for is a system of record for decisions made somewhere else. That is the real cost of generic SaaS in a constrained business: not the licence fee, the parallel process it forces you to run.
Why the usual tools struggle in Nelson
- Core scheduling decisions made outside the software because the software cannot express tide, weather or area status
- Three or four systems holding different versions of the same order, batch or booking
- Reports that take a person two days a month to assemble by hand from exports
- Growth blocked by a process that only works because two experienced people hold it together
What a custom custom software build changes
Build custom when your constraint is the business. If the difference between a good week and a bad one is how fast you can re plan when conditions change, then re planning is your product and it deserves purpose built software. In Nelson that usually means a system that knows tide windows, weather forecasts, harvest area open and closed status, entitlement or contract limits, and crew availability, and can produce a revised plan in minutes. Around that core sit the familiar pieces: CRM (Customer Relationship Management), inventory, booking and reporting, most of which can be bought or built cheaply once the core is right.
- Your competitive advantage is operational responsiveness rather than product alone
- You have evaluated three platforms and each failed on the same structural assumption
- Manual coordination is capping growth and hiring more coordinators is not scaling
- You expect to run this business for five years or more, which is the horizon custom pays back over
- Your process is close to standard and the platform gap is convenience rather than capability
- You are under about NZ$3 million turnover with a small team and no internal project owner
- Cashflow makes a NZ$100,000 capital project genuinely risky this year
- A specialist industry product already exists and covers most of what you need
- The re plan takes ten minutes instead of an evening, which is where the money actually is
- One version of the truth for orders, stock and commitments across the whole operation
- Constraints enforced by the system, so nobody promises product from a closed area or an exhausted entitlement
- Process encoded in software rather than held in two people's heads, which makes the business saleable
- You can change it. When the operation shifts, the software follows within weeks rather than never
- It is a capital project with real risk, and a badly scoped custom build is worse than living with SaaS
- You inherit responsibility for security, hosting, backups and upgrades permanently
- The first version will be wrong in places, and you need budget for a second pass after real use
- Custom software is only as good as the process decisions behind it, and those decisions are yours to make
The features that matter for Nelson
Nelson custom software: the full scope
Everything a custom software build here can cover: MVP development, legacy modernization, systems integration, microservices, database design, bespoke software development and SaaS development.
Custom Software pricing in Nelson: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| One critical workflow built properly | NZ$35,000 to NZ$70,000 | 8 to 14 weeks |
| Operational core covering planning, stock and orders | NZ$90,000 to NZ$160,000 | 5 to 8 months |
| Full platform with mobile, portal and integrations | NZ$160,000 to NZ$260,000 | 8 to 12 months |
From kickoff to launch: the schedule
Exactly what you get
Working software, the source code, the infrastructure definition and documentation that lets someone else take over. Delivered in phases so you can stop after phase one if it is not working out, which is the single best risk control available to you. Anyone unwilling to structure the work that way is protecting themselves rather than you.
Expect a discovery output before any build starts: a written process map, a prioritised feature list, a phase plan and an estimate range with the assumptions stated. If that document does not describe your business accurately enough that your operations manager nods at it, do not proceed to build.
How to choose a developer in Nelson
You are choosing a business relationship that will outlast most staff hires. Weight it accordingly. Look for a team that has shipped operational software for a constrained, seasonal or perishable business, that will put a senior person in the room during discovery, and that talks about your process before talking about technology.
Nelson buyers often compare a local contractor, a Christchurch or Wellington agency, and an offshore team. All three can work. What decides it is who will still answer the phone in year three, and whether the code they leave behind can be picked up by someone else. Ask every candidate what happens if they get hit by a bus, and take the quality of the answer seriously.
- !They agree to everything in the first meeting. Ask what they think is a bad idea in your brief
- !No paid discovery. Ask for a written scope and estimate range you pay for before committing to a build
- !They cannot name a comparable project. Ask for two references you can phone this week
- !Fixed price for an undefined scope. Ask for phased pricing with a firm price per phase instead
- !Hosting and support terms left until after launch. Ask for the annual cost in writing before you sign
Most Nelson teams pricing custom software end up comparing notes on website, inventory management, warehouse management too; the systems share one data spine. 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.
- 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) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
Sara works on Shopify builds at Digital Heroes, turning design files into working storefronts and adjusting them once traffic reveals what shoppers actually do. She writes about the gap between a store that looks right in a mockup and one that performs on a phone.
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 Nelson aquaculture or seafood business?
One workflow built properly is NZ$35,000 to NZ$70,000 over eight to fourteen weeks. An operational core covering planning, stock and orders is NZ$90,000 to NZ$160,000 over five to eight months. A full platform including mobile and partner portals reaches NZ$260,000. Digital Heroes almost always recommends starting with the single workflow that hurts most.
How do we know if we should build or just configure Odoo?
Run a structured evaluation against the three or four things that actually decide your week. If a configured platform can express tide windows, area closures and your allocation rules without heroic customisation, buy it. If it cannot, and you are already running spreadsheets alongside it, the platform is the expensive option because you are paying twice.
Do we need GST and New Zealand tax handled inside custom software?
Only where you raise or receive documents. Most Nelson builds push invoices into Xero or MYOB, which already handle GST at 15 percent and your myIR filing, so the custom system needs correct tax codes rather than a tax engine. If you export, the system also needs to distinguish zero rated export sales from domestic supply on every line.
Can we start small and grow the system?
Yes, and it is the right approach if the foundations are built properly. That means a real database, a documented API and code you own from the first phase. Nelson clients who started with a NZ$40,000 tool and grew it into an operational core did so because phase one was engineered as a foundation rather than a prototype.
How long until we see any return?
The first working phase typically lands in eight to fourteen weeks, and the return shows up as hours back in the operations office within the first month of real use. Full payback on a NZ$150,000 build usually takes eighteen months to three years, driven by labour saved, credits avoided and product not lost. Anyone promising payback in six months is selling.
Who owns the software and what if we change suppliers?
You own the code, the data and the infrastructure accounts. Insist that hosting is in your company's cloud account rather than the supplier's, because that single decision makes changing suppliers a handover instead of a hostage negotiation. Get the assignment of intellectual property written into the contract, not the proposal.
Should we hire developers in Nelson instead of an agency?
Hiring works once you have a system that needs continuous change and you can keep two or more developers busy. Below that, a single in house developer becomes a key person risk worse than the spreadsheet you replaced. Most Nelson operations of NZ$5 million to NZ$30 million turnover are better served by an agency build plus a support agreement.
What ongoing costs come after launch?
Hosting from NZ$200 to NZ$1,500 a month depending on size and redundancy, plus 15 to 20 percent of build cost annually for support, security patching and small changes. Add a change budget for the second year, because real use always reveals things discovery could not. Treat it as operating cost, not an overrun.
How do we avoid a failed build?
Phase the work, pay for discovery, appoint one internal decision maker with authority, and never schedule a go live inside your peak season. Most failed builds in our experience failed on those four points rather than on technology. Ask your supplier to hold you to them.
What should I prepare before contacting a software development agency?
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Who owns the code when an agency builds my software?
How do I vet a software agency before I sign anything?
We run everything on Airtable and spreadsheets. When is it time to go custom?
What happens if I stop paying for maintenance after launch?
Is a solo freelancer enough for my project, or do I really need an agency?
Should we build an MVP first or go straight to the full system?
How do I vet a software development agency before signing a contract?
How many people should be working on my software project?
Who can build custom software for a business in Nelson?
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 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 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.
