Anyone who tried to pay for something in Nigeria in February 2023 remembers what happens when systems built for ordinary days meet an extraordinary one. Transfers hung. Apps timed out. POS terminals declined cards that had money on them. People queued for cash that wasn't there. Most of that software wasn't badly written. It had simply never been asked to carry that much weight.
That month gets remembered as a one-off. It wasn't. The naira moves. Regulations change, sometimes by circular on a Friday evening. Power and networks come and go. Leadership changes, and a system that belonged to the last director slowly becomes nobody's job. For the banks, energy companies and public institutions that keep this country running, that's an ordinary week.
Most enterprise software is designed somewhere calmer. It assumes the network is always on and that people follow the process in the manual. It demos well. Then it meets real conditions and starts to give way, a little at first and then all at once. Walk into most large institutions and you'll find at least one system like that, bought with real money and launched with a ribbon, now quietly ignored.
Ankur exists to build the other kind.
In practice that comes down to a few habits. We learn how the work really moves before we design anything, which usually means time with the people who do the work rather than the people who describe it. We build for the bad day as well as the good one, because providers will fail and volumes will spike, usually at the worst moment. And we stay. Whether a system is still running in five years gets decided after launch, so we plan for that part from the start.
Our mark comes from an anchor. An anchor doesn't stop a ship from moving. It stops the current from deciding where the ship ends up. That's the job we take on for the institutions we work with, and it's why we judge ourselves by one question: is it still holding?
If you run something that can't afford to give way, we'd like to hear about it.