Pirumart
Case Studies

Impact, not feature lists.

Representative engagements illustrating the kind of work we take on across sectors, not a disclosed client list.

FinTech

KashRound

  • Savings tracking
  • Loan management
  • Investment tracking
  • Two-factor auth
Problem

Savings groups, investment clubs and ROSCAs move enormous sums, and most of them run on a WhatsApp thread and one treasurer's spreadsheet. A corrupted file or a treasurer who resigns can take the group's records, and the trust holding it together, with them.

Approach

Our own product, designed and built in-house and running in production: contributions, loans and joint investments kept in one shared record, in the terms groups here actually use, with every member seeing the same balances as the treasurer.

Outcome
Live with real groups
Savings groups, investment clubs and ROSCAs across Uganda run their books on it today.
One shared record
Members see the group balance themselves instead of relying on the treasurer's word.
Beyond contributions
Joint investments in shares, land and businesses are tracked with each member's proportional share.
Logistics

Logistics SaaS

  • React
  • Node.js
  • Mapbox
  • WebSockets
Problem

Dispatchers were juggling multiple disconnected tools to run a single delivery route.

Approach

Consolidated the workflow into a single operations console with a live map, route optimisation, and driver communications.

Outcome
More deliveries per dispatcher
One console replaced the multi-tool workflow, cutting coordination overhead.
Lower fuel cost per route
Route optimisation reduced unnecessary mileage.
Higher driver satisfaction
Consolidated comms reduced back-and-forth with dispatch.
Events & Ticketing

Events Ticketing Startup

  • Next.js
  • Flutter
  • PostgreSQL
  • Mobile Money APIs
Problem

Tickets were sold over WhatsApp and confirmed by hand against mobile money messages; at the gate, staff checked names on a printed list and duplicates still got through.

Approach

A ticketing platform with a web box office and companion mobile apps: buyers get a scannable QR ticket, gate staff scan it with or without a signal, and every sales channel reconciles into one ledger.

Outcome
Faster entry
QR scanning replaced name-list checks at the door.
Single-use tickets
Each ticket scans once, whether the gate is online or not.
One sales ledger
Online, agent and box-office sales reconcile in the same place.
Co-working

Co-working Space Operator

  • Next.js
  • Node.js
  • MySQL
  • Flutterwave
Problem

Desks and meeting rooms were booked in a shared calendar and invoiced by hand, so double-bookings only surfaced when two members turned up for the same room.

Approach

A booking engine with real-time availability, member plans and credits, and payment taken at the point of reservation, plus an operator console showing occupancy.

Outcome
No double-bookings
Real-time availability replaced the shared calendar.
Paid at booking
Reservations confirm on payment instead of on a later invoice.
Visible occupancy
Operators can see utilisation per desk and per room.
Healthcare

Private Hospital Network

  • OpenMRS
  • Java
  • MySQL
  • HL7 FHIR
Problem

Each facility kept its own patient records, so a patient seen at a second site arrived with no history.

Approach

Deployed and extended OpenMRS as the shared clinical record: facility-level configuration, forms designed with the clinicians using them, and reporting mapped to national indicators.

Outcome
History follows the patient
One record spans every facility in the network.
Standards-based exchange
Data moves over FHIR instead of bespoke exports.
Reporting from the record
Indicator reports come out of the same system clinicians already use.
Enterprise Operations

Multi-Branch Enterprise

  • NestJS
  • Elasticsearch
  • S3
  • Tesseract OCR
Problem

Contracts, approvals and scanned records were spread across shared drives and email; finding the current version of a document meant asking whoever touched it last.

Approach

A document management system with versioning, approval workflows, full-text search over scanned files via OCR, and an audit trail on every access.

Outcome
One current version
Versioning replaced parallel copies named final-v3.
Searchable archive
OCR makes scanned records findable by their contents.
Auditable access
Every view, edit and approval is recorded.
Fintech

Microfinance Institution

  • Laravel
  • Android
  • MySQL
  • Redis
  • Mobile Money APIs
Problem

Borrower records, disbursements and repayments were kept in a spreadsheet per branch, so a customer's full exposure was hard to see and arrears usually surfaced only once they were serious.

Approach

A core lending system holding customer records, loan products, disbursement and repayment schedules in one place, with interest and penalties calculated by the system, arrears ageing, and officer access scoped to a branch.

Outcome
One customer record
A borrower's history and current exposure is visible across branches, not per spreadsheet.
Schedules that hold
Repayment schedules, interest and penalties are generated rather than worked out by hand.
Arrears surface early
Ageing reports flag late loans while they can still be recovered.

Your project could be next.

Start a Project