KENYA · GUIDE 0594 · EDITION 4.2
Domain renewal support in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Expired domain
- wrong contacts
- unauthorized transfer
A business can lose website and email continuity when renewal notices go to an old employee or payment is assumed rather than confirmed.
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
Audit one authorized domain record and renewal date.
The pilot scope is: Support renewals for domains the client controls, identifying registrar access, registrant contacts, expiry information, billing approval, and website or email dependencies.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Support renewals for domains the client controls, identifying registrar access, registrant contacts, expiry information, billing approval, and website or email dependencies. |
| Output acceptable | Have the owner verify registrar access and renewal confirmation, checking contact accuracy and continuity of dependent services without unnecessarily changing domain configuration. |
| Costs recorded | Include domain inventory, account-recovery support, reminder setup, billing coordination, renewal verification, and troubleshooting where legacy accounts belong to departed staff or suppliers. |
| Buyer response recorded | Keep registrar details, owner access checks, expiry records, approved payments, renewal confirmation, notification recipients, and unresolved dependencies requiring the client's continued attention. |
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 |
|---|---|---|
| Notice names unfamiliar payee | Compare registrar account and independently verified contact. | Pause payment and verify directly. |
| Paid but expiry unchanged | Check exact domain/period and transaction status. | Ask registrar to resolve with receipt. |
| Recovery email obsolete | Check owner-controlled recovery process. | Update through registrar's authorised verification route, never bypass it. |
Outstanding go / hold conditions
- Actual domains, account state, charges and policy unverified.
- No domain renewed, transferred or payment made.
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.