TenderCodes .eu

Guide

Supplier's Guide: Winning EU Public IT Contracts

Babar Al-Amin
builder of TenderCodes & founder of BrotCode UG
Last reviewed 2026-06-13

Supplier's Guide: Winning EU Public IT Contracts

Most software firms decide whether to bid on a public IT contract in the wrong order. They read the notice, get excited about the budget, then discover three weeks later that they were never the kind of supplier the contracting authority was set up to choose. This guide runs the order the other way: it starts with where the work is, how to read what a notice is actually asking for, and what separates a bid that scores from a bid that gets filed. It is written for the small and mid-sized supplier: the dev shop, the SaaS firm, the integrator deciding whether an EU public tender is worth the pen.

Public procurement is roughly 14% of EU GDP, around €2 trillion of spending every year (European Parliament factsheet). A real slice of that is IT. The barrier to a share of it is not usually capability. It is knowing how the game is scored before you start playing.

What's in this guide

Where to find EU IT tenders

The first place to look is TED, Tenders Electronic Daily, the EU's official journal for procurement. Every contract above the EU thresholds gets published there. The volume is real: TED carries roughly 800,000 procurement notices a year, worth about €815 billion in total (European Commission). A meaningful share of those are IT, and TED is free to search.

Two thresholds decide whether a contract even reaches TED. From 1 January 2026, supplies and services contracts cross the EU threshold at €140,000 for central government authorities and €216,000 for sub-central ones, under Commission Delegated Regulation (EU) 2025/2152 (thresholds page). Most software contracts are services, so those are the numbers that matter to you. Works sit far higher, at €5,404,000.

Below those figures, the contract is run under national rules and published on national portals instead. That is where a lot of the SME-sized IT work actually lives. Each member state runs its own: Germany has the eVergabe platforms and bund.de, France has BOAMP and the PLACE portal, Italy has the regional and national portals feeding into ANAC. If you only watch TED, you miss the contracts sized for a five-person shop.

A note for anyone with UK ambitions. Since Brexit, UK public contracts no longer publish to TED. They go to Find a Tender, the UK's own service for above-threshold notices. The shape of the process is similar, but it is a separate system with its own rules under the Procurement Act 2023. Treat it as a parallel market, not an extension of the EU one.

The practical move is not to refresh TED by hand. Set a saved search on the CPV codes that match your work and let it push notices to you. The software services branch alone is busy: software maintenance and repair services (CPV 72267000) carries 7,896 awards over TED 2009-2026, the most of any software-services sibling, and application software programming (CPV 72212000) carries 1,746. You want the relevant slice of that flowing past you automatically, not discovered late.

Reading a tender notice and its CPV codes

A notice is a structured document, and the structure tells you whether to bid before the prose does. Read it in this order: the CPV codes, the procedure type, the award criteria, the deadlines, then the spec. If any of the first four rule you out, you have saved yourself the spec.

Start with the CPV codes, because they tell you what the contracting authority thinks it is buying. Every notice carries a primary CPV code and often several secondary ones. The code is how the contract was classified, how it was found, and how it will be measured against history. A notice tagged application software programming (CPV 72212000) is a ground-up or enhancement build. One tagged software maintenance and repair services (CPV 72267000) is upkeep of something that already runs. Those are different contracts that reward different suppliers, and the code is the first signal of which one you are reading. Our companion guide, CPV 72000000: IT Services Explained, maps the whole IT-services branch if a code is unfamiliar.

The codes also reveal scope drift, which is where bids die quietly. A notice with application software programming as primary and software maintenance and repair services plus helpdesk services (CPV 72253100) as secondaries is not asking for code. It is asking you to build, run, and support a system for years. If your firm only builds, the secondary codes just told you to walk away or find a partner.

Watch the codes that look alike. Programming services of application software and software development services (CPV 72262000) describe much the same work at different altitudes, and bidders routinely arrive from both onto the same contract. A website build sits under web site design services (CPV 72413000), but the running and hosting of that site is a separate code, web site operation host services (CPV 72415000). If a notice carries both, the authority wants one supplier on the hook end to end.

Then read the procedure type. Open procedure means anyone can submit a bid. Restricted means there is a selection stage first, and you bid only if shortlisted. Competitive procedure with negotiation and competitive dialogue allow the spec to move during the process, which favours suppliers who can shape a solution rather than answer a fixed one. Each procedure has its own deadlines and its own rhythm. A restricted procedure for systems consultancy services (CPV 72246000) means your selection-stage paperwork, the part proving you are allowed to bid at all, matters as much as the eventual technical answer.

