KENYA · GUIDE 0032 · EDITION 4.2
Sage growing in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- misidentification
- thin demand
A highly enthusiastic chef can still require very little sage, so treating culinary interest as substantial weekly volume may produce stock with no suitable outlet.
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
Secure sample feedback before dedicating more than a small growing area.
The pilot scope is: Restrict the first sage planting to a named culinary use and a buyer who can explain expected leaf character, instead of assuming general herb demand.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Restrict the first sage planting to a named culinary use and a buyer who can explain expected leaf character, instead of assuming general herb demand. |
| Output acceptable | Have the intended cook use a delivered sample in the actual dish and comment on flavour balance, leaf condition and preparation effort before accepting repeat supply. |
| Costs recorded | Include customer development time and the cost of maintaining unsold specialist plants, rather than extrapolating sales from a positive tasting by someone without regular demand. |
| Buyer response recorded | Keep a recipe-use note, sample quantity, paid reorder size and time between purchases, using demonstrated consumption to decide whether more nursery or growing space is justified. |
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 |
|---|---|---|
| Plant identity uncertain | Compare original supplier documents and qualified identification | Hold food sales until culinary identity is resolved. |
| Leaves arrive folded and bruised | Inspect pack volume and loaded transport pressure | Use a wider looser pack and recheck on a small delivery. |
| Stems inflate pack weight | Open a sample and weigh stalk removal | Remove stalks before net packing and correct the affected run. |
Outstanding go / hold conditions
- Culinary identification, local production and food handling need validation.
- No medicinal directions, current plug price or growth yield promised.
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.