We take responsibility for the whole path: understanding the process, designing the replacement, engineering it properly, and leaving the institution able to run it.
We start with the process as it actually runs — the paper form, the WhatsApp group, the queue at the counter — and design the system that replaces it without breaking the people who depend on it.
Sankofa · Learn from what came before
Typed, tested applications built on modern web foundations, structured so a second team can pick them up and a regulator can audit them.
Hwe Mu Dua · Quality, excellence, scrutiny
Money and compliance are where systems in Ghana usually fail. We treat both as core engineering, not an integration afterthought.
Dwennimmen · Strength tempered by humility
Ghana Card verification, OTP consent and role separation, so the right person sees the right record and the system can prove it later.
Eban · Protection and safety
The hard part of public sector software is rarely one office. It is the handover between four of them. We build for that handover.
Nkonsonkonson · Unity and human relations
A system nobody in the institution can run is not a delivery. We train the team that inherits it and document what we hand over.
Nsoromma · Guardianship and care
No open-ended time and materials. Each stage has a defined outcome, a fixed price and a decision point at the end of it.
We map the process as it runs today, agree the outcome in writing and price the work before anything is built.
A clickable, reviewable version of the system in weeks — so stakeholders argue with a screen, not a document.
Typed, tested delivery in visible increments, with authorisation, audit and reporting built in from the start.
Training, runbooks and documentation, then a support agreement sized to how critical the system is.
We build on Next.js and TypeScript across the estate, with hand-written styling rather than a framework skin, and PostgreSQL behind it. The point is not novelty — it is that another team can read the code, run the system and extend it after we hand it over.
Before anyone can recommend a supplier they have to answer for the choice. These are the answers, stated plainly, so they can be quoted into a submission without a meeting.
The team that designs a system is the team that maintains it, in the same time zone and the same regulatory context. No offshore handover, no overnight support gap.
In-country hosting, your own cloud tenancy or a region you name. Data residency is a deployment decision you make, not one we make for you.
On full payment the bespoke work is yours. Data exports in open formats at any time, documented schemas, and source code released or placed in escrow as the contract requires.
Administrator and end-user training, written runbooks and handover documentation are part of delivery. We would rather your team could run the system without us than be indispensable to it.
Immutable trails on every action that touches money or a record, server-enforced authorisation, and reporting an auditor can reconcile without a rebuild.
Intermittent connectivity, shared devices, low-end handsets and paper fallbacks are designed for from the first screen, not handled as exceptions later.
National ID verification, GhIPSS and mobile-money rails, and documented APIs so the next system procured can talk to this one.
Each stage has a defined outcome and a price agreed before it starts, with a decision point at the end. We do not bill open-ended time and materials.
Bring the process. We will come back with what it would take to replace it properly.