It is the first question every business owner asks, and the honest answer is that nobody can quote custom software accurately without knowing what it has to do. That is unsatisfying, so this article explains what actually moves the number — which is more useful than a price list you cannot rely on.
Why there is no fixed price
Custom software is priced the way construction is priced. Nobody quotes "a building". They quote a specific building, on a specific site, to a specific spec. Two businesses that both say they need "a billing system" can be six weeks apart in effort, because one needs a single counter and the other needs three branches, GST filing, and stock that reconciles across them.
The five things that actually drive cost
1. Number of distinct screens and workflows
Cost tracks the number of things a user can do, not the number of features on a brochure. A system where staff can create, edit, approve and report on an order has four workflows, not one. When you are estimating, count the actions, not the nouns.
2. How many types of user there are
One user type is straightforward. Three — say, owner, manager and field staff — means permissions, separate views, and testing each path. Every additional role adds work everywhere, not just in one place.
3. Integrations
Connecting to a payment gateway, WhatsApp, an accounting package or a government portal each adds real effort, and the ones with poor documentation add more. Integration work is also where timelines slip, because you are dependent on someone else’s system behaving.
4. Data migration
Moving years of existing records out of spreadsheets or an old system is a project in itself. Messy data costs more than clean data, and everybody’s data is messier than they think.
5. Whether you need it on mobile
A responsive web application works on a phone browser and costs nothing extra. A native app you install from the Play Store is a separate build with its own release process. Be clear which one you actually need — many businesses ask for an app when a responsive web app would do the job.
How to keep the cost down without cutting corners
- 1Start with the one process that hurts most. Not the whole business — the one thing costing you time or money every week.
- 2Ship that, use it for a month, then decide what is next based on what you learned rather than what you assumed.
- 3Resist features that only get used once a year. They can be handled manually far more cheaply than they can be built.
- 4Keep your existing tools where they already work. Replacing software that is fine is spending for no gain.
- 5Ask for the project in phases with a working system at the end of each one, so you are never far from something usable.
Questions to ask before accepting any quote
- What exactly is included, screen by screen — and what is explicitly not?
- Who owns the code and the data when the project ends?
- What happens if we need a change midway? How is that priced?
- What is covered after go-live, and for how long?
- What will it cost to run each month — hosting, third-party services, support?
- Can we see something working before the final payment?
The cost of not building it
Weigh the quote against what the current process already costs you. Staff hours spent re-typing data, stock written off because nobody saw it running out, enquiries that went cold because no one followed up — those are real numbers, and most owners have never added them up. Do that first. Sometimes it justifies the project immediately, and sometimes it shows the problem is not worth software yet. Both are useful answers.
Want to talk through your own situation?
Book a free consultation. We will tell you what we would build, what it would take, and whether it is worth doing at all.