Article
6 min read

Who Wins the Public Market When Everyone Has the Same AI?

AIPublic procurementBid managementAI agentsTender analysis
Piotr Gerke

Piotr Gerke

CTO, leading the engineering & product.

Two desks seen from above: one person working alone at a laptop in the dark beside stacked archive boxes, and a team in daylight working over motorway drawings, a map and folders with the same laptop

Everyone has the same AI now

Your competitors have the same AI you do. The best models (supposedly PhD-level) are a credit card away. Access to intelligence used to be an edge. Today it's close to a utility.

So if everyone has the same brain, what makes yours win?

Not the model, but what your AI knows and sees.

Two bid teams, one tender

A grey Monday in October. Two construction groups open the same tender: 40 km of expressway, lump-sum contract, six weeks to submission. 258 files: specifications, drawings, a bill of quantities and a stack of annexes, some scanned from paper.

Company A. The bid analyst opens a general AI chat. It takes 20 files, so she picks the 20 that look most important. The other 238 stay in the folder. By lunch she has a neat summary and a requirements checklist for the estimators. Nobody asks what was in the files that didn't fit. Two of them, the drainage and noise-barrier specifications, were scanned annexes. The model never saw them, so it never flagged them. It looked complete but was not.

Company B. All 258 files go to an agent connected to the company's bid history and the public tender record. It comes back with the same summary, plus what nobody asked: the drainage annex adds around 40 items to the scope, the bypass job 25 km away finishes in May, the paving crew is booked all summer, and this buyer has awarded its last six road contracts 8–12% below the cost estimate. The bid director reads it twice. Not the answer anyone wanted: bid, but not at the price that wins on paper.

Company A: general AI chatCompany B: agent with context
Documents read20 of 258, the upload limitAll 258, scans included
Scope pricedWhat was on the checklistFull scope, drainage and noise barriers included
Unit ratesUsual assumptionsOwn rates from recent jobs
Crew and nearby workNot in the chatBypass crew free in May, paving crew booked
SubcontractorsNot in the chatTrack record and current quotes on file
Buyer's habitsNot in the chatAwards 8–12% below estimate, price weighted 60%
Penalty clause, section 17.4Not flaggedFlagged at twice the market norm
PriceLowest, on visible scopeHigher, on full scope

May. The bids are opened. Company A is cheapest and wins. The missing scope is worth about 5% of the contract, roughly the margin it planned to make. It's a lump sum, so that work is theirs to build at their own cost. Someone finally reads the drainage specification properly at the first site meeting.

Company B comes second. Nobody celebrates. In September, a better-fitting tender closer to home comes up, and its crew is free to take it.

Same model. Same question. The difference was what each one could see.

The last 5% makes or breaks the bid

Every bid manager knows Pareto. The scope, the dates, the checklist: any AI now does that in minutes.

The last 5% is where tenders are won and lost:

  • The annex that didn't fit in the upload.
  • The clarification on day 19 of 21 that changes the scoring.
  • The revised bill of quantities two weeks before submission.
  • The deadline that moves, then moves again.
  • The new specification uploaded under the same file name.
  • The reference letter that expired in spring.

In public procurement, 95% correct doesn't make the cut. It gets you a disqualification, or a contract you'll regret winning.

AI can be wrong. Manage it like any other risk.

Bidding has always been risk management. AI doesn't change that. It changes the tools.

Use tools built for the job: ones that read every document, show where each answer comes from, track every change to the tender, and tell you what they couldn't read instead of skipping it. Then keep a human on the answers that carry money or eligibility, the way you'd check a junior colleague's work.

Not a smarter model. A better-onboarded one.

Company B didn't have better AI. It had AI that had been properly onboarded. You'd never hand a senior hire a laptop and wish them luck. You'd give them the bid history, the pricing logic, and the people who know which buyers are difficult. An agent harness does the same for AI:

  1. Memory. Bids, prices, references, certificates, CVs. Structured, not scattered across 400 SharePoint folders.
  2. Market knowledge. Every tender, award, buyer and competitor, kept current.
  3. Process. Qualify, analyse, price, assemble, submit. The agent knows where it is.
  4. Tools. Pull documents, fill forms, watch deadlines, alert the right person.
  5. Feedback. Every win and loss flows back in, so the next bid starts smarter.

What it buys you

  • Fewer costly mistakes. Every file gets read, scans included, and every amendment or deadline change is flagged the day it's published. Add your company data, and it also catches the expired certificate or the project manager who left in March.
  • Better bets. Where to bid based on data, not on who's loudest in the Monday meeting. Which buyers are about to re-tender, where competitors win and at what price, which tenders are traps.
  • More time to prepare. The most common tasks run on a set, automated process: qualification check, requirements list, ESPD, reference letters, compliance matrix. That frees up days of a six-week window for what actually wins tenders: pricing, subcontractor quotes and a strong technical offer.
  • One place to coordinate. Every task has an owner and a due date: the estimator, the lawyer, the technical lead, the subcontractors. Everyone works on the same version of the tender, instead of digging through a 60-message email thread the night before submission.

Why it compounds

Public procurement publishes its own market: every tender, every award, every winning price. Add your history of bids, wins and losses, and you get a context layer no competitor can copy. Every bid makes the next one sharper and more accurate.

The gap won't be about who has better AI. It'll be about who started collecting the right context first. Models can be bought next quarter. Context can't.

Where to start

  1. Stop asking "which model?" Ask "what will it know about us?"
  2. Map where bid knowledge lives today. Inboxes, shared drives, Excel trackers, three people's heads.
  3. Make every bid leave a trace. Go or no-go, price, outcome, reason for the loss.
  4. Connect your history to public market data. One without the other is half the picture.
  5. Automate the repetitive work first. It pays back fastest and forces you to structure your data.
  6. Measure what matters. Win rate, disqualifications avoided, margin on contracts won.

Same AI. Different outcome.

Company A and Company B had the same AI. Only one of them knew what it was looking at.

That's why we built Minerva: every tender and award in your market, connected to your own bids, documents and decisions. Tracked from the first file to submission.

AGI won't win your next tender. The company that gave it the right context will.

Book a call in 30 seconds

You will receive:

A video recording of the app right after booking
A platform demo tailored to your company
Key features shown in practice
Concrete examples of working with tenders
Answers about implementation and system capabilities
Book a call

Trusted by 450+ organisations, from growing businesses to large enterprises.