Software Maintenance and Support Costs: What to Budget After Launch

IT support specialist and business owner reviewing system health dashboards on a laptop in a bright Auckland office

Launching new software feels like the finish line, but it is really the start of a long working life. Every application needs looking after once it is live: security patches, bug fixes, hosting, monitoring and the steady stream of small improvements your team will ask for. Software maintenance and support costs are often the least discussed part of a project budget, yet over several years they can add up to as much as, or more than, the original build. Understanding them early helps you plan with confidence and avoid unpleasant surprises.

This guide explains what maintenance and support actually involve, the main factors that drive the cost, typical ways New Zealand businesses pay for it and how to keep the total under control. If you are still at the budgeting stage for a new build, our guide to custom software development costs in NZ covers the upfront side of the equation.

What software maintenance and support actually covers

“Maintenance” and “support” are often used interchangeably, but they describe slightly different things. Support is about helping people and keeping the system available day to day. Maintenance is about keeping the software itself healthy, secure and fit for purpose over time.

Industry practice usually breaks maintenance into four types:

  • Corrective maintenance: finding and fixing bugs that appear in real-world use, including edge cases that testing did not catch.
  • Adaptive maintenance: keeping the software working as its environment changes, such as new browser versions, mobile operating system updates, changes to third-party APIs like Xero or payment gateways, and end-of-life frameworks.
  • Preventive maintenance: work that reduces future risk, such as dependency upgrades, security patching, performance tuning, refactoring messy code and improving automated tests.
  • Perfective maintenance: small enhancements and usability improvements based on user feedback, which is where most “can we just add…” requests land.

On the support side, you will typically see a help desk or ticketing process, incident response when something goes wrong, uptime monitoring, backup checks and hosting management. If your application runs in the cloud, ongoing infrastructure care is part of the picture too, which is where cloud and DevOps services come in.

Why ongoing costs are unavoidable

It is tempting to think well-built software should simply keep running. In practice, the world around it never stops moving. Operating systems and browsers update several times a year. Open-source libraries release security fixes. Apple and Google regularly change their app store requirements. Cloud providers retire older services. Integrations break when a partner changes their API.

There is also a compliance angle. Under the Privacy Act 2020, New Zealand organisations must take reasonable steps to protect personal information and notify the Office of the Privacy Commissioner and affected people about serious privacy breaches. Running unpatched software that holds customer or staff data is a real business risk, not just a technical one. Regular maintenance is one of the most practical ways to show you are taking those obligations seriously.

What drives software maintenance costs

No two systems cost the same to look after. These are the factors that make the biggest difference:

  • Size and complexity. More features, user roles and business rules mean more to test and more that can go wrong.
  • Number of integrations. Each connection to accounting, CRM, payment, shipping or government systems is another dependency that can change without warning.
  • Platforms supported. A web app alone is simpler to maintain than a web app plus native iOS and Android apps, each with its own update cycle.
  • Code quality and documentation. Clean, well-tested, documented code is far cheaper to change than a tangled codebase only one person understands.
  • Technology choices. Mainstream, actively supported frameworks are easier and cheaper to staff and update than niche or ageing ones.
  • Required response times. Business-hours support costs less than a 24/7 commitment with guaranteed one-hour response.
  • Hosting and licences. Cloud hosting, databases, email services, monitoring tools and third-party licences are recurring costs in their own right.

Typical budgeting approaches in New Zealand

A common rule of thumb used across the software industry is to budget somewhere around 15–25% of the original development cost per year for maintenance and support, excluding major new features. Treat that as an indicative starting point, not a quote. A simple internal tool with few users may need much less, while a customer-facing platform with many integrations and strict uptime needs may need more.

Here is how the main components usually stack up. Figures vary widely by provider and system, so use this as a checklist rather than a price list.

Cost component What it includes How it is usually charged
Hosting and infrastructure Cloud servers, databases, storage, backups, domains and SSL Monthly, based on usage (often billed in USD by cloud providers)
Third-party services and licences Email delivery, maps, SMS, monitoring, app store fees, paid libraries Monthly or annual subscriptions
Security and updates Patching, dependency upgrades, OS and framework updates Included in a support plan or billed hourly
Bug fixing and help desk Investigating issues, fixes, user questions Retainer with included hours, or time and materials
Monitoring and incident response Uptime alerts, error tracking, out-of-hours callouts Fixed monthly fee, with higher tiers for faster response
Small enhancements Minor features, reports, usability tweaks Hourly or drawn down from a block of hours

