How Much Does Custom Software Cost in NZ? (2026 Price Bands)

“How much does custom software cost?” is the question every NZ business owner asks first and almost no software company answers on its website. The honest answer is a range, because a customer portal for a 12-person wholesaler and a nationwide job-management platform are different jobs. But the range is narrower and more predictable than the industry lets on, and the factors that move a project within it are knowable before you commit. This article gives you the 2026 bands we quote against, what drives them, how to compare a quote properly, and the questions to ask any supplier.

What does custom software cost in New Zealand in 2026?

These are the typical bands for Avtrix projects, all in New Zealand dollars, excluding GST, and always confirmed as a fixed price after a scoping session. Most NZ software companies charging senior local rates will land in similar territory; offshore-staffed quotes may look 30–50% lower and often cost more by the end (more on that below).

• Single automation or integration — NZ$500 to $5,000, one to two weeks. One workflow end-to-end: a web form into the CRM with a follow-up sequence, Xero synced with a job system, an automated weekly report. This is the smallest sensible engagement and the best way to test a supplier.
• AI agent or document-processing system — NZ$8,000 to $35,000, four to eight weeks. A custom agent that answers and acts on enquiries or calls, or a pipeline that reads invoices and forms into Xero or your ERP, integrated with your existing tools, with training and 60 days of support.
• Dashboards and data — NZ$5,000 to $25,000, three to six weeks. Xero, CRM and operational data connected, cleaned and modelled into live dashboards in Power BI, Looker Studio or a custom web app.
• Custom platform — NZ$25,000 to $150,000+, eight to twenty weeks. A web application, customer portal, job-management system, CRM/ERP or mobile app built around your process, delivered in stages. The lower end is a focused single-purpose system for a small team; the upper end is a multi-region, multi-role platform with mobile apps and several integrations.
• Running costs — from NZ$50 a month. Hosting (NZ$50–200/month for most SME systems), any AI usage passed through at cost, and optional managed support from NZ$300 a month.

Worked examples from our own projects: a nationwide trades business’s job-management platform (web + mobile + Xero integration) sat in the custom-platform band and returned 12 hours a week per manager and a 23% revenue lift — case study; a logistics company’s invoice automation sat in the AI/document band and cut a three-day monthly cycle to two hours — case study. The complete bands, payment terms and FAQs are on our pricing page.

What actually drives the price?

Not the number of screens. In our experience these five factors explain most of the variation between a NZ$30,000 project and a NZ$120,000 one:

1. How many systems must connect. One integration (say, Xero) is quick and well-trodden. Xero plus a CRM plus a job system plus a legacy Access database plus a supplier portal is where time goes — each connection needs mapping, error handling and testing.
2. How messy the data is. Ten clean invoice templates are easy. A thousand different supplier layouts, or fifteen years of customer records with duplicates and free-text addresses, need validation rules, clean-up and more testing.
3. How much judgement the software needs. Recording a job is simple. Deciding whether a job qualifies, pricing it from your rules, and booking it around crew availability is logic that must be specified, built and tested — and, if AI is involved, given guardrails and a human hand-off.
4. Roles, permissions and workflow complexity. One type of user doing one thing is a fraction of the cost of office staff, field crews, regional managers, clients and subcontractors each seeing and doing different things.
5. Compliance and security. Health information (Health Information Privacy Code), financial data, a large customer’s security questionnaire, or an audit requirement each add design and testing work — best done properly once, at the start.

Two things that don’t move the price as much as people expect: the technology stack (a competent team’s choice of framework is a rounding error against the factors above) and “making it look nice” (good design is included in any serious quote; it is not a premium line item).

Fixed price or hourly — which should you accept?

Fixed price, with a written scope, for anything you can define. Hourly billing with no ceiling gives the supplier no incentive to be efficient and gives you no certainty; half of all software projects come in over budget or late (Standish Group, 2020–2024 data) and open-ended commercial terms are a large reason why. A fixed-price supplier has to scope properly before quoting, which is the discipline that makes projects succeed anyway.

The fair version of fixed price looks like this: a written scope (what’s in, what’s out, which systems connect, the success metric); one price and one timeline; monthly running costs stated up front; milestone payments tied to demonstrated working software (commonly 40% at kick-off, 40% at the main milestone, 20% at go-live); and a change process — if you change the scope, you get a re-quote before the extra work, never a surprise invoice after. Time-and-materials is reasonable only for genuinely undefined discovery work, and even then it should have a cap.

Why do offshore quotes look cheaper, and are they?

They look cheaper because hourly rates in some countries are a fraction of NZ rates. They frequently cost more by the end because of what the rate doesn’t include: time-zone lag on every question, requirements lost in translation, a NZ-based “account manager” who isn’t the person building it, rework when the first version doesn’t fit how a Kiwi business actually runs (Xero, GST, NZ addresses, the Privacy Act, the way a trades crew works on site), and data sitting in a jurisdiction you’d have to justify under IPP 12. A NZ-based senior team costs more per hour and typically less per outcome, because there is less of everything except building. Ask any supplier: who exactly will write the code, where do they sit, and where will my data be hosted?

How do you compare a custom quote with off-the-shelf software?

Over five years, not one, and including the labour between systems. A five-year view for a 25-person business typically looks like: three overlapping SaaS tools at NZ$60–120 per user per month (NZ$45,000–90,000 over five years) plus the manual glue — one person spending a third of their week re-keying and reconciling, roughly NZ$25,000 a year — against a fixed-price build plus modest hosting and support that removes the glue in year one. Organisations run 150–300 SaaS apps on average and roughly half of paid licences sit idle (Zylo, 2026), so the audit alone often funds the build. The full framework — when to buy, build or integrate — is in off-the-shelf vs custom software.

What should a NZ business ask before signing?

• Can I see the written scope before I see the price? (If the price comes first, it’s a guess.)
• What is the success metric, and will you report against it after launch?
• Who will build it, where are they based, and will I talk to them directly?
• Where will my data be hosted, and is it used to train any model?
• What are the monthly running costs, itemised?
• What do I own at the end — code, data, accounts, prompts?
• What happens if scope changes? What happens if we stop after milestone one?
• Can you show me a comparable NZ project and let me talk to the client?

A good supplier welcomes every one of these. A supplier who deflects the first two is quoting a number they haven’t earned.

Frequently asked questions

Get a real number

Bands are useful for budgeting; a fixed price is what you can decide on. A free 30-minute discovery call is enough for us to tell you which band your project sits in and whether a smaller first step would prove it. From there, scoping produces the written scope and the one fixed price — no hourly rates, no surprises. See custom software development for how we build.

Sources

• Avtrix Software Solutions, pricing bands and client project data, 2025–2026
• Arcidiacono, IT project failure rates: 2025 update, PM World Journal, January 2026 — Standish Group CHAOS 2020–2024
• Zylo, 2026 SaaS Management Index — application counts and licence utilisation
• Office of the Privacy Commissioner, AI and the Information Privacy Principles — IPP 12 (disclosure outside NZ)

Cost bands are typical ranges, excluding GST; every Avtrix project is quoted fixed-price after scoping. Published 16 September 2026. Written by Ashok Poshamalla, Founder, Avtrix Software Solutions, Taupō.