HomeServicesCustom Business Software
Custom Business Software in New Zealand
Software shaped around how your business actually works, instead of a product that makes you work its way. Worth it when your process is the advantage — and a waste when it is not.
$60k+
Typical project value
2 min
To post a project
What do you need built?
Start here and add detail as you go.
Free - No obligation - Your details stay private
What people usually mean by custom business software
The useful question is never whether software could do this — it almost always could. It is whether the way you do it is unusual enough to justify building rather than buying, and honest developers will help you answer that even when the answer costs them the job.
Replacing the spreadsheet everything runs on
The workbook one person maintains, that the business depends on, that nobody else fully understands. Common, valuable and usually urgent once you notice.
Joining up systems that do not talk
Data re-keyed between products because none of them covers the whole process.
Software around the thing you do differently
Your scheduling, pricing or workflow is why customers choose you. A product would flatten it.
What it costs
Indicative ranges from projects posted here. Use them to sense-check a quote, not to budget precisely.
One process
A single workflow done properly, with the reports around it.
$40k – $90k
Departmental system
Several connected processes, roles and permissions, integrations with what you run.
$90k – $250k
Core business system
The thing the company runs on, replacing several products at once.
$250k+
Questions worth asking a provider
·Which off-the-shelf products did you consider, and why is building better here?
·What would you build first, and what would that cost on its own?
·Who owns the code, and what happens if we stop working together?
·What does it cost to run and maintain each year after launch?
·How will we change it ourselves later — and what will always need you?
Common questions
How much does custom business software cost?
One well-defined process is $40,000 to $90,000. A departmental system with several connected processes, roles and integrations is $90,000 to $250,000. Replacing the system a company runs on starts around $250,000. Budget 15 to 20 percent of the build annually for maintenance and change.
Should we build or buy?
Buy if your process is genuinely standard — a product will be cheaper, better supported and available on Monday. Build when the way you work is the advantage: the scheduling nobody else has, the pricing that wins contracts. A consultant who tells you to buy, when buying is right, is worth listening to on everything else.
How do we avoid a runaway project?
Insist on a first release that is useful on its own, three to four months out, and refuse to approve anything longer before seeing it. Projects fail by growing quietly for a year, not by being technically hard.
What happens to the spreadsheet it replaces?
Keep it running in parallel for a month, then archive it read-only. Do not delete it — the spreadsheet usually contains rules nobody wrote down, and you will want to check against it more than once.
Who owns the code?
You should, and it should be in the contract along with the repository, the cloud accounts and the domains. Ask before you sign, not when the relationship ends.
Related: Internal Business Systems · Customer Portals · Supplier Portals · Workflow Systems · Booking Systems · CRM Development · ERP Extensions · Inventory Systems
Custom Business Software projects open right now
Titles and categories are public. Full briefs, budgets, regions and buyer detail are visible to approved providers only.
Updated daily
No open projects in this category right now. New briefs are posted every week.
Ask whether you should build at all
The strongest signal that custom is right is that you have already tried a product and worked around it. Not that you looked at one and preferred the idea of your own.
Buying is cheaper, faster, and someone else maintains it. Building is right when your process is genuinely a competitive advantage — and a good developer will tell you which situation you are in even though one answer is worth far more to them than the other. That willingness is worth testing for directly.
The spreadsheet is telling you something
Most custom software briefs start with a workbook. It has grown for years, one person maintains it, it has formulas nobody understands, and the business genuinely depends on it.
That spreadsheet is a specification. It shows exactly what the process is, which parts are fiddly, and where the real rules live. Bring it to every conversation — a developer who reads it will quote far more accurately than one working from a description.
It is also a warning. Everything in it is a single point of failure sitting on one laptop.
Build the first slice small
The projects that fail do not fail technically. They fail by growing: another report, another exception, another department, until a year has passed and nothing is in use.
Insist on a first release that is useful on its own within three to four months, even if it covers only part of the process. Real use produces better requirements than any workshop, and it means the money already spent bought something.
Budget for after launch
Custom software is not a purchase, it is an asset with running costs. Set aside 15 to 20 percent of the build cost annually for changes, fixes and keeping up with the systems it connects to.
Businesses that skip this end up back where they started in five years, with software nobody has touched and a spreadsheet growing beside it again.
Comparing quotes
- Did they push back? Anyone who suggests a product, or a smaller first version, is showing judgement.
- What is release one? Specific, and useful by itself.
- Ownership. Code, repository, cloud accounts — in writing.
- Running cost. Annual, not just the build.
- Who writes it. Ask to meet the developer, not only the salesperson.
Describe the process, what it costs you today, and where it breaks. Five developers will tell you what building it takes — and the honest ones will tell you if you should not.
Get up to 5 quotes for your custom business software project
You choose who may contact you. Free to use, no obligation.