Guide · price
How much does custom software cost?
Custom software has no reference price, because it has no reference content. Here is what makes a quote vary, and what people often forget to include.
Custom software has no standard price, because its content varies from one company to another. The quote mainly depends on the number of business rules and exceptions, the roles involved, data migration, integrations and any offline requirement. Be wary of a figure given before any scoping: too low, and it hides costs that will come back; too high, and it may include things you do not need.
Why there is no standard price
Off-the-shelf software has a listed price because its content is fixed: everyone buys the same thing. Custom software has no such point of comparison, since its content is precisely what varies from one company to another. Two companies in the same sector, with the same headcount, can get very different quotes if one handles five business exceptions and the other fifty. Be wary of a figure given before any scoping, in either direction: too low, and it hides costs that will come back as an extra invoice; too high, and it may include features you do not need.
What makes the price vary
The quote depends on a small number of factors, but each one carries real weight. The number of screens and business rules to code matters more than the size of the company: an SME with simple rules costs less than a small outfit with many exceptions. The number of roles to manage also plays a part, because each role multiplies the screens to adapt and the permissions to check. Integrations with existing tools, accounting, ERP, a customer's or supplier's platform, add specific work for each connection. Migrating existing data, whether from a spreadsheet or an old piece of software, is costed separately and often represents a significant share of the budget. The need for mobile and offline operation changes how the application is built, not just how it looks. Finally, hosting and maintenance are costs that continue after delivery, to be budgeted from the start rather than discovered later.
- Number of screens and business rules to code
- Number of roles and permission levels
- Integrations with tools already in place
- Volume and quality of the data to migrate
- Need for mobile and offline operation
- Hosting and maintenance after going live
The items people forget to price in
Some items do not appear in the first figure you are given, and come back later as a surprise. Data migration is the most common one: it is almost always longer than expected, because existing files contain duplicates, inconsistencies and edge cases that only surface once you actually analyse them. Training your teams is another item often left out, even though software no one has learned to use stays unused, whatever its technical quality. Hosting, finally, is a recurring cost that a one-off quote can leave unmentioned, as can the maintenance that follows going live: dependencies to update, security fixes, small regulatory changes. A complete quote names these items, even if it cannot yet price them precisely. If the software already exists and was written by another vendor, auditing the existing system is costed separately, before any quote for further work: see our software takeover page.
How to reduce the cost without reducing quality
The most reliable way to keep a budget under control is to start small. Rather than trying to cover every role and every exception in the first version, we identify the first useful batch, the one that already replaces the current tool for the most frequent use, and we deliver it. Teams use it, which reveals what genuinely matters for what comes next, and the rest of the scope is ordered around this real usage rather than a list drawn up cold. This approach does not reduce the final price if the full scope stays the same, but it reduces the risk of paying for features that, in practice, turn out to be secondary or poorly thought through.
How to compare two quotes
Comparing two custom software quotes purely on their final amount does not make much sense, because the scope behind that amount can be very different. First check that data migration is explicitly listed in both quotes, along with what it covers. Also check whether training and operational documentation are included or billed separately. The engagement model matters too: on a fixed-price basis, the scope is set in advance and changes are costed as extras; on a time-and-materials basis, you pay for time spent and keep control over priorities, but the final budget depends on the actual duration. Neither model is inherently better, but an honest quote states which one applies, and what happens if your needs change along the way.
- Is data migration costed, and over what scope?
- Are training and documentation included?
- Is the quote fixed-price or time-and-materials, and what happens if the need changes?
- Are hosting and maintenance budgeted separately?
Frequently asked questions
How much does custom software cost?
There is no reliable range to give without scoping: the price depends on the number of screens and rules to code, the number of roles, the integrations, and above all the volume of data to migrate. We quote after seeing your real data and rules, not before.
Why does data migration cost so much?
Because an existing file rarely contains what you think it does: duplicates, missing values, inconsistencies built up over the years. This clean-up takes time even when the number of rows looks modest, and it is almost always the longest item in the project.
Fixed-price or time-and-materials: which should you choose?
Fixed-price sets the price for a scope defined in advance, which is reassuring on budget but costs any change as an extra. Time-and-materials bills the time spent, which leaves you in control of priorities but requires tracking progress. The right choice depends on how clear your need is at the outset.
How can you reduce a project's budget?
By starting with a narrow but genuinely useful scope rather than a complete feature list. The first batch delivered reveals what really matters, and the rest of the project is then organised around that real usage, which avoids paying for poorly calibrated features.
Isn't off-the-shelf software cheaper?
Often yes, as long as your rules resemble most other companies'. Custom software is justified when working around a standard tool costs more, in data entry time or errors, than having a tool built that fits how you actually work. If off-the-shelf software is enough, we tell you so rather than sell you an unnecessary project.
A project, a question?
Describe what you need in a few lines: you deal directly with the team, in Lille.