Digital
Your Website Is Not a Brochure
A brochure is finished when it is printed. A business website has jobs to do every day: being found, earning trust, capturing enquiries, and passing them into the rest of the business intact.
- By
- NairobiX Editorial
- Published
- Reading time
- 7 min read

On this page
- 01The brochure model, and why it persists
- 02The seven jobs a business website actually does
- 03Performance is part of the experience
- 04The enquiry form: where most of the value is won or lost
- 05What most business websites get wrong
- 06A realistic example
- 07A practical audit for your own site
- 08Key takeaways
- 09Sources
The brochure model, and why it persists
Many business websites are built like printed brochures: a home page, an about page, a services page and a contact page, designed once, launched, and left alone. The logic is understandable. A website used to be a statement that the business exists. For a long time, that was enough.
Today the website is usually one part of a longer path. Someone sees an advert, hears a recommendation or searches for a problem; visits the site to check the business is credible; then sends a message, fills in a form or taps through to WhatsApp. If the site does its part poorly — or does it well but drops the enquiry at the handoff — the marketing that brought the visitor is wasted.
The seven jobs a business website actually does
On the website
- 01Discovery
- 02Trust
- 03Conversion
- 04Capture
- 05Qualification
Depends on connected systems
- 06Handoff
- 07Measurement
1. Discovery — being found for the right problems
People search for problems and needs, not company names. Pages that genuinely answer those questions are how new customers find a business. Google's guidance is to create helpful, reliable, people-first content — written primarily to help readers rather than to manipulate rankings — and it asks whether a reader will leave feeling they learned enough to achieve their goal [3].
2. Trust — being credible quickly
Visitors decide fast. Nielsen Norman Group's analysis of page-visit data found that users often leave pages within 10 to 20 seconds, but that pages which communicate a clear value proposition can hold attention far longer [1]. Credibility comes from specifics: what the business does, for whom, where it is, who is behind it, and how to reach a person — not from adjectives.
3. Conversion — making the next step obvious
Every important page should answer “what do I do now?” with one primary action. Offering five equal options is the same as offering none.
4. Capture — turning interest into a record
Forms, booking tools and chat links are where interest becomes an enquiry. They should ask only what is needed, work flawlessly on a phone, confirm clearly what happens next, and never lose what the visitor typed.
5. Qualification — understanding the enquiry
A few well-chosen questions — what the enquiry is about, rough timing, the kind of business — let the team prioritise and prepare. Too many questions reduce completions; too few leave the team guessing. The balance depends on the value of the enquiry.
6. Handoff — passing the enquiry on intact
This is where many websites fail invisibly. A form that sends an email to an inbox nobody watches, or a WhatsApp link that arrives without context, breaks the chain. Enquiries should arrive in the system the team actually works from — ideally a CRM — with their source attached.
7. Measurement — learning what works
Page views alone say little. The useful questions are which pages and sources produce enquiries, which enquiries become customers, and where visitors abandon the path. That requires tracking actions, not just visits, and connecting them to outcomes in the CRM.
Performance is part of the experience
A slow or unstable page undermines trust before a visitor reads a word, and many visitors in Kenya browse on mobile connections of varying quality. Google defines three Core Web Vitals and publishes a “good” threshold for each [2].
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading — when the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness — how quickly the page reacts to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability — how much the layout jumps while loading | 0.1 or less |
Google recommends measuring at the 75th percentile of page loads, separately for mobile and desktop [2].
The most common culprits on small-business sites are oversized images, heavy themes and plug-ins, third-party scripts added over the years, and content that moves as it loads. Most are fixable without a redesign.
The enquiry form: where most of the value is won or lost
Of all the elements on a business website, the enquiry form does the most direct work and gets the least design attention. Every field is a small cost to the visitor and a small benefit to the business. The question for each one is whether the benefit is worth the cost at this stage of the relationship.
| Field | Why the business wants it | Usually |
|---|---|---|
| Name | To address the person properly | Ask |
| Phone or WhatsApp | The fastest route to a reply in most Kenyan markets | Ask |
| For proposals and documents | Ask, or make optional if phone is given | |
| What the enquiry is about | To route it and prepare — best as a short list of options | Ask |
| Timing | To prioritise urgent enquiries | Ask if it changes who responds first |
| Budget | To qualify | Often better asked in conversation |
| Company size, job title, address | For segmentation | Rarely worth it on a first enquiry |
NairobiX analysis for typical service businesses. High-value B2B enquiries can justify more questions; simple bookings need fewer.
Three details matter as much as the fields themselves. The form should say what happens after it is submitted — who will respond, and how. It should keep what the visitor typed if something goes wrong, rather than clearing the form. And it should confirm receipt immediately, on the page and ideally by message, so the visitor is not left wondering whether it worked.
Accessible to everyone who might buy
The Web Content Accessibility Guidelines are the international reference for making websites usable by people with disabilities; version 2.2 became a W3C Recommendation on 5 October 2023 [4]. Its additions include a minimum size — or enough spacing — for targets such as buttons and links, and not asking people for the same information twice in the same process [5]. For a business, the practical translation is simple: visible labels on every field, error messages that explain how to fix the problem, enough contrast to read in sunlight, and buttons large enough to tap accurately. These choices help every visitor on a phone, not only those using assistive technology.
What most business websites get wrong
- Describing the company instead of the customer's problem. Visitors arrive with a need; the page should meet it.
- Generic claims. “Quality service” and “customer satisfaction” say nothing. Specifics — what, for whom, how, where — build credibility.
- Contact as an afterthought. A contact page at the end of the menu is not a conversion strategy.
- Forms that go nowhere useful. Enquiries emailed to a shared inbox with no owner or reminder.
- No measurement of outcomes. Knowing traffic but not which visits became customers.
- Launch and leave. A site that is never updated, tested or improved slowly stops doing its jobs.
A realistic example
Illustrative example
A private school's admissions site — a composite, fictional example
A private school's website has attractive photography and a downloadable prospectus. Enquiries arrive through a form that emails the admissions office. Admissions staff say most enquiries come “from the website”, but nobody knows which pages or campaigns bring them, and some parents say they never heard back.
Working through the seven jobs, the school finds that the fees and admissions pages — the ones parents most want — are hard to find on a phone; the form asks for eleven fields; and form emails go to an address checked twice a week. The changes are practical: clear admissions and fees pages written around parents' questions, a shorter form with the child's intended year and start term, an immediate confirmation explaining next steps, enquiries created directly in the admissions CRM with their source, and a follow-up reminder for staff.
None of this needed a new visual design. It needed the website to be treated as the first stage of the admissions process rather than as a brochure.
A practical audit for your own site
Twenty minutes, on your phone
- Open your home page. Within ten seconds, is it clear what you do, for whom, and where?
- Find your main call to action on three key pages. Is there one clear next step on each?
- Submit your own contact form. Where did it go, who saw it, and how long until someone responded?
- Tap your WhatsApp link. Does the message arrive with enough context to reply well?
- Run your key pages through Google PageSpeed Insights and check the three Core Web Vitals.
- Check whether you can see, for last month, which sources produced enquiries — and which produced customers.
Key takeaways
- 01A business website is an active part of the sales path, not a static statement.
- 02Its seven jobs: discovery, trust, conversion, capture, qualification, handoff and measurement.
- 03Speed and stability are part of credibility; Google publishes clear thresholds to aim for.
- 04The most costly failures are often invisible — at the handoff after the form is submitted.
Where NairobiX works on this
Sources
Numbered references in the text point to the sources below. Frameworks, examples and passages marked “Analysis” are NairobiX's own reasoning; examples are composites, not real clients.
- [1]How Long Do Users Stay on Web Pages? — Nielsen Norman Group, 2011
- [2]Web Vitals — web.dev (Google)
- [3]Creating helpful, reliable, people-first content — Google Search Central
- [4]WCAG 2.2 is a web standard (“W3C Recommendation”) — W3C Web Accessibility Initiative, 5 October 2023
- [5]What's new in WCAG 2.2 — W3C Web Accessibility Initiative