About(01)
The personbehind the work
Senior backend and AI engineer, payments infrastructure, e-signature engines, and multi-tenant platforms where correctness is non-negotiable. One person, from Postgres schema to LLM agent orchestration.
Building IléHQ, a WhatsApp-first AI concierge live in Lagos, where a 15-step messaging pipeline orchestrates 30+ autonomous tools over a 17-phase booking state machine and dual-market payments (Stripe + Paystack).
Four-plus years across fintech, PropTech and EdTech: virtual bank accounts and cross-chain money movement at Sendcoins, a tamper-proof e-signature engine at LuliSign, a multi-agent grading system at Velric, and a serverless LMS at Digitaley Drive.
Author of engram-dev, an open-source MCP memory server on PyPI that hit 80% on the LoCoMo benchmark, plus Revi, a self-hosted Sentry alternative. The tools I build to stay my own hardest client.
Toolkit(36)
The stack I reach for
7 disciplines, from Postgres schema to LLM agent orchestration.
Languages04
Backend07
Frontend03
AI / ML08
Data03
Payments & integrations05
Infrastructure06
Path(05)
First production role, Inframent
Built field-mapping for telecom contractors; cut search and navigation time ~25% through caching and state management.
Serverless LMS at scale, Digitaley Drive
Architected an LMS on NestJS + Next.js, global cohorts and a 3-stage Paystack pipeline that automated 70% of manual processing.
Fintech & e-signature infra
Backend for Sendcoins' fiat-crypto platform, multi-chain money movement, idempotent ledgers, KYC/AML, and a tamper-proof e-signature engine at LuliSign.
AI systems & founding IléHQ
A CrewAI multi-agent grader at Velric, then founded IléHQ, a WhatsApp-first AI concierge live in Lagos on a 15-step messaging pipeline.
Open source, engram-dev
Published engram-dev to PyPI, an MCP memory server (FAISS + FTS5 + knowledge graphs) that hit 80% on the LoCoMo benchmark.
How I work
Verifiable phases, honest reporting, no big-bang reveals.
Map before I touch anything
On a new system I read it first and write down how it actually works. No blind rewrites, no guessing at the data model.
Nail the contracts
The schema, the API shapes, the money paths. Get these right and the rest of the build stops fighting you.
Ship in phases you can see
Each phase is something running, not a slide. You watch it work as it lands instead of waiting for one big reveal.
Harden the edges
Loading, error and empty states, the retries, the reconciliation. The unglamorous parts that decide whether people trust it.