Software development company NZ quotes too steep? Three freelance developers build the one tool that replaces five subscriptions

Build or subscribe: when does a NZ SME need a software development company?

You need custom software when the tools you rent no longer match how the business runs and the gap costs you staff hours every week. If a standard product covers most of the job and the rest can wait, keep subscribing.

Many New Zealand SMEs grow into software along a familiar path. First a spreadsheet. Then a job management app such as Tradify or Simpro, an accounting file in Xero or MYOB, a form tool, a scheduling tool and a shared drive. Each one solves a problem, but nobody designed them to work together, so a person in the office becomes the integration: copying a customer from the enquiry form into the job app, then into Xero, then into a report.

That hidden labour is the signal. A software development company NZ owners bring in at this stage is not replacing everything. The best projects keep the products that work well, usually the accounting file, and build one piece in the middle that holds the data your business is really about.

• Build when two or more subscriptions overlap, staff retype data between systems daily, or customers ask for self-service you cannot offer.
• Subscribe when a mainstream product covers the workflow, your team is happy with it, and the only complaint is price.
• Integrate first when every tool is fine on its own and the pain is only the retyping; a sync job is cheaper than a new system.

If integration alone might solve it, our AI and workflow automation page for NZ covers lighter options that start at US$600.

The build vs subscribe maths against Tradify, Simpro and other per-user tools

The honest comparison is total cost over three to five years, including staff time, not the monthly fee against a build quote. Run the numbers with your own figures before anyone writes code.

Per-user pricing is the main thing that changes the maths. A job management product is excellent value for a four-person crew. For a forty-person business with office staff, subcontractors and managers who each need a login, the monthly bill grows with every hire, and you may still be paying for modules you never switched on.

Custom software flips that. You pay once for the build, then for hosting and whatever support you choose. Adding users costs little or nothing. The trade-off is that you own the roadmap: new features cost development time, and nobody ships improvements to you for free the way a SaaS vendor does.

Tradify and Simpro are mentioned because NZ trade businesses often compare against them; we have no partnership with either, and plenty of firms should simply keep using them.

What custom software do NZ small businesses actually commission?

Most requests fall into five shapes: a portal for customers or suppliers, an internal admin panel, a CRM-style pipeline, a management dashboard, and a replacement for an old system nobody can maintain.

A portal gives outsiders a safe window into your data. A landscaping firm might let body corporate managers see scheduled visits and completed-work photos. A wholesaler might let retail buyers reorder from their price list without phoning. An admin panel is the opposite: it is for your own staff, with forms, approvals and history in place of emailing spreadsheets around.

CRM-style tools make sense when your sales stages are unusual, for example a builder who needs consent status, engineer sign-off and client selections tracked per job. Dashboards pull numbers from Xero, the job system and the website into one view. Modernisation projects take an Access database or an old PHP app and move it to a maintained stack while staff keep working.

• Quote and job tracking with photos, variations and sign-offs
• Stock, orders and reorder points for small manufacturers or importers
• Booking and rostering tools where standard apps do not fit your rules
• Compliance registers: training records, equipment checks, site inductions
• Member or client areas with documents, messages and payment history

If yours is mainly a reporting problem, see our Power BI consultant page for NZ; a dashboard on existing data can be quicker than new software.

How can a small offshore team deliver custom software safely for a NZ business?

Safety comes from structure, not from geography: your accounts, your repository, small paid stages, written acceptance tests and a working demo at every step. With those in place, a remote team carries less risk than a local one run on handshakes.

Here is the structure we use. Before any build, you create or approve the cloud account, the code repository and the domain, all in your business's name. We are invited as users. Each stage in the quote ends with something you can click through, not a progress report. You test it against the acceptance list we agreed, and only then does the next stage start and the next invoice go out.

Access is scoped. We ask for the permissions a task needs, and you can remove them at any time from your own admin screens. Production customer data stays in your chosen region; for development we work with anonymised or sample records wherever possible.

