KENYA · GUIDE 0597 · EDITION 4.2
Customer database setup in Kenya: Marketing and Finding Buyers
Reach a buyer who can accept the offer
Small businesses organizing existing lawful customer records.
Demonstrate a privacy-aware contact workflow without repurposing customer lists.
Begin with the problem and specification rather than promising a return on investment you cannot establish. The proposed output is: Configure a customer database using minimal fields and approved access.
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:
Create the customer database around actual service needs, defining identifiers, permitted fields, consent information where relevant, user roles, and duplicate resolution responsibility.
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 staff to find a customer, record an interaction, update contact details, and handle a duplicate without exposing records unrelated to their duties.
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 staff to find a customer, record an interaction, update contact details, and handle a duplicate without exposing records unrelated to their duties. |
| Repeat decision | Record field purposes, import mappings, duplicate decisions, access tests, staff retrieval tasks, correction requests, and agreed ownership of future data quality work. |
Use fictional records to test permissions and search before import.
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 database fails when staff create fresh records for every interaction or collect sensitive details nobody needs, making accurate customer history harder to maintain.
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:
Hi [owner], I can build a 100 contact register with clear ownership and tested access roles. Send a redacted sample and the business purpose for each field. We will resolve duplicates and practise export/revocation before live use.
Replace claims with proof of this offer
| Sales claim to substantiate | Evidence before repeating the promise |
|---|---|
| Required result | Owner can revoke access and apply approved retention/correction process. |
| Input suitability | Check current plan limits. |
| Failure to address honestly | Viewer can edit |
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.