Software market consultation: sounding out the market before your tender
Are you running a market consultation before tendering for software? Then you can test feasibility, standards and realistic requirements before the tender specification is fixed. Appfront takes part in market consultations as a market party and shares knowledge about custom software, covering feasibility, open standards, government integrations and build-vs-buy, without the sales pitch. A sharper tender specification is in our interest too. On this page you can read how a market consultation for software works, how to set one up and what you can expect from suppliers.
What is a market consultation for software?
In a market consultation, you invite interested companies to help you think through the feasibility and conditions of your planned contract before the tender procedure begins, which is how PIANOo describes the instrument. You explore the structure of the market and investigate which ideas and solutions exist. The consultation is not part of the formal tender procedure and is permitted, provided it is open, fair and transparent.
With software, this is especially valuable. Custom software often fits better than an off-the-shelf package when your process differs from the market standard, when you need integrations with government building blocks, or when you want to avoid adapting your way of working to a package's limitations. But build-vs-buy is never an obvious choice. A market consultation helps you sharpen that trade-off before you fix the tender specification, and prevents requirements that nobody can deliver or that are worded too narrowly.
Appfront takes part in software market consultations as a market party. We share knowledge about feasibility, open standards and realistic requirements, without the sales pitch. A better tender specification is in our interest too. If you would like to talk through your consultation or involve us, please feel free to get in touch. This is general information and not legal advice on procurement law.
Testing feasibility
Before you fix your requirements, you test whether your intended solution is technically and practically feasible. The market tells you which approach is realistic, which risks apply and where your draft requirements are too restrictive.
Sharpening build-vs-buy
Is there a suitable package, or is custom the better route? The market shows which standard solutions exist, where they fall short and when custom software is worth the investment for your process.
Formulating realistic requirements
With input from the market, you can formulate requirements and criteria that are both feasible and sharp. This prevents a tender specification that is too narrow for good bids or so broad that comparison becomes impossible.
How to set up a market consultation for software
A market consultation roughly follows four steps, from defining your goal and the right questions to turning the input into a sharper tender specification. You choose the format (written, conversations, a market event or demos) based on what you want to learn. Observe the transparency and equal-treatment rules at every step.
Formulate the problem statement and what you want to learn from the consultation: is it about feasibility, the choice between build and buy, standards, or testing draft requirements? Decide whether the consultation is open or closed.
Ask the market concrete questions about feasibility, suitable open standards and integrations, maintenance, risks and lead time, and about which draft requirements would be unrealistic or unnecessarily restrictive.
Gather input through a written questionnaire, conversations, a market event, or demos and presentations. Make clear in advance how you will handle the input and that taking part gives no advantage in the later tender.
Turn the insights into sharper requirements, criteria and a suitable procedure. Share any information you provide with all potential bidders in good time, so that nobody is favoured or disadvantaged.
Which questions to put to the market
The value of a market consultation lies in asking good questions. Below are the themes most worth putting to the market for custom software, so that your tender specification ends up sharper and more feasible.
Feasibility and approach
Is your intended solution technically and practically feasible in your context? Which approaches are realistic, what risks do suppliers see, and where are the biggest uncertainties? Test this before you fix your requirements.
Open standards and integrations
Which open standards and government integrations are the obvious fit for your process, such as DigiD, eHerkenning, the ZGW APIs, the BAG or the BRP? By asking about this up front, you avoid vendor lock-in and align with government-wide agreements.
Build, buy or a combination
Is there a suitable off-the-shelf package, or is custom development the better route, or a combination of the two? Ask the market which packages exist, where they fall short for your process, and when custom or hybrid development delivers more.
Realistic requirements and criteria
Are your draft requirements feasible and not unnecessarily restrictive? Which requirements rule out good suppliers, and which criteria make bids more comparable? Test your draft programme of requirements with the market.
Maintenance, further development and exit
What do maintenance and further development look like after go-live, and how do you avoid dependence on a single supplier? Ask about source code ownership, documentation, portability and exit scenarios, so you are not locked in later.
Lead time and planning
What is a realistic lead time for design, build and migration, and which dependencies play a role? Testing this helps you avoid a schedule in your tender that the market cannot deliver or that leads to failed tenders.
Which public bodies use a market consultation
Almost any public sector organisation can hold a market consultation before a software tender. We often see a few situations come up, each with its own questions for the market.
Municipalities
Municipalities that want custom software for processes that differ from standard packages, such as services to residents or supervision and enforcement. A market consultation helps with the choice between build and buy and with suitable integrations. See also building software for municipalities.
Provinces and water boards
Provinces and water boards with responsibilities around permits, supervision and area-based working. By consulting the market, you test feasibility and standards before you tender, and take into account government integrations such as the ZGW APIs and the VTH domain (permitting, supervision and enforcement).
Implementing organisations
Implementing bodies and partnerships that work case-based or support complex chain processes. A market consultation helps you formulate realistic requirements and lead times and get the integrations with national building blocks clear up front.
Innovative or complex assignments
Projects where the solution is not yet settled or where the market is changing quickly. This is exactly where a market consultation pays off: you explore what is technically possible and avoid setting requirements the market cannot deliver. Also consider building VTH software as an example for this cluster.
Standards and integrations to ask about
When procuring custom software for government, it pays to probe open standards and government integrations during the market consultation itself. This helps you avoid vendor lock-in and align with government-wide agreements. We build with a modern web stack and have experience with the relevant national building blocks, such as DigiD, eHerkenning, the ZGW APIs, the BAG and the BRP. A tender is usually published via TenderNed.
Why Appfront takes part in market consultations
Appfront builds custom software and knows the government standards and integrations that come with this kind of project. We take part in market consultations to share knowledge about feasibility, standards and realistic requirements, not to sell. A sharper tender specification is in everyone's interest, including ours.
We respect the transparency and equal-treatment rules that apply to a market consultation. We assume our input is made equally available to all participants and that taking part gives no advantage in the subsequent tender. Our answers are well-founded and honest about what is and isn't possible.
You speak with people who understand both the technology and the practice of government software. That keeps the conversation concrete: about integrations, build vs buy, maintenance and lead time. This way, our input helps you write a better tender specification, regardless of who ultimately wins the contract.
See also: procuring custom software (the next step) and Appfront as a software supplier for government. Take a look at our broader services around software for municipalities, VTH software and AI for municipalities and government. Want to talk through your consultation? Get in touch.
- Experience with custom software for government
- Knowledge of open standards and national building blocks
- Honest advice on feasibility, without a sales pitch
- Well-founded answers to your questions to the market
- Insight into build vs buy and realistic lead times
- Respect for transparency and equal-treatment rules
- Attention to maintenance, portability and exit
- A conversation about both technology and practice
- Focused on a sharper, better-founded tender specification
- Independent input, even if you ultimately choose differently
Compliance requirements to include in the tender specification
Government software almost always processes personal data. It pays to include the relevant frameworks in the market consultation and the tender specification from the start: the GDPR for careful processing and data minimisation, and the Baseline Informatiebeveiliging Overheid (BIO) as the information security framework. Ask the market how suppliers meet these requirements and which demonstrable measures they take.
If you are building citizen-facing software, also consider digital accessibility: WCAG 2.1 AA and the statutory DigiToegankelijk obligation apply to government websites and applications. Ask the market about data minimisation, logging, encryption and role-based access. For privacy frameworks, the GDPR is leading.
Want to talk through which security and accessibility requirements are realistic and appropriate for your project? Feel free to get in touch. This is general information and not procurement law advice.
- GDPR-compliant processing and data minimisation
- Baseline Informatiebeveiliging Overheid (BIO)
- WCAG 2.1 AA and DigiToegankelijk where applicable
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least privilege
- Audit logging and traceability
- Open standards and portability
- Documentation for your record of processing activities
Frequently asked questions about software market consultations
Answers to the questions we get most often about market consultations ahead of a software tender.
In a market consultation, you invite interested companies to help you assess the feasibility and conditions of your planned contract before the tender procedure begins, as PIANOo describes the instrument. A market consultation is not part of the formal tender procedure and is permitted, provided it is open, fair and transparent. For software tenders it is especially valuable, because it lets you test technical feasibility and realistic requirements before you finalise the tender documents. This is general information and not procurement law advice.
Software contracts are often complex and the market moves quickly. A market consultation lets you test whether your intended solution is technically feasible, which open standards and government integrations are appropriate, whether build, buy or a combination fits best, and whether your draft requirements are realistic for the market. This stops you from setting requirements in the tender that nobody can meet, or that are drawn too narrowly. The result is a sharper, better-founded tender.
You can choose how to structure the consultation. According to PIANOo, a market consultation can be open or closed, written, oral or a combination, and interactive or non-interactive. For software, you often see a written questionnaire on feasibility and standards, followed by talks or a market event, and sometimes demos or presentations in which suppliers explain their approach. You choose the format based on what you want to learn and how much time you have.
Start with a clear problem statement and the purpose of the consultation, and put concrete questions to the market about feasibility, standards, maintenance and lead time. Good questions cover, for example, which open standards and integrations are the obvious choice, which risks suppliers see, how build vs buy works out, and which requirements would be unrealistic. Make clear in advance how you will use the input, and that taking part gives no advantage in the later tender.
From a professional supplier, you can expect them to think along on feasibility and standards, to be honest about what is and isn't possible, and to give well-founded answers to your questions, without a sales pitch. A good market party will also point out risks, alternatives and places where your draft requirements lead to unnecessary restrictions or higher costs. Appfront takes part with that in mind: better tenders lead to better procurement for the whole market.
A market consultation must always be open, fair and transparent; interested businesses must not gain an advantage or suffer a disadvantage compared with their competitors, according to PIANOo. In practice, this means that any information you give to participants must also be made available in good time to other potential candidates and tenderers, and that a participating market party must not end up in a favoured or disadvantaged position at the time of the tender. Document the process and the information provided carefully.
Yes. Appfront actively takes part in market consultations for software with government bodies, sharing knowledge on feasibility, open standards, government integrations and realistic requirements. We do this without a sales pitch, because a sharper tender is in everyone's interest, ours included. We respect the transparency rules and assume our input will be made equally available to all participants.
Participation in a market consultation is voluntary for suppliers, and the contracting authority can decide for itself whether the consultation is open or closed. Appfront does not charge for contributing to a market consultation; we see it as knowledge sharing that benefits both the market and the tender. If you would like to involve us in your consultation or talk it through, please get in touch.
Involve Appfront in your market consultation?
Are you running a market consultation for a software tender? Invite Appfront, or talk through your approach with no obligation. We'll help you think through feasibility, open standards, build-vs-buy and realistic requirements, without the sales pitch, because a sharper tender is in our interest too. This is general information, not procurement law advice.