In short: what does custom software cost in the Netherlands?
Most custom software in the Netherlands is priced as hours multiplied by an hourly rate: as of September 2026, the Knab Zzp Uurtarievenboekje 2026 puts the average freelance software developer at €94 per hour, and the Talent Monitor by HeadFirst and Intelligence Group puts software developers in the wider flexible market at about €105. At an illustrative €95 per hour, a small integration of 40-150 hours comes to about €3,800-€14,250, a focused MVP of 300-600 hours to about €28,500-€57,000 and a customer portal of 500-1,000 hours to about €47,500-€95,000. After launch, Dutch software suppliers commonly budget 10-20% of the build cost per year for maintenance, plus hosting. All amounts exclude 21% VAT (btw) and are example calculations, not quotes.
Build, buy or integrate: do you need custom software at all?
Before you compare quotes, check whether you need to build anything. Off-the-shelf software, often sold as SaaS, is usually the fastest and cheapest route for generic processes such as bookkeeping, email, scheduling or a standard CRM. The vendor carries the development and maintenance costs, and you pay a subscription. The trade-off is that your process has to fit the product, and your data and roadmap depend on that vendor.
The middle route is often overlooked: connecting the tools you already use. An integration or automation that moves data between your CRM, accounting package and forms can remove manual work at a fraction of the cost of a new application. Our guide to choosing a first automation explains how to find a bounded task that is worth automating.
Custom software makes sense when the process is specific to your organisation, when it gives you an advantage or when workarounds, duplicate data entry and stacked licences have become expensive. Compare the options over several years, not just the first invoice. As an illustrative example, a SaaS tool at €30 per user per month for 20 users costs €7,200 a year, or €21,600 over three years, before any integration or workaround time. A custom build costs more upfront but has no per-user fee; whether it pays off depends on how much manual work and how many licences it replaces.
| Aspect | Off-the-shelf (SaaS) | Integrate existing tools | Custom software |
|---|---|---|---|
| Best suited to | Generic processes that many businesses share | Tools that work well but do not talk to each other | Processes that are specific to your organisation |
| Upfront cost | Low: set-up and configuration | Low to moderate: design and build of the connections | Highest: discovery, design, development and testing |
| Ongoing cost | Subscription, often per user | Subscriptions plus monitoring of the connections | Maintenance, hosting and further development |
| Time to start | Fastest | Fast | Slowest: a first version needs discovery, design and build |
| Fit with your process | You adapt to the product | You keep your tools and remove manual steps | The software follows your process |
| Control over data and roadmap | Limited to what the vendor offers | Shared with the vendor of each tool | High, if ownership and access are arranged |
| Main risk | Price changes, lock-in and missing features | Connections break when a vendor changes its API | Scope creep and underestimated maintenance |
What goes into the price of custom software?
A quote for custom software is more than programming time. The components below appear in almost every project, whether they are listed separately or included in an hourly total. When two quotes differ widely, the difference is usually in how much of this work each supplier has included.
Discovery and scoping
Discovery turns an idea into a scope that can be estimated: goals, users, main workflows, data, integrations and what is deliberately left out. It is usually a short phase with its own price. We recommend it even for small projects, because an estimate without a clear scope is mostly a guess.
UX and UI design
Design covers user flows, wireframes, the visual interface and often a clickable prototype. A prototype lets users test the idea before anything is built, which is cheaper than changing working code later. Internal tools can often use a simpler design based on standard components; customer-facing products usually need more attention.
Development
Front end, back end, database, integrations and the admin functions that users never see but the business needs. This is the largest component. The cost rises with the number of user roles, business rules, integrations and exceptions, not just with the number of screens.
Testing and quality assurance
Automated tests, manual testing on real devices, acceptance testing with your users and fixing what they find. Skipping testing does not remove the cost; it moves it to after launch, when problems are more expensive and more visible.
Security
Authentication, permissions, careful handling of data, updates to third-party libraries, logging and a security review or penetration test before launch. Planning security from the start is cheaper than adding it later, especially when personal data or payments are involved.
Project management and communication
Planning, demos, decisions, documentation and keeping everyone informed. With a freelancer this is often part of the hourly rate; an agency may list it as a separate role. Count your own time as well: someone in your organisation must be available to answer questions and approve work.
Hosting and infrastructure
Servers or cloud services, databases, backups, monitoring, email delivery and separate environments for testing and production. These are recurring costs that continue after launch and grow with usage.
Maintenance and support
Security patches, framework and library updates, bug fixes, compatibility with browsers and connected services, and small improvements. Software that is not maintained becomes less secure and harder to change over time.
What do software developers charge per hour in the Netherlands?
Published figures give a useful reference point, as long as you know what each one measures. The Knab Zzp Uurtarievenboekje 2026, based on research among more than 20,000 self-employed professionals, puts the average freelance software developer at €94 per hour excluding btw, and the average freelance web developer at €73. Freelancer.nl, drawing on Dutch market research from 2025-2026 and its own marketplace data, describes an average range of €70-€110 per hour for freelance web developers, from about €45-€65 for juniors to €90-€120 for seniors. Where a source does not say whether btw is included, we show the figure as published.
Rates in the wider flexible market, which includes seconded professionals, are somewhat higher. Computable reported on 4 September 2026 that the Talent Monitor by HeadFirst and Intelligence Group puts software developers at €104.77 and application programmers at €105.15 per hour. For agencies, Simplicate’s Agencies Benchmark Report Q3 2025, based on almost 550 Dutch creative, digital and marketing agencies, found an average of €105 per hour. That group is broader than software development, so treat it as an indication rather than a benchmark for software agencies specifically.
A higher rate is not automatically more expensive. An agency rate often includes project management, testing, design and continuity when someone is ill or leaves; a freelancer can be very efficient for a well-defined task. Experience matters too: a senior developer who prevents a wrong architectural choice can save more hours than the difference in rate. We recommend comparing the total estimate for the same, clearly defined scope, and asking which roles and activities each quote includes.
| Group | Published rate | Source and date |
|---|---|---|
| Freelance software developer | €94 per hour on average, excl. btw | Knab Zzp Uurtarievenboekje 2026 (article updated 1 July 2026) |
| Freelance web developer | €73 per hour on average, excl. btw | Knab Zzp Uurtarievenboekje 2026 (article updated 3 April 2026) |
| Freelance web developer by experience | €70-€110 on average; from €45-€65 (junior) to €90-€120 (senior) | Freelancer.nl (19 June 2026) |
| Software developer, freelance or seconded | €104.77 per hour on average | HeadFirst and Intelligence Group Talent Monitor, via Computable (4 September 2026) |
| Creative, digital and marketing agencies | €105 per hour on average | Simplicate Agencies Benchmark Report Q3 2025, via Emerce (30 September 2025) |
How much does a web application cost? Example budgets by scope
Because every project is different, the most honest way to show budgets is as example calculations. The table below multiplies an assumed number of hours by an example rate of €95 per hour, close to the Knab average for freelance software developers. The hours are assumptions for a typical version of each scope, not quotes, and your own project can be smaller or larger.
The calculation itself is simple: 300 hours × €95 = €28,500, and 600 hours × €95 = €57,000, excluding 21% btw. At an agency rate, or with specialist roles such as a security engineer or data specialist, the same hours cost more. The biggest variable is almost always the number of hours: integrations with older systems, complex permissions, data migration and unclear requirements add more than a higher hourly rate does.
If you are unsure where your project fits, start with the smallest version that solves a real problem. A small automation between existing tools is often a sensible first step, and it shows you what a larger system would really need. Looking for a website rather than an application? Our guide to website costs covers that separately.
| Scope (example) | What it typically includes | Assumed hours | Example budget |
|---|---|---|---|
| Integration or automation | Connecting two or three existing tools, such as forms, CRM and accounting, with error handling and logging | 40-150 | €3,800-€14,250 |
| Discovery and clickable prototype | Workshops, scope, user flows and a prototype to test with users before anything is built | 40-80 | €3,800-€7,600 |
| Internal tool | A web application for one team, such as planning, approvals or registrations, with a few user roles | 200-400 | €19,000-€38,000 |
| MVP of a new product | Core features, sign-up and login, basic admin, one payment or email service and testing | 300-600 | €28,500-€57,000 |
| Customer portal | Secure login, documents, status updates, several user roles and one or two integrations | 500-1,000 | €47,500-€95,000 |
Fixed price, time and materials or a phased approach?
The pricing model decides who carries the risk when the scope changes, and in software the scope almost always changes as you learn. No model is right for every project; the choice depends on how precisely you can describe what you need today.
Fixed price
A fixed price gives budget certainty for a clearly described scope. It works well for a small, well-understood deliverable, such as a defined integration or a discovery phase. The supplier builds a risk margin into the price, and every change becomes a change request. A fixed price for a vague scope often leads to discussions about what was included.
Time and materials
You pay for the hours actually worked, usually with regular reporting. This suits work where priorities shift based on user feedback. It gives flexibility, but you need a clear backlog, frequent demos and an agreed budget ceiling or review moment to stay in control.
Phased delivery
A phased approach combines both: a fixed-price discovery, then development in short phases or sprints with an estimate per phase, and separate agreements for maintenance. After each phase you decide whether to continue, adjust or stop. We recommend this for most custom projects, because it limits the risk on both sides and lets real use steer the next investment.
What does software cost after launch? Total cost of ownership
The build is a one-off investment; running the software is not. Dutch software suppliers commonly publish a rule of thumb of 10-20% of the build cost per year for maintenance, updates, bug fixes and security patches, excluding hosting. MG Software’s 2026 pricing guide, for example, uses that range. Treat it as a planning assumption rather than a law: a simple internal tool with few integrations may need less, while a customer platform connected to several external services may need more.
On top of maintenance come hosting and infrastructure, third-party services such as email delivery, SMS, maps or AI APIs, monitoring and backups, and your own team’s time for support and training. Connected services change too: when a vendor updates or retires an API, your integration has to follow.
An illustrative three-year calculation shows why this matters. Assume a build of €50,000, maintenance at 15% per year (€7,500), hosting and monitoring at €150 per month (€1,800 per year) and third-party services at €100 per month (€1,200 per year). The running costs are then €10,500 per year, or €31,500 over three years, which brings the total cost of ownership to €81,500 excluding btw. In this example, the initial build is about 61% of the three-year cost. Further development, which most successful software needs, would come on top.
Can the WBSO tax credit lower the cost of software development?
The WBSO is a Dutch tax incentive for research and development (speur- en ontwikkelingswerk, S&O). Employers pay less wage tax for staff who carry out R&D, and self-employed entrepreneurs can claim an extra deduction. Software development can qualify, but the conditions are strict: according to RVO, the work must be technically new for your company and involve concrete technical problems that you solve yourself. Routine development, standard configuration and applying existing techniques do not qualify.
For 2026, RVO lists a benefit of 36% on the first €391,020 of the S&O base, 50% in that first bracket for starters and 16% above it. You must apply before the work starts. Companies with staff can apply until the last day of a month for a period that starts on the first day of the next month; check RVO’s WBSO calendar for the current application dates.
There is an important limitation when you commission software. RVO states that you can only claim S&O hours of yourself and of employees on your own payroll, and that the costs of outsourced research do not qualify. In practice, the hours you buy from an external developer do not count as your S&O hours. The WBSO can still be relevant if your own developers carry out qualifying technical work alongside a supplier. Check the conditions with RVO or a tax adviser before you plan on it; this article is general information, not tax advice.
Changes for 2027 have been proposed. In a news item of 15 September 2026, RVO announced that the fixed S&O hourly wage would rise from €29 to €33, that the coalition agreement announces a broadening of the WBSO for AI and software, and that more details will follow in the WBSO 2027 handbook from November 2026. These changes only become final once the Eerste Kamer (Senate) has approved them.
How can you keep custom software affordable?
The most effective savings come from decisions about scope, not from a lower hourly rate. These are the approaches we recommend most often.
Start with the problem, not the feature list
Describe the process that costs time or causes errors today, and how you will know it has improved. A clear problem makes it easier to leave out features that do not contribute. A good brief also shortens discovery; our article on writing a better website brief applies to software projects as well.
Build a minimum viable product first
Launch the smallest version that real users can work with, then let their feedback decide what comes next. Features that seemed essential in a workshop often turn out to be rarely used.
Phase the investment
Split the project into phases with a clear result and a decision point after each one. That keeps every commitment manageable and lets you stop or change direction without writing off a large budget.
Use proven components and services
Authentication, payments, email delivery, file storage and admin screens rarely need to be built from scratch. Established frameworks, open-source libraries and managed cloud services reduce development time, as long as their licences, costs and data locations suit you.
Integrate before you build
If your existing tools already do most of the work, an integration may solve the problem at a fraction of the cost. Keep custom development for the part that is genuinely specific to your organisation.
Make decisions quickly
Waiting for feedback, unclear priorities and late changes all cost hours. Appoint one product owner with the authority to decide, and reserve time for demos and testing.
Who owns the code? Ownership, exit, security and GDPR
Some of the most expensive problems in custom software are not technical. They appear when you want to change supplier, when a security issue is found or when a customer asks how their data is protected. Arrange these points in the contract and the project plan from the start.
Copyright and source code
Under the Dutch Copyright Act (Auteurswet), copyright belongs to the maker of a work. When employees create software as part of their job, the employer is regarded as the maker unless agreed otherwise (Article 7). That rule does not cover an external freelancer or agency: a transfer of copyright must be agreed in writing and delivered by a deed (Article 2). Without such a transfer, a client who commissions software generally receives a right of use rather than ownership. Agree in writing whether rights are transferred or licensed and what that covers. Suppliers often reuse their own generic components, and open-source libraries keep their own licences; that is fine, as long as it is clear.
Access, documentation and exit
Make sure the code repository, hosting and cloud accounts, domain names and app store accounts are in your organisation’s name, or that you have full administrative access. Ask for technical documentation, deployment instructions and a handover period if you change supplier. For business-critical software where the supplier keeps the source code, a source code escrow arrangement, in which the code is deposited with an independent party, can be an alternative.
Security by design
Security costs least when it is part of the design, the estimate and the acceptance criteria. The Dutch National Cyber Security Centre (NCSC) publishes security guidelines for web applications, intended for both buyers and suppliers, and the OWASP Application Security Verification Standard provides requirements that can be tested. Budget for library updates, logging and an independent security test before launch; our penetration testing guide explains what that involves.
GDPR and privacy by design
If the software processes personal data, the GDPR requires privacy by design and privacy by default. According to the Dutch Data Protection Authority, that means protecting personal data from the design stage, not keeping it longer than necessary and, by default, processing only the data you need for a specific purpose. When a supplier hosts or maintains software that contains personal data, it usually acts as a processor, and you record the agreements in a written data processing agreement (verwerkersovereenkomst).
- Auteurswet, Article 2: transfer of copyright (in Dutch)
- ICTRecht: copyright on software explained (in Dutch)
- NCSC: ICT security guidelines for web applications (in Dutch)
- OWASP Application Security Verification Standard
- Dutch Data Protection Authority: accountability and privacy by design
- Dutch Data Protection Authority: data processing agreements (in Dutch)
- Penetration testing: a practical guide
- Request the free AI visibility and security scan
Questions to ask a software supplier
Use these questions when you compare proposals. A good supplier will answer them clearly, and the answers make quotes easier to compare than the hourly rate alone.
These checkmarks are temporary; your answers are not saved or sent. The checklist helps you prepare and does not replace legal or tax advice.
A practical next step
Start by writing down the process you want to improve, who uses it, which systems are involved and what a successful first version should achieve. Add a budget range and a timeline, even if they are rough. That is enough for a useful first conversation and for an estimate based on a real scope instead of a guess.
Pixel Dev builds custom software, web applications and AI automation, with application security as part of the work rather than an afterthought. We can help you decide whether to buy, integrate or build, define a first phase and estimate it transparently. Bring your process, your current tools and a few examples of where things go wrong today.
Frequently asked questions
How much does an MVP cost in the Netherlands?
It depends mostly on the number of hours. As an illustrative example, a focused MVP of 300-600 hours at €95 per hour costs €28,500-€57,000 excluding btw. A narrower first version or reuse of existing components brings that down; complex integrations push it up.
What is the average hourly rate of a software developer in the Netherlands?
As of September 2026, the Knab Zzp Uurtarievenboekje 2026 puts the average freelance software developer at €94 per hour excluding btw. The HeadFirst and Intelligence Group Talent Monitor reports €104.77 for software developers in the wider flexible market, including seconded professionals. Rates vary with experience, specialism and responsibility.
How much does software maintenance cost per year?
A common rule of thumb among Dutch software suppliers is 10-20% of the build cost per year, excluding hosting. For a build of €50,000, that would be €5,000-€10,000 per year. The actual amount depends on the number of integrations and users, the security requirements and how actively the software is developed further.
Is custom software cheaper than SaaS in the long run?
Sometimes, but not by default. Custom software costs more upfront and needs ongoing maintenance, while SaaS is usually charged per user per month. Compare both over three to five years, including integrations, workaround time and the cost of switching later.
Can I claim the WBSO for software an agency builds for me?
Generally not for the agency’s hours. RVO states that only S&O hours of yourself and of employees on your own payroll qualify, and that the costs of outsourced research do not. If your own staff carry out qualifying technical work alongside the supplier, those hours may count; check the conditions with RVO before the work starts.
Who owns the source code of custom software?
Without agreements, the copyright on software built by an external supplier generally stays with the maker, and the client receives a right of use. Under the Auteurswet, a transfer requires a written agreement and a deed, so arrange ownership or a licence in writing. Also make sure your organisation can access the repository, hosting accounts and documentation.
