$25k – $60k
A focused tool
A single workflow done properly — a custom internal tool, a dashboard, an integration between two systems, or automating one repetitive process. Narrow scope, one or two user types.
Pricing
What does custom software cost in Australia?
Here are honest, indicative ranges — and then the more useful part: what actually moves the number, and why we won't quote a build blind. The range is the least useful thing on this page.
Indicative price ranges
$60k – $180k
A mid-sized system
A system several people rely on daily — multiple workflows, real data modelling, a few integrations, more than one kind of user. The operational backend behind a growing operation.
$180k+
A platform
Infrastructure-level work — connected field systems, monitoring platforms, LIMS-style data systems, or a platform built for the next few years of growth. Multiple subsystems, hardware, and integrations.
These are indicative ranges for planning, not quotes. Ongoing operations support is usually a separate, optional retainer. Every number buys a system you own — source, documentation, and runbooks included.
What moves the number
Six things that decide where you land.
How clear the scope is
A well-understood problem costs less than a vague one. Uncertainty is the most expensive line item — which is why we resolve it before quoting a build.
How many kinds of user
One user type is straightforward. An admin, an operator, a field tech, and a manager — each with different needs and permissions — is four problems, not one.
How much it integrates
A system that stands alone is cheaper than one that has to talk to hardware, legacy databases, or third-party tools that don't share an API.
The state of your data
Clean, structured data is a head start. Data trapped in spreadsheets, inconsistent formats, or one person's head has to be understood and reshaped first.
Compliance & reliability needs
Audit trails, traceability, security, and systems that can't afford downtime all raise the bar — appropriately. Consequential systems cost more because they have to be right.
Depth of understanding required
Some problems can be specified in a conversation. Others need us in the field, watching how the work actually happens, before anyone can say what should be built.
Why we won't quote your build blind
A price that arrives before anyone understands your operation isn't a price — it's a guess dressed up as a plan. We start with a fixed-fee Discovery Sprint that maps the work and gives you a real number to plan from — and an honest verdict on whether to build at all. A Sprint that concludes you shouldn't build is still a successful Sprint.