How to Brief a Web Agency So You Get a Website That Actually Works for Your Business

The biggest reason South African service businesses end up with websites they are quietly disappointed in has nothing to do with the agency's design skills. It has to do with the quality of the brief they were given at the start. If you hand over a vague set of ideas and a competitor's URL you admire, you will get a website built around assumptions. Some of those assumptions will be wrong, and you will only discover that after you have signed off and paid.

Before you approach any agency, get clear on one thing: who is the person most likely to contact you through this website, and what do they need to know before they will trust you enough to reach out? Not your ideal client in a broad marketing sense, but the specific person sitting at a desk in Sandton or Cape Town or Durban who has a problem you solve and is trying to decide whether you are worth calling. Write that person down in a paragraph. What is their role, what have they probably already tried, and what would make them hesitate to enquire? That paragraph is more useful to a web agency than a mood board.

Next, list every action you want a visitor to take on your site, and rank them in order of importance. Most service businesses actually want one or two primary actions: a phone call, a contact form submission, a quote request. Secondary actions might include downloading something, reading case studies, or finding a location. When this hierarchy is unclear, designers fill pages with equal-weight buttons and calls to action that compete with each other and confuse visitors. Your ranked list removes that guesswork.

Then gather your operational constraints before the first meeting. Do you have an existing booking system, accounting platform, or CRM that the website must connect to? Are there compliance requirements in your industry that affect what you can say or how you must display certain information? Do you need the site to function in multiple languages? These are not details you raise at the end of a project. They affect technology choices, timelines, and cost from day one.

When it comes to content, be honest with yourself about who will write it. Many website delays in South Africa are caused not by agencies missing deadlines but by clients who have not produced their text or images. If writing is not your strength, say so upfront and ask what content support the agency offers, or budget separately for a copywriter. A website built on placeholder content almost always ends up with placeholder results.

Ask the agency to explain, in plain language, how the site will be found by people searching for your services. This does not require a deep technical conversation. You simply want to understand whether basic search visibility is included in the build, what form it takes, and what ongoing effort it requires after launch. If the agency cannot explain this clearly, that is useful information.

Finally, establish who owns what when the project is done. Who holds the domain, who can access the hosting account, who controls the content management system login. In South Africa, businesses occasionally find themselves locked out of their own digital assets when a relationship with an agency ends. Ownership of these elements should be documented before work begins, not negotiated after a dispute arises.

A well-prepared brief does not slow down a project. It removes the back-and-forth that adds weeks to timelines and frustration to both sides. The clearer you are before work starts, the more likely the finished site reflects your business accurately and earns its place in your growth strategy.