Outcome
What must a real user complete, and what evidence proves it?
Project brief
Bring enough context to define a responsible Kenya scope.
There is no intake form and no automated promise. Work through the questions below, then call or email Faith Forge Labs directly.
People and place
Who is contracting, operating, approving, and using the system in or around Kenya?
Language
Current baseline: English; Kiswahili content by agreement Who owns final content and native-language review?
Data
Current starting point: Kenya's Data Protection Act requires a current assessment of controller and processor registration, lawful basis, notice, sensitive data, transfers, rights, retention, security, and breach reporting. What data is actually necessary?
Commerce
Current starting point: KES, VAT and digital-service rules, eTIMS invoices, customer status, M-Pesa or other provider access, reconciliation, refunds, and foreign settlement require current review. Who confirms the final model?
Systems
What exists today, who owns access, and what must remain available during the change?
Timing
Kenya is seven or eight hours ahead of Georgia and does not use seasonal clock changes. Who owns decisions, releases, incidents, and support outside the overlap?
Specialist review
Which questions need local legal, tax, sanctions, export, language, accessibility, security, or regulated-industry expertise?
Direct contact