How to Win Public Tenders — A Guide for IT Companies

Public procurement in Poland is worth more than PLN 280 billion a year. The IT sector accounts for 15–20% of that amount — meaning PLN 42 to 56 billion flows through PZP procedures toward technology firms. And yet most Polish software houses, integrators and implementation companies do not even try to bid in public tenders.

Why? Because of “bureaucracy”, because of “JEDZ”, because of “the bid bond”, because of “impossible deadlines”. That is true — the barrier to entry is higher than in B2B sales. But that is exactly why competition is thinner. And the contracts — larger, more stable and more predictable financially.

In this guide we show, step by step, how to win public IT tenders in 2026. From bid/no-bid strategy, through the structure of a winning bid, to the most common mistakes and the tools that automate the whole process. No generalities — with tables, numbers and concrete tricks from the public procurement market.

Public IT Tenders — Why They Are Worth It (and Why Firms Are Afraid)

The public procurement market in numbers

Poland’s public procurement market is one of the largest in Central Europe. According to the Public Procurement Office, the value of contracts awarded in 2025 exceeded PLN 280 billion. The IT sector — covering hardware supply, licences, system implementations, infrastructure maintenance and advisory services — is a stable 15–20% of that pie.

What does that mean in practice? PLN 42 to 56 billion a year reaches IT firms through public procurement procedures. These are not small jobs — the average IT tender above EU thresholds exceeds PLN 2 million. And the contracting authority is not a startup that may vanish after a quarter — it is ministries, marshal offices, hospitals, universities and State Treasury companies.

Barriers to entry — real, but overstated

IT firms avoid public tenders for several reasons:

Formal bureaucracy — tender documentation can run to 200+ pages. SWZ, OPZ, draft contracts, bid forms, declarations — the volume alone puts people off.
JEDZ (Jednolity Europejski Dokument Zamówienia / ESPD) — a form that requires precise information about the company, experience, staff and the absence of exclusion grounds. One error = rejection.
Bid bond (wadium) — in tenders above EU thresholds the required bond reaches 1–3% of the contract value. On a PLN 5 million contract that is PLN 50–150 thousand frozen for the duration of the procedure.
Deadlines — from publication of the notice to bid submission it is often 35–45 days. Sounds like a lot, but with a complex OPZ and the need to gather references — it is a sprint.
Digitisation — e-Zamówienia platforms, miniPortal, qualified signatures — each of these technologies is a potential failure point at the last minute.

The opportunity hidden in the difficulty

The paradox: those barriers are your advantage. In a typical B2B tender for an ERP system you compete with 15–30 firms. In a public tender of analogous scope? On average 3–5 bids. Why? Because most IT firms do not want to “struggle with PZP”.

That means that if you master the process — you win more often, at higher margins, with a predictable revenue pipeline quarters ahead. A public contracting authority does not renegotiate the price after the fact, does not change the scope without an annex, does not disappear from the market — it pays according to the schedule and the contract.

Anatomy of an IT Tender — From Notice to Contract Signature

Before you start submitting bids, you need to understand the full tender lifecycle. Each stage carries specific tasks and traps. Below we break a standard IT tender (open procedure above EU thresholds) into first principles.

Tender process timeline

Stage	Duration	What you do	What to watch
Notice in BZP/TED	Day 0	Identify the tender, download the documentation	Bid submission deadline — write it down immediately
SWZ/OPZ analysis	Days 1–7	Read the conditions, requirements, evaluation criteria	Participation conditions — do you meet them?
Questions to the contracting authority	Days 7–21	Ask questions, wait for answers/modifications	Answers change the SWZ — monitor daily
Bid/no-bid decision	Days 7–14	Internal scoring, preliminary calculation	Do not bid “as a trial” — cost the bid
Bid preparation	Days 14–35	Pricing, documents, references, JEDZ, bid bond	Qualified signature, file format (PDF/XML)
Bid submission	Day 35–45	Upload to the e-Zamówienia platform	Do not wait until the last hour — platform outages
Bid opening	Submission day	Check the opening protocol	Compare your price with the competition
Bid evaluation	14–60 days	Wait, possibly supplement documents	Requests for clarification — reply immediately
Result announcement	After evaluation	Analyse the result, check the scoring	Appeal deadline: 10 days (above EU thresholds)
Appeal to KIO	10 days from the result	Decision: appeal or accept	Filing fee + lawyer — is it worth it?
Contract signature	After standstill	Sign the contract, start the project	Performance security (5–10% of value)

