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 Kenya?
GlobalGov holds 1,592 software development records from 338 distinct buying organisations in Kenya. The most frequent publishers are Central Bank Of Kenya (46 records); Kenya Electricity Generating Company (34 records); Communications Authority Of Kenya (22 records); Kenya National Highway Authority (21 records); Kenya Revenue Authority (20 records); Unclaimed Financial Assets Authority (20 records). Between them the 6 largest account for 10% of everything published, so buying here is spread across many separate authorities.
| Buying organisation | Records | Share |
|---|---|---|
| Central Bank Of Kenya | 46 | 2.9% |
| Kenya Electricity Generating Company | 34 | 2.1% |
| Communications Authority Of Kenya | 22 | 1.4% |
| Kenya National Highway Authority | 21 | 1.3% |
| Kenya Revenue Authority | 20 | 1.3% |
| Unclaimed Financial Assets Authority | 20 | 1.3% |
How long do bidders get to respond to software development tenders in Kenya?
Across the 737 Kenya software development notices that publish both a publication date and a closing date, the median response window is 13 days. A quarter of them allowed 9 days or fewer and a quarter stayed open for more than 16. 440 of them (60%) closed within a fortnight of being published, so on this market a bidder who reviews notices once a week can lose most of the response window before reading one.
How often are software development tenders published in Kenya?
Kenya publishes about 7 notices a month in this category, 87 in the last twelve months. That is 74% fewer than the 333 published in the twelve months before that. Over the last three years there were 764, spread across 91 separate months of activity since 2 August 2018. March is historically the busiest month. No new notice has been published in this category since 26 June 2026, 97 days ago, so treat the figures above as a record of the market rather than as this week's pipeline.
How does Kenya compare with other software development markets?
Among the 50 countries where GlobalGov holds a comparable software development market, Kenya ranks 14th by number of records. The largest is Germany (7,606 records against 1,592 here). Within Kenya itself, software development is the 18th largest of the 83 procurement categories tracked here.
Where do the Kenya software development records on this page come from?
These 1,592 records are collected from 3 official sources: the Kenya PPRA (1,587), the World Bank (4), UN Global Marketplace (1). 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 Kenya
No individual notice in this category currently has a public record page. The market figures above are computed over all 1,592 records GlobalGov holds for it.
Other procurement categories in Kenya
Software Development procurement in other markets
Never Miss a Kenya Government Contract
Finding Kenya tenders usually means a local portal, a local registration and someone who reads the language. Get an alert you can read when a new software development opportunity is published there.
Start Free Trial