The cost of custom software: what really drives the price

“How much does custom software cost?” It is often the first question on a discovery call, and a fair one. The honest answer comes in two parts. Yes, the cost of custom software depends on your project. But it is not random: it follows from a few specific factors, which can be identified and managed.

So you won’t find a price list here: without knowing your project, any figure would be guesswork. Instead, we explain what drives the price, how a project is billed, and how to keep the budget for your business application under control.

Why there is no list price

Custom software isn’t bought off the shelf: you pay for the work needed to design, develop, test and launch it. And two projects with the same name, “a CRM” for example, can require vastly different amounts of effort.

It isn’t the number of screens that makes the difference, but what lies behind them: the rules to follow, the tools to connect, the data to migrate, the level of security required. The price of software development therefore reflects the real complexity of your business. That doesn’t leave you powerless: once you understand these factors, you can act on each of them.

The six factors behind the cost of custom software

1. Scope and business rules

The scope is what the software has to do. But a feature that looks simple can hide a lot of rules: “calculate an amount” can involve discounts by type of customer, exceptions or special rounding. Every rule has to be understood, developed and tested: the more rules there are, the more work there is.

2. Integrations with your tools

Software rarely works on its own: it exchanges data with your accounting software, your email, your CRM or a payment service. Every connection takes work: understanding the other tool, moving the data, planning for what happens when the other system doesn’t respond. A recent tool with a documented interface (an API) is generally easier to connect than old software that has none.

3. The target platforms

Web browser, desktop, iOS, Android: each platform adds design, testing and sometimes publication on the app stores. For example, the CRM/ERP built for a Sydney law firm, a project led by our founder, had to work both at the office and on the move: on desktop, iOS and Android.

If the way you work allows it, a web app that adapts to phone screens already covers many needs.

4. Security and confidentiality

Managing client files or financial information doesn’t take the same work as publishing a catalogue. Role-based access rights, a history of actions, encryption: these protections become essential as soon as the data is confidential. If the software processes personal data, it must also comply with the data protection rules that apply to your company, such as the GDPR in the European Union. It is better to plan for all this from the design stage: adding it afterwards generally costs more.

5. Data migration

Your data may be scattered across spreadsheets, old software and paper files. Migrating it means cleaning it, removing duplicates, adapting it to the new structure and checking the result. This cost item is often underestimated, yet a failed migration can delay the whole launch.

6. Maintenance and improvements

The cost doesn’t stop at launch. Software has to be hosted, monitored, updated to stay secure, fixed when a problem appears, and extended as your business changes. So when you compare two options, think in terms of total cost over several years: the first version is only part of it.

Fixed price, day rate or subscription: three ways to bill

The billing model doesn’t change the work to be done, but it does change how the project is managed. We offer three:

• Fixed price: a price set in advance for a defined scope. You know your budget from the start; in return, the scope has to be precise.
• Day rate: you pay for the time actually spent. This is the right model for consulting, for reinforcing an existing team or for projects whose needs are still evolving. It requires regular monitoring of progress.
• Monthly subscription: maintenance, hosting and improvements are covered every month. The budget is spread evenly, and the software keeps improving.

These models combine well: for example, a fixed price to build the first version, then a subscription to keep it running and evolving.

Why an audit comes before the quote

A reliable quote requires knowing what you already have. Without that, a provider has only two options: inflate the price to cover the unknowns, or underestimate it and announce extra costs along the way. Neither does you any favours.

That is why our custom software projects start like this:

1. A free 30-minute discovery call, to understand your needs and tell you frankly whether we are the right people for the job.
2. An audit, if needed, proposed at the end of the call and carried out on the basis of a quote. We analyse your processes, tools, data and constraints, then give you a detailed, costed proposal.

The audit has another advantage: it sometimes concludes that off-the-shelf software is enough. When that happens, we tell you.

How to reduce the budget for a business application

Reducing the cost doesn’t mean cutting corners on quality. The most effective levers concern what is built, and in what order:

1. Start with a smaller but useful version: the essential features first, in the hands of real users. For the Sydney law firm’s CRM/ERP, the first version went live in under six months.
2. Split the project into stages: each stage has its own scope and budget, and you decide on the next one once you have seen the results of the previous one.
3. Prioritise ruthlessly: classify each feature as “essential”, “useful” or “later”. In practice, some “later” features turn out to be unnecessary.
4. Don’t reinvent the standard: accounting or payroll rarely need to be custom-built. Your software is connected to existing tools, and only what is specific to you gets developed.
5. Validate with mock-ups: clickable mock-ups let you test the screens before a single line of code is written. Correcting a mock-up costs far less than correcting software.

Your checklist before asking for a quote

Gather these elements before your first conversation with a provider: the discussion will be more concrete, and the estimate more accurate.

• the main processes the software must cover, described simply;
• the users involved, their roles and their approximate number;
• the current tools to keep or connect;
• the data to migrate: where it is, in what form, in what quantity;
• the platforms needed: browser, desktop, mobile;
• your security requirements and confidentiality needs;
• the date by which you need a first version;
• a budget, even a rough one, to point towards the right solution;
• the person who will decide on your side.

No need for a perfect document: a page of notes is enough to get started. To go further, follow our method for writing a software requirements specification.

Frequently asked questions

Why don’t you publish your prices?

Because every project is different. A single rate would be too high for a simple tool and too low for a complex project. We prefer to understand your needs, then give you a detailed, costed proposal: at a fixed price, on a day rate or as a monthly subscription.

Does custom software cost more than off-the-shelf software?

At the outset, often yes. Over several years, the comparison can be reversed: a subscription billed per user grows with the size of the team, and the time lost on workarounds (spreadsheets, re-keying) eventually takes its toll. In our custom projects, the code and the data belong to you, and the tool contains only what you need.

What happens if our needs change during the project?

That is normal, and planned for. On a fixed price, a new request is priced separately or moved to the next stage. On a day rate, you adjust the priorities freely. Either way, delivering in short iterations, with regular demos, makes it possible to correct course early, while it is still easy.

In short

There is nothing mysterious about the cost of custom software. It depends on six factors: scope, integrations, platforms, security, data migration and maintenance. Once you know them, you can choose the right billing model, start with the essentials and invest as the results come in.

Thinking about custom software and want to know what will weigh on its budget? Book a free 30-minute discovery call: together, we identify the cost factors specific to your project, and how to keep them under control.