KENYA · GUIDE 0581 · EDITION 4.7
Small business website building in Kenya: Delivery Planning and Acceptance Checks
Editorial update: 28 October 2026 · Business planning reference · Review scope
Plan delivery around observable acceptance
Plan the handover and acceptance record for small business website building, using the specific checkpoints for the example offer.
This is a planning reference for small business website building. The order below is an invented teaching case. It is not a completed customer job, an operating approval or a prediction of demand or earnings.
The example offer and its boundary
Fictional website WEB-81 builds a five-page site for 'Mtoni Cycle Workshop', a made-up bicycle repair business: home, services, process, about and contact. Original sample home copy: 'Bicycle repairs by appointment. Tell us the problem and bring your bicycle for assessment; staff confirm work and price before starting.' The enquiry form requests name, one callback method and a short message. Output is a staging prototype, approved live build only when authorised, owner handover and test log. Payments, customer accounts, booking automation and guaranteed search traffic are excluded.
This page is a work-control sheet. It does not teach a qualified trade, prescribe a food process, approve equipment or replace the appropriate technical procedure. Confirm who has the competence and authority for any specialist task.
Prepare the control record
| Stage to schedule | Checkpoint from the scoped example | Actual record to complete |
|---|---|---|
| Write page/task scope | Do not publish fictional sample facts or claim an address/credential the client has not verified. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Build accessible structure | Keyboard users can reach links and form controls in logical order with visible focus. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Implement enquiry handling | Browser-only required fields are not sufficient; success is shown only after genuine accepted submission. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Test full journeys in staging | The authorised owner receives the test enquiry; failed network/server cases do not falsely say sent. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Release and teach ownership | No DNS/live change occurs without authority; owner can access/recover the site without relying on developer's personal account. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
Keep accepted and unresolved work separate
| Issue to watch for | Evidence question |
|---|---|
| Form displays sent but no message arrives | Check server response, delivery logs and recipient configuration. |
| Menu fails with keyboard | Check focus order and interactive controls. |
| Owner cannot renew domain | Check registrar ownership/recovery contact. |
The issues above are prompts to investigate, not a diagnosis of a real defect. Record what was observed, isolate the affected output where appropriate, and refer the technical decision to the competent person or approved process. Do not copy a hypothetical response into a real incident without assessment.
Reconcile the handover
Use the agreed charging basis: website project. Record ordered, completed, accepted, held and rejected output separately. Track rework time, changed scope, credits and collection dates against the same order reference. No DNS/live change occurs without authority; owner can access/recover the site without relying on developer's personal account.
Proceed within a defined trial limit only after the buyer's acceptance, actual full costs and collections are recorded, and the guide's unresolved checks are addressed. The final business-specific checkpoint is: No DNS/live change occurs without authority; owner can access/recover the site without relying on developer's personal account. Otherwise record a hold, revision or stop decision in file 10.
References and their limits
Forms Tutorial — W3C WAI
Labels, instructions and clear form structure. Reference check recorded 2026-10-26.
Client-side form validation — MDN
Browser validation can be bypassed; server-side checks are also required for submitted data. Reference check recorded 2026-10-26.
Images Tutorial
Purpose-based text alternatives; does not validate marketing performance. Reference check recorded 2026-10-26.
Rights Of A Data Subject
Kenyan privacy principles and data minimisation; not a complete compliance assessment. Reference check recorded 2026-10-26.
Recorded references support only the scope stated beside them. They do not prove current supplier stock, a local quotation, actual buyer demand, operator competence or the feasibility of this particular business. Later editorial changes do not refresh earlier source-check dates.
Prepared by Business Starter Guides using AI-assisted drafting and desk editorial checks. Independent operator trials and specialist certification are not claimed. See the editorial method for the review scope.
Editorial method and evidence limits