The award criteria are the scoreboard. Under the EU directives the award is always based on the most economically advantageous tender, or MEAT, but that term covers two routes. MEAT can be identified on price or cost alone, or, far more common for IT, on the best price-quality ratio, which weighs quality and price together using a published weighting. Member states are free to restrict or forbid awarding on price alone, and several do. The notice publishes the weighting. If quality is 70% and price 30%, the contract is winnable on capability. If price is 80%, a small firm with a strong method but a normal cost base is bidding uphill. Read the weighting before you read the spec, because it tells you whether your kind of firm can win this one.

Writing a winning bid

A winning bid answers the question the contracting authority asked, in the order it asked it, scored against the criteria it published. That sounds obvious. Most losing bids fail exactly there: they answer the question the supplier wished had been asked.

Respond to the specification point by point. Public authorities score against a rubric, and an evaluator who cannot find your answer to requirement 4.3 cannot award you the marks for it, however good the work would be. If the spec is numbered, mirror the numbering. If it lists must-haves and should-haves, address the must-haves first and explicitly. Make the evaluator's job easy and you make their score generous.

Write to the award criteria weighting, not to your own sense of what is interesting. If technical methodology is worth 40 points and team experience 30, the methodology section earns the most words and the most care. A common SME mistake is to pour energy into a polished company-background section that the rubric barely scores, then thin out the methodology the rubric rewards most. The weighting is published. Let it allocate your effort.

Under MEAT, quality is where a smaller supplier competes. The criteria for an IT contract usually reward a credible delivery method, named people with the right stack, a realistic plan for integrating with the authority's existing systems, and evidence you have shipped something comparable. On a contract tagged systems consultancy services, the signature on the architecture design carries the bid more than the size of your bench. On one tagged information systems planning services (CPV 72222200), the authority is paying for foresight it cannot staff in-house, so the bid that proves it has charted this exact route before beats the one that lists the most services.

Make every capability claim specific and provable. "We have extensive experience" scores nothing. "We delivered a case-management system for a regional authority of comparable size, live since 2023, integrated with their existing identity provider" scores, because an evaluator can map it to the requirement. Public-sector IT runs heavily on integration and on accessibility. A website bid under web site design services that demonstrates real WCAG accessibility compliance and names the open-source CMS platform it will use says more than one with a striking mockup.

Price to the contract you read, not to a headline number. On a recurring contract such as software maintenance and repair services, authorities weigh response times, named engineers, and a credible transition-in plan above the day rate. On a multi-seat helpdesk services deal, the disclosed values run from sub-€100k single-site desks to multi-million managed contracts (TED 2009-2026), so the seat count and coverage window set the size of the prize long before price does. Read those first, then price.

Last, leave time for the administrative pass. The European Single Procurement Document (ESPD), references, financial statements, and certificates are not where bids are won, but they are where bids are disqualified. A technically winning bid that misses a mandatory exclusion-grounds declaration does not get marked down. It gets rejected.

Common bid pitfalls

The pitfalls repeat across every IT contract on TED. Most are self-inflicted.

Bidding the wrong code mindset. A notice tagged software maintenance and repair services is steady, recurring, incumbency-sticky revenue, and the authority is wary of handing maintenance to a stranger. If you bid it as if it were a fresh build, you signal you have misread the contract. Match your pitch to what the code says the work is.

Ignoring the incumbent. Many IT contracts, especially maintenance, support, and helpdesk, renew with the firm already doing the work, because that firm knows the system's quirks and the escalation paths. Against an incumbent on software support services (CPV 72261000) or software maintenance and repair services, you compete on response times, named engineers, and a clean transition-in plan, not on being marginally cheaper. If you cannot articulate why switching to you is worth the authority's risk, you are not yet ready to bid.

Missing the questions window. Most procedures let bidders ask clarification questions, and the answers are published to all bidders. Suppliers who skip this give up free intelligence about what the authority actually wants. A well-aimed question can also surface an over-restrictive requirement the authority then relaxes for everyone.

Treating the spec as a wish list. A spec is a contract in waiting. Promising a feature you cannot deliver to win the bid creates a delivery problem you then own for years. Public authorities remember, and past performance follows you into the next evaluation.

Underestimating the administrative load. The selection-stage and exclusion-grounds paperwork is real work, and it has the same deadline as everything else. Firms that start it the day before the deadline lose bids to a missing certificate, not to a weak method.

SME advice: lots, frameworks, consortia

EU procurement rules were rewritten partly to let smaller suppliers in, and the mechanisms that do so are worth understanding before you decide a contract is too big.

