European governments buy software through public procurement. For a SaaS company, that means the buyer must define the requirement, publish the evaluation method and apply the same rules to every bidder.
This preview explains the two decisions that matter first: when to approach the buyer and whether a published tender is worth pursuing. The full 22-page guide covers procurement routes, qualification evidence, pricing formulas, contract risk and first-reference strategies in detail.
Start before the contract notice is published
A public software contract is shaped before bidding begins. The authority decides the scope, requirements and evaluation criteria during procurement planning. Once the contract notice is live, material changes may require the authority to extend the deadline or restart the procedure.
EU procurement law allows authorities to consult suppliers before launching a competition. Article 40 of Directive 2014/24/EU permits preliminary market consultations, including advice from suppliers and independent experts. Taking part does not prevent a company from bidding later. Under Article 41, the authority must instead take proportionate steps to prevent an unfair advantage, usually by sharing relevant information with all bidders and allowing enough time for responses.
For suppliers, three early signals are useful:
- Preliminary market consultations show that requirements are still being tested.
- Prior information notices announce planned purchases and may allow a shorter tender period later.
- Expiring contracts and frameworks indicate when an established category is likely to reopen.
Early engagement should help the authority understand the market, not attempt to secure favourable wording. Explain what the product can do, which requirements would unnecessarily restrict competition and how implementation, security, accessibility and data portability can be tested objectively.
After publication, the task changes. Read the full procurement documents, use the formal clarification channel and assume that every substantive answer will be shared with the other bidders.
Qualify the tender before writing the bid
The contract value alone does not show whether a tender is a good fit. Check the conditions that can exclude the company or make delivery uneconomic before assigning a bid team.
- Can the company pass the selection criteria? These may cover turnover, financial standing, reference deliveries and professional capability. Article 58 normally limits a minimum annual turnover requirement to twice the estimated contract value unless a higher level is justified by specific risks.
- Is the notice for a contract, framework agreement or dynamic purchasing system? A framework can close the supplier list for up to four years. A dynamic purchasing system remains open to suppliers that meet its admission criteria.
- Can the company accept the draft contract? Review liability, service levels, security duties, data location, intellectual property, indexation, exit support and option years before pricing the offer.
- How are price and quality scored? Use the published formula to model realistic competitor prices. The same nominal price weighting can produce very different results under ratio and linear scoring models.
- Can every required document be submitted on time? In an open procedure, the standard EU minimum is 35 days from dispatch of the notice. Electronic submissions can reduce it to 30 days, and some procedures can use 15 days where the legal conditions are met.
From 1 January 2026, Directive 2014/24/EU applies to supplies and services worth at least EUR 140,000 for central government authorities and EUR 216,000 for sub-central authorities. The threshold for social and other specific services is EUR 750,000. Contracts below these figures remain subject to national procurement rules and can be a practical route to a first public reference.
A bid should proceed only when the company can pass the mandatory requirements, deliver the contract on acceptable terms and achieve a credible score. Product quality cannot cure a missing reference, an unacceptable contract term or a document submitted after the deadline.
The full guide continues with the evidence pack a software supplier should maintain, the main procurement vehicles, worked price-scoring examples, routes to a first public reference and ten questions for a bid/no-bid decision.
Sources
- Directive 2014/24/EU on public procurement, in particular Articles 27, 33, 34, 40, 41, 58 and 67.
- Commission Delegated Regulation (EU) 2025/2152, setting the Directive 2014/24/EU thresholds for 2026–2027.
- Directive 2007/66/EC, on review procedures and the standstill period.
- Regulation (EU) 2016/7, establishing the European Single Procurement Document.
- Directive (EU) 2016/2102, on accessibility of public-sector websites and mobile applications.




