What is maatwerk software, and when does a Dutch SME need it?
Maatwerk software is software written for one organisation's process rather than bought off the shelf for thousands of customers. For a Dutch SME it usually means a web app that replaces a spreadsheet, a portal for customers or suppliers, or a layer that ties AFAS, Exact Online or Moneybird to the rest of the business.
You need it when a process that makes or saves you money depends on people copying data between systems. The symptoms are familiar: a planner who is the only person who understands the master Excel file, invoices typed twice, a customer who emails to ask for a status that sits in three places, and a monthly report that takes a full day to assemble.
You do not need it when a standard product already fits. If a planning SaaS covers ninety percent of what you do and the remaining ten percent is a habit rather than a requirement, change the habit. Custom software earns its cost only on the parts of your business that are genuinely different, or where the glue between tools costs you real hours.
A custom software development company in the Netherlands, a zzp developer and a remote team like ours can all build this kind of tool. What differs is price, how you communicate, and what happens to the code afterwards. This page covers those points honestly, including where a remote team is not the right choice.
Custom software or another SaaS subscription: a decision rule
Buy SaaS for commodity processes and build custom software for the process that sets you apart or connects everything else. That rule sounds simple; applying it takes an honest look at where your team's hours actually go.
Start by listing every tool and spreadsheet the process touches, then count the hand-offs where someone copies, exports or re-types data. Each hand-off is a place where errors enter and time leaks out. If there are one or two, an integration between existing tools may be enough. If there are six, and the spreadsheet in the middle is the real system of record, you are already running custom software; it is just fragile.
Choose SaaS when
The process is standard (payroll, bookkeeping, email marketing), the vendor has Dutch-market features you need, and your team would accept small changes to how they work.
Choose custom when
The process is specific to how you quote, plan, produce or serve; several tools must share the same data; or per-user licence fees keep rising as you hire.
Choose a hybrid when
Your bookkeeping stays in Exact Online or Moneybird, your HR in AFAS, and a small custom app sits in between, handling only the part no product covers. For most SMEs this is the cheapest durable answer.
For a deeper general comparison, see our page on no-code versus custom development, which covers tools such as Airtable and Power Apps as a middle step.
Replacing Excel workflows with a portal or dashboard
The most common custom software request from Dutch SMEs is not a grand platform; it is getting a critical spreadsheet out of a shared drive and into a proper multi-user application. Excel is brilliant for thinking and terrible as a shared database.
The warning signs are consistent: files named with dates and initials, a macro only one colleague dares to touch, formulas overwritten by accident, and no record of who changed a price or a delivery date. Once the file is the heart of quoting, planning or stock, each of those is a business risk.
- Map the file first. Every tab, column and formula is documented, including the unwritten rules people apply by habit.
- Separate data from logic. Records go into a database; calculations become tested code; views become screens per role.
- Keep the export. People still like spreadsheets for analysis, so the app exports clean files on demand.
- Move history carefully. Old rows are imported and checked against totals the business already trusts.
- Run in parallel. For the first weeks the team uses the app while the spreadsheet stays read-only as a fallback.
Dashboards follow naturally once the data lives in one database. Our Excel to software conversion page walks through the same approach in more technical detail.
How do you choose a custom software development company in the Netherlands?
Choose on evidence of how they scope, communicate and hand over, not on the size of their office or their list of technologies. A good custom software development company in the Netherlands, or a remote team, will ask more questions about your process than about your budget in the first call.
They write a scope you can read
Ask for a quote that lists screens, user roles, integrations, data migration and exclusions, split into milestones. A single figure for “the platform” means the real scope will be discovered on your invoice.
They talk about handover early
Ask where the code will live, who holds the hosting account, what documentation you receive and whether another developer could take over. If the answer is vague, so is your exit.
They put copyright in writing
Under Dutch copyright law, a freelance maker keeps the copyright unless it is transferred in writing. Ask to see the transfer wording before you sign, not after launch.
They can show similar integrations
If you need AFAS or Exact Online, ask them to explain how the connection authenticates and what happens when the API limit is hit. Specific answers beat logos.
They suggest a small first milestone
A paid discovery or first module shows you their working style for a fraction of the total. We usually propose one.
If you are weighing offshore options generally, our guide to hiring Indian developers covers what to check across different models.
Connecting AFAS, Exact Online and Moneybird to custom software
Most Dutch custom software is only as useful as its connection to the bookkeeping or ERP system, because that is where invoices, relations and often hours already live. The good news is that the three packages Dutch SMEs use most all offer documented APIs.
AFAS Profit
AFAS documents two kinds of connectors in its Profit API documentation: GetConnectors to read data and UpdateConnectors to add, change or delete it. Your AFAS administrator creates the connectors and a token for the app, which means you control exactly which fields our software can see.
Exact Online
Exact Online uses OAuth for app access and limits the number of API calls per company per minute and per day. Custom software has to queue and batch its requests so a busy afternoon does not hit those limits and stop invoices syncing. We build that queue in from the start and log every failed call.
Moneybird
Moneybird's developer documentation covers sales invoices, contacts and external invoices, plus webhooks that notify your app when an invoice changes state. Each webhook request carries a signature header so the app can verify it really came from Moneybird.
Before building anything, we check whether a ready-made connector in the vendor's app store already does the job. If it does, you should use it and spend your budget elsewhere. When it falls short, a custom link starts from US$900; the sibling page on Exact Online integration goes deeper into that choice.
Who owns the source code? IP clauses for custom software in the Netherlands
You should own it, but under Dutch law that only happens if the contract says so and the copyright is actually transferred. Paying for software does not by itself make you its copyright holder.
Article 2 of the Auteurswet requires the agreement to transfer copyright to be made in writing, and the transfer itself to be delivered by a deed (akte). Article 7 gives employers the copyright in works their employees make in the course of their job, but that rule does not cover freelancers or outside suppliers. So when a freelance team builds your software, the transfer has to be written down explicitly.
- Copyright transfer: the code written for you is transferred to your business on payment of each milestone, by signed deed.
- Pre-existing components: open-source libraries stay under their own licences; the quote lists the main ones.
- Repository access: the code lives in a Git repository under your organisation from the first commit.
- Hosting and domains: accounts registered to your business, with our access revocable at any time.
- Documentation: a README, environment set-up notes and an overview of data models, delivered with the final milestone.
This is not legal advice. Ask your own lawyer to draft or approve the transfer wording, and we will sign it as part of the written quote. For our general conditions, see the terms page.
A verwerkersovereenkomst with an India-based developer: what it covers
If the software handles personal data and we have access to it, you are the controller and we act as a processor, so the AVG expects a processing agreement (verwerkersovereenkomst) between us. Article 28 of the GDPR sets out what that agreement must contain, including acting only on your instructions, confidentiality and security measures.
India is not on the European Commission's list of adequacy decisions, so a transfer of personal data to a processor in India normally also needs a transfer tool, most often the Commission's Standard Contractual Clauses, which have a module for controller-to-processor transfers.
- We can often work without production personal data at all, using test data during development.
- Production data stays on EU hosting in your name; access is by named accounts with logging.
- Where support needs live data, access is limited to what the task requires and removed afterwards.
- The processing agreement and SCCs are agreed in your written quote; your counsel reviews and signs off.
Compliance stays your responsibility as controller, confirmed by your own adviser; we build the technical measures that support it. The sibling page on GDPR-compliant website development covers the public-facing side, such as cookie consent.
How much does custom software development cost in the Netherlands?
With BtechWaleTech, custom software starts from US$900 for a focused first release, AI features start from US$600, and maintenance starts from US$120/mo after two free months. Quotes from Dutch bureaus and zzp developers vary widely; local rates, team size and how much consultancy is bundled explain most of the difference.
Whoever builds it, these are the factors that move a custom software quote the most:
- Number of distinct workflows, not number of screens.
- User types and permission rules (staff, managers, customers, suppliers).
- Integrations, and how well documented each API is.
- Data migration from spreadsheets, Access or an older system.
- Reporting and dashboards, especially custom calculations.
- Mobile use: responsive web app versus a separate Android and iOS app.
- Non-functional needs such as audit logs, single sign-on or strict hosting rules.
Running costs are separate: hosting in your name, any third-party APIs, and optional care. Ask every supplier for those yearly numbers too, because a cheap build with expensive upkeep is not cheap.
Milestone-based pricing: paying for working software, not promises
Milestone pricing means the project is split into parts that each deliver something you can use or test, and each part is invoiced only when delivered. It protects you from paying for months of invisible work, and it protects the developer from scope that keeps growing without a conversation.
Our quotes are itemised in USD. Many Dutch clients budget in euros; Wise and most Dutch business banks show the conversion before you pay, so you know the euro amount at that moment. Invoices come from India, and how you book them is a question for your accountant.
- Milestone 1, discovery: process map, data model, screen sketches, integration check, final scope.
- Milestone 2, core workflow: the main process working end to end with test data.
- Milestone 3, integrations: AFAS, Exact Online or Moneybird connected, with error alerts.
- Milestone 4, migration and roles: historic data imported, permissions per user type.
- Milestone 5, go-live: production deployment, training call, handover documents and copyright deed.
If a change comes up mid-project, it is quoted as its own line before any work starts, so the budget never moves without your written approval. See pricing for every service's starting point.
How long does custom software development take?
A focused first release usually takes 6–12 weeks. That range covers a single core workflow with one or two integrations; larger systems are better delivered as several releases rather than one long project.
The biggest timing risk is not code. It is waiting for decisions, sample data and access to the systems we integrate with. An AFAS token or an Exact Online app registration can take days to arrange internally, so we request those in the first week.
We work in two-week cycles. At the end of each, you get a link to a test environment with the new parts working, a short written summary and a list of open questions. If something is not what you expected, you see it within two weeks rather than at launch. A first release that people use daily is worth more than a big release that is still three months away; we will suggest cutting scope before we suggest extending a deadline.
- Weeks 1–2: discovery, data model, integration access requested.
- Weeks 3–6: core workflow built and demonstrated every two weeks.
- Weeks 6–9: integrations, reports, data migration.
- Final weeks: acceptance testing by your team, go-live, parallel running.
Technology choices a Dutch team can take over later
Pick a stack that plenty of Dutch developers know, so you are never tied to the people who built it. Exotic choices make a supplier harder to replace; mainstream ones keep your options open.
We generally build with widely used frameworks such as Laravel or Node.js on the server, React for the interface, and PostgreSQL or MySQL for data, hosted in an EU region such as AWS Frankfurt or Ireland in an account registered to you. Python joins where data processing or AI is involved. None of this is unusual, and that is the point.
Web app first, mobile second
A responsive web app works on phones for most internal tools. A separate Android and iOS app makes sense for offline use, camera-heavy work or customer-facing apps.
Security basics built in
Role-based access, encrypted connections, hashed passwords, audit logs of who changed what, and daily backups tested by restoring them. These are defaults, not extras.
Public pages and search
If part of the system faces the public, such as a quote request form or a knowledge base, it is built with fast pages, clean URLs and structured data so Google and AI search tools can read it. Portals behind a login stay out of search on purpose.
Moving an old desktop or Access application to the web? Our desktop to web application page explains that path.
Working with an offshore custom software team from the Netherlands
Working with a team in India from the Netherlands is a planned mix of written updates and short live calls. India is 3.5 hours ahead in Dutch summer time and 4.5 hours in winter, so our afternoon and evening overlap your late morning and afternoon.
Calls
Kick-off, fortnightly demos and decision calls on Teams, Zoom or Meet, usually between late morning and mid-afternoon Dutch time. Every call ends with a written summary in the project chat.
Everyday contact
WhatsApp for quick questions, 7 days a week, in English. Longer decisions go by email or in the issue tracker so they are searchable later.
Payments
Quotes in USD, paid by Wise, bank wire or PayPal per milestone. Nothing is billed before you approve the written quote; see the refund policy for the general conditions.
Contract
The written quote carries the scope, milestones, copyright transfer and, if needed, the processing agreement. Your lawyer reviews it; we sign what you both agree.
The first two weeks
Days 1–3: kick-off call, walkthrough of the current spreadsheet or tools, list of integrations and access requests. Days 4–10: process map and data model shared for comment, clickable screen sketches, and a written go or no-go on each integration.
There is no local office and no site visit. If watching your team work would help, we ask for a screen recording of a normal day, which often tells us more than a meeting would.
Where AI fits in custom software for Dutch SMEs
AI earns its place in custom software on narrow, repetitive reading tasks, not as a general chatbot bolted onto everything. Reading incoming invoices, sorting emails in Dutch and English, and extracting order lines from PDFs are the usual candidates.
The pattern that works is extraction plus human confirmation. The model reads the document and fills in the fields; a person checks and approves; only then does the data reach AFAS, Exact Online or Moneybird. Mistakes are caught before they are booked, and the approval log shows who confirmed what.
Data protection applies here too. We prefer model providers that offer EU data processing and contractual terms that exclude training on your data, and we keep personal data out of prompts where the task allows it. Where a chatbot talks to your customers, the EU AI Act's transparency duties mean people should be told they are dealing with an AI system; the sibling page on the AI automation agency alternative covers those points.
AI features start from US$600 and usually take 2–4 weeks, either as part of a larger build or added once the core software is in use.
Custom software risks and red flags for Dutch buyers
Most failed custom software projects fail on scope, ownership or silence, not on technology. Watch for these signs before you sign with any custom software development company in the Netherlands or abroad.
- A single total price with no breakdown by workflow, integration or milestone.
- No mention of copyright transfer, or a licence to use instead of ownership.
- Code kept in the supplier's repository or hosting account, with no date for handover.
- Large upfront payment before any working software is shown.
- No discovery phase: the build starts from a one-page wish list.
- Personal data copied to developer laptops with no processing agreement.
- Demos only at the end of the project.
- Promises that the software will be finished faster if you pay more upfront.
None of these automatically means bad intent; they mean you carry the risk. A good supplier answers each point in writing before you ask. Our page on in-house versus outsourced development covers when hiring your own developer makes more sense.
Worked example: a hypothetical Tilburg installer replacing its planning spreadsheet
Say an installation business near Tilburg with a dozen technicians plans jobs in a shared Excel file, sends work orders by WhatsApp, and types completed jobs into Exact Online for invoicing. Customers call the office to ask when the technician is coming.
A sensible first release would be a planning web app with three roles: planners assign jobs on a calendar, technicians see today's jobs on their phones and upload photos and signatures, and the office approves completed jobs. Approved jobs create draft invoices in Exact Online through its API, so nobody retypes them. A simple customer page, reached by a link in a text message, shows the planned date.
That scope would be quoted from US$900, split into five milestones over around ten weeks, with the Exact Online link and data import from the old spreadsheet as separate lines. AI reading of supplier invoices could follow later from US$600. Copyright transfers to the business by deed at each paid milestone; hosting runs in an EU region under its own account.
This is an illustrative scenario, not a past client or a promised result.
Checklist before hiring a custom software development company in the Netherlands
Send these questions to every supplier on your shortlist, local or remote. Comparable answers make quotes comparable.
- Which workflow does the first release cover, and which is deliberately left out?
- How is the quote split into milestones, and what do I see at each one?
- Which integrations are included, and has access been checked?
- How will spreadsheet or legacy data be migrated and verified?
- Where do the code, hosting and domain live, and in whose name?
- What is the exact wording of the copyright transfer?
- Will you sign a processing agreement and, if outside the EU, SCCs?
- Who will I talk to each week, and through which channels?
- What documentation comes with the handover?
- What does maintenance cost after launch, and what does it include?
- How are change requests priced and approved?
- What will you not do on this project?
Send your answers, or just a description of the process you want fixed, and you will receive an itemised quote in about two working days. The Netherlands overview lists everything else we build for Dutch businesses.