Skip to content
Madsoft
HomeWorkCapabilitiesInsightsStudioPartnersContact
Madsoft Technologies

We build the
instruments institutions
run on.

Customs clearance, port operations, national registries — and the machine learning and verifiable ledgers running inside them. We build for institutions where being wrong is expensive, and being unable to prove otherwise is worse.

01What we do

Six practices. One standard.

02The platform

Built once. Deployed three times.

Our clearance platform runs at three national customs administrations. Each deployment is configured rather than rebuilt, so an authority adopting it inherits everything the previous two paid to discover.

That makes a fourth deployment a programme with a known shape and a known cost — not a bespoke quote assembled from guesses.

Discuss a deployment →
  1. 01

    Weighbridge & ticketing

    Capture, OCR intake, axle compliance, custody

  2. 02

    Customs clearance

    Declarations, duty waivers, review and release

  3. 03

    Gate & terminal operations

    Appointments, exit control, terminal registries

  4. 04

    Customs integration

    ASYCUDA, ICUMS and UNIPASS document mapping

  5. 05

    Revenue & reconciliation

    Payments, targets, variance and reporting

  6. 06

    Command centre

    Executive dashboard across every module

03Industries

The same discipline, across sectors.

The mechanism repeats more than people expect. A customs clearance chain, a student record and a patient referral are the same problem wearing different clothes: several parties, one record, and a decision that has to be defensible afterwards.

01In production

Government & Public Sector

Systems where the auditor matters as much as the user, and where the record has to survive being challenged years later.

  • Customs & single window
  • Port and border operations
  • Revenue & reconciliation
  • Registries and licensing
02In production

Education

Institutions running admissions, enrolment, assessment and fees across several departments that each believe they own the student record.

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

Healthcare

Clinical and administrative systems where access control, auditability and uptime are not features but preconditions.

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

Banking & Financial Services

Regulated environments where every balance change needs an attributable trail, and reconciliation is the product rather than a report.

  • Core operations dashboards
  • Loan origination & scoring
  • Payments and settlement
  • Compliance and AML reporting
05In production

Logistics & Supply Chain

Moving goods through checkpoints where several independent parties must agree on one custody history.

  • Fleet and consignment tracking
  • Warehouse and inventory
  • Provenance & traceability
  • Settlement automation
06In production

Hospitality & Retail

Customer-facing brand and booking platforms, built to stay fast where bandwidth is expensive.

  • Reservations and ordering
  • Menu and catalogue management
  • Loyalty programmes
  • Multi-site reporting
04Selected work

Systems in production.

All projects →
05How we work

Measure first.
Then build.

Most failed public-sector software fails before a line is written — scoped from a document instead of from the work. We start on the floor, with the people who will actually use it.

The full engagement model →
  1. 01

    Calibrate

    1–2 weeks

    We sit with the people doing the work and map the process as it actually runs — not as the manual describes it.

  2. 02

    Frame

    1–2 weeks

    Architecture, scope and a fixed price — produced from what we observed, never from the document alone.

  3. 03

    Instrument

    4–12 weeks

    We build the smallest thing that proves the mechanism, put it in front of real operators, and measure it.

  4. 04

    Deploy

    2–4 weeks

    Production means monitored, documented, access-controlled and backed up — verified, not asserted.

  5. 05

    Hand over

    1–2 weeks, then optional support

    Source, runbook and training. We stay because you want us to, not because you cannot operate without us.

National customs administrations
3
Endpoints in production
30+
Sectors delivered
5
Operator screens, one platform
40+

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.