Skip to content
Madsoft
HomeWorkCapabilitiesInsightsStudioPartnersContact

Capability statement

Issued Disclosures reviewed

Custom software for operations that cannot afford to be wrong

Ten systems in production across five sectors.

Madsoft Technologies is a software studio building custom web and mobile platforms, applied AI, verifiable-record systems and cloud infrastructure for businesses and institutions.

Download PDFA4 letterhead · Generated from this site
Registration
SRN 0710144178
Established
2022
Office
Amsterdam Plaza, Brusubi Turntable, Brusubi
Works
The Gambia · Remote worldwide
Engagements delivered
10
Endpoints in production
30+
Sectors delivered
5
Operator screens, one platform
40+
02

Capabilities

Eight practices, each described by what it delivers rather than what it is called.

01

Applied AI & Machine Learning

Models that make a decision, not a demo. We take the noisy signal an organisation already produces and resolve it into something it can act on.

  • Document and ticket OCR pipelines
  • Forecasting, anomaly and fraud detection
  • LLM assistants grounded in your own records
  • Evaluation harnesses, so accuracy is a number
02

Systems of Record

Platforms where the record is the product and the auditor matters as much as the user — a transcript, a licence, a chain of custody, a reconciliation that has to survive being disputed years later.

  • Consignment and chain-of-custody tracking
  • Registries, licensing and institutional records
  • Revenue tracking and reconciliation
  • Role, permission and audit architecture
03

API & Systems Integration

Making two systems that were never designed to meet agree on a single record. This is the hardest part of most large programmes and the part that decides whether the rest of it works.

  • Legacy and third-party platform integration
  • Document and schema mapping between systems
  • Cross-engine databridges, SQL Server to MySQL
  • Versioned REST APIs with health and status surfaces
04

Custom Software Engineering

Products built to be run for years by people who did not write them. Typed, tested, documented and handed over properly.

  • Web platforms and operator consoles
  • Native mobile for field operations
  • API design and system integration
  • Legacy migration without a shutdown
05

Blockchain & Verifiable Records

Distributed ledgers used where they earn their place: when several parties who do not fully trust each other must agree on one history, and that history has to survive being disputed.

  • Provenance and chain-of-custody tracking
  • Smart-contract settlement and escrow
  • Tamper-evident audit and document notarisation
  • Tokenisation and digital asset infrastructure
06

Product & Interface Design

The screen is where a system meets someone who did not choose it, is measured on throughput, and cannot stop to read a manual. We design for that person — the clerk at the counter, the officer at the gate, the registrar at the end of term.

  • Operator consoles organised around the task, not the schema
  • Design systems that survive being handed to another team
  • Interfaces for small screens, metered bandwidth and bright sunlight
  • Accessibility checked in the build pipeline, not audited at the end
07

Cloud, Data & Infrastructure

Infrastructure you own, run by people who answer the phone. For organisations that cannot put their data on someone else's platform — for cost, sovereignty or procurement reasons.

  • Server provisioning, hardening and TLS
  • Containerised deployment and CI pipelines
  • Self-hosted mail with SPF, DKIM and DMARC
  • Database design, backups and monitoring
08

Handover, Training & Support

The part most suppliers leave vague. We write the runbook for an engineer who has never met us, train the people who will actually operate the system, and stay reachable afterwards — on terms you can end.

  • 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
03

Selected work

