KENYA · GUIDE 0147 · EDITION 4.2
Githeri lunch kitchen in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- fuel use
- low selling price relative to labour
Large cooked yield creates false confidence if portions vary or customers expect additions outside the quoted price, reducing returns despite a busy lunchtime queue.
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
Test one service window and measure cooked yield from weighed inputs.
The pilot scope is: Choose a githeri portion and accompaniment arrangement for a defined lunch window, agreeing whether buyers expect a standalone meal or a base with separately priced additions when ordering.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Choose a githeri portion and accompaniment arrangement for a defined lunch window, agreeing whether buyers expect a standalone meal or a base with separately priced additions when ordering. |
| Output acceptable | Have customers assess an ordinary serving for ingredient balance, texture and portion satisfaction, testing the same preparation and holding routine used during the actual service rather than a special sample. |
| Costs recorded | Include ingredient sorting, soaking or preparation, cooking energy, accompaniments, containers and unsold cooked food, deriving the serving cost from observed cooked yield and paid accepted portions sold during service. |
| Buyer response recorded | Record weighed inputs, usable cooked output, portion count, accompaniment use and end-of-service remainder, linking customer comments to the actual batch and meal format sold in the pilot lunch session. |
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 |
|---|---|---|
| Beans remain firm | Review established preparation/cooking process. | Do not serve underprepared batch; competent cook resolves. |
| Too little greens | Weigh cooked yield separately. | Prepare safe replacement or disclose shortage. |
| Portions vary | Check scale tare/scoop. | Reweigh sample and correct packing. |
Outstanding go / hold conditions
- No recipe trial, actual yield or safety validation performed.
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.