A Nigerian product studio building software across business, public life, and applied AI.
Available for projects

I build the systems Nigerian businesses actually run on.

Schools, hospitals, estates, pharmacies, land sales, hotels. Nineteen products in the portfolio — and eleven playable demos you can explore here with sample data. Product cards distinguish live services from prototypes.

What does Mpaukwu Trading do?

Mpaukwu Trading designs and builds software products and digital systems across multiple fields. Its work includes hospital and pharmacy workflows, shop and school management, hotel operations, estate access, food technology, marketplaces, property platforms, computer vision, and AI-assisted systems. The studio also builds custom software, automations, and internal tools for organisations.

Entity proof: Mpaukwu Trading is a CAC-registered business name and sole proprietorship (BN 7294223), active since 10 January 2024 and registered in Ohafia, Abia State, Nigeria. Its 2025 annual return was accepted by CAC on 8 April 2026. Verification uses CAC registration and annual return records, portfolio case studies, founder credentials, and public policy pages. Review the verification details.

11Products you can try live
1,037Automated tests, PlotForce alone
BN 7294223CAC registered since 2024

The portfolio

Nineteen products. Each one solves a specific Nigerian problem.

Choose a product or browse three at a time. Eleven have playable walkthroughs with sample data.

Klas Manager

Schools

Collect online or at the bursar's desk. Keep fees, receipts and parent balances together, and give the school a free website for its stories.

Free softwareOnline + counter feesParent portalSchool webfront

Built onNext.js 15 · React 19 · Prisma · PostgreSQL · NextAuth

MediSeen HMS

Hospitals

Laboratory work and billing belong to the same patient record, so departments do not have to reconstruct the visit from separate notebooks.

TriagePharmacyLaboratoryBilling

Built onReact 19 · TypeScript · PostgreSQL · Docker · Playwright

MyNaijaEstate

Estates

Network dies at the gate. The guard still verifies the pass, and the log catches up when signal returns.

QR & OTP passesOffline guardSOSDues

Built onNext.js 16 · Prisma · PostgreSQL · Passkeys · Web Push · PWA

SortAm

Marketplace

You need a plumber today. Not a phone number from a group chat — a verified one, with the money held until the work is done.

Verified prosQuotesProtected payments

Built onTypeScript · self-hosted · Paystack · eTranzact in progress

StoreBase

Shop operations

“Carry small small” is how half of Nigerian retail actually works. StoreBase tracks that debt instead of pretending it away.

Offline POSMulti-branchDebt tracking

Built onNext.js 15 · Prisma · PostgreSQL · NextAuth · Tailwind

OnsiteBoss

Salons & spas

Braiding starts. Three packs leave the store, the bill grows, and the stylist gets credited — all from one tap.

Live floorRunning billsRecipesCashier

Built onReact 19 · Vite 6 · Fastify · PostgreSQL · Zod

PlotForce

Land sales

Two buyers tap pay on the same plot. One gets it. The other is turned away before any money moves.

Atomic claimsDouble-entry ledgerRefunds

Built onDjango 4.2 · DRF · PostgreSQL · Celery · Redis

In buildTry it live

NaijaStay

Hotels

The till says 44 bottles are left. The shelf says 42. That ₦3,600 gap is the entire product.

Front deskRoom-nightsReconciliation

Built onReact 18 · Vite · Tailwind 4 · offline-first

Oasis Spring Pharmacy

Pharmacy

A prescription-only medicine sits in the cart. Checkout stays shut until a pharmacist has actually looked at it.

StorefrontRx workflowTrackingPWA

Built onNext.js 16 · React 19 · Zod · PWA

VIGIL

Edge-AI vision

A goat at the fence at 5am gets logged. Two people at the fence at 2am make your phone ring.

DetectionThreat scoringAlertsReports

Built onFastAPI · SQLAlchemy · Ultralytics YOLO · OpenCV · React + Vite

OpenKYB

Verification & risk

One company, four spellings, one answer — and every point of the risk score traces back to a document you can open.

Open-sourceEntity resolutionEvidence

Built onNext.js 15 · React 19 · TypeScript · open-source

In buildTry it live

Helm

Portfolio operations

Move a product to “Live” with no users and Helm flags the claim instead of printing it on a slide.

Apps & statusCampaignsTasks

Built onNext.js · PostgreSQL · internal studio tool

In buildTry it live

FleetOS

Fleet & logistics

The bus earned ₦1.26M. After fuel and service it made ₦70,000. Only one of those is profit.

Fleet boardBookingsProfit per vehicle

Built onNestJS backend in development · React front end

SidScan

Automotive hardware

P0420 means your catalytic converter is failing. SidScan says that in plain words, with a naira range.

OBD-IIPlain languageTokunbo check

Built onOBD-II · ESP32-class firmware · companion PWA

OurProfit

Retail operations

POS, stock, staff PINs and owner oversight in one place, so the shop floor and the back office stop disagreeing.

POSInventoryStaff accessCRM

Built onNext.js · PostgreSQL · offline sync

Savour

Food technology

Menus, orders and kitchen flow for Nigerian food businesses that mostly run on WhatsApp today.

MenusOrdersKitchen

Built onNext.js · PostgreSQL

Prism Global

Real estate

A Lugbe Extension development, sold properly online: listings, unit galleries and buyer enquiries that reach a human.

ListingsGalleriesEnquiries

Built onStatic site · CDN · enquiry routing

Africa Connect

AI trust layer

An identity and trust layer for African services, built for the moment the thing on the other end is an agent, not a person.

IdentityTrustAgents

Built onNext.js · identity & trust APIs

