Discovery
We document users, workflows, data, integrations, reports, approvals, security needs and launch requirements. Output: a written scope and delivery plan.
Clear commercial terms before development starts: what discovery covers, what drives cost, how payments are staged, and how support works after launch.
Every project moves through the same commercial path so the estimate matches the actual scope.
We document users, workflows, data, integrations, reports, approvals, security needs and launch requirements. Output: a written scope and delivery plan.
A written proposal with phased scope, deliverables, assumptions, exclusions, timeline and costs. No work starts before approval.
Build and review against agreed milestones, with staged environments, acceptance criteria and change control.
Launch, training and a support arrangement with defined response targets, maintenance windows and improvement planning.
Two projects can look similar on the surface and differ significantly in effort. These are the main cost drivers we scope.
Number of processes, approval steps, exceptions and distinct permission levels.
M-Pesa, bank, SMS, WhatsApp, ERP, accounting, e-commerce, maps, biometric devices and third-party APIs.
Cleaning, mapping and importing historical records from spreadsheets, legacy systems or paper archives.
Operational dashboards, management reports, exports, audit trails and scheduled reporting.
Mobile-friendly capture, offline behaviour, device access and field-team workflows.
Access control, audit requirements, data protection obligations, hosting model and review evidence.
Number of branches, user groups, training needs, parallel running and launch support.
Response targets, coverage hours, monitoring, maintenance windows and planned improvement work.
Defined scope, milestones and acceptance criteria. Suitable when requirements are clear and the organisation needs budget certainty.
A focused first release followed by planned phases. Reduces risk and lets the organisation validate adoption before expanding.
A named team working in agreed sprints on a monthly retainer. Suitable for continuous product development and integrations.
Post-launch hosting, monitoring, backups, security updates, user support, bug fixes and small improvements under an SLA.
Support tiers and targets are agreed in the contract. The framework below shows how coverage is normally structured.
For stable systems with occasional requests.
For systems tied directly to daily revenue or operations.
For platforms where downtime stops the business.
Final response and restoration targets, coverage hours and exclusions are set out in the signed SLA schedule. Review our security and data protection position.
Written requirements, assumptions, exclusions and acceptance criteria.
Functional testing, permission checks, payment edge cases, mobile checks and user acceptance testing.
Administrator training, user guidance and operational runbooks.
Deployment support, monitoring during the first days of live use and a close-out review.
Share the workflow, number of users and integrations you have in mind. We will recommend a discovery scope and an indicative range before you commit.
Custom software cost depends on workflows, user roles, integrations, data migration, reporting, security and support. A fixed list would either under-scope the work or overcharge simple projects. Discovery produces a written estimate tied to a defined scope.
Discovery is a paid, scoped engagement. It produces the requirements, architecture outline, delivery plan and a proposal with phased costs. The discovery fee is confirmed before work starts and can be credited toward the project at our discretion.
Payments are milestone-based and defined in the proposal. A typical structure links payments to discovery sign-off, delivery milestones and launch acceptance rather than one upfront payment.
Changes are handled through a written change-control process that records the request, impact on cost and timeline, and written approval before work continues.
Yes. Most enterprise projects start with a focused first release or a pilot module, then expand after the first workflow is stable and adopted.