What is a professional services addendum?
Who owns custom software built under a professional services addendum in South Africa?
“Copyright in a computer program vests first in its author — the person who exercised control over the making of the program — and is transferred only by an assignment in writing signed by or on behalf of the assignor; the Act’s commissioning rule does not extend to computer programs, so ownership of custom-developed deliverables does not pass to the commissioning customer without an express written assignment.”
“When a supplier undertakes to perform a service, the consumer has a right to performance in a manner and of a quality that persons are generally entitled to expect — a non-excludable baseline that sits behind the services warranty where the customer is a consumer under the Act.”
When you need a Professional Services Addendum
- When a SaaS or cloud provider will do paid implementation, onboarding, configuration, data migration, or integration work for a customer alongside the product subscription, and the parties want a reusable framework instead of negotiating each engagement from scratch.
- When bespoke or custom development is involved and ownership of the resulting code and deliverables needs to be settled in writing — assigned to the customer or retained-and-licensed by the provider.
- When training, consulting, or other professional services are sold and the parties want clear pricing (time-and-materials or fixed-fee/milestone), acceptance criteria, and a change-control process.
- When the provider needs to confirm that its consultants are independent contractors, not the customer’s employees, and to set assumptions and customer dependencies that protect its delivery timeline and price.
- When the customer is a consumer (or small business under the CPA) and the parties want the services warranty to align with the section 54 quality-of-service baseline.
What a Professional Services Addendum should contain
Statement-of-work (SOW) mechanics
Provide that each engagement is performed under its own signed SOW setting out scope, deliverables, timeline, acceptance criteria, fees, and any engagement-specific assumptions. State the order of precedence between the addendum, each SOW, and the master agreement, so a conflict between them is resolved cleanly rather than argued about mid-project.
Pricing model — time-and-materials vs fixed-fee / milestones
Set out how each SOW is priced: time-and-materials (agreed rates against hours actually worked, with estimates and reporting) or fixed-fee / milestone (a set price released against defined, accepted milestones). Spell out expenses, rate cards, and what happens to the price when scope changes — this is the clause most likely to cause friction if left vague.
Acceptance criteria and testing
Define how the customer reviews and accepts deliverables — the testing or acceptance period, the criteria, what counts as a defect, the cure process for rejected work, and deemed acceptance if the customer does not respond in time. Because the engagement is a contract for a result, clear acceptance is what tells both sides when the work is done and payment is due.
Change control
Require that any change to scope, deliverables, timeline, or price is documented and signed off through a defined change-control procedure before the work proceeds. Without it, “scope creep” turns into disputes over whether extra work was included in the original price — change control is the mechanism that keeps a fixed-fee SOW honest for both parties.
Assumptions and customer dependencies
List the assumptions the estimate or fixed fee rests on and what the customer must provide — data, access, environments, decisions, and personnel — by when. Provide that where the customer’s failure to meet a dependency causes delay or extra cost, the timeline and price adjust. This protects the provider against being blamed for delays it did not cause.
IP in the deliverables (assignment or licence)
Make the deliberate, written choice the Copyright Act requires: either assign IP in the custom deliverables to the customer by a written, signed assignment (typically carving out the provider’s pre-existing and generic background IP and tooling, which is licensed rather than assigned), or have the provider retain ownership and grant the customer a defined licence. Silence or loose wording leaves the developer as first owner — exactly the outcome a paying customer does not expect.
Independent-contractor status (no employment)
Confirm that the provider’s personnel act as independent contractors and are not, and do not become, the customer’s employees, and that the provider remains responsible for their remuneration, tax, and statutory obligations. This keeps the engagement squarely a contract for work (locatio conductio operis) rather than a contract of service, and avoids unintended employment and labour-law consequences.
Warranty on services
Warrant that the services will be performed with reasonable skill and care, by suitably qualified personnel, in accordance with the SOW — with a defined re-performance remedy for breach. Where the customer is a consumer, align this with the CPA section 54 quality-of-service right, which cannot be excluded. The warranty should sit within the master agreement’s overall liability cap unless the parties intend otherwise.
Professional services addendum vs SaaS subscription vs employment
| Feature | Professional services addendum | SaaS subscription | Employment |
|---|---|---|---|
| Legal nature | Locatio conductio operis (contract for work) | Licence / contract to provide ongoing access | Locatio conductio operarum (contract of service) |
| What is delivered | Defined deliverables / outcomes under each SOW | Continuous access to the product | An employee’s labour over time |
| Pricing | Time-and-materials or fixed-fee / milestone | Recurring subscription fee | Salary / wage |
| IP in outputs | Must be assigned or licensed in writing | Provider keeps the product IP; customer gets a licence | Generally vests in the employer by operation of law |
| SA touchpoint | Copyright Act (assignment in writing); CPA s 54 | Common law; CPA; POPIA; ECTA | LRA / BCEA and labour law |
Common South African pitfalls
- Assuming payment buys ownership: under the Copyright Act the developer is first owner of custom software, and copyright passes only by a written, signed assignment. A customer who pays for bespoke development but never gets a proper written assignment does not own it — the single most common and costly IP mistake in SA services engagements.
- A “belongs to the customer” clause that does not actually assign: a clause stating the deliverables “are the property of” the customer, without effecting a valid written assignment of copyright, can fail to transfer ownership. The wording must do the work the Copyright Act requires, and should address background IP and tooling separately.
- No change control: without a defined procedure for agreeing and pricing scope changes, a fixed-fee SOW becomes a battleground over whether extra work was included. Scope creep is managed by change control, not by argument after the fact.
- Weak or missing acceptance criteria: if the SOW does not say how deliverables are tested, accepted, and paid for — including deemed acceptance and a cure process for defects — the parties end up disputing whether the work is “done”. For a contract for a result, acceptance is the trigger for both completion and payment.
- Blurring the contractor / employee line: failing to confirm independent-contractor status, or directing the provider’s people as if they were staff, risks unintended employment and labour-law consequences. The addendum should keep the engagement a contract for work, not a contract of service.
Frequently asked questions
Who owns custom software built under a professional services addendum?
By default the developer does. Under the Copyright Act 98 of 1978 copyright in a computer program vests first in its author — the person who exercised control over its making, ordinarily the provider — and is transferred only by a written, signed assignment. The Act’s commissioning rule does not cover computer programs, so paying for bespoke development does not automatically make the customer the owner. The addendum must expressly assign the IP to the customer or grant a defined licence, in writing.
What is the difference between a SOW and the professional services addendum?
The addendum is the master framework — the standing terms that govern all services engagements (IP, change control, acceptance, warranty, contractor status). A statement of work (SOW) is the document for a specific piece of work, setting out its scope, deliverables, timeline, and price. Each engagement runs under its own signed SOW, beneath the one addendum.
What is the difference between time-and-materials and fixed-fee pricing?
Under time-and-materials the customer pays for hours actually worked at agreed rates, usually against an estimate — flexible, with the customer carrying the risk of overrun. Under fixed-fee / milestone pricing the provider commits to a set price for a defined scope, often released against accepted milestones — more certain for the customer, with the provider carrying the overrun risk. Change control governs scope changes either way.
Do I need a written IP assignment for custom development?
Yes. The Copyright Act requires an assignment of copyright to be in writing and signed by or on behalf of the assignor. An oral agreement, or a clause that loosely says the work “belongs to” the customer, may not transfer ownership. To own custom deliverables, the customer needs an express written assignment in the addendum or SOW — there is no automatic transfer.
What is acceptance testing and why does it matter?
Acceptance testing is the defined process by which the customer reviews a deliverable against agreed criteria and signs it off (or rejects it for cure). It matters because a professional services engagement is a contract for a result — acceptance is what tells both sides the work is complete and payment is due, and a clear deemed-acceptance rule prevents the customer stalling indefinitely.
Are the provider’s consultants my employees?
No — not if the addendum is drafted correctly. The provider’s personnel act as independent contractors; the engagement is a contract for work (locatio conductio operis), not a contract of service. The provider remains responsible for their pay, tax, and statutory obligations. Directing them as if they were your staff, however, can blur the line and create unintended labour-law exposure.
What is change control and why do I need it?
Change control is the procedure for agreeing and pricing any change to a SOW’s scope, deliverables, timeline, or fee, in writing, before the changed work proceeds. It is what keeps a fixed-fee engagement honest: without it, additional requests turn into disputes over whether they were included in the original price. It protects both customer and provider from scope creep.
Does the Consumer Protection Act apply to professional services?
It can. Where the customer is a consumer — including a small business below the CPA threshold — section 54 of the Consumer Protection Act gives a non-excludable right to services performed in a manner and of a quality persons are generally entitled to expect. The services warranty in the addendum should align with that baseline rather than purport to fall below it.
Sources & authority
This guide is general information, not legal advice. It reflects the law as at June 2026.