For municipalities · October 2026

Dundir

Every award has to survive a challenge.

Dundir is designing procurement software that writes the reasons for an award at the moment it is made, inside your own network. It is in development with design partners; nothing in this deck runs at a client yet.

The problem

The reasons, rebuilt after the fact.

When an award is challenged, the defence is assembled from email threads and shared folders. The reasons should exist the moment the decision does.

2.130

Dutch public buyers must give the reasons for an award, to every bidder.

Aanbestedingswet 2012, art. 2.130 [EVID-008]

€8,354

Swing on one subcontractor’s total when a generative AI tool was given the same bids in a new session.

Hamppi 2025, Table 6, p. 62 [EVID-002]

2026

Declarations of performance cover climate indicators from 8 January 2026, more environmental indicators from 2030 and the rest from 2032, as each product family’s standards come in.

CPR 2024/3110, art. 15(3) [EVID-050]

Procurement decisions Stage: research and design

The same rules for every bidder.

A language model writes an answer. An optimisation engine works one out.

Hard requirements are fixed first: certification, delivery date, budget ceiling, CO₂ limit. Price and reliability are weighed inside them, by weights you set. Same input, same answer, and the reasons written down at award.

price →↑ reliabilitydelivery dateCPR certifiedbudget ceilingCO₂ limitoptimum
Schematic of the design, no datasolver: research and design

Deployment Stage: design

Inside your own network.

Data and models are designed to stay inside the municipality’s network.

No cloud account is needed to switch it on. Tender data is designed never to leave the building: a decision taken at the start, not a setting.

your networkofficesite servergate edgepublic cloudno egress
Deployment design: data and models stay inside your networkdesign

The design

From specification to handover.

Specification, solver, gate, Wkb dossier, contract memory: one loop, so what is promised at award can be checked on delivery.

  1. 01Specificationdesign
  2. 02Solverresearch and design
  3. 03Gate checklab prototype
  4. 04Wkb dossierdesign
  5. 05Contract memorydesign
The design in five steps. Only step 03 exists today, as a bench prototype.

Where we stand

Stage, not product.

Module Stage
Procurement solver research and design
Smart gate lab prototype
Supplier record and contract memory design

What we have not proven yet. That the solver buys better than an experienced buyer. The literature supports the problem and the local design; the rest has to come from pilot data, and we do not have it yet.

What we are asking for

A design partner, not a customer.

  • One procurement category. Closed tenders with their award reasons, compared again under the same rules.
  • Your policy, written down. The criteria and weights you already apply, as the engine’s input.
  • Sparring. On what a challenge needs from the record, and how public buyers can take part in a pilot.

Dundir

dundir.com · info@dundir.com

Sources

European Union. 2024. “Regulation (EU) 2024/3110 on Construction Products.” https://eur-lex.europa.eu/eli/reg/2024/3110/oj/eng.
Hamppi, Joni. 2025. “Integrating AI into Procurement Processes in Construction.” Master’s thesis, Aalto University, School of Engineering. https://aaltodoc.aalto.fi/items/0abb3c95-dd08-4913-b563-6d34b21a6f44.
Koninkrijk der Nederlanden. 2012. “Aanbestedingswet 2012, Artikel 2.130.” Staatsblad 2012, 320. https://wetten.overheid.nl/BWBR0032203/2016-05-01/1.