Website design cost in South Africa is a scope question, not a package label.

Type "website design cost South Africa" into Google and you will land in one of the most searched, and most ambiguous, phrases in this category. To one supplier it means a homepage layout. To another it means a full marketing website with copy, CMS and analytics attached. To a third it means a logo plus a Figma mockup. Two of those suppliers can quote the exact same phrase and hand you numbers that are not remotely comparable, because they never quoted the same job.

Before comparing a single rand figure, name the job precisely. Are you buying brand exploration, wireframes, high-fidelity UI, a CMS-backed build, copywriting, photography direction, CRM wiring, or some combination of all of it? Design is the part you see first. The thing you are actually paying for is a working system that explains your offer, earns trust and captures a mobile enquiry.

Nexus prices platform websites at Launch from R3,000, Business from R5,500 and Pro from R8,000. Custom development starts from R5,000, ecommerce from R7,500. Treat those as starting positions for a defined scope, not a promise that every SME needs an identical shape of site.

Page count tells you almost nothing on its own. Ten near-identical service pages built from one template can be cheaper to deliver than four pages that each need a different journey, a calculator, a gated download and a booking flow. Ask how many genuinely unique templates and responsive states are being designed and tested, that number, not the sitemap length, sets the price.

Content readiness is a cost driver wearing a design disguise. When the messaging is unresolved, a designer ends up building visual structure around copy nobody has actually approved, then rebuilding it once stakeholders finally agree on the offer. That second pass is not a design failure, it is discovery work, and it should show up on the invoice as exactly that.

Conversion mechanics belong in this same conversation, not a separate one. Forms, WhatsApp paths, confirmation states, analytics events and where proof sits on the page are not decoration layered on top of the design. For most SMEs, they are the actual reason a website gets bought in the first place.

• Number of unique templates and complex components
• Brand assets available vs brand work still unfinished
• Copywriting, photography and content migration ownership
• Integrations: CRM, booking, payments, WhatsApp, analytics
• Accessibility, multi-language and compliance requirements
• Revision process, stakeholder count and approval speed

A design-only engagement can genuinely help when a build team already exists in-house, or when information architecture needs to be settled before anyone commits to a platform. It is a bad fit when you expect a live, working website at the end and the quote never once mentions build, CMS, hosting handover or QA, that gap does not disappear; it just shows up later as a second invoice you did not plan for.

Watch for beautiful mockups that no realistic budget can actually implement. A Figma file full of custom animation, a unique layout on every single page and no plan for who manages the content can force an expensive rebuild the moment reality meets the design system. Ask directly whether the design is buildable, affordably, on the platform you intend to use.

If brand identity is still unresolved, settle it before deep website design begins. Skip that step and you pay twice, once for exploratory UI built on shaky foundations, and again once colours, type and messaging finally settle and half the layout no longer fits.

1. Write the business outcomeOne sentence: who should enquire, buy or book, and what must be true on launch day.
2. Count unique templates, not nav itemsList homepage, service template, about, contact, blog/article, landing and any special components.
3. Assign content ownershipWho supplies approved copy, images, logos, policies and product data, and by which dates?
4. List conversion and measurementForms, WhatsApp, calls, thank-you states, GA4 events and CRM routing should appear explicitly.
5. Normalise commercial termsOnce-off vs 12-month total, hosting, revisions, support window, exclusions and acceptance criteria.

• “Unlimited pages” with no template or content model defined
• Stock homepage only, no service-page or conversion thinking
• No mobile QA, analytics, redirects or form testing mentioned
• Design delivered as images with no CMS or editable structure
• SEO rankings or lead volume promised inside a design quote
• Brand identity assumed finished when only a logo file exists
• Monthly price with no disclosed total or ownership terms

Low price is not the risk. Buying a broad commercial outcome while paying for a narrow visual deliverable is the risk.

Nexus website design procurement principle

Plenty of SMEs add a city to the search (Johannesburg, Cape Town, Pretoria, Durban) because they want a supplier who understands local context and can be held accountable in person. Location genuinely matters for workshops, photography sessions and industry familiarity. It should not automatically double the price for work that a remote-capable team handles just as well over a call and a shared document.

Judge a local supplier on process clarity and evidence of relevant work, not proximity alone. A disciplined remote delivery rhythm with strong written briefs often beats a vague local relationship built mostly on being reachable for coffee. If on-site brand photography or in-person workshops are genuinely needed, price those as their own explicit sessions rather than folding them into a vague "local premium."

Start with the national cost logic in this guide, then add local logistics on top only where they are real. Templates, content, integrations and ownership still decide most of the number.

A founder collected three quotes for the same brief: "Quote A" at a low headline price, "Quote B" in the middle, and "Quote C" noticeably higher. The founder’s first instinct was to go with Quote A on price alone, until running all three through a version of the comparison sheet above.

Quote A covered five templated pages with no content, analytics or mobile QA mentioned anywhere, a genuinely different, narrower job than the other two. Quote C included a full brand refresh the founder had not actually asked for, inflating the price for work outside the real brief. Quote B, once scoped precisely to the actual need (service pages, a working enquiry flow, basic tracking, no unnecessary brand work) turned out to be the most accurately priced for the job actually being bought, not simply the middle number by coincidence.

Design stops being vanity the moment it changes how fast a visitor understands, trusts and decides to act. People judge in seconds whether a business looks organised, relevant and safe to contact, and weak hierarchy, inconsistent spacing, unclear CTAs and a slow mobile layout quietly suppress enquiry rate even while traffic looks perfectly healthy in analytics.

That is exactly why conversion UX deserves a seat in the design conversation rather than a bolt-on afterward. Proof placed near the CTA, service scope written in plain language, contact paths visitors can actually find and a calm visual hierarchy are commercial decisions dressed up as aesthetic ones. Treat them as commercial decisions in the brief.

After launch, let real behaviour drive the next round: which sections get skipped, where mobile visitors give up, whether forms silently fail, and whether people prefer WhatsApp to email. Iterate from evidence, not from another round table debating font weight.

If you are early in the process, write a short website brief and run a cost calculator to frame the scope before you collect three quotes. If quotes already exist, put them onto the comparison sheet above before arguing about which one "looks nicer", that argument is much shorter once the scope is actually comparable.

Nexus can point you toward Launch, Business, Pro, custom or ecommerce once the commercial job is clear. The goal is a site you can launch, measure and improve, not the most decorative proposal sitting in your inbox.

Keep the signed scope as your change-control baseline once work starts. A new page idea that surfaces mid-project should be classified as in-scope, deferred, or re-quoted, that single habit is what keeps a design project calm and commercially honest instead of a slow-motion argument about "but I thought that was included."