KENYA · GUIDE 0630 · EDITION 4.7
Coding clubs in Kenya: Customers and Market Demand
The buyer and the buying decision
Parents, schools or adult beginners seeking structured introductory programming practice. The offer to test is: Host coding clubs that produce small original projects and safe learning habits.
Run coding clubs around age-appropriate projects, available devices, learner starting points, safeguarding arrangements, and a clear balance between guided work and independent problem solving.
Separate interest from an accepted order
Run one session creating a small interactive program with a clear learning objective.
The purpose of this test is to establish whether the buyer accepts the specified result, delivery arrangement and payment terms. An encouraging interview does not establish repeat demand. Ask what the buyer currently uses, what would make them change supplier and who has authority to approve the first order. Record a refusal as carefully as an enquiry so that unsuccessful offers do not disappear from the evidence.
Collect evidence specific to this offer
Keep project intentions, learner explanations, debugging attempts, prompts, collaboration observations, account barriers, and independent changes that indicate what the next club activity should reinforce.
| Question to resolve | Evidence to retain |
|---|---|
| What exactly will the buyer accept? | Ask learners to explain and change their own project, checking what happens when an input changes rather than accepting a copied working program as learning evidence. |
| What is included in the first trial? | Run coding clubs around age-appropriate projects, available devices, learner starting points, safeguarding arrangements, and a clear balance between guided work and independent problem solving. |
| How will a prospect see the offer? | Show an original demo project and work through approved school or guardian channels. |
| What must happen before repeating the trial? | Participants can describe and modify the code; do not promise employment or advanced competence. |
Decide whether to continue
Review the specification with the buyer before committing to tools or stock. A trial is commercially useful only if actual costs, rejected work, time spent and cash collected can be reconciled. A club looks productive but teaches little when every child reproduces the same demonstration and cannot explain why their program behaves differently after a small change.
If a buyer changes the required output, record a new scope and re-cost the test. Do not count a request for a different product as proof of demand for the original one. Keep personal contact details in your private records and use customer statements publicly only with permission.
Turn the example into a buyer test
Fictional CODE-130 runs a 90-minute six-learner Scratch club using an original collect-star game. Green flag sets score to zero and moves star to a random position. Clicking star changes score by one and moves it again. Output is each learner's saved project plus a reset/click test record, not a public child profile.
| Buyer discussion | Evidence to retain |
|---|---|
| Specification to confirm | No child account creation or public publishing without authorised process. |
| Output to inspect | Expected score three then zero; keep files private. |
| Failure that can defeat acceptance | Score never resets |
Ask the buyer to describe one acceptable and one unacceptable result. Record the decision maker, price basis, quantity, handover point and payment date privately. A sample request, an encouraging conversation and an accepted order are different evidence. Keep the first commitment within your demonstrated capacity; no customer interview or successful trial is asserted here.
What a failed test should change
Inspect green-flag stack.. If the offer cannot meet that check, revise the specification or process before promising a repeat. Keep rejected offers and reasons in the same register as positive replies so that your record does not exaggerate demand.