Start with the operation, not the screens
The strongest software projects begin with how work actually moves: who approves, what gets recorded, where money changes hands, and what reports leadership needs at month-end.
Before choosing frameworks or colours, document users, edge cases, approvals, and the mobile journeys that matter most. A law firm needs contact conversion and practice credibility. A property operator needs units, tenants, and rent visibility. A fintech needs ledger discipline from day one.
The planning checklist
Use this checklist in your first discovery conversations — whether you work with Afri-Silicon or another partner.
1. Users and roles
List every person who touches the system: customers, agents, branch staff, managers, auditors. Define what each role can see, create, approve, and export. Role confusion is the most common source of rebuilds.
2. Mobile journeys first
Identify the three tasks that must work perfectly on a phone. For a SACCO, it might be deposit, statement, and loan application. For property, it might be listing search, tenant payment, and maintenance request. Design these before admin dashboards.
3. Money movement and records
If money is involved, map every state: initiated, pending, confirmed, reversed, reconciled. Define who can trigger each transition and what audit trail is required. M-Pesa integrations belong in scope conversations early — not as a phase-three surprise.
4. Integrations and notifications
SMS, email, WhatsApp, payment gateways, accounting exports, and third-party APIs should be listed with priority. Kenyan operations often depend on SMS confirmations and M-Pesa callbacks — treat them as core infrastructure.
5. Reporting and compliance
Define what leadership needs weekly and monthly. For regulated sectors, note data retention, export requirements, and Kenya Data Protection Act considerations upfront.
6. Release phasing
Split the vision into releases: a focused MVP that solves one operational pain, then modules for growth. Afri-Silicon typically scopes a 6–10 week MVP after a 2-week discovery sprint with a fixed proposal.