Key dates to remember

The whole process — from notice to contract signature — typically lasts 2 to 4 months. In tenders with appeals to KIO it can stretch to 6+ months. That is why a tender pipeline requires planning at least a quarter ahead.

Bid/No-Bid Strategy — How to Choose Tenders Wisely

The biggest mistake firms make when entering public procurement? Bidding on everything that looks “more or less a fit”. The cost of preparing one IT tender bid is PLN 5,000 to 25,000 (team time + bid bond + any guarantees). At a 15–20% win rate that means that for every won bid you “burn” 4–6 losses. The maths is brutal — you have to choose wisely.

5 bid/no-bid evaluation criteria

Before you decide to bid, score the tender on five dimensions:

1. Contract value vs. bid cost Does the potential profit justify the investment in preparing the bid? A PLN 200 thousand tender at a bid cost of PLN 15 thousand and a 10% margin yields a potential profit of PLN 20 thousand — at a 20% chance of winning the expected value is PLN 4 thousand. Negative.

2. Competence fit Does your firm actually have experience in the required scope? The contracting authority wants a HIS system implemented in a hospital — have you done that before, or is it “we’ll definitely manage”? The references required in the SWZ do not lie.

3. Contracting authority history Does this contracting authority publish tenders regularly? Do you know its specifics? A first bid to a new contracting authority is an investment in a relationship — but you have to calculate that consciously. A contracting authority with repeatable orders (e.g. system maintenance on 3-year cycles) is gold.

4. Known competition Do you know who else will bid? If in the previous tender of this contracting authority a large integrator won at a price 40% below yours — think twice.

5. Potential margin At a realistic cost calculation (not an “optimistic” one) is there a margin that justifies the risk? Remember the cost of performance security, guarantee costs and the risk of contractual penalties.

Scoring: a weighted assessment of factors

Instead of deciding “on gut feel”, use simple scoring:

Criterion	Weight	Scale 1–5	Weighted points
Value vs. bid cost	25%	?	?
Competence fit	30%	?	?
Contracting authority history	15%	?	?
Competition	15%	?	?
Margin	15%	?	?
TOTAL	100%	—	?/5.0

Rule of thumb: Scoring below 3.0 = do not bid. Scoring 3.0–3.5 = bid only if you have spare capacity. Scoring above 3.5 = priority.

Firms with the highest win rate in public tenders (30–40%) submit fewer bids, but better chosen ones. The key metric is not “how many we submitted”, but “how many we won ÷ how many we submitted × value of wins”. Concentrate resources where scoring shows a real chance — and let the rest of the tenders go without regret.

How to Write a Bid That Wins (Structure and Tricks)

Once you have decided “bid” — it is time to prepare a bid that will collect the maximum points. In IT tenders evaluation criteria usually split into price and non-price. A typical split is 60% price + 40% quality criteria — but there are tenders where the weight of price is only 40%.

How does price scoring work?

The formula is simple and unchanging:

Points for price = (lowest price ÷ your price) × criterion weight × 100

If the lowest bid is PLN 1,000,000, yours is PLN 1,200,000, and the weight of price is 60% — you get: (1,000,000 ÷ 1,200,000) × 60 = 50 points (instead of a max of 60). You lose 10 points.

