What Should a Small Business Website Include?
The pages, content and practical features that help customers understand your business and take action.
Read the guideA clear brief helps you get a useful quote, avoid unnecessary revisions and build a website around what your business actually needs.

Prepare your business goal, intended customers, essential features, available content, budget range and preferred launch date. You do not need a finished website plan. A good designer can help shape it, but they need accurate information about your business to make useful recommendations.
Hiring a web designer goes more smoothly when you arrive with clear goals, content and examples. This guide shows what to prepare.
Many business owners postpone contacting a web designer because their photographs are not finished, their company profile needs work or they do not know how many pages they need. Others request a quote with little more than “I need a professional website.” Neither extreme makes the process easier.
The useful middle ground is to know what you want the website to achieve, gather the information you already have and clearly identify what you need help creating. Your designer can then separate the website build from additional work such as copywriting, photography or brand development.
This checklist is for South African businesses planning a first website or replacing an existing one. It is designed to help you have a more productive conversation, not to turn you into a technical project manager.
| Prepare before asking for a quote | Agree before production begins |
|---|---|
| Your main business goal | What the website will deliver and how it will be checked. |
| Services and intended customers | Page structure, messaging and contact journeys. |
| Essential features | Detailed behaviour, integrations and exclusions. |
| Available text and images | Who creates, reviews and supplies missing content. |
| Budget and preferred date | Scope, payment milestones, dependencies and delivery dates. |
“Look modern” describes an appearance, not an outcome. Start with the action that matters most. Do you want visitors to request a quote, book an appointment, buy products or check your credibility before calling?
Choose a primary goal, then explain the supporting tasks. A consultancy may need qualified enquiries and a credible project portfolio. A salon may need bookings, clear service information and directions. Those requirements lead to different page structures.
Tell your designer who normally buys from you, what they ask before committing and what makes them choose one provider over another. Include the areas you serve and any limits on availability, delivery or project size.
Illustrative brief: “We provide commercial cleaning for offices in Pretoria. We want facilities managers to request a site assessment. They usually ask about service schedules, staff supervision and which areas we cover.”
This gives the designer more useful direction than “make it corporate.” If you are planning a local business website, our web design in Pretoria and Pretoria North pages are relevant starting points for discussing your requirements.
You do not have to arrive with a perfect sitemap. List the information customers need to make a decision. That might include services, project examples, company background, frequently asked questions and contact details.
Page count is only one part of the scope. A simple page with a telephone number is a different job from a booking page that manages staff availability, deposits, confirmations and cancellations.
Separate launch essentials from later additions. This helps a provider suggest a workable first phase without quietly excluding something you thought was included.
You can explore our web design and development services to frame the discussion, but you do not need to choose technical tools before your requirements are understood.
Your designer needs to understand the substance of the page before they can judge the layout. A short explanation, a long service description and a detailed product catalogue cannot simply be swapped into the same space without consequences.
Gather your business name, service descriptions, contact details, operating hours and service areas. Add the questions customers ask repeatedly and any process information that helps people understand what happens after they contact you.
If you need copywriting, say so at the quotation stage. Rough notes or a conversation can be a useful starting point, but writing and fact checking still require time. Nominate someone who can approve technical claims, prices and service details.
Keep original images rather than sending only compressed screenshots. Let your designer prepare appropriately sized web versions. Do not download photographs from another company’s site and assume they are available for your use.
Bring two or three website references and describe what you like: readable typography, clear service navigation or how project work is presented. Also mention anything you dislike. References should guide the conversation, not become instructions to copy someone else’s website.
Our website portfolio can help you discuss presentation and functionality. Focus on what would help your customers, rather than asking for every effect you see.
A realistic budget discussion helps the designer prioritise. Explain what you can allocate to the initial project and ask which ongoing costs are separate, such as hosting, software licences, maintenance or content work.
Do not compare quotes only by the final total. Check who writes the content, how many revisions are included, which functions are covered and whether migration, testing and training are part of the proposal.
A launch tied to an exhibition, opening date or campaign needs a different plan from a flexible refresh. Tell the designer about the event early and distinguish a preferred date from a genuine business dependency.
Ask what must be supplied before the delivery timeline starts. Missing photographs, delayed approvals or incomplete product information can affect the schedule even when the designer’s work is progressing.
Several stakeholders can contribute, but the designer needs a clear approval route. Combine feedback into one agreed response and separate factual corrections from preferences. This reduces contradictory instructions and repeated revisions.
If you already have a website, record the providers that manage your domain, hosting, business email and content system. Confirm who owns the accounts and who can grant access. Do not assume your current designer controls all of them.
For the initial conversation, an account inventory is usually more useful than a collection of passwords. When access is needed, use individual invitations and the minimum permissions appropriate to the task where supported. Avoid placing passwords in the project brief or a general email thread.
Keep your business as the account owner wherever practical. Agree on what happens to access, licences and ongoing services if your working relationship with the provider ends.
List the pages and features that must remain available. Identify important content, downloads, enquiry routes and business email dependencies. Ask who will handle migration, backups and any changed page addresses before approving the project.
Never assume that replacing the website also requires replacing the domain or disrupting your business email. Those changes should be discussed explicitly rather than becoming an unexpected part of launch day.
“SEO included” needs a definition. Ask whether the quote covers page titles, content structure, internal links, indexing checks or migration planning, and whether ongoing optimisation is separate.
Provide the services and locations you genuinely want to be found for. Share customer questions in their own words. You do not need to supply a list of repeated keywords or ask for a separate page for every nearby suburb.
Google advises businesses to ask providers about their approach, communication and expected results, and warns against guaranteed first place rankings. See Google’s advice on choosing SEO support. A useful proposal promises defined work, not control over search results.
Ask what support is included after launch and for how long. Fixing a defect in an agreed feature is different from requesting a new feature. Defining that distinction early helps both sides.
You can use the following outline for a short project brief. Clear bullet points are enough. Mark anything you do not yet know as “needs discussion” instead of inventing an answer.
This is enough to start a useful conversation. The designer should ask follow up questions, identify gaps and turn the agreed requirements into a written scope before substantial production work begins.
No. Bring what you have and explain what is missing. Agree on who will write and approve the content, whether that work is included and when it must be ready. Final content can affect layouts and delivery dates.
A rough list of information and customer tasks is enough to start. Your designer can recommend a page structure. Ask the final proposal to specify what is included so that page count and functionality are not left ambiguous.
Not necessarily. Explain what you already have and let the technical requirements inform the hosting discussion. Keep ownership and billing arrangements clear if the provider helps set up an account.
Some providers offer branding as an additional service. Ask whether it is included, what files you will receive and when it needs to be approved. Do not assume a website quotation automatically covers logo design.
Ask who controls the domain and hosting, what website access you receive, which licences are transferable and how you can move to another provider. Get the answers in writing before work starts.
A clear explanation of your business, customers and main website goal. Everything else becomes easier to prioritise when the designer understands the job the website needs to do.
You do not need to arrive with a finished design or technical specification. You do need an honest picture of what your business needs, what you already have and where you want guidance.
That gives your designer something concrete to respond to. It also helps you judge whether their proposal addresses your priorities, rather than simply offering an attractive website with an unclear scope.
Elev8Web provides web design, development and SEO services for South African businesses. Learn about the agency or explore our work.
Tell us about your business, the website you need and what you already have prepared. We can help you identify the next steps.
Keep reading. See all guides.
What Should a Small Business Website Include?
The pages, content and practical features that help customers understand your business and take action.
Read the guideHow Much Does a Website Cost in South Africa?
Understand what affects a website quote and what to consider beyond the initial build.
Read the guideAI Website Builder or Professional Developer?
Compare the tradeoffs in control, flexibility and support before choosing how to build your website.
Read the guide