The part most suppliers leave vague
independent
Every supplier promises a handover. The question is what it consists of, and whether anything depends on your agreeing to it.
Verified by someone who is not us
Before final payment, a third party of your choosing rebuilds and deploys the system from source using only our documentation. If they cannot, it is not finished. It is the one test that cannot be passed with good intentions, and it changes how everything is written from the first week.
Training the people who will actually operate it
Not a presentation for managers: sessions with the registrar, the clerk, the gate officer and the administrator who will use this on Monday, recorded so the next person to hold the job can watch them. Plus an administrator's path for the things that go wrong at 7am — a stuck queue, a locked account, a failed import.
Support by choice, never by hostage
Retained support exists because systems need attention, not because you cannot leave. Source, credentials and infrastructure are in your name throughout, and the documentation assumes a stranger. If you end the arrangement, nothing stops working and nothing has to be prised out of us.
- Runbooks written for an engineer who never met us
- Training for the team who will operate it, recorded
- Independent build verification before final payment
- Retained support by choice, never a hostage arrangement
- 01Runbooks for deployment, recovery and the common failures
- 02Recorded role-by-role training for the people who operate it
- 03An independent rebuild from documentation, before final payment
- 04A support arrangement with a notice period and no lock-in
A previous system is unmaintainable because only its author understood it
Your team cannot deploy a change without the supplier
Nobody is certain what would happen if the supplier stopped answering
- 09
Managed Cloud & Mail Infrastructure
Self-hosted mail, container deployment and DNS for organisations that need their data to stay where they can point at it.
- 08
Institutional Records Platform
A public platform and a full records system behind it, covering five distinct staff and student roles on one data model.
What exactly is in a handover?
Source in your repository, credentials in your accounts, infrastructure in your name, runbooks written for an engineer who never met us, recorded training, and an independent rebuild. The procurement page sets it out as commitments rather than intentions.
Do you offer ongoing support?
Yes, as a retained arrangement with a notice period. It covers monitoring, patching, incident response and a change allowance. It is renewed by choice, and the system runs without it.
Can our own team take it over completely?
That is what it is built for. The usual pattern is a few months of retained support while your team gets confident, then a support arrangement that tapers or ends.
What if we need you back later?
Then we come back, at the usual rates. The documentation means that is a short engagement rather than an archaeology project.
Start here
Bring us the problem nobody has solved.
A 30-minute technical briefing. We will tell you what we would build, roughly what it costs, and honestly whether we are the right people for it.
- ask@madsoftech.com
- Telephone
- +220 872841578
- Office
- Brusubi, The Gambia