Custom software vs SaaS: the ownership economics every NZ business should understand

The question NZ mid-market businesses rarely ask early enough is: what does this software actually cost over five years? Most SaaS pricing conversations focus on the monthly fee per user at the moment of signing. Few model what happens to that number as headcount grows, as modules get added, and as the gap between what the platform does and what the business actually needs keeps widening.

This is not an argument against SaaS. It is an argument for making the build-vs-buy decision deliberately — with a clear view of the costs on both sides — rather than defaulting to subscription software because it appears cheaper at sign-up.

How per-user pricing scales

SaaS pricing is designed to be easy to start. A platform at $60–$120 per user per month feels manageable at ten users: $7,200 to $14,400 a year. At 30 users, you're paying $21,600 to $43,200. At 60 users — a realistic size for a NZ mid-market distribution business including office staff, sales reps, and warehouse team — you're between $43,000 and $86,000 per year for a single platform.

Add the other SaaS tools a typical complex NZ business runs — a separate inventory or warehouse management system, a CRM, an accounting platform, a B2B ordering portal — and total annual software subscription spend frequently reaches $150,000 to $300,000 for a business of this size. None of it builds equity. At the end of year five, you own nothing, the vendor has revised its pricing at least once, and you are paying more than you planned when you signed.

This is not unusual. It is how SaaS pricing is structured. The question is whether, at the point your subscription spend reaches this level, the software still fits your business well enough to justify it — or whether you are paying heavily for a platform you have outgrown.

What subscription software can't give you

Per-user fees are only part of the story. The deeper problem for complex NZ businesses is fit.

SaaS platforms are built for the widest possible market. They model the processes that most businesses follow, and they invest in features that benefit the most customers. When your operations diverge from the norm — and in distribution, wholesale, manufacturing and logistics, they will — your options narrow quickly.

For NZ distributors and B2B businesses specifically, the divergence tends to appear in the same places: customer-specific pricing (negotiated rates per account, not just discount tiers), catch weight and variable-unit invoicing, ERP integration at the depth the business actually needs (customer pricing, AR status, lot tracking, order write-back — not just a basic invoice sync), and NZ-specific compliance requirements (GST handling for multi-entity structures, zero-rated exports, IRD seven-year record-keeping requirements that interact poorly with SaaS data-retention policies).

When your operations land outside what the platform supports natively, you face a fixed set of options: build workarounds inside the platform (which compound over time into technical debt), buy additional third-party integrations (adding cost and another vendor relationship), wait for the vendor to build what you need (if they ever do), or switch to something else. None of these options is free, and all of them extract a cost that does not show up in the per-user fee.

The vendor relationship problem

SaaS platforms operate on the vendor's roadmap, not yours. A feature your business needs may be requested, acknowledged, and deprioritised for years because it does not move the needle for enough of the vendor's global customer base. From the vendor's perspective, that is a rational decision. From yours, it means the software is not going to get better at your specific problem.

There is also the acquisition and consolidation risk that is particularly relevant in the NZ and ANZ market, where many business software tools are regional subsidiaries or resellers of US and UK platforms. When a vendor is acquired — and in enterprise software, consolidation is constant — pricing changes, integration APIs are deprecated, and product strategies shift. Businesses that own their core software are not immune to this, but they are not dependent on it. The code does not disappear when a vendor changes hands.

When SaaS is the right call

For standard processes, SaaS is often the correct choice. Email and calendar, HR and payroll, document management, standard CRM, basic accounting for simple structures — these are processes where SaaS platforms are mature, widely adopted, and where the vendor's investment keeps pace with regulatory and compliance changes. If your business process matches what the platform does, you get a well-maintained, continuously improved tool without carrying development cost.

The question is whether your core operational software — the system your business runs on — falls into this category. For commodity processes: yes. For the logic that makes your business specifically work — your pricing model, your customer relationships, your warehouse operations, your ERP integration layer — the answer is usually more complicated.

The signals that ownership starts to make sense

There are consistent patterns that appear when NZ businesses are ready for this conversation:

• Workaround accumulation. Your team has developed documented (or undocumented) workarounds for things the platform does not do. These workarounds consume staff time, create error risk, and have been in place long enough that no one remembers what life looked like before them.
• Integration complexity. You are running multiple systems with point-to-point integrations between them. Data entry is duplicated across platforms, and reconciling discrepancies takes regular effort. The integrations are fragile and require attention when any connected system updates.
• Per-user cost at scale. Your annual subscription spend across the systems supporting your operations has reached a level where the five-year total would fund a significant custom build — and the custom build would fit your operations rather than constraining them.
• Competitive constraint. You have identified operational capabilities you cannot build on your current platform — things that would reduce costs, improve customer experience, or open new revenue — but the platform will not support them.
• Data ownership concern. Your business data — customer pricing, order history, AR records — lives entirely in a system you do not control, hosted in a jurisdiction your contracts may not pin down clearly, by a vendor whose ownership or pricing structure may change.

What owning your software actually means

"Owning your software" is sometimes misunderstood as running your own servers or employing internal developers. In practice, it means something more specific: the code is yours, the data is yours, and the system is built to your specification — not a vendor's idea of what your business should look like.

Most NZ businesses that own their core operational software work with a development partner who handles hosting, infrastructure, monitoring, and ongoing changes. The business does not need an internal engineering team. What it has is a relationship with a partner who understands its specific system — rather than a support ticket queue to a vendor who knows nothing about its particular operations.

NZ food distributors and wholesalers — including businesses like Starfoods, Hamilton Foods, FoodFirst and Firstlight Frozen — run their entire operations on software built and operated this way. Ordering, pricing, inventory, ERP integration, invoicing, customer account management: all of it on a platform built for their specific requirements, without per-user licence fees compounding year on year.

This model is not the right fit for every business, and it is not the right starting point for a business that has not yet identified where its operations diverge from what standard platforms offer. But for established NZ businesses that have outgrown the tools they started on, it is worth running the numbers honestly — not just the monthly fee, but the five-year total including workaround cost, integration overhead, and what the platform will not let you build.

If you are at the point where that comparison is worth making, the custom ERP vs off-the-shelf guide covers the decision framework in more depth — including the pragmatic middle path that most growing businesses actually take. For the NZ-specific accounting angle, the custom accounting software guide covers what owning your back-office looks like in practice. And if you want to talk through what your specific operation would involve, reach out to the Zeabyte team — we build and operate custom ERP and operational software for established NZ businesses, and run the Provender B2B ordering platform that connects to 25+ accounting and ERP systems without displacing them.