16 July 2026 · Kenya Web Studio

How a small-business website turns visits into useful enquiries

A practical guide to service pages, proof, mobile contact routes, forms and tracking for Kenyan businesses that need qualified enquiries rather than anonymous traffic.

Begin with the enquiry your team can answer

A website cannot fix an undefined sales process. Decide what a useful enquiry contains before arranging the homepage. A fabricator may need the site location, approximate measurements, finish and installation date. A law firm may need the practice area and a safe way to request a call without publishing confidential facts.

Write down what your team asks during the first phone call. Those questions reveal which pages, photographs and form fields the website needs. They also expose details that should not be requested online. Keep the first form short enough to finish on a phone, then collect sensitive documents through an agreed private channel.

Choose one primary action for each page. A visitor reading an itinerary may ask for a trip quote. Someone viewing a completed office fit-out may request a site visit. Sending both visitors to a vague contact page adds work and strips away context.

Match each page to a specific buying question

A homepage introduces the business. It rarely has enough room to answer every service question. Create service pages for offers that differ in buyer, scope or enquiry details, then give each page a clear path to related work.

Page names should use the language customers use. Internal labels such as solutions, capabilities or experiences can hide useful information. A heading such as steel gate fabrication in Nakuru tells the visitor and the search engine what the page covers.

Location pages need substance. Describe the actual service area, delivery or site process and local project constraints. Swapping town names in the same paragraph produces pages that help nobody and may compete with the stronger national page.

State who the service is for and what is delivered.
Explain the information needed before work starts.
Link two or three relevant projects with written scope details.
End with the next action and what happens after submission.

Project proof needs captions and scope

A gallery of attractive screenshots or photographs asks the buyer to infer too much. Add the project type, location where publication is permitted, work completed and a short explanation of the problem. If the website included a catalogue, booking path or payment method, say so plainly.

Separate delivered features from measured business results. Mobile-first design, M-PESA checkout and structured quote forms describe the work. Claims about lead growth, revenue or search position require before-and-after data. Do not turn a guess into a percentage.

The strongest project page lets a buyer inspect the live work, read the decisions behind it and see where the same approach might fit their business. When a client site blocks embedding, use a current screenshot and a direct link instead of an empty frame.

Mobile contact routes need visible choices

Kenyan business traffic often arrives on a phone, but mobile-first work involves more than stacking desktop sections. Buttons need enough space, text needs a readable size and galleries should not force several megabytes of downloads before the contact details appear.

Offer the contact methods the business can maintain. WhatsApp suits quick questions and sharing a location. A written brief suits projects with several requirements. Phone calls suit urgent clarification. Displaying every channel is useful only when someone responds consistently.

Tell the visitor what follows. A short line such as 'We reply within one business day with the next sensible step' removes uncertainty. Avoid countdowns, fake availability and automatic claims that a quote will be ready before anyone has read the scope.

Keep important controls at least finger-sized and clearly labelled.
Use input types that open the correct mobile keyboard.
Do not make WhatsApp the only route for a detailed brief.
Test the entire form on a small Android-sized viewport.

Measure completed actions, not button decoration

Analytics should record WhatsApp, phone and email clicks, but those events do not prove that a conversation happened. Treat them as contact intent. Count a contact form only after the server stores it, and count a booking only after the system creates the appointment record.

Keep the original campaign source with the lead. Useful fields include the UTM campaign, source, medium, Google click ID, first landing path and referrer host. Do not copy the visitor's email, phone or message into Google Analytics.

Review leads by quality. A keyword that produces ten price-shopping chats may be less useful than one that produces two detailed requests inside the working budget. Connect advertising reports to the actual enquiry record instead of judging campaigns by click-through rate alone.

Fix the page where the enquiry breaks

Read real enquiries and compare them with the page that produced them. Repeated questions usually point to missing content. Requests outside the service area may require a clearer location statement. Briefs without measurements may need one extra form field or a checklist beside the form.

Performance matters at this stage. A heavy project gallery can delay the page long enough for a mobile visitor to leave. Resize photographs, serve modern formats, lazy-load media below the first screen and watch Core Web Vitals on the production domain rather than a development server.

Make one change at a time when traffic is limited. Rewrite the service introduction, adjust the form or add a project example, then examine the next set of qualified enquiries. Changing the page, ad and offer together makes the result hard to interpret.

Need this fixed on your site?

Start a project