Skip to main content

PROOF OF DELIVERY

Case Studies

Four engagements described in detail: a state revenue platform, a national health insurance system, a banking platform serving four licensed microfinance banks, and a university e-learning estate. Every organisation named here is a real client and every system described is in service.

How to Read These Case Studies

Most technology case studies are written to flatter the vendor. We have tried to write these differently, and the main difference is what we leave out. Each one states what the client’s situation was, what we built, how it is put together and what it connects to. None of them claims a percentage improvement, a naira saving or a reduction in waiting time.

That omission is deliberate. We can evidence what we built because the systems exist and you are welcome to see them running. We cannot independently evidence what changed in the client’s business afterwards, because those measurements belong to the client and are theirs to give. Publishing a figure we cannot stand behind would undermine everything else on this page.

What we can do is put you in front of the people who ran these projects on the client side, and they will tell you what it cost, how long it took and what it was worth. Those conversations are arranged through [email protected]. If you want the version with the difficulties left in, that is exactly what a reference call is for.

Case One: An Internally Generated Revenue Platform for Gombe State

State internally generated revenue in Nigeria fails for structural reasons rather than technical ones. Multiple agencies collect against separate revenue heads, each with its own receipting and its own designated account, and no shared identifier ties a payer’s obligations together. The consequence is that an administration can rarely state with confidence what was assessed, what was collected and what reached the treasury, and reconciling the three is a manual exercise performed long after the fact.

We delivered a consolidated revenue platform for Gombe State covering assessment, demand notice generation, collection across payment channels and reconciliation back to the state’s accounts. The platform holds the revenue schedule as configuration rather than as code, so a change to a rate or the introduction of a new revenue head is an administrative action taken by the state rather than a change request raised with us.

The engagement is notable for how it was handed over. The entire platform ships as a containerised stack carrying its own database and configuration, which means the state, an auditor or a future supplier can reproduce the exact running environment from the repository alone. That was a deliberate decision against our own commercial interest: it makes the state genuinely able to leave. We think a client who is free to go is a better client than one who is trapped.

  • Consolidated assessment, demand notice generation, collection and reconciliation on one platform
  • Revenue schedule held as configuration, maintained by the state rather than by the supplier
  • Containerised delivery, so the production environment reproduces exactly from the repository
  • Database and configuration shipped with the stack for audit and continuity
  • Field collection supported through a dedicated mobile application for officers away from a counter
  • No supplier lock-in: the state can stand the platform up without us
Case One: An Internally Generated Revenue Platform for Gombe State

Case Two: A National Health Insurance Platform

A national health insurance authority has two populations to serve and they want opposite things. The enrolee wants a card that works, a clinic that accepts it and an answer about what is covered. The authority wants enrolment integrity, claims that can be adjudicated, facilities that can be held to a standard, and returns it can defend. Systems built for one of those populations tend to fail the other.

We built for both against a single record. The citizen-facing side is a mobile application covering enrolee authentication and profile, health records and vitals, appointment scheduling, an assisted health enquiry service and a citizen reporting channel for raising problems with a facility. The administrative side is a web platform covering enrolee management and verification, provider and facility management, appointments, health records, pharmacy and laboratory workflow, claims processing, billing, compliance reporting and analytics, governed by role-based access control.

A companion Android client handles near-field card operations, because a scheme that issues cards needs those cards to be readable at the point of service rather than only in the head office. The platform is deployed on managed container infrastructure so that capacity follows demand rather than being provisioned for a peak that occurs twice a year.

  • Enrolee mobile application and administrative web platform working against one record
  • Enrolment, verification, appointments, health records, pharmacy and laboratory workflow
  • Claims processing, billing, compliance tracking and analytics for scheme administration
  • Citizen reporting channel so problems at a facility reach the authority directly
  • Companion Android client for near-field card operations at the point of service
  • Role-based access control across every administrative module
Case Two: A National Health Insurance Platform

Case Three: One Banking Platform, Four Licensed Microfinance Banks

Nigerian microfinance banks hold a core banking licence and a core banking system, and very often have no practical way to put a modern application into a customer’s hand. Licensing a channel platform per bank is unaffordable at their scale, and commissioning a bespoke build per bank is worse, because each one then carries its own security posture, its own integration defects and its own maintenance burden.

We built a single multi-tenant middleware that sits between customer channels and the core banking system, and we run four licensed banks on it: Ultra Pay Microfinance Bank, Tudun Wada Microfinance Bank, Kura Microfinance Bank and Quantum Microfinance Bank. Each bank is isolated at the database level with its own secrets, its own branded portal and its own institution code for inter-bank settlement. They share one codebase, one deployment pipeline and one security posture, which is what makes the economics work.

The platform handles tiered know-your-customer onboarding to the Central Bank of Nigeria model, account services, intra-bank and inter-bank transfers with name enquiry, loan products with amortisation schedules and loss classification, and outbound webhooks that are signed and retried with dead-letter handling. Every state-changing operation writes to an append-only, hash-chained audit log. That last decision was taken early and it is the one we would defend hardest: a bank that cannot reconstruct exactly what happened cannot answer its examiner, and an audit trail that can be edited is not an audit trail.

  • Four CBN-licensed microfinance banks live on one multi-tenant codebase
  • Database-per-tenant isolation, separate secrets, separate branded portals
  • CBN tiered KYC with bank verification and national identity number interfaces
  • Intra-bank and inter-bank transfers with name enquiry, plus loans and deposits
  • Append-only, hash-chained audit log across every state-changing operation
  • Mobile and internet banking channels delivered per bank on the shared platform
