Why custom software used to be out of reach
For most of the last twenty years custom software was priced for companies with IT departments. A small business that wanted a tool built around how it worked got a six-figure quote, a twelve-month timeline and a project team it never met. So it made do with a spreadsheet, an off-the-shelf product that did most of the job, and a few hours a week of somebody's time filling the gap.
Three things have changed, and together they put custom software within reach of a business with ten or twenty staff.
1. The scope has shrunk
The expensive version of custom software is the one that tries to replace everything at once. The version a small business can afford replaces one process: the quoting spreadsheet, the job sheet on paper, the customer emails asking where their order is.
A single-workflow web app is a defined thing. It has one or two types of user, a handful of screens and a clear job. Applicable scopes and prices it as a fixed project, and it sits at the low end of the custom application bracket, in the same NZ$4,000 to NZ$50,000+ range as a website. Larger multi-role systems run up to around NZ$250,000, but you do not have to start there.
2. AI has cut the hours
In 2023 Applicable wrote that AI would make custom software cheaper to build. It has. Senior developers now use AI tools to write routine code, generate tests, review for errors and produce documentation. The parts of a project that used to be days of careful typing are now hours of careful review.
What this does not do is remove the need for experienced people. Someone still has to understand your business, decide what to build, check the output and own the result. What it does is change what a fixed budget buys: the same money now covers more scope, or the same scope costs less. Applicable's quotes reflect that.
3. The building blocks are better
Modern web platforms, hosting and integration interfaces mean a developer no longer builds logins, payments, email or file storage from scratch. Xero, most CRMs and most industry systems now have interfaces to build against. A tool that connects to your accounting package is a scoped integration, not a research project.
What "afford" really means
The question is rarely whether you can find the money. It is whether the software pays it back. Work it out honestly:
- Hours per week your team spends on the manual version, multiplied by what those hours cost.
- Enquiries or orders lost because the current process is slow or error-prone.
- Subscription fees for tools that do part of the job.
- The cost of the mistakes: double bookings, missed compliance renewals, invoices that go out wrong.
Set that against a fixed build price and a monthly support retainer. For most single-workflow tools the payback is measured in months, not years. If it is not, Applicable will say so on the scoping call and suggest something smaller or an off-the-shelf option.
How to keep it within budget
Scope first, then price, then build. Applicable does not start building until the scope is written down and priced. Changes are quoted before they are built, so the number you signed is the number you pay. Logan Wedgwood, CEO of Advisory.Works, described the team as "ahead of timeline, under budget and transparent for the duration of our projects."
Prototype before you build. A clickable prototype in front of your own staff costs little and catches the expensive misunderstandings early.
Launch the smallest useful version. The first release should do one job well. Everything else goes on a roadmap and gets built when the first version has proved itself.
Own what you pay for. You own the code, the data and the hosting accounts. No platform fee that rises with users, and no lock-in if you ever want to change vendors.
When it is bigger than that
Some projects are genuinely large: many roles, deep integrations, complex compliance, a platform the whole company runs on. Applicable will tell you if your project is one of them rather than pretend it is a small one.
Key takeaways
- A small NZ business can afford custom software by scoping one workflow at a time instead of a whole system.
- A single-workflow web app sits in the same NZ$4,000 to NZ$50,000+ bracket as a website; larger applications run up to around NZ$250,000.
- AI-assisted development has cut the hours a senior developer needs, so a fixed budget now buys more scope.
- Applicable scopes first, prices the scope and quotes any change in writing before building it.