Conclusion: You do not have to have the lowest price — you have to make up the difference with non-price points. If on non-price criteria you score 38/40 points and the cheapest competitor only 25/40 — you win despite a higher price.

Presenting experience — references and case studies

Contracting authorities demand proof of experience — typically 2–3 projects of similar scope and value completed in the last 3–5 years. Key rules:

Format references exactly according to the SWZ template — if the contracting authority provides a table, fill it column by column. Extra columns or a changed layout is a rejection risk.
Give concrete figures — not “a large implementation project”, but “ERP implementation for 450 users, value PLN 2.3 million, completed 2024-11”.
References must confirm the required scope — if the SWZ requires “implementation of an ERP-class system in a public body employing min. 200 people” — your reference must meet those conditions literally.

Delivery schedule — realistic, not ambitious

Many contracting authorities score a shorter delivery time. It is tempting to promise 4 months instead of 6 to pick up extra points. But beware:

An unrealistic schedule means contractual penalties for delay (typically 0.1–0.5% of contract value per day).
Contracting authorities check realism — if your schedule is glaringly short relative to the scope, they may request clarification.
Better to give up 2–3 points for a longer deadline than risk losses of hundreds of thousands of zloty in penalties.

Project team — CVs with names, surnames and certificates

In IT tenders contracting authorities regularly require key personnel to be named. This is not a formality — those people must actually deliver the project, and changing them requires the contracting authority’s consent.

Name real people — not “we plan to hire a project manager with a PMP certificate”. Point to Jan Kowalski with PMP certificate no. 1234567.
Certificates must be current — PMP, PRINCE2, ITIL, vendor certificates (Microsoft, Oracle, SAP) — check expiry dates.
Team experience = points — the more years and projects you can document for the named people, the better. One sentence “15 years of experience” is less than a list of 5 concrete projects with dates and scopes.

7 Mistakes That Cost Contracts (and How to Avoid Them)

Based on an analysis of more than 1,400,000 historical tenders in the BudOS database we identify seven of the most common causes of lost and rejected bids in the IT sector.

1. Not reading the SWZ — formal exclusion

Problem: The contracting authority requires experience in “a minimum of 3 projects each worth no less than PLN 500,000” — and you submit 2 projects of PLN 800,000 each. Combined value higher, but formally you do not meet the “minimum of 3” condition.

Solution: Read the SWZ with a pencil in hand. Underline every quantitative condition. Make a checklist and tick point by point. One person reads, a second verifies — always in a pair.

2. Price too low — suspicion of an abnormally low price

Problem: You want to win on price and submit a bid 30% below the estimated contract value. The contracting authority requests explanations of an abnormally low price. You cannot prove that you will perform the contract for that amount without a loss.

Solution: If your price is 30%+ below the estimated value (or below the average of the remaining bids) — prepare a detailed calculation in advance. Show: personnel costs, overhead, hardware, licences, subcontractors. “Because we have low overheads” is not enough.

3. References not in the required format

Problem: You have the experience, but the references are a letter of recommendation from a client — and the contracting authority requires a completed list of services according to the template in annex 5 to the SWZ plus confirming evidence (acceptance protocols or references).

Solution: Prepare a “reference bank” — standardised project descriptions with all the data (contracting authority name, value, dates, scope, contact persons). Update it after every completed project. When a tender appears — you match from the bank, you do not scramble in a panic.

4. Missing the submission deadline

Problem: The bid is ready, but the e-Zamówienia platform refuses to accept the file at 11:57 — because the file weighs 150 MB and the upload on the office connection takes 8 minutes. Deadline: 12:00. Game over.

Solution: Submit the bid a minimum of 24 hours before the deadline. Not the day before — not “in the morning on the day” — a full 24 hours earlier. Technical problems with platforms happen and the contracting authority does not take them into account.

5. Incorrectly completed JEDZ