Engagements are described by sector, scale and mechanism. Several are active contracts under confidentiality, so client names, locations and repositories are shared under NDA rather than published.

  1. Enterprise

    2026

    Operations Command Center

    A live executive command centre joining five production databases into a single operational picture.

    • Five production databases federated into one view
    • Thirteen operational sections, updating live
    • Revenue target against collected, tracked daily

    React 19 · TypeScript · Vite · Tailwind · Recharts · Express · MySQL · JWT

  2. Logistics

    2026

    Consignment Workflow Platform

    An AI-assisted platform that replaced paper weighing tickets and manual release approvals end to end — web console, API and field mobile app.

    • Forty-plus role-specific operator screens
    • OCR ticket capture with barcode and QR custody
    • Web console, API and native field app as one system

    React · Next.js · React Native · PostgreSQL · OpenAI · OCR · Twilio · SendGrid

  3. Enterprise

    2026

    Systems Integration API

    A production REST API bridging two authoritative systems that each held half of the same record, with public health and status surfaces.

    • Thirty-plus endpoints running in production
    • Public health, status and integration surfaces
    • Zero external authentication dependencies

    Next.js · MySQL · SQL Server · Zod · JWT · nginx · PM2

  4. Logistics

    2026

    High-Volume Operations Platform

    Vehicle processing, documentation and revenue management for one of the region's busiest commercial sites, delivered bilingual.

    • Bilingual across every operator surface
    • Live monitoring over websockets
    • Virtualised tables built for peak-volume days

    React · TypeScript · Vite · Chakra UI · i18next · Socket.IO · Zustand · Docker

  5. Enterprise

    2025

    Supply Chain Traceability Ledger

    Blockchain traceability from farm to retail — QR and RFID custody, smart-contract settlement, offline-first for producers in the field.

    • Farm-to-retail custody on an immutable ledger
    • Smart-contract settlement replacing manual reconciliation
    • Offline-first capture with biometric-secured accounts

    React Native · Solidity · ethers.js · Redux Toolkit · Stripe · Secure Store

  6. Education

    2026

    Institutional Records Platform

    A public platform and a full records system behind it, covering five distinct staff and student roles on one data model.

    • Five role-specific portals from a single data model
    • Signed PDF documents generated on demand
    • Migrated to self-hosted infrastructure with no downtime

    React · Express · MySQL · JWT · Chart.js · OCR · React PDF · Nodemailer

  7. Cloud

    2026

    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.

    • Containerised deployment with reproducible migrations
    • Full SPF, DKIM and DMARC delivery configuration
    • Monitoring, backups and documented runbooks at handover

    Docker · Node.js · Postfix · Dovecot · OpenDKIM · Nginx · VPS

04

How an engagement runs

Durations are typical for a large-scale system and are not a quote. A focused internal tool compresses by roughly half.

What you receive

  • Observed process map, as performed rather than as documented
  • Stakeholder and role inventory with actual permissions in use
  • Constraint register — connectivity, power, hardware, language, literacy
  • An honest note on whether we are the right supplier for this

What we need from you

  • Site access during a normal working day
  • Time with operators, not only managers

05

Sectors

In production means a system operating today, with a reference available. The rest is capability without a delivered reference yet — the distinction is made here because an evaluation will check it.

  • Logistics & Supply Chain

    In production

    Consignment and custody tracking · Warehouse and inventory · Provenance & traceability · Settlement automation

  • Education

    In production

    Student information systems · Admissions & enrolment · Fees and finance portals · Results and transcripts

  • Enterprise Operations

    In production

    Operations dashboards · Workflow and approvals · Incentive and payout administration · Multi-system integration

  • Hospitality & Retail

    In production

    Reservations and ordering · Menu and catalogue management · Loyalty programmes · Multi-site reporting

  • Public Sector & Institutions

    In production

    Registries and licensing · Records and reporting · Revenue & reconciliation · Internal operations platforms

  • Healthcare

    Capability

    Patient records & scheduling · Pharmacy and inventory · Billing and claims · Referral and lab workflows

  • Banking & Financial Services

    Capability

    Core operations dashboards · Loan origination & scoring · Payments and settlement · Compliance and AML reporting

06

Entity and 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

Commercial terms

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.

07

Data, security and handover

Data 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.

Security practice

  • 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

Handover and exit

  1. 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.

  2. 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.

  3. 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.

  4. 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.

08

References

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

Book a technical briefing

Thirty minutes with the engineers who would build it. We will tell you what we would build, what we would not, and whether we are the right people for it.