The Scenario: A 40-Person Services Firm Buying Its Third Website
Picture a 40-person engineering consultancy outside Johannesburg. Their 2018 page-builder site still loads, but the enquiry form goes to a personal Gmail address, the domain is registered in the web designer's name, and nobody knows how to add a team member. The MD has approved a replacement budget but doesn't know where to start. This is a commissioning playbook for that decision-maker: how to define what you need, compare build paths, write a brief developers can quote against, and what to insist on in the contract so you own your digital assets. Every ZAR figure is an indicative estimate, clearly labelled as such, because no authoritative dataset for South African SME website costs exists.
Why SME Website Development in South Africa Goes Wrong Before a Single Line of Code
The most common failure is not technical. It is a mismatch between what the business thinks it is buying and what the developer thinks it is building. The business says 'we need a modern website'; the developer hears 'redesign the homepage'. Nobody defines what it must achieve commercially: how many enquiries, from which audience, through which channels. Without that shared definition, scope creeps and the result is judged on aesthetics rather than results.
Warning: If your brief does not state what a successful enquiry looks like (a form submission, a phone call, a WhatsApp message), every later decision becomes a matter of taste. Taste cannot be tested or budgeted.
A second error is treating the website as a one-off project rather than an asset needing maintenance and measurement. Our firm never budgeted for ongoing changes, so the site froze in 2019; when they wanted a new service line, the developer had disappeared and the CMS login was lost.
What an SME Website Is Actually For: Enquiries, Not Brochures
For most SMEs the website is the first filter in a sales process. A prospect searches, lands on a page, and decides within seconds whether to make contact. That depends less on visual polish than on clarity: does the page answer the visitor's question, and is the next step obvious? An enquiry-focused site typically has three components: a clear value proposition on every landing page, a frictionless contact mechanism (form, phone, WhatsApp), and credibility evidence (client names, case studies, certifications). It is also cheaper to maintain than a media library of brand assets: fewer pages, simpler navigation, less custom design. The success metric is not 'traffic' but 'qualified enquiries per month'.
The Commissioning Playbook, Step One: Agree the Commercial Goal and Enquiry Path
Before speaking to any developer, write your commercial goal in one sentence, e.g. 'Generate 20 qualified enquiries per month from Gauteng-based manufacturers' or 'Allow existing clients to book service calls online'. Then define the enquiry path: a contact form, phone number, WhatsApp link, calendar booking, or quote request. Each has implications for POPIA consent and measurement. For a services firm it is often a form landing in a shared inbox with a CRM notification; for a retailer, a WhatsApp click or phone call. Write it down; it becomes page one of your brief.
Step Two: Build the Page and Content Inventory Before Requesting Quotes
Quotes vary wildly because each developer estimates a different number of pages. Produce a page inventory: Home, About, Services (three to five sub-pages), Case Studies, Team, Contact, Privacy Policy, plus POPIA legal pages such as a cookie policy and, if applicable, a PAIA manual. For each page, note whether copy and images exist or must be created. This prevents the 'we assumed ten pages' conversation mid-project and helps you cut pages nobody will maintain, like a blog that goes stale after three posts. If you don't have a content plan, don't budget for the page.
Step Three: Decide the Build Path - DIY Builder, Freelancer, Small Agency or Retainer Partner
There is no single right way to build an SME website. The best path depends on internal capacity, budget, and how much you value ongoing support. The four common options are a DIY template builder (e.g., Wix, Squarespace), an independent freelancer, a small agency, or a retainer partner handling both build and ongoing optimisation.
Comparing the Four Build Paths on Cost, Control and Maintenance Burden
| Build path | Indicative ZAR range (setup) | Control & ownership | Ongoing maintenance burden | Best for |
|---|---|---|---|---|
| DIY template builder | R2,000 - R8,000 per year (subscription) | You own the account but are locked into the platform | You do everything; limited support | Very small businesses with strong internal admin and simple needs |
| Freelancer | R15,000 - R45,000 once-off | Varies; insist on domain and hosting in your name | Ad hoc, often hourly; availability risk | Businesses with a clear brief and modest customisation needs |
| Small agency | R40,000 - R120,000 once-off | Generally good if contracted properly | Support retainer or ad hoc; documented handover | SMEs needing design, development and some strategy in one package |
| Retainer partner | R60,000 - R200,000+ build, plus monthly retainer | Full handover with training; ongoing partnership | Managed by partner; proactive maintenance and improvements | Businesses treating the website as a revenue asset with continuous optimisation |
These ranges are indicative, exclude VAT, and will vary with complexity. The cheapest option is rarely the lowest total cost of ownership: a R5,000 DIY site consuming 40 hours of your time per year is not cheaper than a R40,000 agency build that runs itself.
Tip: Ask each supplier to quote on the same page inventory and integration list. Otherwise you are comparing apples to oranges.
What Drives Website Cost in ZAR: The Variables That Move the Quote Most
Page count is the most obvious variable: doubling unique page templates can double design and development effort. Copywriting matters: if you cannot supply final text, the developer may charge for content creation or leave placeholder text that never gets replaced. Integrations (CRM, email marketing, payment gateways, booking systems) add complexity and testing time. Custom design typically costs more than customising a theme. Ecommerce adds product setup, payment rails, and tax rules. Compliance work (POPIA consent, accessibility) is often quoted separately, if specified at all.
Step Four: Write a Brief a Developer Can Quote Against Accurately
A good brief is a specification, not a wish list. It should include the commercial goal, page inventory, integrations, content responsibilities, ownership requirements (domain, hosting, CMS), compliance requirements (POPIA, accessibility), and the measurement plan. State your budget range so the developer can scope to fit rather than over- or under-scoping. If you have a preferred CMS (e.g., WordPress), say so; if not, ask the developer to justify their recommendation. The brief becomes the basis for the contract and protects both parties from scope disputes.
Step Five: Non-Negotiables for the Contract - Ownership, Access and Handover
The most expensive mistake an SME can make is not owning its own digital assets. Before signing, insist that the .co.za domain is registered in your business name through a ZACR-accredited registrar, with you as registrant contact. The hosting account must be in your name, even if the developer manages it. The CMS administrator account must be handed over with credentials and training. Third-party integrations (payment gateways, CRM, email platforms) must be documented with account ownership clarified. Include a support clause specifying response times and costs for post-launch fixes.
Warning: If the developer refuses to register the domain in your name or hand over admin access, walk away. You are not buying a website; you are renting one.
POPIA and Your Website: What the SME Must Specify at Brief Stage
The Protection of Personal Information Act (POPIA) governs how you collect, store, and use personal information from visitors. Common non-compliance points: contact forms collecting data without a consent checkbox or privacy policy link; cookie banners setting analytics cookies before consent; newsletter signups that don't explain how data will be used. At brief stage, specify that the developer must implement a consent management solution for cookies, ensure all forms include a privacy policy link and explicit consent where required, and document data retention rules. The Information Regulator has published guidance on direct marketing and consent; your developer should know it.
Also consider whether your site targets children, handles special personal information, or transfers data across borders (e.g., a US-based email provider). Each scenario adds POPIA obligations. A brief that says 'POPIA compliant' is meaningless; one that lists the specific forms, cookies, and data flows is actionable.
Accessibility and Core Web Vitals as Contract Requirements, Not Afterthoughts
Accessibility and performance are easier to design in than to retrofit. Specify a baseline of WCAG 2.2 Level AA: alt text, sufficient colour contrast, keyboard navigability, and form labels. This widens your audience and reduces legal risk. For performance, require that the site meets Google's Core Web Vitals thresholds (LCP, INP, CLS) on mobile. INP replaced FID in March 2024, so any developer still quoting FID is out of date. Write these into the contract with a testing protocol (e.g., a Lighthouse audit before sign-off). Deep performance optimisation is covered in our page speed article, but the baseline must be contractual.
The .co.za Domain and Hosting Decisions That Affect South African Visitors
A .co.za domain signals local presence and builds trust, but has specific registration rules. The .za space is administered by ZADNA, with registrations handled through accredited registrars. Ensure your developer uses a registrar that lets you manage DNS records yourself, or at least provides clear documentation. For hosting, decide whether to host in South Africa or use a global provider with edge caching. Local hosting can reduce latency for South African visitors, but a well-configured CDN can mitigate overseas hosting. Ask the developer to justify their recommendation based on your audience location.
Step Six: Measuring Outcomes in Enquiries, Calls and WhatsApp Clicks
Traffic is a vanity metric. The metrics that matter are form submissions, phone calls (tracked via call tracking numbers or click-to-call events), WhatsApp clicks, and quote requests. Set up event tracking in Google Analytics 4 (or an alternative) for each. If you use Google Ads or Meta Ads, ensure conversion tracking is configured correctly and, where possible, server-side. Prebo Digital's custom reporting approach focuses on these bottom-funnel actions rather than sessions. A simple monthly report showing enquiries by source is enough to start.
Common Ways South African SMEs Lose Money After Launch
Three common leaks: (1) neglecting updates, leading to security vulnerabilities and plugin conflicts; (2) ignoring mobile experience, driving away the majority of visitors; (3) failing to maintain content, so the site becomes outdated and loses credibility. Budget for a maintenance retainer or allocate internal time; a site that isn't updated is slowly dying.
What a Good Handover and Support Arrangement Looks Like
A proper handover includes a credentials document (domain registrar, hosting, CMS, FTP/SFTP, database, third-party services), a recorded training session, a sitemap and page inventory, documentation of custom code and integrations, and a support agreement with defined SLAs. Insist on a post-launch warranty period (e.g., 30 days) during which bugs are fixed at no cost. After that, a maintenance plan should cover updates, backups, security scans, and a set number of content changes per month. A retainer partner like Prebo Digital can add value here, but even with a freelancer, get the handover in writing.
Building a Site That Survives Its First Two Years Without a Rebuild
A website that lasts is built on a stable platform, documented, and maintained. Choose a CMS with a long track record and a large talent pool (e.g., WordPress) so you are not dependent on one developer. Avoid custom-built systems unless you have a technical team to support them. Keep the design simple and modular so pages can be added without a redesign. Most importantly, treat the site as a product, not a project: assign an internal owner, set a quarterly review, and measure enquiries relentlessly. Follow this playbook and your third website will be the last one you need to commission for a while.