Case Three: One Banking Platform, Four Licensed Microfinance Banks

Case Four: A University e-Learning Estate at Full Population

Learning platforms are usually procured on a demonstration and judged on a pilot, which is why so many of them fail in their second semester. The behaviour that matters appears only at full population, when every faculty is running simultaneously, assessment deadlines cluster, and the platform is carrying years of accumulated course material rather than a handful of sample modules.

We delivered and operate the e-learning platform for Aliko Dangote University of Science and Technology, Wudil. It runs a long-term support release on a containerised stack with the university’s own branding and faculty structure, and it carries the institution at genuine scale: 37,791 user accounts, 2,636 academic courses and more than 778,000 course enrolments across eight faculties.

The engineering decision worth describing is reproducibility. The stack ships with the production database and file area, so an identical copy of the live site can be stood up on a laptop in minutes. Upgrades, theme changes and configuration work are rehearsed against the real estate rather than against a sample, which is the difference between a planned maintenance window and an incident in assessment week. It also means the university is not dependent on us being available to recover the service.

  • 37,791 user accounts carried on the production platform
  • 2,636 academic courses across eight faculty categories
  • More than 778,000 course enrolments held in the live estate
  • Containerised stack running long-term support releases of the platform and database
  • Production database and file area shipped with the stack for exact reproduction
  • Upgrades rehearsed against real data before any live maintenance window
Case Four: A University e-Learning Estate at Full Population

Further Delivered Work

Engagements beyond the four described above. Each corresponds to a system in service; follow the portfolio for what each one does and what it was built on.

Client or platform Sector What we delivered
Sufuri, Kano State Government & Transport Commercial tricycle registration, KYC, driver licensing, GPS tracking and collections, with agent and rider applications
EASEE Electric Mobility, Kaduna State Transport Contactless transit ticketing over NFC and EMV card reading for an electric three-wheeler network
Federal Ministry of Water Resources and Sanitation Government Citizen application for the National Water and Sanitation Intelligence Platform
Federal University of Science and Technology Kabo Education University management portal with student registration, academic structure and fee collection
ET&A Capital Financial Services Investment and research platform with subscriptions, gated research notes and a deal room
Elite Hope FX Financial Services Bureau de change platform across eight fiat currencies and four crypto assets with full accounting
RiceConnect Agriculture & Commerce Business-to-business and business-to-consumer rice marketplace with cart and checkout
Fairmont Shark Retail & Distribution Electric-vehicle showroom and online shop with a client-operated administrative dashboard

References, Site Visits and Pilots

How do I obtain a named reference?
Write to [email protected] describing the sector and the type of work you are considering. We identify two or three clients whose engagement genuinely resembles yours, seek their written consent, and then introduce you directly. Most of the turnaround is waiting for the client to respond rather than anything on our side. We do not give out client contact details before consent, and we will tell you if a client has declined rather than substituting a weaker reference silently.
Can we visit a live site and see the system in use?
Yes, and we encourage it, because it is far more informative than a demonstration we control. Site visits are arranged with the host client and usually last half a day, with time for your team to speak to the people doing the work without us in the room. We ask visitors to sign the host’s confidentiality undertaking and to respect any areas the host places off limits. Travel and accommodation are at the visitor’s cost.
Why are there no results figures on this page?
Because we cannot evidence them ourselves. What a system changed inside a client’s organisation is measured by that client, against baselines they hold, and it is theirs to disclose. We would rather publish nothing than publish a figure we selected and cannot stand behind under questioning. Ask on a reference call and the client will tell you directly, including where the result was smaller than anyone hoped.
What does a proof-of-concept pilot involve?
A pilot is a time-boxed deployment against agreed success criteria in one real location: one revenue zone, one clinical department, one branch, one faculty. It uses your data and is measured against criteria we both write down before it starts, not afterwards. Pilots are chargeable at cost recovery, and where a pilot proceeds to a full contract we credit that cost against the contract value. Scope and price are quoted per engagement.
Can you provide a reference in our specific sector?
In banking, government revenue, transport, health and education, yes, with more than one to choose from. Our book is thinner in oil and gas and in large-scale retail, and where we cannot offer a genuinely comparable reference we say so directly instead of offering an unrelated one and hoping you will not notice the difference.
Will you let us speak to a client where the project went badly?
We will speak frankly about the engagements that ran into difficulty and what we changed as a result. Not every client is willing to relive a difficult project for a stranger, which is fair enough. Ask on the reference call and we will tell you what actually went wrong on projects of your type, including the ones where the fault was ours.
How do you handle competitors among your reference clients?
Carefully. We do not introduce a prospective client to a direct competitor of theirs without both parties knowing exactly who they are speaking to and agreeing in advance. Where a sector is small, and microfinance banking in a single state can be very small, we will offer an adjacent reference instead and explain why.

On client names and figures

The organisations named on this page are real clients and the systems described are real deliverables in service. We publish the relationship and the scope of work. We do not publish contract values, and we do not attribute a performance figure to a named organisation on a public page without that organisation’s written consent. Several of our engagements are not represented here at all, at the client’s request.

Named references, including direct contact with the client-side project managers who ran the work, are available under a mutual non-disclosure agreement. Write to [email protected] or call +234 802 913 8013, tell us the sector and the type of engagement you are evaluating, and we will match you to the closest comparable client and seek their consent. Our standard mutual NDA is available on request from [email protected].

Ask for the reference that matters to you

The most useful thing we can give a prospective client is thirty minutes with someone who has already done what you are about to do. Tell us what you are planning and we will arrange it.