Problem: JEDZ (European Single Procurement Document) is an XML/PDF form in which you declare that you meet the conditions and that there are no grounds for exclusion. One checkbox filled in literally as “No” instead of “Yes” in the experience section = a request to supplement or rejection.

Solution: Complete the JEDZ on the ESPD platform (espd.uzp.gov.pl). Check it three times. Prepare a template JEDZ for your firm — updated quarterly — which you copy and adapt to the specific tender.

6. Missing bid bond or guarantee

Problem: The bid-bond transfer leaves the company account the day before the deadline — but settlement takes 2 business days (Friday → Monday?). At bid opening the bond is not on the contracting authority’s account. Bid rejected — no discussion.

Solution: A bank or insurance guarantee instead of a transfer — you submit it electronically with the bid, zero risk of banking delays. The cost of a bid-bond guarantee is 0.5–2% of the bond amount — for a PLN 5 million tender that is PLN 250–1,500. Worth it.

7. Ignoring contracting authority questions (SWZ modifications)

Problem: Another contractor asked a question, the contracting authority changed the OPZ — and you did not check the answers. Your bid is prepared against the old version of the requirements. You do not meet the new condition.

Solution: Monitor the e-Zamówienia platform every day until the bid submission deadline. Answers to questions can modify: deadlines, scope, technical requirements, evaluation criteria. Every modification is a potential change in your bid.

Non-Price Criteria — How to Score Maximum Points

In IT tenders non-price criteria are often the only way to win despite a higher price. Contracting authorities are increasingly aware that “cheapest” does not mean “best” — which is why the weight of quality criteria is rising. In 2026 typical non-price criteria in IT cover the following areas.

Typical non-price criteria in IT tenders

Criterion	Typical weight	How to score max points
Team experience	10–20%	Name people with the strongest track record; concrete projects, dates, scopes
Delivery time	5–15%	Propose a realistic but ambitious deadline; do not cut “for the sake of it”
Warranty period	5–10%	Offer a longer warranty (e.g. 36 months vs. the required min. 24 months)
SLA / response time	5–15%	Concrete parameters: response in 2h, fix in 8h, availability 99.5%
Delivery methodology	5–15%	Describe the approach (Agile/Scrum adapted to the public sector)
Delivery concept	10–20%	Prepare a detailed technical description that goes beyond the minimum
Training	3–10%	More training hours, broader scope, e-learning included

How to describe team experience — specifics beat generalities

Contracting authorities award points for the experience of key personnel. The difference between 0 and maximum points is the quality of the description:

Weak (2/10 points): “Project manager — 10 years of IT experience, delivered implementation projects.”

Strong (8/10 points): “Project manager Jan Nowak — PMP certificate (no. 2345678, valid until 2027-12), PRINCE2 Practitioner certificate. Experience: (1) Implementation of the enova365 ERP system for the City of Wrocław, 350 users, value PLN 1.8 million, 2023–2024; (2) Migration of Clinical Hospital No. 4 IT infrastructure to Azure cloud, 120 VMs, value PLN 950 thousand, 2024; (3) Build of an e-services platform for the Kraków County Office, 45,000 residents, value PLN 2.1 million, 2024–2025.”

See the difference? Specifics — dates, values, scopes, contracting authority names — build credibility and give the contracting authority a basis to award the maximum number of points. A generality does not give them that option even if they want to.

Delivery concept — your edge over “form fillers”

Some tenders require a “description of the method of performing the contract” or a “technical concept”. This is a criterion where large firms insert generic text on autopilot — and smaller, more engaged teams can gain an advantage.

Prepare a description that:

Refers to the contracting authority’s specifics (not a generic “implementation plan”)
Shows knowledge of its infrastructure (if the information is in the OPZ)
Proposes solutions to problems described in the documentation
Contains a concrete schedule with milestones and deliverables
Describes risk management specific to this project

Appeals to KIO — When Is It Worth It?

