Procuring custom software
A tender or private request for custom software stands or falls with the preparation. This guide helps buyers and project managers write a good request — from describing the desired outcome to requirements versus wishes, standards such as ZGW, BIO and WCAG, and clear exit and ownership provisions. We explain where requests often go wrong and how Appfront bids as a build partner: transparent, realistic and without promises that cause problems later. This is general information, not procurement law advice.
What does tendering for custom software mean?
Tendering for custom software means that, as a government organisation, you put an assignment for bespoke software out to the market through a formal procedure. Unlike with an off-the-shelf package, you are not buying an existing product, but the building of a solution that fits your process exactly. That calls for a request that describes the desired result clearly, without specifying the solution so tightly that good parties drop out.
For many government processes, custom software is a better fit than a standard package: you are dealing with specific laws and regulations, integrations with government registers and work processes that do not fit a generic product. Custom software gives you control over the functionality, the standards the software complies with and ownership of your data — provided you set those points out properly in the request. A standard package may look cheaper, but it sometimes leads to expensive modifications or lock-in if it does not fit.
The procedures, threshold amounts and rules around tendering are described by PIANOo, the Dutch public procurement expertise centre. Always check there for the current amounts and rules — they are revised periodically. Appfront acts as a build partner and bidder, not as a procurement lawyer: this page provides general information, not procurement law advice. For the legal side, you work with your own procurement and legal departments.
Outcome instead of over-specified requirements
Describe the result the software must achieve and the processes it supports, rather than prescribing every field and every button. That way you keep control of the end result and give bidders room to arrive at the best solution using their expertise.
Requirements versus wishes
Distinguish between hard requirements, which determine whether a bid qualifies, and wishes, on which you compare and score quality and approach. Too many hard requirements needlessly close off the market; well-chosen wishes steer towards the best value for money.
Exit and ownership arranged
Set out in the request who owns the source code and data, how data is handed over on termination and what documentation is delivered. Clear exit provisions prevent lock-in and keep switching to another party realistic.
From request to award: the steps
Careful preparation makes the difference between a tender that produces comparable, realistic bids and a process that stalls later. Below are the steps you go through when preparing a request for custom software, from sharpening the need to the award and management afterwards. PIANOo describes the deadlines and rules that apply for each procedure.
Determine which problem the software solves, which processes it supports and what result you want to achieve. Describe the outcome and the hard constraints, not a technical design worked out in fine detail.
Set out the requirements and wishes, name the relevant standards (such as ZGW, BIO and WCAG) and define exit and ownership provisions. Choose the procedure that fits the estimated value; PIANOo publishes the current thresholds.
Publish the tender brief, answer questions in the Q&A document (nota van inlichtingen) and evaluate bids against the award criteria. A market consultation beforehand sharpens the brief and tests feasibility.
After award, the build phase begins, with clear agreements on delivery, documentation, maintenance and further development. Make sure the exit arrangements from the tender brief also end up in the contract.
What a good software tender brief contains
A tender brief that produces comparable, realistic bids always contains the same building blocks. Below are the elements we see missing most often in software tender briefs — and which make the difference between a smooth project and one that stalls along the way.
Outcome-focused description
Describe the goal, the processes and the desired result rather than a tightly fixed technical design. This keeps you in control of the outcome and gives bidders room to apply their expertise to find the best solution — without inadvertently excluding good suppliers.
Requirements, wishes and award criteria
Separate hard requirements (knock-out criteria) from wishes you score on, and link these to transparent award criteria. Keep the number of requirements focused and realistic, so you steer towards the best price-quality ratio and not unintentionally towards the lowest price alone.
Making standards explicit
Name the standards that apply to your process, such as the ZGW APIs, the Baseline Informatiebeveiliging Overheid (BIO, the government information security baseline) and WCAG 2.1 AA for accessibility. Specifying standards ensures the software fits into the wider government landscape and prevents lock-in.
Integrations and existing systems
Describe which registers and systems the software needs to integrate with — think of DigiD, eHerkenning or TenderNed. A clear picture of the existing IT landscape prevents surprises during the build and makes bids easier to compare.
Exit and ownership provisions
Specify who owns the source code and data, how data is handed over on termination and what documentation is delivered. Good exit arrangements belong in the tender brief, not only in the contract phase, and keep switching to another supplier realistic.
Maintenance, further development and realism
Ask not only for the build, but also for maintenance, support and further development after delivery. Test timelines for realism: a tender brief that leaves room for honest assumptions yields more reliable bids than one that invites overoptimistic promises.
Who this guide is for
Preparing a software tender brief is relevant to a wide range of government organisations. The principles — describing outcomes, requirements versus wishes, standards and exit provisions — are the same everywhere, but the relevant integrations and standards differ per process.
Municipalities
Municipalities commission custom software for case-based working, services and specific implementation processes. Standards such as ZGW and integrations with DigiD often play a role here. Read more about building software for municipalities.
Implementing organisations
Implementing organisations and public service providers that support processes such as grant allocation or schemes digitally. Think of clear integrations and strict requirements around information security. See, for example, building subsidy software.
Provinces and water boards
Provinces and water boards that procure custom software for supervision, permits or area-based processes. Here too, the BIO applies for information security and WCAG for accessibility, plus integrations with national registers where relevant.
Procurement & tendering via TenderNed
In the Netherlands, tenders are published via TenderNed, the government's tendering platform. If you want to link TenderNed to your own procurement or contract system, read about building a TenderNed integration.
Standards and frameworks to take into account
When you put out a tender for custom software, you name the standards and frameworks that apply to your process, so the software fits the government landscape and you avoid lock-in. Exactly which ones are relevant depends on your organisation and process. You publish tenders via TenderNed; the procedures are described by PIANOo. Below are the frameworks we come across most often.
How Appfront works as a bidder
Appfront bids on tenders for custom software in a transparent and realistic way. We describe what we do and don't know, are open about assumptions and risks, and make no promises that cause problems later during delivery. A tender is best served by honest bids, not the most optimistic ones.
We work outcome-driven and deliver clear documentation and portable code. We make ownership, exit, standards and maintenance explicit, so you are not tied to us. No black box, but agreements that a future supplier can also pick up and continue.
If you are preparing a tender or have a market consultation under way, we are happy to advise, without obligation, on feasibility and on how you formulate outcomes, requirements and wishes. You work with a fixed point of contact who understands both the technology and the process.
Also see our pages on building software for municipalities and building subsidy software, or contact us to talk through your tender.
- Transparent bids, open about assumptions and risks
- Realistic planning, no promises that cause problems later
- Outcome-driven development based on your actual process
- Works with government standards such as ZGW, BIO and WCAG
- Clear agreements on ownership and exit, with no lock-in
- Clear, portable documentation and code
- Experience with integrations to government registers
- Fixed point of contact who understands both technology and process
- Attention to maintenance and further development after delivery
- Helps think things through during market consultations and preparation
Information security and privacy in the tender
Custom software for government almost always processes personal data. Include information security and privacy as hard requirements in your tender. The Baseline Informatiebeveiliging Overheid (BIO) is the mandatory information security framework for government; refer to it explicitly, along with data minimisation and appropriate logging and audit trail.
In addition to the BIO, the GDPR applies to the processing of personal data and, for public websites and applications, WCAG 2.1 AA applies for digital accessibility. Ask bidders to demonstrably comply with these frameworks and to document the data flows, so your processing register stays complete. Which requirements apply exactly is something to agree with your own security and privacy officers.
Want to discuss how to embed BIO, GDPR and WCAG concretely in your tender? Get in touch, no obligation. We're happy to help, though this does not replace procurement law advice.
- BIO as the information security framework
- GDPR-compliant processing and data minimisation
- WCAG 2.1 AA accessibility where publicly accessible
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Logging and audit trail with traceable data flows
- Clear agreements on data storage and retention periods
- Documentation for your record of processing activities
See also: market consultation for software (the step before the tender), Appfront as a software supplier for government, and the requirement pages BIO-compliant software and digitally accessible software.
Frequently asked questions about tendering for software
Answers to the questions buyers and project managers ask most often. General information, not procurement law advice.
If you publish notices from your own procurement system, take a look at our eForms integration.
A tender is the procedure by which a public sector organisation puts a custom software contract out to the market, so that interested suppliers can submit a suitable quote. Depending on the estimated value of the contract, you opt for a private request to a few parties or a European tender procedure. PIANOo, the Dutch public procurement expertise centre, describes the applicable procedures and publishes the current threshold amounts. A good tender request describes not only what you want technically, but above all which result the software must achieve for your organisation.
That depends on the estimated value of the contract. For contracts above the European threshold amounts, a European procedure is in principle mandatory; below them, you can often issue a multiple or single private request, within the limits of your own procurement policy. The exact threshold amounts are revised periodically and are listed on the PIANOo website, so never quote a fixed amount from memory, but refer to the current source. We provide general information here, not procurement law advice; consult your procurement or legal department.
Describe the desired result (the outcome) rather than a technical design worked out in fine detail. Set out which problem you are solving, which processes the software supports, which standards apply and which constraints are firm. If you prescribe every button and every field, you rule out better solutions and take on the risk that the design does not work later on. A functional, outcome-focused request gives bidders room to use their expertise to arrive at a suitable solution, while you still keep a grip on the end result.
Requirements are knock-out criteria: if a bid does not meet them, it is rejected. Wishes are points on which you compare and score bids against each other, often linked to award criteria. A common mistake is to make everything a requirement; that needlessly restricts the market and filters out good parties. Keep the number of hard requirements sharp and realistic, and use wishes to reward quality, approach and future-proofing. That way you steer towards the best price-quality ratio rather than the lowest price.
Specify the standards that are relevant to your process, so that the software fits into the wider government landscape. Common ones are the Zaakgericht Werken APIs (ZGW) for case data, the Baseline Informatiebeveiliging Overheid (BIO) for information security and WCAG 2.1 AA for digital accessibility. Depending on the process, integrations such as DigiD, eHerkenning or TenderNed may be added. By making standards explicit, you prevent supplier lock-in and keep your architecture open. Which standards exactly apply depends on your organisation and process.
Because they determine whether you own your data and software when the contract ends, and whether you can move to another party without major hurdles. Specify who owns the source code and data, how data is handed over on termination, which documentation is delivered and how long handover and aftercare last. Without clear exit provisions, lock-in arises: you are stuck with one supplier because switching becomes too expensive or too risky. Good exit arrangements therefore belong in the tender request, not only in the contract phase.
The most common mistakes: specifying the solution down to the last detail instead of describing the outcome, listing too many points as hard requirements, missing or vague exit and ownership provisions, no attention to maintenance and further development after delivery, and unrealistic timelines that only seem achievable with overoptimistic promises. A clear description of the existing systems that need to be integrated is also often missing. A tender that addresses these points produces more comparable bids and a project that is less likely to stall during delivery.
We bid transparently and realistically: we describe what we do and don't know, we make no promises that cause problems later, and we are open about assumptions and risks. We work outcome-first, deliver clear documentation and make explicit agreements on standards, ownership, exit and maintenance, so you are never locked in to us. If you are preparing a tender or running a market consultation, we are happy to help assess feasibility. Feel free to get in touch via our contact page, with no obligation.
Preparing a software tender?
Tell us which process you want to support and where you are getting stuck in the preparation: defining the outcome, requirements versus wishes, standards or exit provisions. We will help you think through feasibility and how to sharpen the tender, with no obligation. Please note that this is general information and does not replace procurement law advice.