How to Choose a Web Developer in South Africa

Spending real money on a website and getting burned is a common fear: a site you cannot edit, a domain you do not control, or a developer who disappears after launch. If you are working out how to choose a web developer in South Africa, judge them on three things: live work you can check, ownership agreed in writing, and a clear answer about what happens after launch. Price matters, but only once those three are in place.

Yes, I am a web developer, so read this knowing that. These are the same questions I would want a client to ask me. For what a typical mid-range budget should get you, see what R9,500 actually buys you.

Can you show me live sites built for real clients?

One developer's guide puts it simply: every developer should be able to show you live websites they have built for real clients, not mockups and not template demos ^[1]. It suggests asking for at least three ^[1].

• Open each site yourself. Check it loads quickly on your phone and belongs to a real, trading business.
• Ask what exactly they did on each one: design, build, hosting, or all of it.
• Read reviews. Directories let you filter providers by location, budget and services and read client reviews ^[3], which is useful for a shortlist.

Be wary of paying custom prices for template work. The same guide warns that if someone quotes thousands for a WordPress site built on a pre-built theme, you are paying for assembly, not development ^[1]. Theme-based sites can be a perfectly good choice; the price should simply match what you are getting.

For my own work, the client projects are live and linked from my case studies and work pages, so you can check them rather than take my word for it.

Who owns the domain, the code and the content?

This is the question that protects you most, and the one most often skipped. The same guide lists "who owns the domain, hosting, and code after launch?" among the questions to ask before hiring ^[1].

• Domain: you should be the registrant, the legal holder named on the registration, with the account login in your hands. For .com domains, ICANN confirms it is your right to transfer between registrars, using an authorisation code the registrar must provide within five calendar days of your request ^[5].
• Code and content: agree in writing that the site's code, design files and content are yours on final payment, subject to the licences of any themes or plugins used.
• Hosting: a developer hosting the site on their account can be fine, if it is agreed in writing and you can move it when you choose.

“Ask who owns it before you pay the deposit, not after you want to leave.”

What is actually in writing?

A good quote lists the pages, features, hosting, and what support looks like after launch. One South African development firm advises asking for detailed quotes that show both upfront costs and long-term support or maintenance fees, so there are no surprises later ^[3].

If your site will collect customer information, such as enquiry forms, accounts or orders, POPIA adds a requirement. Where someone processes personal information on your behalf, such as a developer or host, section 21 of the Act requires a written contract making sure they maintain proper security measures ^[4], and obliges them to tell you immediately if they believe the information has been accessed by someone unauthorised ^[4]. A good developer will happily put this in writing. For your specific obligations, get professional advice.

What happens after launch?

The launch is the start, not the end. Ask:

• Who updates the site and its plugins, and how often?
• How do you request changes, and what do small changes cost?
• Who do you call if the site goes down or the checkout breaks?
• What are the yearly hosting and renewal costs?

In my experience, vague answers here are a common source of trouble later. I go through what proper upkeep should cover in what website maintenance includes.

Web developer red flags worth walking away from

In my experience, these are the signs that a project is likely to end badly, whatever the price:

• No live client work, only screenshots or template demos.
• Vague answers about who will own the domain and the code.
• A quote with one total and no breakdown of pages, features or hosting.
• Pressure to pay everything upfront, rather than a deposit and milestones.
• No mention of what happens after launch, or "we will sort that out later".
• Asking you for your email or banking passwords instead of setting up separate access.

None of these proves bad intent on its own. But a developer who is confident in their work will answer each point clearly, and usually before you have to ask.

Freelancer, agency or website builder?

There is no single right answer. A freelancer gives you a direct line to the person doing the work, but is one person. An agency has more people and more layers. A website builder can be the cheapest way to start, but depending on the builder and plan, you may give up some ownership, portability and flexibility. I compare them in freelancer vs agency vs website builder.

Do not assume local means second best. One international hiring platform points out that South Africa runs on GMT+2 all year ^[2], which makes working hours easy to line up. Judge communication directly: how clearly a developer answers your first few questions tells you more than where they are based. One local firm notes South African rates can be lower than in North America or Europe ^[3]. The questions above matter more than the location.

What to do next

• Shortlist two or three developers from live work and reviews.
• Ask the ownership and after-launch questions, and get an itemised quote.
• Make sure you are the registrant of your domain and hold the account login.
• Get code and content ownership, and any handling of customer data, agreed in writing.
• If unsure, start with a small, well-defined first phase.

If you want to put these questions to me directly, get in touch and I will answer them in writing before you commit to anything.