βWe need a website. How much will it cost?β is a reasonable first message, but it is rarely enough to begin a dependable web project. A clinic may need enquiries routed to the right branch. A manufacturer may need a product catalogue. A school may need admissions information that parents can find on a phone. Those are different jobs, even if each begins with the word βwebsiteβ.
A useful web design brief helps a Kenyan business turn a broad intention into decisions a designer, developer and internal team can act on. It does not need to be a polished strategy document. It needs to be honest about the goal, the audience, the content, the operational constraints and who will approve the work.
That clarity protects both sides. It helps the business receive a proposal based on the work it actually needs, and it helps the web team avoid building a beautiful site that cannot answer the customerβs most important question.
Begin with the decision the website should support
Do not start with colours, competitor screenshots or a list of pages. Start with the business outcome. Is the website meant to generate qualified enquiries, support online sales, explain a complex service, reduce repetitive customer questions, recruit staff, process bookings or establish credibility before a sales meeting?
Choose a primary objective and a small number of supporting objectives. A site can serve several purposes, but everything cannot be equally urgent. When the goal is lead generation, the project should prioritise clear service pages, contact routes, response handling and measurement. When the goal is ecommerce, product data, payment flows, delivery policy and stock operations need early attention.
Describe success in observable terms without inventing targets. βA visitor can request a site visit from a phoneβ is a stronger starting point than βmake the website modernβ. The first statement can be designed, tested and assigned to an owner.
Describe the people who need to use it
A web design brief should identify the real audiences rather than a vague βeveryoneβ. Consider customers, prospects, distributors, parents, job applicants, existing clients and internal staff. For each priority group, record what they are trying to do, what information they need before acting and what could make them hesitate.
Context matters. A Nairobi buyer looking for a professional service may want proof of expertise, a clear scope and a consultation route. A customer comparing products may need price, specifications, delivery terms and a simple way to ask a question. A person using a mobile device with an unstable connection needs an experience that does not depend on heavy media or a long, complicated form.
Use actual customer questions from sales calls, emails, WhatsApp conversations and support tickets. They are usually more useful than generic persona language because they reveal what the new website must explain.
Set the project boundaries before discussing the build
Scope is the difference between a manageable web project and an endless collection of late requests. List the pages, functions and integrations that are included in the first release. Be specific about whether the work includes copywriting, photography, product entry, translation, search migration, hosting, analytics, training, ongoing maintenance or advertising landing pages.
For example, βa website with five pagesβ leaves too much open. A more useful scope might name Home, About, three service pages, a contact page, a blog template, enquiry form, analytics setup and a short administrator handover. If ecommerce is required, note product count, product variations, payment provider, delivery rules, customer accounts and who will maintain inventory.
Separate future ideas from launch requirements. A booking portal, membership area or customer dashboard may be valuable, but it should be planned as a later phase if it cannot be defined or tested properly now. This is not about shrinking ambition; it is about protecting the first release from avoidable risk.
Bring the content inventory to the first conversation
Many web projects slow down because the layout is ready but the business cannot supply approved text, images, product details, legal information or contact details. A brief should identify what already exists, what needs updating and who is responsible for providing it.
Collect brand assets, approved logo files, colour or type guidance, service descriptions, product data, staff biographies, photographs, certificates, testimonials with permission, location information, policies and existing brochures. Also list content that should not be reused because it is outdated, inaccurate or owned by another supplier.
Good copy depends on decisions. A web writer cannot safely fill missing information with claims about pricing, delivery, results, qualifications or coverage. Assign an internal subject-matter reviewer early, give them a review deadline and decide who has final approval.
Map the essential customer journeys
A page list is not enough. The team should know how a person reaches the site, what they see next and how the business handles the resulting action. Draw the journeys that matter most: a Google search to an enquiry, an Instagram link to a booking, a returning client to a support page, or a paid advert to a product checkout.
For each journey, define the entry page, the reassurance needed, the intended action, the confirmation shown and the internal response. Check where the form data goes, who receives phone or WhatsApp enquiries, how quickly someone responds and whether staff can see the information they need.
Our article on why business websites fail to generate leads is a useful reminder that traffic alone does not create a reliable enquiry process. The website and the business response need to work together.
Give useful references, not a design scavenger hunt
Reference websites can be helpful when the brief explains what is being referenced. Say whether you like the navigation, the service-page structure, the photography style, the way a form works or the level of detail in the copy. A folder of unrelated screenshots gives a designer little insight into the reason behind a preference.
Also state what should be avoided: excessive animation, a style that feels too corporate for the audience, stock imagery that does not fit the market, or a layout that makes important information hard to find. Avoid asking for an exact copy of another companyβs design. The goal is to learn from a pattern, not reproduce somebody elseβs intellectual property or brand identity.
Decide how local trust will be represented
Kenyan buyers often want practical signs that a business is reachable and accountable. The right signals depend on the organisation, but may include a real service area, a clear phone number, customer-service hours, team information, verified testimonials, physical-location details, delivery terms or a straightforward explanation of how consultations work.
Use genuine local imagery where possible and do not present an unrelated Western office as if it were the businessβs premises. If people appear in new photography or stock imagery, choose representations that fit the audience and do not lean on stereotypes. The same care should apply to language, currency, address formats and contact channels.
Plan for search, performance and accessibility early
Search optimisation, speed and accessibility are easier to build into a structure than to bolt on at the end. Record important existing URLs, pages that attract enquiries, paid campaign destinations, relevant search terms and any planned changes to the domain, CMS or navigation. A redesign should not casually remove content that customers or search engines still use.
If the project changes URLs or platforms, treat it as a migration with a documented inventory and redirect plan. Our website migration SEO checklist explains the practical controls around redirects, analytics and launch testing.
Accessibility decisions are equally concrete: readable contrast, heading structure, descriptive labels, keyboard access, alt text and usable error messages. Use the website accessibility checklist to turn this part of the brief into testable requirements rather than a general promise.
List the technical and operational constraints
A developer needs to know who controls the domain, hosting, DNS, email, analytics, payment accounts, CRM and third-party tools. Make a secure access plan; do not place passwords in a general project brief. Confirm whether licences or subscriptions are current, whether a previous supplier retains access and whether the business owns the accounts that matter.
Note integrations such as payment gateways, booking software, inventory systems, email platforms, maps, live chat, customer portals or member areas. Explain the desired outcome and the system owner, not merely the tool name. An integration can affect data protection, testing, support, cost and project timing.
Also agree on maintenance. A launch is not the end of a websiteβs operational life. Someone must update software, monitor backups, renew domains, manage forms, review content and respond to security issues. The practical priorities in our website maintenance checklist can help turn that responsibility into a plan.
Make approval and feedback workable
Projects lose time when several people offer contradictory feedback without a final decision-maker. Name one primary contact and one person with authority to approve milestones. Agree how feedback will be collected, how long reviews may take and what counts as a change to agreed scope.
Ask reviewers to respond to the goal and user journey, not only personal taste. βThe admissions information is hard to find on mobileβ is actionable. βMake it popβ is not. Where stakeholders disagree, return to the documented audience, business objective and evidence from actual customer questions.
Test before the launch announcement
The brief should reserve time for testing. Check major pages on phones and desktops, complete forms, verify notification emails, test calls and WhatsApp links, review spelling and prices, confirm map locations, check policies, test purchases or bookings where relevant and make sure analytics events are recorded.
Use realistic test cases. A successful homepage load does not prove that a customer can complete a critical action. For ecommerce, follow a product through selection, payment response, confirmation and fulfilment notification. For lead generation, check the whole route from form submission to staff acknowledgement.
Ask every proposal to state its assumptions
Two proposals can appear to cover the same website while assuming very different responsibilities. One supplier may expect the client to provide final copy, photography and product data before design begins. Another may include content planning, image sourcing and data cleanup. The brief should ask each bidder to state what is included, excluded, dependent on the client and priced separately.
Request a milestone plan tied to decisions and deliverables rather than a single launch date. Useful milestones might include discovery approval, content readiness, wireframe approval, design approval, development review, content migration, testing, training and launch. Ask what happens when client feedback is late, a third-party integration changes or content arrives after the approved milestone.
Comparisons should also account for ownership and ongoing cost. A lower build quotation may rely on paid plugins, proprietary templates or subscriptions that the business must renew. A more expensive proposal may include migration, accessibility checks, analytics, training and post-launch support. The brief does not need to choose the answer in advance; it needs to make the assumptions visible enough for a fair decision.
Protect ownership, privacy and handover
State that the business should control its domain, hosting account, analytics property, advertising accounts and essential third-party services, with named administrators and a documented handover. Suppliers can have appropriate access without becoming the only people able to renew a domain, retrieve a backup or see performance data.
List the personal information the website will collect through enquiries, recruitment, purchases, bookings, newsletter forms or customer accounts. That inventory helps the team design suitable notices, permissions, retention and access controls. The Office of the Data Protection Commissionerβs guidance on consent is an authoritative Kenyan reference, but a website project team should not substitute general design advice for legal review where the processing is sensitive or complex.
Define the handover evidence expected at launch: administrator accounts, source and design files where agreed, licence records, backups, DNS notes, integration documentation, analytics access, a list of renewals and a short training record. Confirm what support is available after launch, what counts as a defect and what becomes a new change request.
Plan redesign risks before approving visual change
If the project replaces an existing site, add a factual inventory of current URLs, downloadable files, forms, analytics events and pages that attract organic traffic or paid visits. Decide which content moves, combines or retires. Googleβs site-move guidance recommends preparing URL mappings, implementing appropriate redirects and monitoring both old and new URLs. Those tasks belong in scope before development, not in a rushed launch-day note.
Ask the team to change fewer major systems at once where practical. A new domain, new CMS, new URL structure, rewritten content and redesigned customer journey create several possible causes if traffic or enquiries fall. A phased plan may not always be possible, but the brief should at least identify the combined risk and reserve time for monitoring.
Accessibility acceptance criteria should also be explicit. W3C guidance on labelling form controls, for example, turns a vague requirement into something that can be reviewed. A brief that names testable requirements gives designers and developers a fair target and gives the owner a meaningful basis for acceptance.
A web design brief checklist
- Primary business objective and priority audience.
- Top customer questions and essential journeys.
- Included pages, features, integrations and future phases.
- Content inventory, owners and approval dates.
- Brand assets and useful, explained references.
- Existing URLs, campaign pages and migration needs.
- Domain, hosting, analytics and third-party account ownership.
- Accessibility, mobile, performance and security requirements.
- Project contact, approver, review process and launch tests.
- Ongoing maintenance and support responsibilities.
Give the project a decision-ready start
The best web design briefs do not pretend that every decision is already made. They identify what matters, expose the gaps that need an answer and give everyone a shared basis for scope, cost and delivery. That makes the first proposal more useful and the eventual website more likely to support real business work.
Dot Digital can help shape the brief, audit the current site and deliver web design services in Kenya around a clear customer journey. Bring the questions your customers ask most often; they are usually the right place to start.







