KENYA · GUIDE 0630 · EDITION 4.2
Coding clubs in Kenya: Marketing and Finding Buyers
Reach a buyer who can accept the offer
Parents, schools or adult beginners seeking structured introductory programming practice.
Show an original demo project and work through approved school or guardian channels.
Begin with the problem and specification rather than promising a return on investment you cannot establish. The proposed output is: Host coding clubs that produce small original projects and safe learning habits.
Make the first message specific
Explain what you will deliver, what is excluded and what the prospect needs to confirm before a quotation. Use this scope when preparing a sample, demonstration or introduction:
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.
Ask who approves purchases, who accepts the output and how payment is arranged. These can be different people. An informal recommendation is useful for an introduction but does not replace the buyer's approval.
Use proof that matches the promise
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.
Keep approved examples, inspection records or handover evidence that demonstrate this result. Obtain permission before using a customer's name, photograph, premises or work. Do not invent reviews, imply an endorsement or display private contact details as marketing proof.
Follow the lead through to collection
| Stage | What to record |
|---|---|
| Contact | Source of the introduction and permission to follow up. |
| Qualified enquiry | Required specification, buying authority and timing. |
| Quotation | Scope, exclusions, price, delivery and payment stages. |
| Accepted result | 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. |
| Repeat decision | Keep project intentions, learner explanations, debugging attempts, prompts, collaboration observations, account barriers, and independent changes that indicate what the next club activity should reinforce. |
Run one session creating a small interactive program with a clear learning objective.
Review what it cost to obtain and fulfil a paying order, including travel and follow-up. High enquiry counts do not compensate for a route or delivery arrangement that loses money. Keep cancellations, complaints and refusals visible when evaluating a channel.
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.
Expand outreach only when the promised scope can be delivered reliably. Use permission-based follow-up and an achievable response time instead of bulk unsolicited messages.
A scope-led outreach draft
The supplied draft below is ready to adapt, not a message already sent:
Hi [school], I can facilitate an original Scratch collect-star session where six learners build, test and privately save a working project. Please confirm equipment and safeguarding arrangements before booking.
Replace claims with proof of this offer
| Sales claim to substantiate | Evidence before repeating the promise |
|---|---|
| Required result | Expected score three then zero; keep files private. |
| Input suitability | Test save/reopen before session. |
| Failure to address honestly | Score never resets |
Remove placeholders and replace assumed prices with an approved scope and actual cost estimate. Do not advertise technical certification, current stock, guaranteed income or results you cannot substantiate. Record enquiries, accepted quotes, declined quotes, delivered orders and collected balances separately; a sent message is not a sale.