What Does Custom Software Actually Cost in Australia?

Almost every Australian development agency answers this question with "it depends" and a contact form. That's not useless — it genuinely does depend — but it's not what you need when you're trying to work out whether to even start the conversation.

So here are real numbers, the ranges we actually quote, and an honest account of what moves a project from one end of the range to the other.

The three tiers, with real numbers

$8,000 – $15,000 · One process, done properly

A single-purpose tool that replaces one painful spreadsheet or manual process. A quoting calculator with your pricing rules. A booking system. An inspection app that captures photos and produces a PDF. One or two user types, one core workflow, no complex integrations.

This is the tier most businesses should start in, and the one most often skipped in favour of something grander that then stalls.

$15,000 – $30,000 · A system the business runs on

Multiple connected workflows and several user roles. Typically: customers and jobs, scheduling, quoting, invoicing, a reporting dashboard, and one or two integrations — usually Xero and something operational. Mobile-friendly for field staff.

This is where most successful projects for 5–30 person businesses land.

$30,000 – $45,000+ · Complex logic or heavy integration

Systems where the hard part isn't the screens, it's the rules. Multi-site costing. Pricing engines that have to be defensible when a customer challenges them. Approval chains and audit trails. Several integrations, permissions that genuinely matter, real reporting.

Above about $60,000 you're generally into product territory rather than internal tooling, and the question changes from "what does it cost" to "what's the return".

What actually drives the number up

People assume cost scales with the number of screens. It doesn't. Screens are the cheap part. Here's what actually moves the price:

• Integrations. Every system you connect to adds cost, and the cost is in the failure handling, not the connection. Roughly $2,500–$8,000 per integration depending on whether it's one-way or two-way.
• Business rules and edge cases. "We charge standard rates, except for these four customers, and except after 3pm on Fridays, and except when it's a warranty job." Each exception is real work. This is the single most underestimated cost in every project.
• Roles and permissions. One user type is simple. Five user types who each see different data and can take different actions is a different system.
• Data migration. Getting fifteen years of history out of a spreadsheet where the date format changed three times is genuinely expensive. Budget for it honestly, or decide to start clean.
• Offline and field use. An app that must work in a basement or a paddock with no signal costs considerably more than one that assumes a connection.
• Compliance. Health, legal, financial and government work carries requirements that are non-negotiable and take real time.

Custom vs SaaS: when the lines actually cross

The honest comparison isn't build cost versus monthly fee. It's total cost over the period you'll actually use the thing.

Take a business with 12 staff on a job management platform at $60 per user per month. That's $8,640 a year, and it rises when you hire, when the vendor raises prices, and when you need the tier with the feature you actually wanted.

• Year 1: SaaS $8,640 · Custom ~$25,000 build + $1,800 hosting = $26,800. SaaS wins clearly.
• Year 3: SaaS ~$27,000 (with modest price rises) · Custom ~$30,400. Roughly level.
• Year 5: SaaS ~$48,000 · Custom ~$34,000. Custom is now well ahead, and you own the asset.

Those are illustrative figures, not a promise — your seat count and vendor pricing decide the real shape. But the pattern holds: SaaS almost always wins year one; custom usually wins somewhere between year two and year four, and the crossover comes sooner the more people you employ.

Below about five users, off-the-shelf is usually the better economic answer and we'll tell you so. The argument for custom below that headcount is a process nothing off-the-shelf can do, not the money.

The costs people forget

• Hosting: $50–$300 a month for most business systems.
• Maintenance: budget 10–20% of build cost per year if you want it actively looked after — dependency updates, security patches, small changes. Skipping this is viable for a year or two, then it isn't.
• Your own time. The biggest hidden cost. Expect to spend real hours on decisions, testing and edge cases. Projects where the owner disengages after the kickoff are the ones that go wrong.
• Training and transition. Running the old and new systems in parallel for a few weeks is normal and sensible.

How to keep the number down

1. Start with the one process that hurts most Not the whole business. The single workflow costing you the most hours. It'll be cheaper, land sooner, and teach you what you actually need next.
2. Get a fixed price, not an hourly rate An hourly arrangement transfers all the estimation risk to you. A fixed price transfers it to the developer, which is where it belongs — they're the one who can estimate.
3. Write down your exceptions first As above. This is free and saves thousands.
4. Insist on working software every two weeks Not status reports. If you can't use part of it by week four, you have no evidence anything is going right.
5. Own the code Make sure the contract says the source code and data are yours. This costs nothing to agree at the start and is very expensive to fix later.

Common questions