Custom software costs whatever it takes to understand the job, connect it to the tools you already run, and keep it working after it ships. The code is the smallest part of that, so any price given before someone has looked at how your business runs is a guess.
That is frustrating when you want a number. It is also the straight answer. The drivers below will show you whether your job sits at the simple end or the hard end before anyone quotes.
Why is there no standard price?
Because two jobs with the same name can be very different sizes. Two businesses both ask for a booking system. One needs a form that drops a name into a calendar. The other needs deposits, a waiting list, make-up sessions, reminders by text and a page the bookkeeper can read.
Same words. Different work.
A quote that arrives before anyone has asked how your week runs has priced the words, and the real job turns up later as extras.
What drives the cost up or down?
Seven things, roughly in order of how far they move it.
- How clearly the job can be written down. A job that runs the same way every time is quick to build. Every exception ("unless it is a repeat customer", "except in December") is another rule to design and test, and the exceptions nobody mentions until the build is underway cost the most.
- How many tools it has to work with. Each connection to your accounts, calendar, inbox or job app is its own piece of work. Some tools let other software read and write to them easily. Others make it hard, and that shows up in the price.
- The state of your records. Bringing old customer records across is quick when they live in one place and agree with each other. When the same customer appears three times with three phone numbers, someone has to decide which one is right first.
- Who uses it. A screen only your team sees can be plain. Anything a customer or a parent touches has to work on every phone, make sense to a stranger, and cope with a typo in an email address.
- What it holds. Personal details, children's details, health information or payments raise the bar on security and on who can see what. Pay for that bar.
- What it costs to run. Hosting, text messages and the outside services it calls each carry a monthly bill. Ask whose account they sit on, and who pays when use goes up.
- Looking after it. Prices change, a supplier updates its app, a new starter needs access. Someone keeps the software working through all of it, every year it runs.
How do developers set a price?
Three common ways. By the hour, which leaves you carrying the risk when the job grows. A fixed price for a fixed scope, which turns every change into a variation. Or a price set against what the system is worth to the business, usually a build fee plus a monthly amount for running it and changing it as you change.
All three can be fair. What matters is knowing which one you are being quoted, and what happens when the job changes halfway through. It will.
What does the current way cost you?
This is the number that gets skipped, and it decides whether any price is worth paying. Count the job as it runs today for one normal week: how many times it happens, how long each one takes including the checking and fixing, and who does it.
Then add what you already pay for the tools around it.
A system that gives back an hour a day to each of three people is worth far more than its fee suggests. One that saves twenty minutes a week is worth little, however clever it looks in a demo.
Does tax change the sum?
It can change when you claim it. The ATO treats software subscription fees as an operating expense you generally claim in the year you incur them, while software someone develops for your business is in-house software, usually a capital cost with its own rules, including some for small business. Your accountant can tell you which applies to you.
How do we work out a price?
From the job, never from a rate card. Our first call is about how the work runs today and where the hours go, and the cost of building only comes up after that. The work is then scoped to what we are building for that one business. There are no packages and no hourly billing, and the owner sees what the system is worth before committing to anything.
We work this way for a plain reason. A price set before anyone has seen the job is either padded to cover what nobody asked about, or it grows once the exceptions arrive. Neither is fair to the person paying.
Where does pricing go wrong?
- Two quotes for two different jobs. One includes connecting your accounts and bringing your records across. The other leaves both to you without saying so. Compare them line by line before you compare totals.
- Forgetting the running costs. The build is paid once. Hosting, texts and changes are paid every year.
- The whole wish list at once. Build the job that gives back the most first. Each later piece builds on the records and connections already in place, so it costs less.
- Building what you could buy. If a tool off the shelf does the job the way your team works, buy the tool. Your team didn't reject the tool. It didn't fit covers the signs you have outgrown one.
In short
- The price follows the job, and the code is the smallest part of it.
- Exceptions, connections to your tools and the state of your records move it most.
- Ask how the price is set, and what happens when the job changes.
- Count what the current way costs for one week before you compare quotes.
- Running costs come every year, so ask about them up front.
One step for this week
Pick the one job you would most like off your plate. Write down every step it takes today, every exception you can think of, and every tool it touches. Then count it for five working days.
That one page is worth more than an early quote, because whoever prices the work can now price your job and not a guess at it. When it is written, custom software built around how your business already runs is what we build, and that page is where our first call starts.

