KENYA · GUIDE 0597 · EDITION 4.2
Customer database setup in Kenya
Configure a customer database using minimal fields and approved access.
A CONCRETE EXAMPLE · ILLUSTRATIVE
Fictional database CRM-97 organises 100 business contacts with ContactID, organisation, approved contact channel, relationship owner, enquiry status and permission/source note. SampleC0042 belongs to a business contact supplied by client, not scraped leads. Output is restricted database, duplicate-review queue and staff exercise. Marketing sends, identity enrichment, credit scoring and unlimited retention are excluded.
Who is the first customer?
Small businesses organizing existing lawful customer records.
Test the offer
Use fictional records to test permissions and search before import.
What your operating pack contains
- A business-specific operating guide PDF
- Offline itemised costing and quotation tool
- Supplier request and sales message drafts
- Job-card and quality-response documents
- Offline operations desk: supplier comparison, work checkpoints, accepted deliveries and cash tracking
- Cashflow and launch review: downside scenarios, break-even, 13-week cash plan and trial decision
- Source register and unresolved checks
Delivery and quality
Roles limit access appropriately and record counts reconcile.
Cost drivers
- records
- cleanup
- permission complexity
Use your own supplier quotations. Worked figures in the pack are illustrative and do not establish a verified startup budget or profit forecast.
Evidence and scope
Rights Of A Data Subject ↗
Kenyan privacy principles and data minimisation; not a complete compliance assessment. · Checked 2026-10-26
Share and manage access to files and folders — Google Drive ↗
Folder/file access inheritance and restricted sharing; actual permissions must be tested. · Checked 2026-10-26
Keeping leading zeros and large numbers — Microsoft ↗
Import identifier columns as text to preserve zeros and precision. · Checked 2026-10-26