Software Development Government Tenders in Estonia

How custom software is specified, bought and handed over

Bespoke software is bought as a delivery capability rather than as a product, and the tender documents that matter are rarely the functional requirements. They are the schedules covering intellectual property, source code and exit. Public buyers in this category normally require assignment of the code they pay for, or a licence broad enough to let another supplier maintain it, together with documented handover and a transition period at the end of the term. A bidder proposing a proprietary platform the buyer cannot leave is answering a different question from the one asked.

The delivery structure has converged on phased, incremental work: a discovery or inception phase that is separately priced and separately assessed, then build phases that can be stopped at defined points. Pricing is commonly a capped rate card by role rather than a fixed price for a fixed specification, because the specification is expected to change. That places weight on the rates themselves and on the blend of seniority a bidder proposes, and it is why these competitions frequently include a worked scenario or a technical assessment instead of relying on references alone.

Three compliance requirements sit outside the code and sink otherwise strong bids. Accessibility conformance is generally mandatory for anything citizen-facing and is tested on delivery, not promised at bid. Independent security testing before go-live, with remediation at the supplier's cost, is standard. And hosting, data residency and the separation between the development supplier and the operating environment are usually fixed by the buyer rather than proposed by the bidder. Suppliers who treat these as boilerplate discover at contract signature that they have priced none of them.

This section describes how this category is bought generally, across the public buyers that publish it. The figures elsewhere on this page are measured for this market alone.

Who buys software development in Estonia?

GlobalGov holds 756 software development records from 85 distinct buying organisations in Estonia. The most frequent publishers are Siseministeeriumi infotehnoloogia- ja arenduskeskus (70 records); Tervise ja Heaolu Infosüsteemide Keskus (44 records); Riigi Infosüsteemi Amet (39 records); Rahandusministeeriumi Infotehnoloogiakeskus (37 records); Keskkonnaministeeriumi Infotehnoloogiakeskus (35 records); Tallinna Tehnikaülikool (31 records). Between them the 6 largest account for 34% of everything published, so buying here is spread across many separate authorities.

What are software development contracts worth in Estonia?

547 of the 756 records publish a contract value. The median is $648,000 and the largest single published value is $648.0M. By size, 12 under $100k, 319 between $100k and $1M, 185 between $1M and $10M, 31 above $10M. The remaining 209 publish no value at all, so every figure here describes the priced subset only, and values are as stated by the buyer rather than as finally awarded.

How long do bidders get to respond to software development tenders in Estonia?

Across the 348 Estonia software development notices that publish both a publication date and a closing date, the median response window is 33 days. A quarter of them allowed 31 days or fewer and a quarter stayed open for more than 35. Short turnarounds are the exception rather than the rule here: only 2 (0.6%) closed within a fortnight of being published.

How often are software development tenders published in Estonia?

Estonia publishes about 8 notices a month in this category, 99 in the last twelve months. That is 24% fewer than the 131 published in the twelve months before that. Over the last three years there were 369, spread across 59 separate months of activity since 29 June 2016. February is historically the busiest month. The most recent was published 8 September 2026.

How does Estonia compare with other software development markets?

Among the 50 countries where GlobalGov holds a comparable software development market, Estonia ranks 23rd by number of records. The largest is Germany (7,606 records against 756 here). Within Estonia itself, software development is the 2nd largest of the 41 procurement categories tracked here.

Where do the Estonia software development records on this page come from?

These 756 records are collected from 1 official source: TED (756). GlobalGov is an independent aggregator and is not affiliated with any of them; each record links back to the notice on its issuing portal. The set is rebuilt nightly, and the counts on this page were taken on 2026-10-01.

Open Software Development tenders in Estonia

Showing 9 of the 9 notices open in this category today. Openness uses the same definition as the Estonia market page: active, not marked awarded, cancelled, closed or expired, and either closing in the future or published within the last 90 days with no stated closing date.

Other procurement categories in Estonia

Software Development procurement in other markets