• Your business owns the cloud account, repository, domain and third-party API credentials
• Stages of two to four weeks, each with a demo and a written acceptance list
• Pay per stage; stop after any stage and keep everything built so far
• Sample or anonymised data in development, live data only in your region
• Written handover notes updated at each stage, not only at the end

For a broader look at the model, read in-house vs outsourced software development.

Syncing custom software with Xero or MYOB: what works and what to avoid

Use the official Xero or MYOB API with an app registered under your own business, sync only the records the workflow needs, and decide which system is the source of truth for each field before building anything.

Whether your books live in Xero or MYOB, your custom tool should not try to become an accounting system. It should create draft invoices, look up contacts and read payment status, then let your bookkeeper do what they already do in the accounting file.

The design question that saves the most pain is ownership of each field. If a customer's phone number can be edited in both your portal and Xero, which one wins? We write that down per field in the scope. Then we build the sync to respect it, log every call, and retry sensibly when the accounting service is slow or a token has expired.

Deeper detail on the accounting side lives on our Xero integration developer page.

Where should your software development company host NZ data: Auckland or Sydney?

For most NZ SMEs, hosting in Sydney, Melbourne or Auckland keeps latency low for staff and customers and keeps data close to home. Auckland now has regions from both AWS and Microsoft, so a New Zealand-only setup is possible if your clients ask for it.

AWS lists Asia Pacific (New Zealand), code ap-southeast-6, alongside its Sydney and Melbourne regions, and Microsoft lists New Zealand North in Auckland among its Azure regions. Newer AWS regions have to be switched on in the account before use, which we walk you through during setup.

Which region is right depends on the services you need, your customers' expectations and cost. Some managed services arrive in newer regions later than in Sydney. Sydney is a sensible default for many projects; Auckland makes sense when a council, health or iwi-related client wants data held in New Zealand. Either way, the account and the bill are yours, and we document which region every component sits in.

• Region choice written into the scope, with the reason
• Automated daily backups, kept in the same country as the live data unless you choose otherwise
• Uptime and error alerts sent to your email as well as ours
• A short plan for restoring from backup, tested once before launch

The Privacy Act 2020 and a software team based overseas

Your business stays responsible for the personal information in your software, wherever the developers sit. Our job is to build it so that meeting your obligations is straightforward; your own lawyer confirms the legal position.

The Office of the Privacy Commissioner explains that when a cloud provider or contractor holds information purely on your behalf, it is generally treated as still held by you, while Information Privacy Principle 12 governs disclosures to overseas parties who use the information for their own purposes. In practice, that means we should act as your service provider with narrow access, and your hosting should sit where you decide.

The build supports that in concrete ways. We collect only the fields a workflow needs, which is what IPP1 expects. Access is role-based, so a subcontractor cannot see payroll. Sensitive fields are encrypted, admin actions are logged, and exports are limited to the people you nominate. If something goes wrong, the Act requires notifying the Commissioner and affected people about breaches likely to cause serious harm, and your audit log is what tells you who was affected.

We do not give legal advice and do not claim any certification. Ask your adviser to review the privacy statement and any data-processing terms before launch.

Who owns the code, and do you need software escrow?

You should own the code outright once each stage is paid, and it should live in your repository from the first commit. When the code is already yours, formal escrow is usually unnecessary for an SME project.

Software escrow exists to protect a buyer when the supplier holds the source code: a third party keeps a copy and releases it if the supplier fails. That makes sense for licensed enterprise products. For custom software built for one business, the simpler protection is to never let the supplier hold the only copy.

So the repository is created under your GitHub, GitLab or Azure DevOps account. We commit to it daily. Deployment scripts, database schema and environment settings (minus secrets) are in there too, along with a README that explains how to run the project locally. If you want belt and braces, a scheduled export of the repository to storage you control costs almost nothing.

• Repository in your account from day one, with us added as collaborators
• Intellectual property assigned to you in the written quote once each stage is paid
• Third-party libraries listed with their open-source licences
• No proprietary framework of ours that you would need to licence later

