Technology Law

SaaS Agreement: Template vs Bespoke for SA Companies

When a template is fine. When it isn’t. And what the real cost of getting it wrong looks like under POPIA, ECTA and the Consumer Protection Act.

Written by

Martin Kotze

Attorney, Conveyancer & Notary Public

About
Quick answer

SaaS templates work for pre-revenue startups, low-ACV self-service products, and internal-tools businesses. They fail predictably the moment an enterprise customer pushes back, the moment you cross a border with data, the moment a regulated buyer asks for a POPIA operator-agreement schedule, or the moment annual contract value exceeds ~R250,000. The most common failure mode for SA businesses using foreign-drafted templates: missing POPIA s 21 operator-agreement coverage, mismatched governing-law and forum clauses, missing ECTA s 43 disclosures, and CPA-incompatible cancellation and renewal terms. Bespoke SA-drafted SaaS contracts start at R12,000 for a single MSA, and around R25,000–R35,000 for a complete SaaS contract stack (MSA + SLA + DPA + T&Cs + privacy). For background reading on what a SaaS agreement covers, see our SaaS agreements guide.

The six predictable template failures

  • Foreign jurisdiction defaults (Delaware, California, England & Wales) that SA courts will not enforce or that strip SA-resident customers of CPA protections.
  • No POPIA Chapter content — leaving SA-customer personal data without the section 21 operator-agreement coverage POPIA requires.
  • CPA-incompatible cancellation, auto-renewal and refund terms (the CPA cooling-off and 24-month cap routinely conflict with US-defaulted SaaS terms).
  • Liability-cap structures designed for US tort exposure that under-protect against POPIA penalty exposure (up to R10m per breach).
  • ECTA section 43 disclosure gaps for SA customers transacting electronically.
  • Missing electronic-signature compliance with ECTA section 13 — the US e-signature analysis does not map.

When a template is genuinely enough

  • Pre-revenue SaaS startups testing the market with a self-service product, where customer ACVs are under R5,000/month.
  • Internal-tools SaaS sold only to a small known customer base, where the contracts are renegotiated bilaterally anyway.
  • Open-source-style products with usage-based pricing and limited enterprise commitments.

When bespoke is mandatory, not optional

  • Annual customer contract value exceeds approximately R250,000 — bespoke is cheaper than the future renegotiation when an enterprise buyer pushes back on your template.
  • Customers in regulated industries (banking, healthcare, insurance, public sector) where their procurement teams will require POPIA-specific schedules and audit rights.
  • Cross-border deals where data flows out of SA — section 72 of POPIA requires contractual safeguards that templates rarely cover correctly.
  • AI-enabled SaaS where the customer needs warranties about training-data provenance, model bias, and output-IP.
  • Where you are the customer evaluating a vendor's template — almost always worth a bespoke negotiation rather than signing as-is.
  • Post-Series A SaaS where investors and customers expect institutional-grade contracts.

Frequently asked

Can I just adapt a Stripe or AWS-style template to SA law?

You can — but adapting takes more time than drafting from scratch under SA law. Foreign SaaS templates are deeply structured around their home jurisdiction's default rules. Pulling out the US/EU references and dropping in SA equivalents leaves footprints — undefined terms, dangling cross-references, mismatched concepts. A SA-drafted SaaS template costs less than a thorough adaptation.

Why are SA SaaS bespoke agreements typically R12,000+ rather than R3,000?

A bespoke SaaS agreement covers: a master subscription agreement (10–15 pages), an order form / subscription schedule, an SLA, a POPIA data processing addendum, and ECTA / CPA compliance terms. Drafting these properly to fit your specific product, customer mix, and risk profile takes 6 to 10 hours of senior attorney time. Templates can be cheap because they treat all SaaS as the same — and your customers don't.

What is the minimum bespoke documentation a SA SaaS company should have?

Three documents: (1) a master subscription agreement that customers sign (electronically under ECTA s 13); (2) an SLA defining uptime, response, and remedies; (3) a POPIA-compliant data processing addendum addressing section 21 obligations. If you sell self-service to consumers, add: a website T&Cs, a privacy policy, and ECTA section 43 disclosures. For B2B enterprise sales, prepare a separately-signed operator agreement template.

How long does bespoke drafting take?

For a single bespoke SaaS agreement: typically 5 to 10 working days from instruction. For the full SaaS contract stack (MSA + SLA + DPA + privacy + T&Cs): 10 to 15 working days. Most engagements include one round of revisions in the fixed fee, with additional rounds quoted separately.

Should I use one of the SA legal template marketplaces?

SA legal template marketplaces have improved, but quality varies dramatically. The key checks: (i) was the template drafted by a SA attorney admitted to the High Court (check the LPC); (ii) when was it last reviewed against POPIA, Cybercrimes Act, ECTA amendments; (iii) does it cover the operator-agreement requirements you need. A marketplace template can be a starting point — but plan to spend R5,000-R8,000 having it reviewed before relying on it for material contracts.

Why you can trust this: Martin Kotze has been an admitted Attorney of the High Court of South Africa, registered Conveyancer, and Notary Public since 2014, practising from Pretoria. The firm is regulated by the Legal Practice Council under firm registration F17333.

This guide is general information, not legal advice for your specific matter.