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 license 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 South Africa?
GlobalGov holds 807 software development records from 232 distinct buying organizations in South Africa. The most frequent publishers are Eskom (27 records); Council for Scientific and Industrial Research (CSIR) (22 records); State Information Technology Agency (16 records); Stellenbosch Municipality (15 records); State Information Technology Agency (13 records); Eskom (12 records). Between them the 6 largest account for 13% of everything published, so buying here is spread across many separate authorities.
| Buying organization | Records | Share |
|---|---|---|
| Eskom | 27 | 3.3% |
| Council for Scientific and Industrial Research (CSIR) | 22 | 2.7% |
| State Information Technology Agency | 16 | 2.0% |
| Stellenbosch Municipality | 15 | 1.9% |
| State Information Technology Agency | 13 | 1.6% |
| Eskom | 12 | 1.5% |
How long do bidders get to respond to software development tenders in South Africa?
Across the 797 South Africa software development notices that publish both a publication date and a closing date, the median response window is 24 days. A quarter of them allowed 15 days or fewer and a quarter stayed open for more than 31. 255 of them (32%) 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 South Africa?
South Africa publishes about 30 notices a month in this category, 361 in the last twelve months. That is 247% more than the 104 published in the twelve months before that. Over the last three years there were 558, spread across 59 separate months of activity since 12 February 2017. May is historically the busiest month. The most recent was published 1 November 2026.
How does South Africa compare with other software development markets?
Among the 56 countries where GlobalGov holds a comparable software development market, South Africa ranks 33rd by number of records. The largest is Germany (15,580 records against 807 here). Within South Africa itself, software development is the 8th largest of the 66 procurement categories tracked here.
Where do the South Africa software development records on this page come from?
These 807 records are collected from 2 official sources: eTender (806), 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-11-22.
Open Software Development tenders in South Africa
Showing 4 of the 5 notices open in this category today. Openness uses the same definition as the South Africa 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.
Tender for the supply and delivery of original equipment manufacturer (OEM) printer specific consumables for identity (id) card printers and as well as upgrading of the existing id card software packages to the Tshwane police department for a period of three (3) years on and when required basis.
Appointment of a Service Provider to Design, Implement, and Maintain Software-Defined Wide Area Network (SD-Wan) Solutions and WI-FI Services for a Period of Three Years Across the Head Office and Nature Reserves
For the Provisioning of Hardware, Architecture, Designing, Purchase and Software of Infrastructure for Transnet Port Terminals (TPT), Transnet National Ports Authority (TNPA) and Transnet Corporate Centre (TCC) for a Period of Five (05) Years
Other procurement categories in South Africa
Software Development procurement in other markets
Never Miss a South Africa Government Contract
Finding South Africa 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