KEN DESIGNERS — WEBSITE AND SOFTWARE PROJECT BRIEF
Version: 4 October 2026. Original planning template; adapt to your business.
Complete what you know. Mark unknowns for discovery. Do not send passwords,
payment credentials, private customer records or production access in a brief.

1. BUSINESS
Business name:
Business type and location/service area:
Contact person and role:
Existing public website:
Current tools and how the process works:

2. PURPOSE
Problem we want to solve (one real example):
Primary outcome of the first release:
Current baseline, if measured:
How we will judge a useful improvement:

3. USERS AND WORKFLOWS
User roles (customers/staff/managers):
Devices, connection limitations and accessibility needs:
Normal task: starting information -> steps -> expected result:
Exception task: what can go wrong -> expected handling:
Who approves or changes each record:

4. SCOPE
Must work at launch:
Useful but optional:
Later phases:
Pages/templates or record types:
Approximate users/products/branches/data quantities:
Reports/exports needed:

5. CONTENT AND DATA
Text/images/brand assets already approved:
Content still needed and who supplies it:
Editing frequency and responsible staff:
Data sources/formats and anonymised sample availability:
Who validates imported records/totals:
Old URLs or functions that must keep working:

6. INTEGRATIONS
Provider and required business workflow:
Account owner (no credentials):
Access/capabilities confirmed or still unknown:
Pending/failed/duplicate event handling required:
Who reconciles discrepancies:
Provider charges or limits to verify:

7. DELIVERY AND OWNERSHIP
Budget range in KES; tax treatment to clarify:
One-off versus operating-cost allowance:
Target date and reason:
Content/approval deadlines:
Decision maker:
Expected accounts, licences and source rights at handover:
Documentation, training, export and backup/recovery requirements:
Support hours and incident reporting needs:

8. ACCEPTANCE SCENARIOS
For each: role / starting data / action / expected result / approver.
Include a normal task, an error, a permission boundary and a recovery check.
Website: phone enquiry reaches the intended recipient; all agreed links work.
Store: correct variant/price persists; staff can process and reconcile an order.
Software: permissions, reports, imports and exports meet agreed examples.

9. QUESTIONS FOR THE SUPPLIER
Assumptions and exclusions:
Discovery needed before a fixed quotation:
Milestones and review evidence:
Recurring costs, renewal dates and billing currency:
Change-request process:

Discuss your completed brief: https://kendesigners.com/contact/
Websites: https://kendesigners.com/services/website-design-kenya/
Software: https://kendesigners.com/services/custom-software-development-kenya/