It is the first question almost every business asks, and the honest answer is: it depends on what the software has to do. A simple internal tool and a multi-company operational platform are both "custom software", but they sit at very different points on the cost curve. What you can control is how clearly you define the problem, and that has more influence on the final bill than any hourly rate.

What actually drives the cost

  • Scope of workflows. Every role, approval step and exception adds screens, rules and testing.
  • Integrations. Connecting to accounting, ERP, telematics or customer systems is often the largest single item.
  • Data migration. Moving years of spreadsheets or legacy records needs mapping, cleaning and validation.
  • Platforms. Web only, or web plus iOS and Android apps.
  • Security and compliance. Audit trails, permissions and data protection requirements.
  • Ongoing support. Hosting, monitoring and improvements after launch.

Budget in phases, not in one big number

The most reliable way to control cost is to split delivery into phases. A short discovery phase maps the workflow and produces a prioritised scope. A first release then solves the most expensive problem, usually the manual handover or the spreadsheet that everyone depends on. Later phases add the next most valuable improvements, informed by real usage rather than assumptions.

The cheapest feature is the one you never build because discovery proved nobody needed it.

Hidden costs to plan for

Licences for third-party services, cloud hosting, app store accounts and time from your own team for testing and feedback are easy to forget. So is training: software that people do not understand rarely delivers its return. Ask any partner to show these items separately so you can compare proposals fairly.

How to get an accurate estimate

Bring real examples: the forms, spreadsheets, emails and reports your team uses today. Describe who does what and where things go wrong. A good partner will turn that into a scoped proposal with clear assumptions, rather than a single figure that changes once work begins.

The bottom line

Custom software is an investment in how your business operates. Judge it against the cost of the problem it removes: hours lost to re-keying, errors, delays and missed visibility. When the scope is tied to those costs, the budget conversation becomes much easier.