Market

TenderAI: public procurement is 14% of GDP. Why is nobody drafting with AI?

15 June 2026 Blackflake Editorial 7 min read

Public procurement across the EU and UK is roughly 14% of combined GDP — well over a trillion euros of contracts awarded each year through structured competitive tenders. Behind every award is a bid response: a document written to a published rubric, evaluated against specific weights, scored, and ranked.

The bid-writing process has not materially changed in 30 years. Word templates. Reused case studies. Two weeks of weekend work by a BD lead. A desperate final-day QA pass. And a non-trivial share of bids disqualified for mechanical reasons — page limits, missing signatures, wrong format — before their content is ever read.

Why this is an unusually clean AI opportunity

The rubric is published. Every tender call includes an evaluation methodology. Weights per section. Mandatory criteria. Pass/fail thresholds. This is not an opaque evaluator; the scoring criteria are in the call document.

The structure is consistent. Across UK Contracts Finder, TED, Polish BZP, and regional portals, bid responses share the same shape: firm profile, methodology, past-performance evidence, pricing narrative, team bios, compliance attestations. Section names vary. Section requirements rhyme.

The failure modes are well understood. Bids lose for predictable reasons: rubric-misaligned emphasis, missing mandatory criteria, disqualifying format errors, weak past-performance framing, or pricing structures that miss the evaluation model. Each of these is a specific, addressable failure mode — the kind an agent with the right rubric awareness can catch.

The buyer has motive. A mid-sized firm preparing 20 bids a year currently dedicates 2–4 person-weeks per bid. Compress that to 2–3 days, and the firm either (a) submits more bids at the same cost, (b) wins a higher share by putting better-framed content into fewer bids, or (c) competes for contracts it currently ignores because the bid-overhead is prohibitive.

Why it hasn’t happened yet

Wrappers fail here for the same reason they fail in legal work. A generic LLM can draft a plausible-looking response. It cannot guarantee mandatory-criteria compliance. It cannot score itself against the published rubric. It cannot catch a missing signature or a violated page limit. Bid-writing is high-stakes because the response gets mechanically filtered before it’s read — and a wrapper has no filter awareness.

Consulting firms are the incumbent. The bid-writing consulting market is fragmented but well-margined. Firms like Bloom Procurement Services (UK), national consultancies, and boutique specialists earn success fees on contract wins. Their moat is expertise; their scaling constraint is headcount. None of them have strategic incentive to build the product that displaces their own billing model.

What TenderAI is and isn’t

It is: a composed pipeline of agents — tender discovery, eligibility scoring, rubric-aware section drafting, pricing-model-aware commercial composition, and a compliance gate that rejects the format failures that kill otherwise-winning bids. Details on the TenderAI page.

It is not: a replacement for the human bid lead. The final positioning, the pricing decision, the strategic choice of which contracts to chase — those remain with the firm. TenderAI compresses the mechanical work so the human can concentrate on the judgment work.

"Public procurement is the largest, cleanest services-as-software opportunity in Europe. The rubric is published. The stakes are real. The current solution is Word templates."

Why UK and Poland first

Both markets have high-quality published tender portals (Contracts Finder, BZP), post-Brexit regulatory divergence that creates ongoing rule changes, and a high SME population currently priced out of public-sector contracts. Both are markets where the bid-writing consultancy market is profitable enough to displace and under-automated enough to disrupt.

TenderAI is in active build, with UK Contracts Finder and Polish BZP integrations prioritised. Pilot slots for Q3 2026. Contact: enterprise@blackflake.com.


— Blackflake Editorial · Blackflake 15 June 2026 · Łódź, Poland