Dundir

For municipalities

2026-07-30

Every procurement decision your team makes has to survive a challenge.

From a losing supplier, from an auditor, from the city council - and you’re building that defence case in email threads and shared folders right now.

As of January 2026, CPR adds a new layer: carbon footprint declarations, starting with precast concrete and steel.

Audience: head of procurement, digital transformation lead, or CFO at a Dutch municipality. Let them feel the audit-trail anxiety before pivoting to the CPR timeline - the second is a concrete deadline landing on top of an existing structural problem.

What you get

• A defensible procurement decision, built the moment you make it - not reconstructed after a challenge lands
• The same evaluation criteria applied to every supplier, every time - no inconsistency for an auditor to find
• Certification and CPR compliance gaps flagged automatically, before a bid closes
• Every score backed by a cited source - the explanation is already written when the council asks

Runs on your infrastructure

Not a cloud service, not an external API sending your tender data outside your control. Your data sovereignty requirements are the default, not an add-on.

Built as you go. That’s your audit trail. It’s also what you show the council.

This audience doesn’t care what Dundir does technically - they care what it means for their exposure. Lead with the defensible-decision framing, not the feature list. “Built as you go, not reconstructed after the fact” is the line to land twice if needed.

How it works

STEP 1

Configure the policy

Price · quality · sustainability
SROI · CPR indicators, your weights

→

STEP 2

AI scores each supplier

Against your criteria,
every procurement

→

STEP 3

Gaps get flagged

Certification & CPR
shortfalls, before the bid closes

→

STEP 4

Audit-ready record

Built at the moment
of decision, not after

Every score comes with a cited data source. For this audience, explainability isn’t a feature - it’s the compliance requirement.

“Cited data source” matters more to this audience than to any other segment - explainability isn’t a feature, it’s the compliance requirement.

Why local, not cloud

• The vendor may not be there for year 5 of the contract. OpenAI, the most visible name in AI, posted a $20.9B operating loss against $13.1B revenue in 2025 - leaked financials independently verified by the Financial Times (Zitron 2026). No frontier AI lab has yet proven this business model holds at the scale a public body would depend on
• The model you build against will not stay still. Anthropic commits to a minimum 60 days’ notice before retiring a model - Claude Sonnet 4 and Opus 4 were gone 62 days after notice, June 2026 (Anthropic 2026). OpenAI gives 6 months for production models, as little as 2 weeks for preview ones (OpenAI 2026). A multi-year contract means repeated forced migrations, on the vendor’s calendar
• The compliance basis for “cloud is fine” has already collapsed once. The EU-US Data Privacy Framework survived its first court challenge in September 2025, but it replaced Privacy Shield - which the same court struck down in 2020 - and is already under appeal (General Court of the European Union 2025)

$20.9B OpenAI operating loss, 2025, on $13.1B revenue (Zitron 2026)

None of this is a technical gap a cloud vendor can promise around. A model that runs on your own server doesn’t need a competitor’s balance sheet to hold, its deprecation calendar to skip you, or a legal framework that’s already fallen once to survive the next challenge.

This reframes local deployment from a compliance checkbox into a risk-management argument - the numbers are cited and dated, not FUD, and they describe the market generally, not a dig at one named vendor. For a finance- or procurement-literate audience this lands harder than privacy alone: a ten-year public contract can’t depend on a vendor’s burn rate, deprecation cadence, or a legal basis that’s already been struck down once before.

Are you sure

• Most organisations lack structured tracking of delivery and compliance data - the audit trail is retroactive document chasing
• The Aanbestedingswet and EU Directive 2014/24 don’t accept “we meant to document it” (Rijksoverheid 2024)

Jan 2026 carbon footprint declarations begin for precast concrete & steel (European Parliament and Council 2024)

In force since Jan 2025. Broader indicators from 2030. Full life-cycle reporting by 2032. The tooling for this doesn’t yet exist in the Dutch market.

Note (2026-07-23): this slide states the CPR timeline precisely - phased, not a blanket 2026 mandate. A municipality audience is exactly the kind that will know the real timeline; overstating it here would cost credibility immediately.

Can you do it

• Windesheim University anchors the research side - a KIEM or RAAK-PRO grant can fund the pilot before a commercial contract exists
• The deployment model is one Dutch public-sector IT already has a category for: on-premise and sovereign, not experimental
• We’re not asking you to be the first municipality to trust an AI vendor with tender data - we’re asking you to be first to have it explained, cited, and audit-ready

342 Dutch municipalities in the addressable market

The ask: a research-partnership pilot, funded through the Windesheim grant track - lower risk than a commercial contract, and it gets your procurement policy encoded before the next CPR tranche lands.

Deliberately generic here - no named individual’s relationships are claimed as a secured Dundir asset until that person has actually committed. Close on the grant-funded pilot as the lowest-friction entry point for a public-sector buyer.

References

Anthropic. 2026. “Model Deprecations.” https://platform.claude.com/docs/en/about-claude/model-deprecations.

European Parliament and Council. 2024. “Regulation (EU) 2024/3110 (Construction Products Regulation, CPR).” European Union. https://eur-lex.europa.eu/eli/reg/2024/3110/oj/eng.

General Court of the European Union. 2025. “Latombe v European Commission (Judgment Upholding the EU-US Data Privacy Framework Adequacy Decision).” https://iapp.org/news/a/european-general-court-dismisses-latombe-challenge-upholds-eu-us-data-privacy-framework.

OpenAI. 2026. “Deprecations.” https://developers.openai.com/api/docs/deprecations.

Rijksoverheid. 2024. “Aanbestedingswet 2012.” https://wetten.overheid.nl/BWBR0032203.

Zitron, Ed. 2026. “Exclusive: OpenAI Losses Increased Nearly 8x in 2025, with Spending Hitting $34 Billion.” https://www.wheresyoured.at/exclusive-openai-financials/.