There is a number attached to my work that I am asked about often: the systems I have built have processed ₦960,046,349.60 in institutional financial activity. The natural instinct, mine included once, is to read it as a business milestone. I want to argue that this is the least interesting way to read it, and that the figure actually measures something institutions almost never quantify: operational trust.
Money is the most honest signal an institution sends
Institutions say many things. They sign up for pilots, attend demos, express enthusiasm. None of that is evidence. The only signal an institution cannot fake is where it routes its mission-critical activity, and nothing is more mission-critical than money. Fees are how a school survives. Collections fund salaries. Reconciliation errors become governance crises. When an institution moves its financial operations onto a system, it places its continuity in that system’s hands.
That is why I read the ₦960 million figure the way I do. Institutions did not route nearly a billion naira through School Vault because the interface was pleasant. They did it because, repeatedly and at the level of daily operations, the infrastructure held.
How operational trust is actually earned
Watching institutions cross the line from using a system to depending on it taught me that operational trust accumulates in stages, and none of them can be skipped:
- Reliability first. The system works on the bad days: exam week, fee deadline week, the week the bursar travels. One failure at a critical moment costs more trust than a year of uptime builds.
- Consistency second. The numbers agree with themselves. What the administrator sees matches what the parent sees matches what the report says. Institutions forgive missing features; they do not forgive contradictions.
- Visibility third. The system makes the institution more legible to itself. When leaders can finally see collections, gaps, and flows in real time, the system stops being software and starts being how the institution knows things.
- Dependence last. The quiet milestone: staff stop maintaining the parallel paper process “just in case.” The institution has internalized the infrastructure. This is the moment a tool becomes an operating layer.
Why I refuse the revenue framing
Founders are coached to present big numbers as traction. I resist that framing for a specific reason: it teaches the wrong lesson about what was achieved. Revenue measures what a company extracted. Throughput of mission-critical activity measures what institutions entrusted. The second is harder to earn, harder to fake, and far more predictive of whether infrastructure will still matter in a decade.
It also keeps my own incentives honest. A team optimizing for revenue can be tempted toward whatever sells. A team optimizing for entrusted activity has exactly one path: be relied upon, every day, at the moments that matter most. That discipline is the whole culture of infrastructure work.
What this means beyond my own systems
I would offer this reframe to anyone building for African institutions, whether in education, health, finance, or civic systems. Stop asking how many institutions signed up. Ask what they have trusted you with. Adoption metrics flatter; entrustment metrics tell the truth. An institution that routes its critical operations through your system has given you the only endorsement that matters, and it has given it in the currency institutions take most seriously.
The ₦960 million milestone will grow, and at some point it will pass a billion and become a different headline. But the reading will stay the same. The number is not the achievement. The achievement is what the number proves: that infrastructure built on the conviction that Africa’s institutions cannot scale on fragmented manual systems can earn the deepest kind of institutional confidence, the kind measured not in words but in what institutions are willing to place inside it.