Lots split a large contract into smaller pieces you can bid for separately. The EU directives push contracting authorities to divide contracts into lots or explain why they did not, precisely so an SME can win a slice without bidding the whole thing. Read the lotting structure first. A €4M framework you cannot deliver often contains a €300k lot you can. Bid the lot you can win, not the contract you cannot.

Framework agreements are the shape much public IT work takes, and they reward a two-stage strategy. A framework sets up a panel of approved suppliers, then individual work orders, the call-offs, get awarded against that panel later. Several of the contracts under systems consultancy services and web site design services are frameworks with call-offs. The implication for an SME is sequencing: getting onto the framework first is the gate, then you win the actual work against the other named suppliers. A framework place is not revenue. It is the right to compete for revenue, and you plan for both stages.

Consortia and subcontracting let you bid work larger than your firm. If a notice carries primary and secondary codes spanning build, run, and support, no single small supplier covers all of it, but a consortium can. Pair a build shop strong on application software programming with a managed-service firm strong on helpdesk services, and the combined bid covers a scope neither could win alone. The rules let you rely on the capacity and references of other entities, including consortium partners and subcontractors, to meet the selection criteria. That is the formal route by which a small firm bids a large contract.

Use the proportionate-requirements rule. Selection criteria, such as minimum turnover, must be proportionate to the contract. An authority generally cannot demand a turnover more than twice the contract value without justification. If a requirement looks designed to exclude smaller firms, the clarification-questions window is where you challenge it, and the answer goes to every bidder.

One honest caveat. The mechanisms above are real and they favour you, but they are also the parts of the rules most likely to vary by member state and by how a given authority drafts its notice. The EU directives set the floor. National transposition and the specific contract notice set the detail. Read the notice's own terms as the binding version, and treat the general rules here as the starting frame, not the final word on any single tender.

Commonly confused codes for bidders

Bidders lose time, and sometimes lose bids, by misreading which code a contract really sits under. These are the pairs that trip suppliers most often when deciding whether a notice fits.

A few more codes worth a saved search if your work touches them: web server software package (CPV 48222000) for product-side web infrastructure, web server software development services (CPV 72212222) for the build of it, technical computer support services (CPV 72611000) for on-site technical support, and system implementation planning services (CPV 72224100) for the planning that precedes a rollout.

How do I start bidding for government contracts in the EU?
Register on TED and the national portal of any country you want to work in, set saved searches on the CPV codes that match your work, and read three or four full notices end to end before you bid your first one. The first bid is mostly about learning the structure. Pick a contract sized to your firm, ideally a single lot, and treat it as practice that can also win.

What is MEAT in a tender?
MEAT is the most economically advantageous tender, the basis every EU award is made on. It comes in two forms: price or cost alone, or the best price-quality ratio that weighs quality and price together using a published weighting. The price-quality-ratio form is the usual case for IT, and it is the one the rest of this guide assumes. The weighting tells you whether a contract is winnable on capability. Read it before you commit to bidding.

Do small companies actually win EU public IT contracts?
Yes, and the rules are written to help. Lots split large contracts into smaller pieces, frameworks let you compete for call-offs once you are on the panel, and consortia let you bid scope larger than your firm by combining with partners. The internal data backs the pattern: under helpdesk services, disclosed award values run from under €100k to several million (TED 2009-2026), so a real share of the work is SME-sized.

Should I bid against the incumbent supplier?
Only if you can name why switching to you is worth the authority's risk. On maintenance, support, and helpdesk contracts the incumbent has a real edge, because it already knows the system. Compete on response times, named engineers, and a clean transition-in plan. If your only argument is a slightly lower price, the answer is usually no.

How do I know which CPV code a tender uses, and does it matter to my bid?
The notice publishes its CPV codes directly, primary and secondary. They matter because they tell you what the contracting authority thinks it is buying, which suppliers you are competing against, and whether the scope reaches beyond what your firm does. Read the codes first. If you are unsure what one means, the IT services guide breaks down the 72-branch, our complete guide to EU IT tenders covers the whole picture from both sides of the table, and the guide for IT procurement officers shows how the people scoring your bid think about the same codes.

About the author. Babar Al-Amin builds TenderCodes and runs BrotCode UG (LinkedIn), a Berlin Rails consultancy. He has bid on EU public IT contracts from the supplier side, which is the lens this guide is written through, and writes more on his own LinkedIn. More on who is behind this and how it is maintained on the About page.

Last reviewed: 13 June 2026.

If you build software and want the relevant tenders to find you instead of the other way round, subscribe to alerts for the CPV codes that match your work. It is free, and it is the saved search this whole guide tells you to set.