I build secure, intelligent systems: national-scale infrastructure for the public sector and financial institutions, plus consumer products taken from zero to launch. Writing production code since I was 12.
Across fintech, public sector, and consumer. My largest work is protected under NDA; what follows is the visible portion. Open any project for the full case study.
My most significant work is built for the public sector and financial institutions and protected under NDA: national-scale access control, revenue digitization, and operational security. I translate executive requirements into architecture, then lead senior teams through delivery.
Escrow-based fintech that builds trust into digital transactions: real-time tracking, dispute resolution, three-party broker flows, and payments for buyers and sellers. I built the technical foundation from scratch and led the pivot into a full marketplace.
A privacy-first AI co-pilot that reads a student's inbox and Canvas read-only, surfaces buried obligations, and reasons about how one slip cascades across academics, money, standing, and visa status.
An AI-native workspace that puts GitHub, Google Calendar, and Jira behind one conversational interface. Ask in plain English and the agent routes the request, pulls context across every tool, and takes the action. Beyond chat it ships consolidated KPI dashboards, sprint intelligence, and a delivery forecast that folds merges into projected finish dates and flags slippage before it lands.
A mobile-first commerce and escrow platform securing payments between individuals and businesses: real-time tracking, automated workflows, and dispute protection end to end. I owned technical direction and hands-on delivery.
Ikot Ekpene, Nigeria's "Raffia City", has fertile land and 51% unemployment, the second highest in the country. AgriLink is the link that's missing: a working marketplace-and-training prototype that lets farmers sell produce to verified buyers, gives buyers search and listings, and adds local weather plus an agricultural expert in chat. Built under Afrinovators, a student agritech think tank at ALU.
A conversational task manager you talk to: speech-to-text capture, intelligent reminders, productivity insights, and sync with GitHub, calendars, Notion, and Jira for one connected workflow.
A full social platform: feed, stories, reels, direct messaging, voice notes, and audio and video calling, shipped free on Android. I started it at 13 with a design well past my ability, left it for three years rather than cut it down, and came back at 16 to finish the thing I'd drawn. Sole developer on all of it.
Real interfaces, not mockups. Scroll each walkthrough and the screen follows along.
University obligations hide in the boring places: an inbox, a Canvas announcement, a finance portal. Qobi's landing page makes one claim: nothing important stays unseen.
Today's view answers a single question: what actually matters before midnight. Items are ranked by consequence, not by timestamp.
Each obligation is traced downstream: a missed assignment becomes a grade risk, then a fee, then a standing issue, then a visa problem. This reasoning is the product.
Permissions are explicit and revocable, and Qobi never writes to a student's inbox. The constraint cut scope and bought trust, the right trade for a product handling sensitive academic data.
Merges, throughput, cycle time, review latency and deploys next to calendar deadlines and overdue items: GitHub, Jira and Google Calendar resolved into a single KPI surface with live auto-refresh. The consolidated view is the whole pitch, made literal.
“How are the state of things” expands into seven traced steps: listed threads, checked sprint status, assessed delivery risk, cross-checked Jira against GitHub, checked for unplanned work. Then it answers. Visible tool calls are a trust decision: an agent with write access to real systems has to be auditable.
Each initiative carries a target date, a burn-up against it, velocity, projected finish and days late. Khove folds GitHub merges into the forecast and writes the narrative, “projected to finish 46 days late, watch for slippage,” with the linked tickets that explain why.
Jira rendered as flow rather than a board: throughput, cycle time, stale in-progress work, and burndown against ideal across active and upcoming sprints. The numbers a lead actually reports on, without opening Jira.
Two-way Google Calendar sync with standups, sprint ceremonies and reviews in a month view, plus fifteen agent suggestions waiting for review. Planning and shipping stop being separate tabs.
The home screen hides the machinery. Buyers see balances and orders; the protection is implied, not explained.
Troco started as a payments tool. I spearheaded the repositioning into a full marketplace, which meant rebuilding discovery, listings, and seller identity on top of the existing escrow core.
Every order carries a state: funded, in transit, delivered, disputed, released. The UI exposes exactly one next action, because ambiguity in a payment flow is a support ticket.
Chat lives inside the order, so evidence and conversation share context. Resolution is part of the product rather than an email thread after the fact.
The home screen is a grid of verbs a farmer already uses: sell, buy, find buyers, weather, tips, ask an expert. No dashboard, no jargon, and a greeting by name. Designed for low digital literacy, which the research named as a key driver of the problem.
Details, photos, review. Crop name, quantity, price in naira, and location prefilled to Ikot Ekpene, because the fastest listing is one where the app already knows where you are and what you grow.
Local weather, pest and disease guidance, daily farming tips, and a route to an expert. This is the substitute for one extension officer per 2,000+ farmers: advice that doesn't depend on someone visiting.
Verified buyers negotiating a 500kg maize order sit in the same inbox as an agricultural extension specialist. Commerce and expertise in one thread, because for a smallholder they're the same conversation.
The day opens already planned. Tasks arrive grouped by effort and deadline so the first interaction is a decision, not a triage session.
Speech-to-text capture with intent parsing: "remind me to review the PR before standup" becomes a scheduled, assigned, linked task. A voice interface has no room to think out loud, which made latency the whole design problem.
Work, study, and personal stay separated, because a productivity tool that mixes contexts gets abandoned in week two.
GitHub, calendars, Notion, and Jira write back both ways, so the app never becomes a second place to maintain the truth.
Onboarding makes one promise and gets out of the way. At 13 I over-designed everything; the version that shipped is the one that learned restraint.
Stories across the top, then posts at full width with the interface receding into the dark. The whole thesis was that the app should disappear while your friends look.
Multi-reaction rails, social proof on who engaged, inline comments, unread badges on chats. This is the layer that took three years of skill to build, and the reason I paused instead of shipping something smaller.
As a Solutions Architect and embedded Product Manager, I lead senior engineering teams on confidential, high-stakes systems: access control, revenue digitization, cloud infrastructure, and operational security, at national scale.
Much of my most significant work is protected under NDA. What you see on this site is a deliberate sample, not the sum.
I started coding at 12, and I'm still early. I gravitate toward hard things: systems where getting it wrong actually costs something. I'm driven by building with purpose. Not just apps, but impact.
Placeholders below, marked as samples. Send me the real quotes and I'll swap them in; the slider scales to as many as you add.
He operates years beyond his age. We handed him an ambiguous, high-stakes brief and he came back with an architecture the entire senior team trusted on day one.
Teni built Troco from nothing and had a thousand people using it in three months. Rare to find someone who ships that fast and that carefully.
Calm, precise, and relentless. He reads the boring places so the important things don't stay unseen, and ships before anyone expects it.
The kind of engineer who is fluent with executives and code in the same meeting. He owns the whole problem, end to end.
Experience, architecture work, products, and education, in a clean document you can read on screen or save as PDF.
Open to founding-engineer roles, architecture work, and collaborations with real stakes. Email is fastest; the form sends it straight to me.