“AI procurement” is not one market. A team selling training, a knowledge-management product and an implementation consultancy need different searches and different qualification evidence.
Use this guide to build a Dutch buyer watchlist with one row per relevant need. The examples are historical public records, checked on 13 September 2026; they are not advertised here as open tenders or confirmed future revenue.
Two public records that change the search
| Public record | What the source establishes | Supplier decision |
|---|---|---|
| Gemeente Maastricht: Opleidingsaanbod Learn@Maastricht, publication TN-532939, 19 June 2025 | Lot 3 concerns data-driven and AI-supported working; the lot's main CPV is 80000000, education and training | Relevant to a suitable training provider; not automatically an AI software purchase |
| IVO Rechtspraak: Kennismanagementsysteem Rechtspraak, TN 555193, document dated 3 November 2025 | A market consultation prepares a possible knowledge-management procurement; the buyer explicitly says a subsequent tender and its form are not yet decided | Put it in a research queue; inspect subsequent official notices before treating it as a live competition |
Sources: Maastricht notice, pages 1 and 7–8; IVO Rechtspraak consultation, printed pages 3 and 5.
These two deliberately selected cases do not estimate Dutch market size or the frequency of classification gaps. They show why buyer need and notice stage matter more than an “AI” label.
Separate your offer into three searches
Training and adoption: test Dutch terms such as datagedreven werken, opleiding, training and kunstmatige intelligentie. Inspect training classifications as well as the actual lot description. Exclude training you cannot deliver; do not treat any mention of AI as product demand.
Knowledge systems: test kennismanagement, kennisbank, zoekfunctionaliteit and informatievoorziening. Review source integration, access permissions, migration, governance and exit requirements. A knowledge-system project need not be an AI project.
Implementation and support: test the actual work you sell: integration, managed support, data architecture or application development, using Dutch buyer language. Classifications are a starting point, not proof of suitability.
These terms are search suggestions, not validated high-volume keywords or a guarantee of portal matching behavior. Compare separate keyword and code passes using the monitoring log. Record fields searched and code-descendant settings.
Build a buyer watchlist, not a pile of links
For each record, keep buyer identity, official source, notice date and stage, relevant lot, scope evidence, your capability, missing information, next check and owner.
For Maastricht, the action is to research subsequent awards and similar training needs—not to respond to an expired deadline. For IVO Rechtspraak, the action is to check whether a later procurement was actually published. Do not contact named staff through channels inconsistent with the published procedure.
Keep three queues: research/consultation, current competitions requiring qualification, and awards for account context. A keyword match does not move a record from one queue to another.
Know the data boundary
TenderNed's dataset guidance distinguishes historical datasets from current-notice access. It also states that new XML API access requests are temporarily waiting-listed. A publicly readable page is not proof that unrestricted API access or a complete historical archive is available.
Record the source edition, retrieval date and notice types included when analysing a downloaded dataset. Do not add repeated notices or modifications together as if they were separate contracts.
Qualify the shortlisted work
Check required references, delivery language, access to data, deployment environment, service responsibilities, procurement route and submission rules. Separate the proposed AI component from the rest of the service. Bring unresolved requirements into the cross-border readiness brief.
Then use buyer intelligence and bid capacity to select the next action.
Assess your Dutch buyer watchlist with Duke. Bring known records and ask which sources and workflows can be demonstrated in your account. This guide does not certify product coverage.
Editorial owner: Antoine Simon. Review by 13 December 2026. The Netherlands procurement guide remains the owner for general market-entry questions.