Software Licensing Tenders: Mastering Enterprise Renewals

The Recurring Revenue Engine

For ICT

resellers, software license renewals are the closest thing to a 'holy grail' contract type. Unlike hardware, which is typically a once-off sale with a fixed delivery obligation, software contracts such as Microsoft Enterprise Agreements, Oracle licensing, or SAP support recur annually or every few years. They offer predictable, high-volume revenue with minimal physical logistics

cost. Because this recurring revenue is so attractive, competition for these contracts is intense, and government buyers have built a fairly standardised set of compliance hurdles specifically to keep this market orderly and to prevent grey-market or unlicensed software from entering the public sector.

Understanding this dynamic matters before you even open a tender document. Software licensing tenders are won less on 'who has the best product' — the product is usually fixed, since the department already runs Microsoft or SAP or Oracle and is simply renewing or expanding — and more on who can prove legitimate supply, price the renewal competitively without going insolvent on margin, and wrap in enough service value to differentiate an otherwise identical bid.

The Golden Ticket: Manufacturer Authorization Form (MAF)

The single most important document in a software tender is what's generically called the Manufacturer Authorization Form (MAF), sometimes labelled a Letter of Authority, a Reseller Certificate, or a Letter of Support depending on the vendor.

Government departments cannot legally buy licensed software from just anyone; they need assurance that the licenses being supplied are genuine, properly sourced, and will be supported by the manufacturer. Tender documents will usually state plainly that failure to submit a valid MAF from the original equipment manufacturer (OEM) results in automatic disqualification, regardless of how competitive the price is.

1. Bid-specific letters carry more weight. A MAF that names the specific department and references the tender number by name demonstrates that you actually engaged the vendor about this bid, rather than reusing a generic annual accreditation letter.
2. Partner tier matters for pricing, not just eligibility. Your accreditation level with the vendor (commonly tiered as something like Silver, Gold, or Platinum) often determines the buy-price you receive from distribution, which flows directly into how competitively you can price the bid.
3. Expiry dates are a frequent trap. A MAF or partner certificate that expires partway through the bid validity period, or before contract commencement, can be treated as non-compliant even if it was valid on the submission date.

Competing in a Commoditized Market

If several accredited partners all bid for the same Microsoft or SAP renewal, and they all obtain a similar buy-price from the same distributors, the natural question becomes: how do you actually win? The honest answer is that you rarely win purely on the license line item. You win on margin discipline and value-added services layered around the licenses.

The Margin Squeeze

Licensing tenders are inherently low-margin, high-volume business. Bidders chasing the healthy margins typical of hardware or professional services will be priced out immediately. Many winners bid at a thin margin, sometimes in the low single digits, purely to secure the cash flow, the client relationship, and the platform for future add-on work. The real profit is usually generated by the services layered around the license, not the license itself.

Value-Added Services as the Real Differentiator

Bidders who consistently win software renewals bake genuine, costed services into their proposal rather than simply undercutting on price:

• Consumption and utilisation reporting. Providing regular reports on which licenses are actually active helps a department right-size its next renewal, and demonstrates you are managing the account rather than simply invoicing it.
• Adoption training
  . Offering structured workshops on using the licensed platform (for example collaboration or productivity tools) effectively increases perceived value without materially increasing your cost base.
• Bundled technical support hours. A defined bank of remote support hours for installation, activation, or configuration issues gives evaluators something tangible to score beyond price.
• License optimisation and compliance reviews. Helping a client avoid both under-licensing (a compliance risk if audited by the vendor) and over-licensing (wasted budget) is a genuinely valuable, low-cost service to offer.

Understanding SITA's Role

The State Information Technology Agency (SITA) plays a central role in ICT

procurement

for national and provincial government. For large transversal agreements with major software vendors, SITA often negotiates the master commercial terms centrally, while individual departments still need an accredited fulfilment partner (a reseller) to actually transact the order and provide local support.

This means some tenders are restricted to suppliers already listed on a specific SITA transversal contract, while others are run as open tenders by the department itself, particularly for software outside the major transversal agreements or for smaller, specialised systems. Before investing time in a bid, confirm whether the opportunity is open to the general market or limited to suppliers already accredited on the relevant SITA panel — bidding on a restricted opportunity without the underlying accreditation wastes preparation time on a bid that cannot be awarded to you.

Structuring the Contract: Perpetual, Subscription, and Enterprise Agreements

Not all software tenders are structured the same way, and misreading the contract model is a common costing mistake:

• Perpetual licenses with annual maintenance. The client buys the license once and pays an ongoing annual maintenance or support fee (often referenced as a percentage of the license value) for updates, patches, and vendor support. Your bid must price the maintenance renewal correctly for the years covered by the tender, not just the initial purchase.
• Subscription or SaaS licensing. The client pays per user, per month or per year, for as long as the subscription is active, with no perpetual ownership. These tenders are typically simpler to price but carry renewal risk if the department's user numbers shrink mid-term.
• Enterprise Agreements (EA) and similar volume licensing programmes. These bundle multiple products across an organisation's full user base, often over a multi-year term, and usually include 'true-up' provisions where the client pays for additional users added during the term. Your bid should clearly state how true-ups will be invoiced and at what rate, so there is no dispute later.

The Risk: Exchange Rate Fluctuations

Most enterprise software is priced in US dollars even where the client is invoiced in rand. A multi-year contract can turn from profitable to loss-making if the rand weakens materially over the contract term. The standard protection is a clearly stated Rate of Exchange (ROE) clause in your bid: state the exchange rate your pricing assumes, and specify how invoicing will treat currency movement beyond an agreed tolerance band. Without an explicit ROE clause, you are effectively absorbing currency risk on behalf of the client for the full contract term, which on a large multi-year renewal can be a significant, uncosted liability.

Software Asset Management and Audit Readiness

Vendors periodically audit their public sector customers for license compliance, and an under-licensed department can face significant retrospective true-up costs. Bidders who position themselves as a Software Asset Management (SAM) partner — helping the client maintain an accurate license inventory, track deployments against entitlements, and prepare for vendor audits — build a stickier, more defensible relationship than a bidder who simply processes purchase orders. This is a genuine differentiator on technical scoring criteria that reward service depth rather than price alone.

Common Mistakes in Software Licensing Bids

• Submitting a generic, undated partner certificate instead of a bid-specific MAF referencing the tender number and closing date.
• Ignoring the true-up mechanism in multi-year Enterprise Agreements, leading to disputes when user numbers grow mid-contract.
• Pricing in rand without an ROE clause, leaving the bidder exposed to currency risk on dollar-denominated licensing.
• Underestimating the credit facility required to fund a large invoice to distribution before the department pays, particularly on multi-million rand renewals with 30- to 60-day payment terms.
• Failing to confirm licensing tier and edition against the exact specification, which can result in a technically non-compliant bid even where the vendor and product family are correct.

Conclusion

Software licensing tenders are ultimately a game of financing discipline, compliance documentation, and risk management rather than product differentiation. Secure your MAF early and make it bid-specific, ensure you have the credit facility to fund large distributor invoices ahead of client payment, price in a rate-of-exchange clause to protect against currency swings, and build genuine value-added services into the bid rather than competing purely on license margin. The MAF gets you to the table; disciplined pricing and service depth are what keep the contract profitable.