Business website planning helps you agree on the purpose, content and scope of a project before design begins. For a small business in Kenya, a useful website should explain the offer, answer common questions and make enquiries straightforward. A written brief gives both the business owner and designer a shared starting point.
This article expands the planning stage of our web design and branding guide. Use it to prepare for a first website or identify what your existing site needs to do better.
Define the main visitor and action
Describe your typical customer in practical terms: what are they trying to arrange, what information is missing, and what would make them hesitate? A transport buyer may need routes and shipment requirements. A restaurant visitor may need the menu, location and booking details.
Choose one main action for each important page. Examples include requesting a quote, booking a consultation or viewing a specific service. Secondary actions can help, but five equally prominent buttons make the decision harder. Write button labels that explain the destination.
Build a page map around real questions
A homepage should introduce the business and guide visitors into detail. Service pages explain what is included, who the service suits and how to begin. An About page gives relevant background, while a portfolio demonstrates the work. Contact information should remain easy to find from all of them.
For example, a business offering both website and graphic design benefits from separate service pages because customers arrive with different needs. Educational articles then explain related decisions without making the service pages excessively long. Our web design page shows the service side of this structure.
Prepare content before detailed design
Gather your business description, service details, contact information, logo files and approved photographs. For every proposed page, write the question it answers and the action it supports. Note what you already have and what still needs writing or photography.
Use genuine examples wherever possible. If an image is a design concept or illustration, label it accordingly. Do not invent testimonials to fill a layout. Missing proof is a reason to simplify a section, rather than publish claims the business cannot support.
Separate essentials from later improvements
Start with the features needed to complete the main customer journey. A service website may need an enquiry form and a clear portfolio before it needs a customer portal. List optional additions separately and explain which business problem each one solves.
Compare proposals using the same scope: page count, copywriting, image sourcing, mobile layouts, revisions, form setup, training and ongoing care. Ask who owns the domain and where recurring charges appear. A low initial quote is difficult to evaluate if these items remain unclear.
Plan for hosting and ownership
Keep your domain registration, hosting access and business email under accounts the business can recover. Agree on appropriate access for your designer. Khush Design Tech uses Namecheap; our Namecheap hosting guide explains what to check before launch.
Allow time for content review, technical setup and testing. A launch date depends partly on when photographs, approvals and access arrive. Record those dependencies alongside the design schedule instead of treating them as last-minute tasks.
Agree on acceptance checks
Ask someone unfamiliar with the project to find a service and send an enquiry on a phone. Check the destination inbox, confirmation message, navigation and contact links. Review headings and page organisation against the W3C page structure guidance so the layout remains understandable beyond its visual appearance.
Use the mobile design checklist during this review. Record concrete issues, such as a hidden submit button, rather than vague feedback such as “make it modern”.
Your first planning task
Create a one-page brief with your audience, main action, essential pages, available assets and unanswered questions. Review relevant examples in our portfolio, then send your project brief. A clear starting point helps turn design decisions into useful business outcomes.