Custom Software Development: Cost, Steps, and a 2026 Guide
What custom software actually costs, how a project runs week by week, and the signs that custom is the wrong answer. With real price ranges instead of "it depends".
Aug 21, 2026
Custom software is an application built specifically for one company and its processes, instead of bought off the shelf and bent into shape afterwards. You'll also see it called bespoke software, custom-built software, or a line-of-business application.
Most guides on the subject carefully avoid the one question you actually have: what does it cost. This one starts there. Then the types of software, the real steps of a project, and the cases where we tell people not to build custom at all.
We build these tools from Bordeaux, for small and mid-sized companies. The numbers below come from delivered projects, not a theoretical rate card.
What does custom software cost?
Budget €5,000 to €15,000 for a first useful scope in production, €15,000 to €40,000 for a complete line-of-business application, and €40,000 or more for a programme spanning several departments.
Here it is by scope:
| Scope | Indicative budget | What you get |
|---|---|---|
| First useful scope (1 process) | €5,000 to €15,000 | One complete process replaced and in production: a quote configurator, a single price grid, an order flow. |
| Complete business application | €15,000 to €40,000 | Several processes, roles and permissions, migration of your existing data, integrations with your tools. |
| Multi-department programme | €40,000 and up | A scope touching several departments, delivered in successive batches against milestones. |
These are indicative and firm up after scoping. They assume development in France, a single point of contact, and you owning the code.
Why these numbers came down. The same first scope — one complete process live in production — cost around €30,000 three years ago. It now starts at €6,000. AI-assisted development, Claude Code in our case, absorbed most of the routine work: boilerplate, tests, migration scripts, documentation. What hasn't changed is the time it takes to understand your business and settle the edge cases, and that's where the value sits.
That's what moves the line for a smaller company. A tool that could never justify €30,000 justifies €6,000. Custom software used to be for companies that could amortise an enterprise budget. It isn't anymore.
What actually moves the price
- The number of exceptions, far more than the number of features. One process with four special cases costs more than two simple processes.
- Integrations: ERP, accounting, email, file storage. Every system to connect adds work and tests.
- Data migration. The most underestimated line item when you're coming from spreadsheets. Ten years of inconsistent data does not migrate in an afternoon.
- How much AI is genuinely needed: transcription, reconciliation, document extraction. Worth it where it removes real work, pointless elsewhere.
And after go-live? Budget 15 to 20% of the initial cost per year for hosting, changes, and keeping it healthy. That's the figure SaaS-versus-custom comparisons always skip, in both directions: custom has no per-seat licence, but it isn't free to run either.
What are the 4 types of software?
The classic classification splits software into four families:
| Type | What it is | Examples |
|---|---|---|
| System software | Runs the machine and manages its resources. | Operating systems, drivers. |
| Application software | Serves a human or business purpose directly. | CRM, ERP, office suites, your custom application. |
| Programming software | Used to build other software. | Compilers, development environments. |
| Middleware | Makes software talk to other software. | Message buses, connectors, integration APIs. |
Custom software is almost always the second family: application software, written for your processes rather than for a market.
What are the 5 types of software?
The five-family version keeps the four above and pulls out one more category, depending on which classification you follow:
- Embedded software, which lives inside a device rather than on a computer: industrial machine, terminal, sensor.
- Or utility software, when the classification prefers to separate maintenance tools (backup, antivirus, compression) from system software.
These splits describe what a program is, technically. They're useful in a computing course and much less useful for deciding what to buy. For a buying decision the question isn't "which type of software is this" but "off-the-shelf product, configurable ERP, or custom". We've laid out those three options, with the criteria for choosing, on our custom software and ERP tooling page.
How do you build custom software?
In five steps. The principle behind them: ship one useful scope in weeks, rather than a complete project in a year.
The five steps of a project
- 1
Scoping (1 to 2 weeks) — a workshop with the people who do the work. We map the real process, not the one in the procedure manual. That's where the exceptions that drive the price are hiding.
- 2
Lean spec — a few pages on scope, business rules, and edge cases. Precise enough to quote, short enough to be read.
- 3
First scope delivered (4 to 8 weeks) — one complete process, in production, used by real people. That's what validates the choices before committing the rest of the budget.
- 4
Iteration with your teams — real usage drives changes in short cycles. The priorities stay yours.
- 5
Data migration and go-live — migrating spreadsheets and history, consistency checks, cutover, training.
The step everyone underestimates is the first. A rushed scoping gets paid for twice: once in wasted development, once in rework. If you're preparing yours, our software spec guide has the one-page template we use.
How long does custom software take to build?
Budget 4 to 8 weeks for a first scope in production, and a few months for a complete business application.
What stretches a project is almost never the development. It's waiting on approvals, getting access to existing data, and business decisions nobody wants to make. A project with an internal champion available a few hours a week moves twice as fast as one without.
Custom, off-the-shelf, or low-code: how to choose
Custom is the right call when:
- Your business runs on spreadsheets nobody dares modify any more.
- You're paying licences for a tool your teams work around.
- The way you work is a competitive advantage, not a defect to correct.
- Your data already exists, but across four systems that don't talk to each other.
Custom is the wrong call when:
- An off-the-shelf product covers 90% of the need. Payroll, accounting, and standard invoicing are well served by products.
- Your process isn't stable yet. Clarify it first, or you'll freeze the mess into code.
- Nobody internally can give the project a few hours a week.
Low-code genuinely occupies the middle ground: fast and cheap to start, constraining as soon as the business logic gets complicated or the volumes grow. We compared all three approaches, and where each breaks, in low-code, no-code, or custom.
The mistakes that cost the most
- Specifying a solution instead of a problem. "Add a dropdown here" hides the real need and rules out a better answer.
- Trying to ship it all at once. A project cut into deliverable slices can be corrected. A single big-bang delivery gets discovered too late.
- Treating data migration as a formality. It's often a third of the real effort.
- Forgetting who will maintain it. Software with no owner on the client side drifts within two years. If that's already your situation, the right entry point is code audit and project takeover.
Our take
Lower build costs don't change the main risk: solving the wrong problem. Software delivered fast and well, against the wrong need, is still money burned.
So start small, on a process that hurts, with a budget you'd accept losing. If the first slice delivers, the rest gets decided on evidence rather than on a sales promise.
Tell us what's breaking in your team. We'll tell you honestly whether custom software is worth it, including when the answer is no. Get in touch.
Related: custom software and ERP tooling, the software spec guide, and business process modeling.