What does custom software cost in New Zealand?

A starting price is a scope threshold

YuNet’s narrowly scoped custom software MVPs are priced from NZ$20,000+GST. That is an entry point for a defined first release, not a fixed price for every customer portal, warehouse or business system.

The reliable quote follows discovery: which people and records are involved, what must connect, what needs migrating and how the finished work will be accepted. Separate discovery work, if required, is agreed before it starts.

Five things that change the scope

• People and permissions: staff, customers and managers may need different views, approvals and an audit trail. Specify who can see and change each record.
• Workflows and exceptions: receiving a normal order is only one path. Include corrections, returns, cancellations and the person who resolves a disagreement.
• Integrations: identify the system that owns each record, the sync direction, access permissions and what should happen when a connection fails.
• Migration: check the condition of existing stock, customer and transaction records, what needs cleaning and which history must remain available.
• Sites and rollout: one team using one workflow is different from several warehouses changing systems while the business stays open.

Choose the first useful release

Reduce the first release to a workflow a real team can use. The aim is a working business process with clear acceptance checks, rather than a long list of disconnected features.

1. Choose one workflow, site or team, and describe its normal path and important exceptions.
2. Agree the records and connections needed on day one, and how the current operation will keep running during the change.
3. Write down acceptance checks, training and handover. Keep later features in a separate list with their own scope.

Budget for operating the system too

Ask for one-off and ongoing costs separately. A development quote should make clear which of these are included and which are paid outside the build.

• Hosting, backups, monitoring, recovery and the person responsible for keeping the system available.
• Third-party licences, payment services, integrations and usage-based services such as AI. Their fees and limits can change independently of the build.
• Maintenance, security updates, support, training and future changes. Clarify ownership, access, data export and handover terms.

What to prepare for a reliable quote

An anonymised example of a real job is usually more useful than a feature wishlist. You do not need a complete specification before contacting us.

• Describe what starts the job, who handles it, where delays occur and what a successful outcome looks like.
• List the current tools, the records to keep and the connections that must continue working.
• Name the first users or site, any fixed dates and the business constraints that affect a changeover.
• Ask the written scope to state deliverables, exclusions, assumptions, acceptance checks, migration and ongoing costs. Confirm GST treatment and how scope changes are agreed.

A concrete example of scope

MegaFood’s published case brings pallet movements, customer stock access and storage billing into one platform, with invoices sent to Xero and payment status syncing back. It shows what our team delivered; it is not a price or timeline estimate for your operation.