Build
Custom software & information systems
When the problem is a process rather than a brochure. Enrolment, membership, licensing, case management, inspection and reporting: the systems an organisation runs on every day, built so that the people who use them do not need a manual.
Who this is for
You have a process that currently runs on a spreadsheet, a WhatsApp group and somebody’s memory. It works until the person who understands it is on leave, and nobody can answer a question about last quarter without opening four files.
A county issuing permits
Applications, inspections, approvals and renewals, with an audit trail that survives a review.
A SACCO with 4,000 members
Statements, loan applications and repayments, reconciled against M-Pesa without manual matching.
An NGO reporting to donors
Field data collected offline, indicators calculated once, and the quarterly export produced in minutes.
A school handling admissions
Applications, places, fees and parent communication in one place, with proper consent handling.
What you get
A mapped process
Written down before anything is built, and agreed by the people who actually do the work.
Roles and permissions
Who can see what, who can approve what, and a record of who did what and when.
Reporting built in
The reports you already produce by hand, generated from the same data the system runs on.
Data protection by design
Lawful basis, consent, retention and access reviewed as part of the build, not bolted on after.
Training your team keeps
Recorded sessions and a written guide, so a new staff member does not need us.
Source code and documentation
In your name, in your repository. You are never locked in to us.
How the build runs
Each stage ends with something you can open, and a decision you have to make. No month of silence.
- 011–2 weeks
Process mapping
We sit with the people doing the work and write down what actually happens, not what the manual says.
- 021 week
Data model and scope sign-off
One document: what the system will do, what it will not do, and what it costs. You sign it before we build.
- 034–14 weeks
Build in two-week blocks
At the end of each block you get a working link and a short note on what changed.
- 042–3 weeks
Parallel run
Your team uses the new system alongside the old one until they trust it. Nobody is switched over on a Friday.
- 051 week
Handover and care
Code, documentation, training, and a support arrangement with a response time in writing.
What we need from you
Three things, and a project runs on time.
Most delays are not technical. They are a decision nobody was able to make, or data nobody could find.