About
Nurudeen Abdul-Majeed
Founder and engineer, Afatech Enterprise
Why I built it
In 2023 I sat in a firm in Tamale while a clerk rebuilt a month of time from a paper diary and a partner searched three cabinets for a client's ledger card before a hearing. The firm was good at law and had no system that knew what a Circuit Court was, so every deadline lived in one person's head and every invoice took a week. I started Dangana that month, and the first thing it did was compute a filing deadline around a public holiday. Everything since has been built against the desks I saw that day.
Background
What I have shipped
I build and run web systems for organisations in Ghana, and have done so for six years. Before Dangana I shipped a donor management system that a non-profit still runs its campaigns on, an agricultural trade platform taking mobile money and card payments through Paystack and Hubtel, and a restaurant ordering system that handles a dinner rush without falling over. Each of those runs in production with backups I have restored and monitoring I read every morning, which is the habit this system inherits.
The rest, with the code where it is public, is at manuru.dev (opens in a new tab).
The company
Afatech Enterprise
- Registered name
- Afatech Enterprise
- Location
- Northern Region, Tamale, Ghana
The question nobody asks
If something happens to me
Every partner wonders what happens to the firm if the one person who built its system is gone. Here is the answer, in the order it matters.
- 01
The firm owns its deployment, database and files
The system runs on infrastructure in the firm's name, with one database and one document store that belong to the firm. Nothing runs on my servers, so nothing stops if I do.
- 02
The source code is licensed to the firm
The licence grants the firm the source code with the right to maintain and modify it for its own use. If Afatech Enterprise ceases trading, the firm can engage any engineer to keep the system running. I chose a licence over an escrow because it needs no third party to release anything.
- 03
The documentation is complete
Every module is documented to the point that an engineer who has never met me can deploy, back up, restore and change the system. The build itself is not accepted as finished until that documentation exists, so this is a working rule rather than a promise.
- 04
A named backup engineer
A second engineer with access to the code and the documentation will be named here, with the firm's agreement, once the arrangement is signed. Until then this line says so rather than pretending.
Support
How support works
One person built this and one person answers for it. That is a strength when the cover for absences is written down, so it is.
What is included
Fixes to anything that does not work as documented, updates to the version the firm runs, and help by WhatsApp, phone or email for the people using it. Changes the firm asks for beyond that are quoted first.
Response times
A reply within four working hours. Anything that stops the firm working gets a fix or a workaround within one working day, and everything else within five.
How to reach me and when
Monday to Friday, 8am to 6pm. You will talk to the person who built it, not a ticket queue, on the numbers below.
When I am away
The firm is told in advance, and the backup engineer covers the response times above for the duration. Nothing waits for a holiday to end.