In plain English
Choose a South African web design agency by testing how it thinks, scopes and hands work over. Ask for a written diagnosis, named deliverables, accessibility and search requirements, content responsibilities, acceptance tests, ownership, support terms and evidence behind claims. Prefer clear limits and verifiable processes over guaranteed rankings, vague packages or unexplained technical control.
What should a useful agency proposal define?
The proposal should connect a diagnosed business and customer problem to a defined scope. Look for named pages or templates, content responsibilities, integrations, accessibility target, search migration work, analytics, review rounds, acceptance tests, launch process, training, support and exclusions. A long feature list is not a method, and a fixed package may still contain unresolved dependencies. The proposal should also identify the actual delivery team and disclose which specialist or subcontracted roles remain unconfirmed at signing time.
Ask who owns each input and decision, which assumptions affect cost and what constitutes completion. W3C planning guidance recommends clear goals, responsibilities, resources, reviews and acceptance testing, including for agency-delivered work. Use that discipline in procurement. Request a discovery stage when the agency cannot responsibly scope legacy content, integrations or platform constraints from the sales call alone.
Sources for this section: Plan web accessibility.
How can you judge evidence without relying on a polished portfolio?
Ask the agency to explain one relevant project from problem through trade-offs, testing and handover. Confirm which work it performed and whether any results are permissioned, measured and comparable. A screenshot can demonstrate visual output; it cannot prove accessibility, search growth, enquiry quality or commercial impact. References should be contacted only through an agreed and respectful process.
Google's hiring guidance recommends understanding proposed techniques, requesting a technical and search audit, and avoiding guarantees of first place in search results. Apply the same scepticism to conversion guarantees and invented benchmarks. A credible supplier distinguishes delivered work from projections, exposes risks and can show how a claim would be verified rather than asking the buyer to trust confident language. Ask to see the test method or source record behind any claim that materially affects the buying decision.
Sources for this section: Do you need an SEO?.
Which ownership, data and handover questions matter?
Write down who controls the domain, hosting, content system, source code, design files, analytics, advertising tags, third-party licences, backups and administrator accounts. Clarify what the client receives on termination, which services carry recurring fees and how exports or migration work. Avoid shared credentials; require named access, appropriate permissions and an offboarding process. Confirm whether recovery can happen without the agency and how quickly a nominated client administrator can regain control safely after an access failure.
If the agency handles enquiry or analytics information, document purpose, roles, access, vendors, retention, security responsibilities and incident escalation, with appropriate professional review. POPIA establishes conditions for lawful processing and security safeguards; a generic claim of compliance is not an implementation plan. The website owner should know where personal information travels and who can retrieve, change or delete it.
Sources for this section: Protection of Personal Information Act 4 of 2013.
How should you compare shortlisted agencies beyond price?
Use a weighted scorecard built before final presentations. Include problem understanding, proposed method, content support, accessibility, technical quality, search continuity, evidence quality, ownership, support, team availability, total ongoing cost and confidence in assumptions. Score the written evidence, record material concerns and invite clarification. The cheapest build can carry expensive dependencies; the highest fee does not establish capability.
Consider delivery fit in the South African context without inventing a local advantage. Confirm working hours, remote or on-site expectations, payment terms, tax documents where relevant, hosting locations, response coverage and the people who will do the work. Finish with reference checks and a contract review appropriate to the purchase. Select the clearest accountable system, not the most theatrical pitch. Use the same questions with every bidder so charm, familiarity or proposal length does not silently change the standard.
Sources for this section: Plan web accessibility, Do you need an SEO?.
Official references
- Plan web accessibility (W3C Web Accessibility Initiative)
- Do you need an SEO? (Google Search Central)
- Protection of Personal Information Act 4 of 2013 (Information Regulator South Africa)