KENYA · GUIDE 0149 · EDITION 4.2
Chapati and beans kitchen in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- labour bottleneck
- food holding
Selling every chapati can still leave unwanted beans when combination demand differs from separate-piece purchases, making a single expected meal count unreliable for planning both components.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Trial one short lunch session and cost both chapati production and bean portions.
The pilot scope is: Specify the chapati count and bean serving as a complete lunch, deciding how separately sold chapati or extra beans are recorded so the meal offer remains commercially understandable during service.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Specify the chapati count and bean serving as a complete lunch, deciding how separately sold chapati or extra beans are recorded so the meal offer remains commercially understandable during service. |
| Output acceptable | Have buyers assess chapati texture, bean consistency and portion balance after the usual carrying interval rather than only tasting the meal beside the cooking surface. |
| Costs recorded | Include chapati labour, oil, bean preparation, fuel, containers and component leftovers, measuring complete meal cost without hiding one component's surplus in average kitchen expenses. |
| Buyer response recorded | Record component production, complete meals, separate purchases and leftovers independently, planning the next batch from actual buying combinations rather than assuming every chapati accompanies beans. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| Chapati uneven size | Compare dough weights. | Reportion next batch and reject undersized pieces. |
| Stew wets bread | Check pack separation/leak. | Use suitable separate bread wrapping. |
| Raw dough sampled | Review handling practice. | Stop tasting and clean affected contact surfaces. |
Outstanding go / hold conditions
- Actual recipe/yield and applicable kitchen permissions unverified.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.