The National Appeal Chamber (Krajowa Izba Odwoławcza, KIO) is the body that hears appeals against contracting authority decisions in public tenders. An appeal is a serious decision — it costs money, time and the relationship with the contracting authority. But sometimes it is the only way to defend your rights.

Typical grounds for appeal

The most common reasons for filing appeals in IT tenders:

Incorrect bid evaluation — the contracting authority miscounted points, did not apply the criteria in line with the SWZ or omitted your documents.
Defective description of the subject-matter — the OPZ is written “for a specific contractor” (e.g. it requires a certificate of manufacturer X that only one firm in Poland holds).
Unjustified rejection of the bid — the contracting authority decided you do not meet a condition, even though your documents confirm it.
Incorrect request for clarification — the contracting authority did not give you a chance to supplement formal gaps, even though PZP requires it.
Failure to reject a competitor’s bid — the competitor does not meet the conditions, but the contracting authority did not notice or ignored it.

Cost of an appeal to KIO

Item	Cost
Appeal filing fee (below EU thresholds)	PLN 7,500
Appeal filing fee (above EU thresholds, supplies/services)	PLN 15,000
Appeal filing fee (above EU thresholds, works)	PLN 20,000
Lawyer specialising in PZP	PLN 5,000–15,000
Time to prepare	5–10 team working days
Total cost of an appeal	PLN 12,500–35,000

Statistics — is it worth it?

According to KIO data for 2025, around 35% of appeals are upheld (in whole or in part). That means every third appeal ends in success. But beware — that statistic covers appeals prepared by professionals. “Amateur” appeals written without a lawyer have a win rate closer to 10–15%.

When an appeal pays off:

The contract value is high (min. PLN 500 thousand) — the cost of the appeal is a fraction of the potential profit.
You have strong legal grounds — not “I think so”, but a concrete breach of PZP provisions.
The point difference is small — e.g. you lost by 2 points on a contested criterion.
The contracting authority made an evident arithmetic or procedural error.

When to let it go:

You lost by 20+ points — even if one criterion was scored wrongly, a correction will not change the result.
You have no hard evidence — “I feel something is off” is not enough.
You care about the relationship with the contracting authority — an appeal does not build trust (though legally it cannot result in discrimination in future tenders).

How Technology Helps You Win (Monitoring + Scoring + Automation)

In 2026, IT firms that still monitor tenders “manually” — browsing BZP, TED and contracting authority platforms — waste time and miss opportunities. Three pillars of technological support for the bidding process change the rules of the game.

Notice monitoring — you never miss a deadline

The problem: more than 800 notices a day are published in BZP. TED adds hundreds more from the EU. Manual filtering takes 1–2 hours a day and is error-prone.

The solution: automatic monitoring with alerts. The system scans all notice sources, filters by industry, value, location and keywords — and delivers a ready list of tenders matching your profile. Every day, without delay, without omissions.

What you gain:

Zero missed deadlines — push alerts on new notices and approaching deadlines.
Early detection of tenders — the earlier you know, the more time to prepare.
Monitoring of answers to questions and SWZ modifications — automatically, without checking the platform every day.

AI scoring — you bid where you have a chance

Manual bid/no-bid assessment is 2–4 hours per tender (SWZ analysis, contracting authority history, competition assessment). At 30 tenders a month to assess — that is a full-time job for one person.

AI scoring analyses the tender in the context of your firm — competences, experience, historical win rate with similar contracting authorities, competitor activity — and in seconds returns a score: “78% chance — bid” or “12% chance — skip”.

BudOS analyses 1.4 million historical tenders so that every bid/no-bid recommendation is based on data, not intuition. The algorithm takes into account:

Your firm’s history of wins and losses
The contracting authority’s profile (how it scored in the past, what weights it used)
Competitor activity (who bid with this contracting authority)
Fit of requirements to your references and certificates
Price patterns (which prices won historically)

Document automation — faster and without errors