Commercial terms such as confidentiality are agreed in your written quote; our general terms of engagement set out the rest.

How do you choose a software development company in NZ or offshore?

Judge a supplier on how they scope, not on how they pitch. A good one asks awkward questions about your data, users and edge cases before quoting, and puts ownership, stages and acceptance criteria in writing.

A quick test: send the same two-paragraph brief to three suppliers. The weak reply is a price with no questions. The better reply lists what they assumed, what they need to know, and which parts of the brief are risky. The best reply suggests cutting something from the first release.

• Do they propose staged delivery with a demo at the end of each stage?
• Will the repository, hosting and API credentials be in your name?
• Can they explain their choice of stack in plain English?
• Who exactly will write the code, and can you talk to them directly?
• What happens to support after launch, and at what starting rate?
• How do they handle a change request halfway through a stage?
• Will they show you working software from a similar domain, even if anonymised?

We keep a longer list of questions to ask a developer before signing; most apply equally to web software. Our portfolio shows the kinds of projects the three of us have built.

How much does custom software cost in New Zealand, and what drives the price?

With us, a first release of custom business software starts at US$900 and usually takes 6–12 weeks. Local quotes vary widely; the difference mostly reflects team size, overheads and how much of the discovery work is included.

Rather than guessing at other suppliers' rates, it is more useful to know what makes any quote grow. The single biggest driver is the number of distinct user roles, because every role multiplies the screens, permissions and tests. Next come integrations, especially two-way accounting sync, then data migration from years of inconsistent spreadsheets.

• User roles: owner, office, field staff, customers, suppliers
• Screens and reports in the first release (fewer is faster and cheaper)
• Integrations: Xero or MYOB, email, SMS, maps, payment links
• Migrating and cleaning historical data
• Offline use or a companion phone app
• Audit, approval and permission rules
• How quickly you can review each stage

Our pricing page shows every starting price. For a feel of how app budgets are built, the app development cost guide for NZ uses the same staged approach.

The staged scope-to-launch process for NZ software projects

We build in four stages: scope, foundation, workflow and launch. Each ends with a demo you can click and a sign-off before anything further is billed.

Scope turns your brief into screens, user roles, data fields and acceptance tests. Foundation sets up hosting, logins, the database and the first real screen, usually the one your team uses most. Workflow adds the remaining screens, the Xero or MYOB link and the reports. Launch covers data migration, training videos, go-live and the first fortnight of close monitoring.

Because the stages are priced separately, you are never more than one stage of spend away from a decision. If the foundation demo reveals that the idea needs rethinking, we stop, rewrite the scope and requote the rest. Changing direction at week three costs a fraction of what the same change costs at week ten.

Which tech stack should a NZ custom software project use?

Choose a mainstream, well-documented stack that plenty of developers in New Zealand could pick up later. Boring is a feature when you own the code for ten years.

For most business software we use TypeScript with React or Next.js on the front end, Node.js or Python on the back end, and PostgreSQL as the database. Those choices mean a future NZ developer, an Australian contractor or another offshore team can read the code without learning anything unusual. We avoid proprietary low-code platforms for core systems because you would be renting again, just from a different vendor.

There are sensible exceptions. If your team lives in Microsoft 365, an internal tool on Azure with Microsoft sign-in may suit you better. If the workflow is simple and changes rarely, a well-configured off-the-shelf product plus a small integration can beat a full build. We will say so in the scope rather than build something you do not need.

Related reading: what a web application developer does and building software you might later sell as SaaS.

Red flags when hiring a software development company in NZ or overseas

Whether you hire a software development company NZ-based or a remote team, most failed projects share a small set of warning signs, and all of them are visible before you pay a deposit. Watch for vague scope, no staged payments and code held on the supplier's side.

The quiet risk is a project with no single decision-maker on the client side. Remote or local, software drifts when three managers give conflicting feedback. Name one person who approves each stage, and give them a couple of hours a week to do it properly.

