KENYA · GUIDE 0610 · EDITION 4.2
Refurbished computer sales in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Stolen inventory
- Hidden hardware failure
Refurbished sales lose trust when all units share a flattering generic description despite different battery condition, missing ports, or faults not revealed before purchase.
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
Buy a small verified lot only after checking ownership, repairability and likely buyer needs.
The pilot scope is: Sell refurbished computers with documented condition, tested functions, included accessories, software status, known limitations, and clear repair or return terms appropriate to the supplied device.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Sell refurbished computers with documented condition, tested functions, included accessories, software status, known limitations, and clear repair or return terms appropriate to the supplied device. |
| Output acceptable | Ask buyers to try realistic work tasks, checking battery where applicable, ports, display, storage, keyboard, and connectivity against the condition description rather than cosmetic appearance. |
| Costs recorded | Include acquisition, diagnosis, replacement parts, cleaning, legitimate software, test time, failed units, packaging, and the support exposure attached to each individually described refurbished device. |
| Buyer response recorded | Record device identifiers, acquisition condition, repairs, tested functions, disclosed limitations, included items, buyer acceptance, returns, and supplier patterns that affect future refurbishment purchasing decisions. |
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 |
|---|---|---|
| One unit differs | Compare serial/spec sheets. | Correct that advertisement individually. |
| Old owner files remain | Check authorised sanitisation evidence. | Stop resale and resolve securely. |
| Adapter overheats/damaged | Inspect matched specification/condition. | Stop use and obtain safe compatible replacement. |
Outstanding go / hold conditions
- No units sourced, sanitised or tested; software support/licensing requires verification.
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.