Preparing a tender bid is 60% repetitive work: filling in forms, assembling annexes, formatting CVs, generating JEDZ, preparing lists of services. Automating those elements means:

JEDZ generated automatically from current company data — without filling it in by hand every time.
Reference bank with intelligent matching — the system suggests which projects best fit the requirements of a specific tender.
Document templates adapted to the contracting authority’s requirements — the bid form, list of services, list of persons fill themselves from the database.
Completeness check — the system verifies that all required annexes are attached before the bid is sent.

The effect? Bid preparation time drops from 40–80 working hours to 15–30. Risk of formal errors — from 15–20% to below 3%. And your team can prepare more bids in the same time — but only those with high scoring.

FAQ — Frequently Asked Questions

Can a small IT firm (10–20 people) win public tenders?

Yes — and more often than you think. Many IT tenders are worth PLN 200–800 thousand, where large corporations do not bid (the contract is too small) and smaller firms with the right experience have a real chance. The key: you must have references in the required scope and value. If you do not — start with smaller contracts (below PLN 130 thousand net, basic procedure) and build a portfolio.

How much does it cost to prepare one IT tender bid?

The real internal cost (team time) is PLN 5,000–25,000, depending on tender complexity. On top of that comes the bid bond (frozen for the duration of the procedure, returned after award) and any bid-bond guarantee fees (0.5–2% of the bond amount). For tenders that require a site visit or a prototype — the cost can be higher.

How long does the whole process take from notice to contract signature?

Typically 2–4 months. Open tender above EU thresholds: a minimum of 35 days for bid submission + 30–60 days for evaluation + 10 days standstill + contract signature. If someone files an appeal with KIO — add 2–6 weeks. In the basic procedure (below thresholds) it can be faster: 1.5–2.5 months.

Is a consortium worth it?

A consortium makes sense when you cannot meet the participation conditions on your own (e.g. you lack references in one area and a partner has them). Caution: a consortium complicates delivery (joint and several liability, task split, settlements) and requires a consortium agreement — prepare it before you submit the bid. Do not form a consortium for the sake of it — if you meet the conditions yourself, bid alone.

Which electronic platforms are required to submit bids?

Since 2021 all public tenders in Poland are run electronically. The main platform is e-Zamówienia (ezamowienia.gov.pl) — notices are published there and bids are submitted there. Some contracting authorities use commercial platforms (Marketplanet, Logintrade, SmartPZP). You need: a qualified electronic signature (e-ID or a commercial certificate), a Trusted Profile and an account on the relevant platform. Test uploading dummy files before a real submission — technical problems are not an excuse contracting authorities accept.

Summary — From Knowledge to Won Contracts

Winning public IT tenders does not require magic — it requires a system. Firms that consistently win contracts from the public sector do three things differently:

They choose wisely — they do not bid on everything, but concentrate resources where scoring shows a real chance (bid/no-bid based on data, not intuition).
They prepare without errors — every document checked, every criterion addressed, every deadline met. Zero formal errors = zero lost chances.
They maximise non-price points — concrete descriptions of experience, realistic schedules, a strong team with certificates. They win on quality, not only on price.

Technology — notice monitoring, AI scoring and document automation — is a multiplier that lets you do those three things faster, cheaper and more effectively. Instead of one person browsing BZP for 2 hours a day — an algorithm scanning 800+ notices in seconds. Instead of “feeling” at bid/no-bid — scoring based on 1.4 million historical tenders. Instead of filling in JEDZ by hand for the twentieth time — automation that eliminates human error.

The public IT procurement market in Poland is PLN 42–56 billion a year. The contracts are large, stable and predictable. Competition — thinner than in B2B. The only barrier is knowledge and process. Now you have both.

Want to see how AI scoring and automation look in practice for your firm? Book a BudOS demo — we will show which tenders from the last month you had the best chance of winning and how much time you will save on bid preparation.

Book a call →