Ask three developers what it costs to build "custom software" for your business, and you get three numbers that barely seem to describe the same thing: one quotes eight thousand euros, another twenty-five thousand, a third well over a hundred thousand. Unlike a chatbot or a template website, custom software has no fixed shape. A single internal tool that automates one manual process and a multi-user platform that talks to five other systems are both "custom software", and the price gap between them is not markup, it is scope.
This guide walks through what custom software actually costs for a Dutch SME in 2026, what a development project looks like once you commission one, what to prepare before you call a developer, and the one part of the contract that quietly turns into a legal question the moment the software touches customer data.
Custom or off-the-shelf: the first decision
Before pricing anything, decide whether you need custom software at all. Accounting, CRM, HR, e-commerce and project management already have mature off-the-shelf packages that cover most of what a typical SME needs, maintained by a vendor with a whole customer base funding further development.
Custom development earns its cost once your process genuinely does not fit an existing tool — your pricing logic or approval flow is specific enough that bending a package around it costs more in workarounds than building the real thing — or you need to connect systems with no standard integration between them. If the remaining gap is a minor inconvenience rather than a daily blocker, it is usually cheaper to live with than to close with custom software.
The trade-off runs the other way too. Own custom software, and no vendor can raise your subscription price or force a new interface on you. You also own the responsibility: someone has to keep it running and patched for as long as you use it.
What custom software costs in 2026
| Project type | What it typically includes | Typical build cost |
|---|---|---|
| Simple internal tool | One core workflow automated, single user role, one or two integrations | EUR 8,000 - 20,000 |
| Mid-size business application | Multiple modules, several user roles and permission levels, a handful of integrations (CRM, accounting, e-mail) | EUR 25,000 - 75,000 |
| Complex platform | Many integrations, multiple user types (internal and customer-facing), custom reporting, higher security requirements | EUR 80,000 - 200,000+ |
On top of the build price, budget separately for hosting and maintenance. Depending on scope this typically runs from a few hundred to a couple of thousand euros a month, covering server costs, security patching, monitoring and small fixes. Ask for this as its own line item in any quote — a build price with no mention of what happens after launch is not a complete quote.
What the project actually looks like
A development project that skips straight to coding usually costs more in rework than the time it would have taken to plan properly. A well-run project moves through the same broad stages regardless of size:
- Intake and process mapping. The current process gets mapped as it actually runs today, not as the org chart says it should — talking to the people who use it daily surfaces the exceptions a manager's description usually misses.
- Requirements and design. What the software needs to do gets written down concretely, and a clickable prototype gets reviewed before a line of production code is written, so misunderstandings surface on a mockup instead of a finished feature.
- Development in short cycles. Rather than disappearing for months, a competent team builds in short sprints and delivers working, testable pieces along the way, so you can redirect early if something drifts.
- Testing and a staged rollout. The software is tested against real data and edge cases, then rolled out to a small group before the whole company depends on it, so problems surface with five users instead of fifty.
- Handover and documentation. You receive the source code, access credentials, and documentation of how the system is built — everything a different developer would need to pick up maintenance if your relationship with the current one ends.
What to prepare before you call a developer
The quality of a quote depends heavily on what you can tell the developer up front. Before the first call, have ready:
- A written description, in your own words, of the process you want automated or the problem you want solved — not a feature list borrowed from a competitor's product.
- A list of the systems the new software needs to talk to (CRM, accounting, e-mail, a supplier's ordering system), and whether those systems have an existing integration option.
- Who will actually use the software day to day, and what they are allowed to see and do — this shapes the permission structure more than almost anything else.
- A rough budget range. Developers scope far more accurately toward a stated range than toward an open question, and it saves both sides a round of quotes that were never realistic.
What to settle in the contract before you sign
- Ownership of the code. Confirm explicitly that you own the source code once the project is paid for, not just a licence to use it — without this in writing, switching developers can mean rebuilding from scratch.
- A clear scope and change process. A fixed price only means something against a fixed scope. Agree up front how a change request outside that scope gets priced, so "just one more thing" does not quietly become a second project billed at the first project's price.
- A maintenance arrangement, not just a handover. Decide before launch who fixes a bug found in month three, what the response time is, and what happens if the original developer becomes unavailable.
- A processing agreement, if the software touches personal data. This is the part most SMEs forget, because it is not really a software decision — it is a legal one. If your developer builds, hosts or maintains software that processes personal data on your behalf — customer records, an HR system, a booking tool with client names and e-mail addresses — you are the *verwerkingsverantwoordelijke* (controller) under the AVG, and the developer or hosting party is your *verwerker* (processor). The Autoriteit Persoonsgegevens states plainly that outsourcing a processing activity to a processor requires a processing agreement under Article 28 AVG, setting out exactly what the processor is and is not allowed to do with the data. You remain responsible for the processing even though you outsourced it; that responsibility does not transfer to the developer just because they wrote the code. Two details are worth pinning down specifically in that agreement: the processor may only bring in a subprocessor — a separate hosting provider, for instance — with your written permission, and if the processor has a data breach involving your data, they are obliged to inform you as soon as possible, because reporting it to the Autoriteit Persoonsgegevens within 72 hours, where required, remains your duty, not theirs.
None of this is paperwork reserved for large companies. Any SME commissioning a booking system, a customer portal or an internal HR tool is, in AVG terms, outsourcing a processing activity the moment personal data touches that system — and the processing agreement belongs in place before development starts, not retrofitted after launch.
Maintenance after launch
The invoice for the build is rarely the last one. Budget for ongoing hosting, security patching as the frameworks underneath the software age, monitoring so a problem is caught before a customer reports it, and a channel for small fixes as your business changes shape around the tool. Software nobody touches after launch accumulates small breakages that go unnoticed until they compound into a much larger fix — treat maintenance as a standing line item from day one, not an afterthought.
When off-the-shelf is still the smarter choice
The build-vs-buy question is worth revisiting even after you have a working relationship with a developer. If a new off-the-shelf tool later covers what your custom system does, at a fraction of the ongoing maintenance cost, switching is a legitimate option, not an admission the original build was a mistake — requirements and the market both move. The same question that justified custom development in the first place is worth asking again periodically, not just once at the start.
Common mistakes
- Signing a fixed price against a vague scope. A fixed price only protects you if both sides agree, in writing, on exactly what it covers.
- Skipping the processing agreement. If personal data will pass through the software, this belongs in the contract before development starts, not as an afterthought once the AVG comes up in an unrelated conversation.
- Treating launch as the finish line. Software that nobody budgets to maintain degrades quietly until it becomes urgent and expensive to fix.
- No plan for who owns the relationship long-term. If the one developer who understands the system leaves or the agency closes, you need the documentation and code access to hand it to someone else without starting over.
FAQ
What does custom software development cost? In the Netherlands, a simple internal tool with one core workflow typically runs EUR 8,000 - 20,000, a mid-size business application with several modules and integrations EUR 25,000 - 75,000, and a complex platform with many integrations and user types EUR 80,000 - 200,000 or more. Hosting and maintenance are separate ongoing costs, typically a few hundred to a couple of thousand euros a month depending on scope.
What's the difference between custom software and off-the-shelf software? Off-the-shelf software is built once and sold to many businesses: proven functionality, built-in support, a lower price, but you adapt your process to fit the tool. Custom software fits your process exactly and you own the result, but you carry the full development cost and the ongoing responsibility for maintaining it.
How long does a custom software project take? A simple internal tool can be built in a few weeks to a couple of months. A mid-size application typically takes three to six months, and a complex, multi-integration platform can run six months to over a year, depending on how many systems it connects to.
Who owns the source code once it's built? This should be settled explicitly in the contract before development starts. Confirm in writing that you own the source code once the project is paid for, not just a licence to use it — without that, switching developers later can mean rebuilding from scratch.
Do I need a data processing agreement for custom software? If the software processes personal data on your behalf — customer records, an HR system, anything with names or e-mail addresses tied to individuals — yes. Under Article 28 AVG, outsourcing that processing to a developer or hosting party requires a processing agreement setting out what they are and are not allowed to do with the data, and you remain responsible for the processing even though you outsourced the work.
Talk to us before you commission a build
Not sure whether your problem needs a custom build or an existing package would do the job, or what a fair quote actually looks like for your scope? Our Web & Software Development team scopes both directions honestly, including telling you when an off-the-shelf tool is the better answer. If the software will handle sensitive customer or employee data, our Cybersecurity & Identity team can review the processing agreement and access setup before you sign anything.