When comparing proposals, make sure prices are stated consistently, ideally in NZD excluding GST, and check whether hosting is passed through at cost or bundled with a margin.

Common support models and when each fits

Pay as you go (time and materials)

You only pay when something needs doing. This suits stable, low-risk systems with few users, though there is rarely a guaranteed response time and preventive work tends to be skipped.

Monthly retainer or support plan

A fixed monthly fee covers a defined set of services, such as monitoring, security updates and a set number of support hours. This is the most common choice for business-critical software because it gives predictable costs and a team that knows your system well.

Service level agreement (SLA)

An SLA formalises response and resolution times, often by severity. A total outage might require a response within an hour, while a cosmetic issue can wait for the next scheduled release. SLAs cost more, but they are worth it when downtime directly affects revenue or customers.

Dedicated or ongoing development team

If your software is central to how you compete, you may be better served by a small ongoing team that handles maintenance and a continuous roadmap of improvements. This blurs the line between support and software development, which is often a good thing.

How to keep maintenance costs under control

The cheapest maintenance is the maintenance you designed for from the start. A few habits make a big difference over the life of a system:

  1. Invest in quality during the build. Automated tests, code reviews and clear documentation cost a little more upfront and save far more later.
  2. Automate deployments and monitoring. CI/CD pipelines, error tracking and uptime alerts let problems be spotted and fixed quickly, often before users notice.
  3. Keep dependencies current. Small, regular upgrades are much cheaper than a painful jump across several major versions every few years.
  4. Review cloud usage. Right-size servers, remove unused resources and use reserved or scheduled capacity where it makes sense.
  5. Agree a clear scope. Separate “keep it running” work from new features so you can see what each is costing you.
  6. Plan a roadmap. Batching enhancements into planned releases is more efficient than a constant trickle of urgent requests.

If an older system is already expensive to look after, ongoing patching may not be the best use of money. Our article on legacy software modernisation explains how to decide between refactoring, rebuilding and replacing.

Questions to ask a support provider

Before you sign a support agreement, whether with the team that built your software or a new provider, ask:

  • What exactly is included in the monthly fee, and what is billed separately?
  • What are the response and resolution times for different severities, and are they available outside business hours?
  • Who will look after our system, and how is knowledge documented if team members change?
  • How are security updates handled, and how often are dependencies reviewed?
  • Where is our data hosted, how is it backed up and how quickly can it be restored?
  • Do we have full access to our source code, hosting accounts and credentials?

A good software development company will answer these clearly and put them in writing.

Frequently asked questions

How much should we budget each year for software maintenance and support?

A widely used guideline is around 15–25% of the original build cost per year, plus hosting and third-party services. It is only indicative. The real figure depends on complexity, integrations, the number of platforms and how quickly you need issues resolved.

Is hosting included in maintenance costs?

Not always. Some providers bundle hosting into a support plan, while others pass cloud costs through separately. Ask for hosting, licences and support labour to be listed as separate lines so you can compare quotes fairly.

Can we skip maintenance if the software is working fine?

You can for a while, but risk builds quietly. Unpatched libraries become security vulnerabilities, integrations break when partners change their APIs and eventually a large, expensive upgrade becomes unavoidable. Regular small updates are almost always cheaper.

What is the difference between maintenance and new development?

Maintenance keeps existing functionality working, secure and up to date. New development adds capabilities that did not exist before. Many support plans include a small allowance for minor enhancements, with larger features scoped and quoted separately.

Do we need 24/7 support?

Only if downtime outside business hours genuinely costs you money or harms customers, for example an online store, booking platform or logistics system. Many internal business tools are well served by business-hours support with good monitoring.

Can a different company maintain software we had built elsewhere?

Yes, provided you have access to the source code, hosting and documentation. A new provider will usually start with a code review and handover period to understand the system before taking on support.

Plan for the long term from day one

Software maintenance and support costs are not a sign that something went wrong. They are the normal cost of keeping a valuable business asset secure, reliable and useful as your organisation grows. The key is to understand them upfront, choose a support model that matches how critical the system is and keep an eye on quality so costs stay predictable. If you would like help estimating ongoing costs for a new project or reviewing the support arrangements for an existing system, book a free 60-minute consultation with our Auckland team. We will give you straightforward, practical advice tailored to your business.

Share Article:
About Author

Consectetur sollicitudin cubilia facilisis lobortis lacus a ac phasellus. Mus pulvinar enim suspendisse pharetra id commodo platea nunc aliquet.