Vision models & Nigerian training data

Applied AI research

Detection models trained on Nigerian scenes, because a model trained elsewhere does not see a Nigerian street.

Computer visionDataset workResearch

Built onPyTorch · Ultralytics · Nigerian-scene datasets

Method

Business process, engineering, automation and operational discipline in one loop.

Useful after the demo is over. The studio opens every layer rather than handing over a front end and wishing you luck.

01

Product strategy

We learn your language first — the words your staff already use for the work — then design around that, not around a schema.

02

Data and workflows

Roles, states and money movements modelled explicitly, so the admin panel can explain the business rather than just edit it.

03

Backend and APIs

Multi-tenant boundaries, double-entry ledgers, approval ladders and audit trails. The parts that are expensive to retrofit.

04

Infrastructure

Coolify, VPS, Docker and offline-capable clients, chosen for who actually operates it after handover.

Readiness

Built for operators who need systems to hold together.

A product is not ready until it has been abused. The readiness audit is the version of that done deliberately, before real users do it for you.

Boundaries

Roles and tenant access

Can a guard reach the finance page? Can one company read another’s records? Checked, not assumed.

Money

Payment leakage

Where value can escape: abandoned checkouts counted as revenue, commission paid on sales that unwind, refunds nobody approved.

Recovery

Reliability

What happens when the network dies mid-transaction, and whether the record survives it.

Evidence

Audit trail

Whether an administrative change can be attributed, reviewed and reversed months later.

Engagements

What this costs, published.

Most studios make you ask. Pick what you need and the range updates — so you can tell before any call whether this is the right conversation.

1 · What do you need?
2 · What is in it?
3 · Who operates it after handover?

Case studies

Four builds, including what I deliberately did not build.

The last line of each is the one almost nobody writes, and the one worth reading.

01MediSeen HMS
The problem
Hospitals ran on paper files, a pharmacy book and three spreadsheets that never agreed.
What I built
Patient registration, triage, consulting room, pharmacy, laboratory, admissions and billing on one record, with an offline-capable deployment for facilities that cannot rely on connectivity.
What it changed
Charges are raised by the department that does the work, as it does it — so the bill is the sum of what happened rather than what anyone remembered.
What I deliberately did not build
No native mobile app. Hospitals asked for it; the browser reaches every machine already on the ward, and a second client would have doubled the surface to keep correct.
Read the full case study →
02MyEstate
The problem
Gatehouse logbooks could not say who approved a visitor, or which guard was on duty when they came in.
What I built
Resident-approved QR and OTP passes, an offline-capable guard workflow, SOS alerts, dues and estate communication — on a prepaid token model so a small estate can start without a subscription.
What it changed
A pass is spent the first time it is used, and the gate verifies on the device. Estates kept working through outages that used to stop them.
What I deliberately did not build
No facial recognition. It was the most requested feature and the easiest to sell; it was also the one most likely to be wrong about a real person at a real gate.
Read the full case study →
03StoreBase
The problem
Shop owners tracked informal credit in exercise books, and could not tell profit from turnover.
What I built
Offline-first POS and inventory with multi-branch staff roles, a CCTV view for owners, and explicit “carry small small” debt tracking.
What it changed
Two flat pricing tiers and a 14-day trial, because the buyers would not sign anything they could not predict the cost of.
What I deliberately did not build
No accounting integration. Shops here do not keep books in the systems those integrations expect, so it would have been a feature for a user who does not exist yet.
Read the full case study →
04SortAm
The problem
Finding a trustworthy artisan meant asking a WhatsApp group and hoping.
What I built
A fully self-hosted marketplace with verified professionals, booking, quotes and payments held until the work is done, with Paystack live and eTranzact in progress.
What it changed
Self-hosted on purpose: the trust layer is the product, and renting it from a platform that could change its rules was the one risk worth engineering away.
What I deliberately did not build
No instant payouts. Artisans asked for them constantly; releasing money before the customer confirms would have removed the only reason customers trusted the platform.
Read the full case study →

Straight comparisons

The honest version of “why not just…”

Compare five products against named alternatives, with concise recommendations and public sources.

Choose a product to compare

Before you start

What founders usually ask first.

How much does it cost to build a custom SaaS product in Nigeria?
It depends on scope, but most founder-led MVPs land in the low-to-mid millions of Naira, priced against the actual workflows involved (roles, payments, admin surfaces) rather than a flat package rate. Share the operating problem and a straight quote follows.
How long does it take to build an MVP?
A focused MVP with one or two core workflows typically takes 4 to 8 weeks. Multi-role platforms with payments, admin controls, and integrations run longer. The timeline is set after mapping the actual workflow, not guessed upfront.
Do you offer support after launch?
Yes. Every build ships with a deployment and handoff plan, and ongoing support arrangements are available for bug fixes, feature additions, and infrastructure monitoring.
What is a SaaS production readiness audit?
A defensive review of a product you already own or have permission to test: attack surface, role and tenant isolation, payment leakage, deployment posture, and abuse cases, ending in fix tickets and a Go or No-Go readiness score.
Can you take over a product built by another developer?
Yes. This usually starts with a readiness audit of the existing codebase so the real state of the product (and its risks) is clear before committing to a handover.
Do you work with clients outside Nigeria?
Yes, remotely across Africa and globally. The studio is Nigeria-based and Nigeria-first in its thinking about payments, trust, and field realities, but the engineering itself travels.

Start building

Bring a business process, a product idea, or a SaaS risk.

We will turn it into a system with a clear workflow, an admin surface somebody can actually operate, a deployment path, and a readiness plan.

Message on WhatsApp Project intake form