Product design and discovery
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.
We design and engineer digital platforms for government, health, education, financial services and enterprise — built in Ghana, for how institutions here actually work.
A permit that takes six months is not a technology problem. It is a trust problem.
Nobicel Ltd exists to close that gap. We study how an institution actually works before we replace anything, then build software that is fast for the person at the counter and defensible to the auditor who reviews it a year later. Every platform we ship is designed to be handed over, run and inspected by the people who inherit it.
The domains change. The requirements — verifiable identity, real payment rails, multi-agency handover and an audit trail — do not.
We describe the work by the problem it solves rather than by product name. The platforms themselves are named and demonstrated privately, under NDA.
Much of what we build handles citizen identity, health records, land title and payroll. Those systems do not belong on a public website — so we show them live instead, to people who are actually evaluating us.
A short enquiry — who you are, the sector, and the problem you need solved. Enough for us to know whether we are the right firm for it.
If it is a fit, we propose a call. If it is not, we say so rather than take up your time.
We sign an NDA before naming platforms, clients or architecture. Ours is short, and we are equally happy to sign yours.
We walk you through the systems themselves — live, not slides — with the engineers who built them, then follow up with referees and a written capability statement.
We are not a body shop and not a design studio. We take a process from how it runs today to a system an institution can operate on its own.
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.
Typed, tested applications built on modern web foundations, structured so a second team can pick them up and a regulator can audit them.
Money and compliance are where systems in Ghana usually fail. We treat both as core engineering, not an integration afterthought.
Ghana Card verification, OTP consent and role separation, so the right person sees the right record and the system can prove it later.
The hard part of public sector software is rarely one office. It is the handover between four of them. We build for that handover.
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.
We take our principles from the Adinkra tradition — each symbol below names something we hold ourselves to, not decoration.
A permit, a payslip, a patient record and a land title are not features. Someone is waiting on the other side of each one, and we build with that person in mind.
We write systems expecting an auditor, a regulator or a journalist to look inside them one day. That expectation makes the work better, not slower.
Health records, payroll and identity data carry real consequences when handled carelessly. Access is enforced, actions are logged, and nothing is shared that does not need to be.
Ghanaian institutions have processes refined over decades. We study them before replacing them, and we keep what earned its place.
Intermittent connectivity, shared devices, mobile money and paper fallbacks are the operating conditions here — not edge cases to be handled later.
We would rather train the team that inherits a system than be indispensable to it. Documentation and handover are part of delivery, not an extra.
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.
Three engineers and operators start building together, on the conviction that the systems Ghanaian institutions run on should be built here, by people who understand the process being replaced.
HR and payroll for a largely field-based workforce — rostering across sites, attendance captured on site, and statutory deductions applied automatically. It became the foundation of everything we later built for payroll.
District permitting, land allocation with GPS boundary capture, and public infrastructure fund accountability across the districts — the first platforms designed around multi-agency handover rather than a single office.
A health record opened by national ID under patient consent, a case record shared across the institutions that touch it, and personnel verification tied to a payroll control. The work that taught us how much of this is a trust problem.
Registered with the Registrar-General's Department on 29 May 2026 (CS113710526), consolidating the team's work under one company with a seat in Tse Addo, Accra.
The payroll platform goes to pilot with automatic statutory calculation and disbursement across bank and mobile-money rails. We also stop publishing our platforms, and move to demonstrating them privately under NDA.
Our company profile carries registered particulars, the portfolio in full, our security posture and how we engage — everything a procurement or due-diligence review needs in one place.