Technology requirements consulting is the work of establishing what a business actually needs from a system before anything is bought or built. This page covers both sides: what a business should require from a consultant, and what someone setting up as one needs in place.

It is an unregulated field in South Africa. Anyone may describe themselves as a technology consultant, there is no licence and no compulsory qualification — which makes the buyer’s own diligence the only real protection.

Business Requirements at a Glance

For a business engaging a consultant, what to establish before signing.

Registration and Legal Requirements

Vendor independence is the question that matters most. A consultant who receives commission from a software vendor has an interest in the recommendation, and that must be disclosed. It does not necessarily disqualify them, but you are entitled to know. Ask directly, in writing.

Buy deliverables, not days. An open-ended day rate with no defined output is where consulting engagements overrun. Define what you will receive — a requirements document, a vendor evaluation, an implementation plan — and pay against it.

Own the output. Unless the contract says otherwise, ownership of what a consultant produces is not always where a client assumes it is. State explicitly that deliverables and any customisation belong to you, and that you may use them without further payment.

POPIA obligations flow through. Where a consultant processes personal information on your behalf, they are an operator under POPIA and a written agreement is required, with security obligations and breach notification. This is a legal requirement, not a formality.

Beware the consultant who is also the implementer without that being disclosed and priced separately. Independent requirements work followed by a competitive implementation process produces better outcomes than a single party doing both, unless you have deliberately chosen otherwise.

Documents and Ownership Information Required

For someone setting up as a consultant, the business requirements are those of any professional services business.

Tax, Licence and Compliance Requirements

The contracting question that determines everything for a consultant is whether you are genuinely independent or effectively an employee. SARS applies tests to distinguish independent contractors from employees, and where a person works exclusively for one client, under its supervision, on its premises and its hours, the arrangement may be treated as employment for tax purposes with PAYE consequences for the client.

That matters to both sides. Clients engaging long-term full-time contractors should take advice, and consultants should understand the personal service provider rules under the Income Tax Act, which can result in a company being taxed at a higher rate with limited deductions.

Labour law may also apply. The Labour Relations Act contains presumptions about who is an employee, and a person engaged as a contractor may nonetheless be found to be an employee with the protections that carries. Structure and document arrangements honestly rather than labelling them conveniently.

Professional indemnity insurance is the practical necessity. Requirements work that leads a client to buy the wrong system creates real exposure, and clients of any size will ask for cover.

Certifications are commercially useful rather than legally required. Business analysis, project management, enterprise architecture and vendor-specific certifications signal competence in an unregulated field. Confirm the requirements with the certifying body directly.

For public sector work, Central Supplier Database registration and a valid tax compliance status are prerequisites, and B-BBEE status affects scoring.

Process, Deadlines and Ongoing Obligations

Businesses should define the outcome they want before engaging anyone, ask about vendor independence directly, and contract for deliverables with clear intellectual property ownership.

Consultants should get the entity, tax compliance, insurance and standard terms in place before taking a first engagement, and should be clear-eyed about the independent contractor tests rather than discovering them at an audit.

Frequently Asked Questions

Is technology consulting regulated in South Africa?

No. There is no licence and no compulsory qualification, which makes the buyer’s own diligence — references, scope, independence and insurance — the only real protection.

Why does vendor independence matter?

A consultant receiving commission from a software vendor has an interest in the recommendation. Ask directly and in writing. It does not disqualify them, but you are entitled to know.

Who owns the work a consultant produces?

Not always the client, unless the contract says so. State explicitly that deliverables and customisations belong to you and may be used without further payment.

When is a contractor treated as an employee?

SARS and labour law apply tests looking at supervision, exclusivity, premises and hours. A long-term full-time contractor may be treated as an employee for tax or labour purposes regardless of the label.

Contracting, tax and data protection requirements are set under the Income Tax Act, the Labour Relations Act and POPIA and are amended. Confirm current requirements with SARS, an attorney and the Information Regulator as applicable.

Related Requirements