systems nominal — accepting new work

I build the backend, the bots,
and the bits users never see —
but always feel.

Full-stack software, APIs that don't fall over, and the AI and automation layered on top. Currently maintaining a student platform used by thousands at a Nigerian university — designed, built, and deployed end-to-end by me.

// what I run

Five systems, one operator

These are the core competencies I apply to every project — from idea to production.

SystemWhat it coversNotes
Full-stack builds
Node.js / Express backends, MongoDB, and interfaces from plain HTML/CSS to React — shipped as one coherent product, not handed off in pieces.
deployed on 3 platforms
APIs & backend
REST APIs designed to survive contact with real traffic — rate limiting, input sanitisation, HMAC-verified webhooks, and auth that doesn't leak.
hardened w/ helmet
UI/UX
Design systems built from CSS custom properties — consistent color, type and spacing tokens that hold up across dark mode, mobile, and new features.
token-based
AI & automation
LLM pipelines that process real files at scale — long-running background workers, key rotation, and progress reporting, not a single API call in a demo.
handles 80MB+ jobs
Telegram bots
Conversational bots that browse content, run quizzes as native polls, and answer questions with AI — built to keep working while you sleep.
built w/ Telegraf

// currently in production

Selected work

Real platforms, still running, still being extended.

● live — flagship build

ProjectPQ

A student super-app for University of Port Harcourt, built solo. It combines a library of past exam questions with AI-generated explanations, auto-graded CBT quizzes, a CGPA calculator, a LiveKit-powered group study room, push notifications, and a vendor marketplace with escrow — all aimed at 20,000+ students.

20,000+target students
6core features shipped
1person building it
Node.js / Express MongoDB AWS S3 Socket.io LiveKit Gemini AI Telegram Bot
View the live platform ↗

ProjectPQ Market

A vendor marketplace built into the platform — escrow-backed transactions, a dashboard for sellers, and shareable vendor profile pages with proper social preview cards.

FlutterwaveMonnify

First Baptist Church, Ovom

A freelance church website built on the same design-token system used across my other work — clean, fast, and easy for a non-technical team to maintain.

Design systemFreelance
View site ↗

// how it gets built

The approach

No agency layers. This is how a project actually moves when one person owns it end to end.

understand

Start from the real constraint

Every platform I've built has had a real limit to design around — low-end devices, patchy Nigerian payment rails, or a budget that rules out a full team. Good architecture starts by naming that constraint, not ignoring it.

build

Ship in working slices

Features go out as complete, usable pieces — a quiz that grades itself, a bot that actually answers, a payment page that actually confirms — rather than a wall of code merged all at once.

harden

Security is not a later step

Rate limiting, input sanitisation, and webhook verification go in alongside the feature, not after an incident. I test this thinking on platforms like PortSwigger's Web Security Academy and TryHackMe as a matter of habit.

Have something that needs to run reliably?

Tell me what you're building — a platform, an API, a bot, or all three. Let's discuss your requirements.

✉ Email me