Vet a Freelance Developer in South Africa: 8-Step Checklist

Before you vet a freelance developer, know what you are protecting yourself from. The cost of a bad hire is rarely the fee. It is the lost months, the half-built product nobody else can finish, and code you may not have the right to use. Most of that is avoidable with a short checklist, run before any money changes hands. Here is the version that protects a South African business.

Why you should vet a freelance developer before comparing rates

The cheapest quote often becomes the most expensive outcome. A developer who underprices and then abandons the project leaves you paying someone else to start again, often from code that was never handed over or documented. Ownership is the other trap. Under the Copyright Act, the author of a computer program is the person who exercised control over its making, and the author is the first owner of the copyright unless the work was made by an employee. With a freelancer that can be the developer, and an assignment to you only has effect if it is in writing and signed. The hourly rate is a small number next to that.

The 8-step checklist

Run these in order before you commit the budget. Each one closes off a way the hire can go wrong.

1. Check real, shipped work. Ask to see live products you can open and use, and the code behind them. Then ask what they personally built and what a team built, so you know whose work you are buying.

2. Talk to two past clients. Ask about deadlines, communication and whether the handover was clean. They will tell you how the project actually ended, which is the part that matters most.

3. Get the IP assignment in writing first. Agree, before you pay, that all copyright in the code is assigned to you. Section 22(3) of the Copyright Act says an assignment has no effect unless it is in writing and signed by or on behalf of the person assigning it.

4. Agree scope, milestones and acceptance. Write down what done means for each milestone and how you will sign it off. A clear definition of done stops a disagreement turning into a stalemate.

5. Require source code and documentation. Make full source code plus build and run instructions a deliverable you own, handed over at each milestone, not a favour at the end.

6. Ask about open-source and reused code. Require disclosure of any third-party or pre-existing code and its licence. Open-source licences, listed by the Open Source Initiative, come with conditions, and you inherit them once the code is in your product.

7. Start with a small paid test task. A paid task of one to three days shows real quality and communication in a way no interview can.

8. Stage the payments with holdbacks. Pay against accepted milestones and hold a final portion until handover, so abandonment costs the developer, not you.

Freelance developer red flags

Any one of these is a warning. Two or more together is a reason to walk away.

The paid test task

The best single filter is a small, paid test task before the main contract. An interview shows how someone talks about work; a paid task shows the work. Scope it to one to three days, pay a fair rate, and ask for the same things the full project needs, in miniature: working code in a repository you can see, a short note on how to run it, and clear communication along the way.

For example, a Stellenbosch wine farm hiring a freelancer to build an online booking system could first pay for a three-day task: one booking form that saves to a database and sends a confirmation email. After three days the owner knows whether the developer writes clean code, meets a deadline and explains problems clearly, for a small fraction of the full budget.

If the developer will see customer data

If the developer works with personal information, such as a customer database, they are processing it on your behalf, and POPIA applies. Section 20 requires anyone processing personal information for you to keep it confidential. Section 21 requires a written contract that obliges them to keep it secure, and it requires them to tell you immediately if they have reason to believe someone accessed it without authorisation. Give them test data where you can, and only the access they need.

Studio or freelancer?

The same checks apply to a studio, although a company is less likely to vanish than one person. Ask any provider for a fixed price against a written scope, the IP assignment and the source-code handover in the contract. As one reference point, Zaiq’s published prices start from R8,000 for a focused build and state that you own the result.

For the contract clauses in detail, see hiring a developer in South Africa: contracts and IP. This is general guidance, not legal advice. For your contract, speak to a South African commercial or IP lawyer.