KENYA · GUIDE 0581 · EDITION 4.2
Small business website building in Kenya: Marketing and Finding Buyers
Reach a buyer who can accept the offer
Owner-managed firms needing a manageable web presence.
Show owners a task-focused prototype and separate setup from ongoing costs.
Begin with the problem and specification rather than promising a return on investment you cannot establish. The proposed output is: Build a small business website around verified services and a clear enquiry task.
Make the first message specific
Explain what you will deliver, what is excluded and what the prospect needs to confirm before a quotation. Use this scope when preparing a sample, demonstration or introduction:
Build a small site around the buyer's main customer action, with approved content, account ownership, hosting responsibility, and maintenance scope.
Ask who approves purchases, who accepts the output and how payment is arranged. These can be different people. An informal recommendation is useful for an introduction but does not replace the buyer's approval.
Use proof that matches the promise
Ask a new visitor to find services, contact the business, and submit a test enquiry on phone and desktop without guidance.
Keep approved examples, inspection records or handover evidence that demonstrate this result. Obtain permission before using a customer's name, photograph, premises or work. Do not invent reviews, imply an endorsement or display private contact details as marketing proof.
Follow the lead through to collection
| Stage | What to record |
|---|---|
| Contact | Source of the introduction and permission to follow up. |
| Qualified enquiry | Required specification, buying authority and timing. |
| Quotation | Scope, exclusions, price, delivery and payment stages. |
| Accepted result | Ask a new visitor to find services, contact the business, and submit a test enquiry on phone and desktop without guidance. |
| Repeat decision | Record customer journeys, form deliveries, owner edits, device issues, approval changes, and unresolved maintenance responsibilities before the site's agreed handover. |
Build a fictional-data prototype of the key enquiry page.
Review what it cost to obtain and fulfil a paying order, including travel and follow-up. High enquiry counts do not compensate for a route or delivery arrangement that loses money. Keep cancellations, complaints and refusals visible when evaluating a channel.
A finished site fails commercially when enquiries reach an unattended mailbox or the owner cannot update essential opening and contact details.
Expand outreach only when the promised scope can be delivered reliably. Use permission-based follow-up and an achievable response time instead of bulk unsolicited messages.
A scope-led outreach draft
The supplied draft below is ready to adapt, not a message already sent:
Hello [owner], I can build five clear pages around one reliable repair enquiry, with owner-controlled access and a tested handover. Please confirm your actual services, address and who answers enquiries. I will show a fictional-data staging version first and separate build cost from hosting and maintenance.
Replace claims with proof of this offer
| Sales claim to substantiate | Evidence before repeating the promise |
|---|---|
| Required result | No DNS/live change occurs without authority; owner can access/recover the site without relying on developer's personal account. |
| Input suitability | Read actual plan limits, charges and export/backup options before quoting. |
| Failure to address honestly | Form displays sent but no message arrives |
Remove placeholders and replace assumed prices with an approved scope and actual cost estimate. Do not advertise technical certification, current stock, guaranteed income or results you cannot substantiate. Record enquiries, accepted quotes, declined quotes, delivered orders and collected balances separately; a sent message is not a sale.