• A single large upfront payment with no stage demos
• Code hosted in the supplier's own account 'until the end'
• A quote with no assumptions or exclusions written down
• Promises of every feature in the first release
• No mention of backups, error monitoring or who fixes bugs after launch
• A proprietary platform you cannot export from
• Reluctance to let you speak with the person writing the code

If a previous supplier has already left you stranded, read what to do when a developer leaves a project midway; we can audit and quote a rescue.

Working with a software team in India from New Zealand: the first two weeks

India is six and a half hours behind New Zealand standard time and seven and a half behind during NZ daylight time, from late September to early April. Our morning is your afternoon, so a 3 pm NZ call is easy, and anything you send before you leave work is usually answered or built by the next morning.

Quotes are in USD. You pay each stage by Wise, bank wire or PayPal; Wise is handy here because it converts straight from a NZD account. Invoices come from India, and we do not advise on how your accountant treats them. The agreement is the written quote plus our published terms, and ownership moves to you as each stage is paid.

Handover, maintenance and what happens after launch

After go-live you get 2 months of free maintenance for bugs and small adjustments. After that, care starts from US$120/mo, or you can take the code to another developer, since everything already sits in your accounts.

Software needs looking after in a way that a brochure website does not. Libraries receive security patches, the Xero or MYOB API changes versions, browsers update, and staff find edge cases nobody predicted. The free period covers the settling-in phase when most of those surprises appear.

Handover is continuous rather than a single event. By launch you have the repository, a README that explains local setup, a deployment guide, an architecture diagram, a list of every external service with its owner, and short screen-recorded videos showing admin tasks. If you later hire an in-house developer, those documents are their first week.

For ongoing support options, see maintenance and support from freelancers.

Does custom software help your NZ business get found online?

Internal software does not rank on Google by itself, but a customer portal or public tool can support your visibility when its public pages are fast, crawlable and clearly written. Anything behind a login is invisible to search engines, which is exactly what you want for private data.

The visibility wins usually come from the edges of the system. A public quote calculator, a service-area checker or a stock availability page can answer real searches if it has proper headings and loads quickly on a phone. Structured data on those pages helps search engines and AI answer tools understand what your business offers.

Google states it has no special requirements for appearing in AI Overviews beyond normal search best practice, so the same fundamentals apply: helpful content, a sound technical base and pages Google can index. If search visibility is the bigger goal, our SEO services for NZ businesses page explains the monthly work involved.

Worked example: a hypothetical Hamilton equipment-hire business

This scenario is invented to show how a staged project could run; it is not a client story. Say a Hamilton equipment-hire firm with twelve staff tracks hires in a job app, stock in a spreadsheet and invoices in Xero, and two office staff spend their mornings reconciling the three.

In the scope stage we would find that the job app is fine for scheduling deliveries, but stock availability, damage reports and deposits live in the spreadsheet. The recommendation would be a custom admin panel for stock and hires, a small customer portal to check availability and sign hire agreements, and a one-way push of invoices into Xero. First release from US$900, planned over about ten weeks.

Foundation would deliver the stock register and a working hire screen on AWS in Sydney, under the firm's own account. Workflow would add damage photos, deposits, the Xero push and a dashboard of utilisation by item. Launch would import three years of spreadsheet history after cleaning duplicate item codes. The owner could then decide whether to drop the job app later or keep it; nothing forces that choice.

Checklist before you contact any software development company in NZ

Preparing six things before the first call halves the time to an accurate quote and makes supplier comparisons fair. None of them requires technical knowledge.

• A list of every tool you pay for today, with monthly cost and number of users
• The one workflow that hurts most, written as steps a new employee would follow
• Sample documents: a quote, a job sheet, a report, the spreadsheet you want gone
• Who will use the software, grouped by role, with rough numbers
• Any systems it must talk to: Xero, MYOB, email, SMS, your website
• Your preferences on hosting location and who approves each stage
• A realistic budget band and a date that actually matters

Send those on WhatsApp or through our contact page and we will reply with questions and a staged quote.