Buyer's Guide

How to Choose a Web Developer in South Africa Without Getting Burned

South Africa has thousands of web developers — from freelancers charging R2,000 to agencies quoting R100,000 for the same scope. This guide helps you tell the difference between good and expensive, cheap and risky.

Updated November 2026 • 12 min read

Start With Your Actual Requirements

Before you contact a single developer, get clear on what you actually need. Most businesses significantly over-scope their first website — and pay for features they never use.

A basic question set to answer before you start:

  • What is the primary goal of the website? (Generate leads, sell products, build credibility, provide information?)
  • How many pages do you genuinely need at launch?
  • Who will manage content after launch — and how technical are they?
  • Do you have existing branding (logo, colours, fonts) or does that need to be created?
  • What's your budget range, and what's the hard limit?
  • When does it need to be live?

The Portfolio Is Everything

Any developer can claim they build "premium, SEO-optimized, high-converting websites." Only their portfolio can prove it.

When evaluating a developer's portfolio, don't just look at how the sites look. Check:

Do the sites actually load fast?

Open their portfolio examples on your mobile phone. Count the seconds until you see content. Anything over 3 seconds on 4G is a problem.

Are the sites still live?

If a developer's portfolio examples are dead links or redirect to 'coming soon' pages, ask why.

Does the work match your industry?

A developer who's built 10 restaurant sites understands your challenges. Someone who's only built SaaS dashboards may struggle with service business conversions.

Can you see the Google rankings?

If the developer claims their sites are 'SEO optimized,' Google the business names in their portfolio. Are those sites ranking for local terms?

Questions to Ask Before You Pay a Deposit

Q:Who actually builds the site?

Many agencies outsource work overseas or to subcontractors you'll never speak to. Ask directly: 'Who writes the code for my project? Is it you personally, a team member, or a subcontractor?'

Q:What happens to the code when we're done?

You should own the source code outright. Some developers host on proprietary platforms or retain the code to prevent you from leaving. This is a red flag.

Q:What do you need from me to start?

A well-organized developer will have a clear content brief. If the answer is vague, expect delays.

Q:How many revision rounds are included?

Unlimited revisions sounds good. It's not — it usually means poorly scoped work that never ends. Defined revision rounds (2–3 is standard) are better.

Q:How is payment structured?

Industry standard: 50% deposit, 50% on delivery. Be cautious of developers who want 100% upfront or drag payment to after months of work.

Q:What does 'maintenance' cost after launch?

Understand exactly what's included in any ongoing fees — and what happens to your site if you stop paying.

Red Flags to Walk Away From

✕ No portfolio, or portfolio links that don't work
✕ Promises to 'get you to #1 on Google' as part of a standard package
✕ No written contract or scope document before work begins
✕ Refuses to give a fixed price ('it depends on how long it takes')
✕ Can't explain what technology they'll use to build your site
✕ Pressure to sign immediately or 'lose the slot'
✕ All communication through a salesperson — you never speak to the actual developer
✕ Lock-in clauses that charge you to access your own site or domain

Check These Yourself in Ten Minutes

You don't need to be technical to verify a developer's claims. Pick two sites from their portfolio and run these checks before you ever get on a call:

  1. Run the site through Google PageSpeed Insights (pagespeed.web.dev) on the mobile tab. Look at the real-user data if it shows, not just the lab score. If a portfolio site scores poorly, yours will too.
  2. Search site:theirclientsdomain.co.za on Google. If the site has been live for months and almost nothing is indexed, the "SEO included" promise didn't deliver.
  3. Look up who owns the client's domain. A .co.za WHOIS lookup shows the registrant. If the registrant is the developer rather than the business, that client can't easily leave. Ask whether yours would be registered in your name.
  4. Open the site on mobile data, not Wi-Fi. Most South African visitors are on a phone with a capped or slow connection, so heavy sliders, autoplay video and huge images hurt in a way you won't notice at your desk.
  5. Message one of their past clients. Ask one thing: "Did they deliver on the date they promised?" Late delivery is the most common complaint, and a past client will answer honestly.

South Africa–Specific Things Most Guides Skip

Your domain should be registered in your name

A .co.za domain is a business asset. Insist you are the registrant and that you hold the login to the registrar account. If the developer registers it under their own name 'for convenience,' you may need their permission, or a fee, to move it later.

POPIA applies to your contact form

The Protection of Personal Information Act covers any personal details you collect, and a contact form collects names, emails and phone numbers. Your site should have a privacy policy that says what you collect and why, and your developer should know where form submissions are sent and stored. If they've never heard of POPIA, that tells you something.

Where the site is hosted matters

Don't accept a site hosted on a machine in someone's office. With load shedding and unreliable connections, your site should sit on a professional host with proper uptime. Ask where it's hosted and what happens if their service goes down. For a South African audience, a host with a nearby or CDN-backed presence also loads noticeably faster.

Get the quote in rand, and know what it includes

Get the quote in rand, state whether VAT is included, and confirm that domain renewal, hosting and any third-party licences (themes, plugins, stock photos) are either included or listed separately. Surprise renewal costs are the most common billing dispute.

Have them explain it in plain language

A good developer can explain what they're building, why, and what it will cost in terms you understand. If every answer is jargon, you'll struggle to hold them to what was agreed.

What a Good Written Scope Should Contain

Whoever you hire, get this in writing before you pay anything. A one-page scope is enough for a small business site, and it protects both sides.

  • The exact list of pages and any special features (booking, WhatsApp button, quote form, shop)
  • What you supply (logo, text, photos) and the date you'll deliver it by. Delays on your side usually delay the launch too
  • The number of revision rounds and what counts as a revision versus a new request
  • The total price, the payment schedule, and what is and isn't included after launch (hosting, domain, updates)
  • A launch date and what happens if either side misses a deadline
  • Who owns the finished site, the code, and the domain once you've paid in full
  • How you can move the site elsewhere if you decide to leave, and any fee for doing so

If a developer won't put these points in writing, treat that as your answer.

Freelancer vs Agency vs Boutique Studio

Type Pros Cons
Freelancer Low cost, direct communication, flexible Single point of failure, may take on too much work, limited specialization
Large agency Full team, project management, diverse skills High cost, you're not the priority, communication via account managers
Boutique studio Specialized skills, personal service, accountable Limited capacity, may not suit large complex projects

For most South African SMEs, a boutique studio or experienced freelancer hits the best balance of quality, communication, and price.

We're Happy to Be Evaluated

Ask us all the hard questions. Check our portfolio. Call our clients. If we're the right fit, you'll know. If we're not, we'll tell you.