Everything an evaluation committee needs.
Public bodies are asked to buy software from suppliers who disclose almost nothing until contract stage. This page exists so that a procurement officer can assess us before making contact.
Last reviewed 3 September 2026
Who you would be contracting.
- Legal entity
- Madsoft Technologies
- Registration number
- SRN 0710144178
- Registered owner
- Nema Ceesay
- Registered address
- No. 8 Stanley Street, Banjul, Kanifing Municipality, The Gambia
- Office address
- Amsterdam Plaza, Brusubi Turntable, Brusubi, West Coast Region, The Gambia (Plus Code C73C+G56)
- Year established
- 2022
- Registered with
- Registrar of Companies, Ministry of Justice
How we contract.
Contracting models
Fixed-price against a defined scope, time-and-materials for open-ended work, or a retained monthly capacity. Public bodies generally require the first; we will quote fixed-price once discovery is complete, not before.
Payment structure
Milestone-based, tied to demonstrable delivery rather than elapsed time. We do not invoice a milestone that has not been accepted in writing.
Subcontracting
We disclose any subcontracted component before award. Core engineering is performed in-house; we do not resell another firm's delivery under our name.
Residency and ownership.
Residency
Systems can be deployed entirely within your jurisdiction, on infrastructure held in your name. We default to this for public-sector work rather than offering it as an upgrade.
Ownership
Source code, infrastructure accounts, DNS records and credentials are registered to the client, not to us. On completion we hold no key that you cannot revoke.
Access control
Named individual accounts with least-privilege roles, no shared credentials, and access to production granted for a defined window and revoked afterwards. Every action against a record is attributable.
Personal data
Data minimisation by default: we collect what the process requires and no more. Retention periods are agreed in writing and enforced in code, not policy alone.
Practices we commit to.
- Encryption in transit throughout; encryption at rest for personal and financial data
- Credentials held in a managed secret store, never in source control
- Dependency and vulnerability scanning in the build pipeline
- Backups taken on a defined schedule, with a restore drill performed before go-live
- Audit logging of privileged actions, retained independently of the application
- Documented incident response with a named contact and a defined response window
What you own at the end.
- 01
Source in your possession
Held in a repository the institution controls, updated continuously through delivery — not handed over as an archive at the end.
- 02
Independent build verification
Before final payment, a third party of your choosing builds and deploys from the delivered source using only the delivered documentation. We support that exercise at our cost.
- 03
Runbook and training
Operational documentation written for an engineer who has never met us, plus training for the team who will run it. Recorded, so it survives staff turnover.
- 04
Exit provisions
Documented export of all data in non-proprietary formats, executable by your staff without our cooperation. Agreed in the contract, not promised in a meeting.
What we can provide.
Several engagements are active public-sector contracts under confidentiality. We do not publish client names, but we will arrange direct reference calls with existing clients for shortlisted procurements, subject to their consent.
- Reference calls with current public-sector clients
- A technical walkthrough of a comparable production system
- Architecture and security documentation under NDA
- Named CVs for the engineers who would be assigned
Asked before the first call.
- Who owns the source code and the infrastructure?
- You do. Source code, infrastructure accounts, DNS records and credentials are registered to the client rather than to us, and the repository is one the institution controls throughout delivery — not an archive handed over at the end. On completion we hold no key you cannot revoke.
- Can the system be hosted inside our own jurisdiction?
- Yes, and it is our default wherever residency matters rather than a paid upgrade. Systems can be deployed entirely within your jurisdiction on infrastructure held in your name, which is usually what makes a data-residency requirement answerable rather than negotiable.
- How do you price and contract work?
- Fixed-price against a defined scope, time-and-materials for open-ended work, or a retained monthly capacity. Public bodies generally require the first. We quote fixed-price only once discovery is complete, because a price quoted from a specification is a guess dressed as a commitment. Payment is milestone-based and tied to demonstrable delivery, and we do not invoice a milestone that has not been accepted in writing.
- Do you subcontract the work?
- Core engineering is performed in-house, and we do not resell another firm's delivery under our name. Where any component would be subcontracted we disclose it before award rather than after.
- What happens at handover, and can our team run it without you?
- That is the test we hold ourselves to: if your team cannot operate it without us, it is not finished. Before final payment, a third party of your choosing builds and deploys from the delivered source using only the delivered documentation, at our cost. You get a runbook written for an engineer who has never met us, recorded training for the people who will operate it, and contractual export of all data in non-proprietary formats your staff can execute without our cooperation.
- Will you provide references from existing clients?
- Yes, for shortlisted procurements and subject to those clients' consent. Several engagements are active public-sector contracts under confidentiality, so we do not publish client names — but we will arrange direct reference calls, a technical walkthrough of a comparable production system, architecture and security documentation under NDA, and named CVs for the engineers who would be assigned.
- What do you need from us to start?
- Site access during a normal working day and time with the people doing the work, not only their managers. The first phase maps the process as it is actually performed, including the workarounds and paper forms that keep it moving — those are requirements, and a system built without them is one people route around. After that we need a decision-maker who can approve scope, and access to the existing systems and schemas.
- Where is Madsoft Technologies based and registered?
- Our office is at Amsterdam Plaza, Brusubi Turntable, in Brusubi, The Gambia, and we work remotely with clients beyond it. The company has been registered with the Registrar of Companies at the Ministry of Justice since 2022; the registered address on that certificate differs from the office, and both are published in full on this page rather than supplied on request.
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.