How much does custom software development cost?

It is the first question almost every enquiry contains, and the honest answer is that nobody can price custom software from a one-line description. What we can do is explain what moves the number, so you can tell early whether a project is a few weeks of work or several months.

Cost is driven by scope, not by screens

People often estimate software by counting pages. That is a poor proxy. A ten-screen application with one user role and no integrations is far cheaper than a four-screen application that syncs with an ERP, enforces an approval hierarchy and has to reconcile conflicting data. The work lives in the rules, not the layouts.

The five things that actually move the number

1. 01Number of distinct user roles. Each role adds permissions, screens and edge cases. Going from one role to three is rarely three times the work, but it is never free.
2. 02Integrations. Every external system — payment gateway, CRM, accounting package, government portal — adds authentication, error handling, retries and a category of bug you cannot reproduce locally.
3. 03Data complexity. A flat list of records is cheap. Hierarchies, versioning, audit trails and historical corrections are not.
4. 04Non-functional requirements. Offline support, real-time updates, regulatory compliance and high availability can each cost more than a whole feature.
5. 05How clear the requirement is. Ambiguity is expensive. Discovery is where you buy that clarity, and it is much cheaper than buying it during development.

Fixed price or time and materials?

Fixed price works when the scope is genuinely settled — a defined integration, a known set of screens, an agreed data model. It protects you from overruns, and in exchange the estimate carries a risk margin and changes cost extra.

Time and materials works when you expect to learn during the build, which is most new products. It is cheaper when scope is stable, and it demands more involvement from you. A common middle path is a fixed-price discovery phase that produces a scoped, fixed-price build.

How to get a useful estimate quickly

• Describe the problem, not the solution. 'Our dispatch team re-enters every order into two systems' tells us more than 'we need a dashboard'.
• Name the systems it must talk to, and whether they have an API.
• Say how many people will use it and in how many different roles.
• Say what has to be true on day one, and what can wait for version two.
• Share your budget range. It is not a negotiating position — it decides which of several valid approaches we propose.

What to budget beyond the build

Custom software has a running cost: hosting, domains, third-party services, security updates and the small changes every live system needs. Plan for ongoing maintenance from the start rather than treating the launch as the end of spending.