The cost of custom software is set by its scope: how many users and roles, how many workflows, which systems it connects to, and how much of it must work offline, on mobile or at scale. The same one-line idea can be a two-week tool or a six-month platform, which is why an honest price comes after a short discovery, not before it.
What drives the price?
| Factor | Why it matters |
|---|---|
| Number of workflows | Each process (quote, order, dispatch, invoice) is screens, rules and tests |
| Users and roles | Permissions and approval chains add logic to every screen |
| Integrations | Connecting accounting, payment, SMS or existing systems is often the hardest part. See system integration |
| Data migration | Cleaning and importing years of spreadsheets takes real time |
| Platforms | Web only, or also mobile apps, or offline use on site |
| Reporting | Dashboards and exports people actually need |
| Design quality | Simple, clear screens take design work, and pay back in training time |
| Scale and security | More users, sensitive data or compliance needs raise the bar |
Why do fixed quotes on vague briefs go wrong?
When the brief is "a system to manage our orders", the vendor must guess. If they guess low, the project runs out of money halfway, or they cut corners. If they guess high, you overpay for risk. Either way, the argument comes later. A discovery phase removes the guessing.
How does a phased build keep the budget safe?
- Discovery: map how the work happens today, find where time and money leak, and agree the scope of the first phase in writing.
- First phase: build the smallest version that solves the most expensive problem, and put it in people's hands.
- Measure: see what is used and what is missing.
- Next phase: decide with real usage, not assumptions.
Each phase has its own fixed scope and estimate, so you can stop after any phase with working software.
What costs come after launch?
Hosting, monitoring, backups, security updates and small improvements. Budget for them from the start, so the system doesn't decay after the launch party.
How do you compare quotes?
Ask each vendor what exactly is in scope, how changes are priced, who owns the code and data (it should be you), what testing is included, and what support costs after launch. A detailed scope is worth more than a low number.
Is custom software worth it for you?
Compare the cost with what the problem costs today: staff hours spent copying data, errors, lost orders, licences for tools that don't fit. See custom vs off-the-shelf for the decision itself.
Get a written estimate after a short discovery call.