User, device, and outcome
Who is the Kenya user, what must they finish, what devices and network conditions matter, and what evidence proves success?
Project packet / eight operating questions
Before asking for a technology or date, write down what the customer does, what the server records, what the provider confirms, what staff must see, and how everyone recovers when the expected path breaks.
Operating lanes
Who is the Kenya user, what must they finish, what devices and network conditions matter, and what evidence proves success?
Which fields are essential, who decides the purpose, who processes them, where they move, and who resolves ODPC or registration questions?
Which provider relationship exists, what methods and callbacks are supported, and who owns settlement, refunds, disputes, and support?
What queue, status, manual correction, report, alert, phone or messaging support, and recovery path must exist behind the customer screen?
Runbook
Show the workflow, URLs, screenshots, messages, spreadsheets, source, sample records, provider references, and known failures.
Name business, language, data, provider, tax, content, technical, acceptance, release, incident, and customer-support owners.
Choose devices, browsers, data cases, connection constraints, payment states, staff actions, accessibility checks, and production proof.
Define backup, staging, cutover, rollback, monitoring, measurement, reconciliation, handoff, and when the result will be reviewed.
Call or email after preparing the facts. Faith Forge Labs still reviews scope, access, safety, screening, lawful delivery, timing, and the evidence needed for acceptance.