I work at the intersection of Product, Business, and System to turn ideas into software users want, businesses can sustain, and that is engineered to perform, evolve, and scale.I build. I improve. I own.
How the Product, Business, and System framework shapes a real engineering decision.
Sellers, service pros, realtors, and logistics providers needed fundamentally different mobile experiences. The app still had to stay fast, lightweight, and easy to evolve as the product grew.
How do you make one app feel purpose-built for each vendor without building four products?
Each vendor needed a different workflow, dashboard, and set of actions, while the product had to feel consistent across vendor types.
One team, a tight timeline, and a growing product ruled out building four separate apps—the solution had to stay economical to maintain and evolve.
The architecture had to balance reuse, maintainability, and scale without forcing unrelated experiences together.
One adaptive application, shaped around each vendor's business model.
2,000+ PRODUCTS · <3S STARTUP · <50MB APK · <1% CRASH RATE
Measurable outcomes across open-source, real-time products, and engineering systems.
Different challenges call for different kinds of engineering involvement.
BUILD
I help turn ideas into working products—shaping what makes sense to build, making the engineering tradeoffs, and doing the hands-on work to build and ship the software.
IMPROVE
I help identify the changes worth making and engineer them—whether that means removing friction, improving performance and reliability, or making the product capable of more.
OWN
I take responsibility for a product or critical engineering area, making technical decisions, building and shipping, collaborating where needed, and following through as it evolves.
A selection of products I've built, improved, and owned—and the engineering decisions behind them.
Fixtures supported by the product's real-time architecture.
Fixtures supported by the product's real-time architecture.
A real-time football experience, engineered from the ground up.
I built Spotip from its earliest version and later led its development—bringing live scores, predictions, match details, and contests together while engineering for thousands of fixtures, complex match states, and constant updates.
Building the foundations while the product kept moving.
An evolving financial product needed engineering foundations that could evolve with it. I restructured its backend around clearer domain boundaries, improved delivery infrastructure, and built AI-powered workflows while product development continued.
A simple payment journey. A complicated transaction lifecycle.
I designed and built the cross-platform mobile experience, simplifying how customers pay electricity bills while engineering transaction recovery, meter verification, and token handling.
SCREENSHOTS: PRODUCTION UI · DEMO DATA
Making a simple component genuinely simple to use.
I built a lightweight, dependency-free React Native bottom sheet that handles complex interactions internally, so developers can focus on building their interfaces.
Additional products and systems engineered across mobile, web, and infrastructure.
Restored critical ordering and delivery flows across two existing apps, including address discovery, location handling, navigation, and reliability.
PRODUCT RECOVERY / GEOLOCATION
Reworked engineering foundations while improving product discovery, performance, and reliability across an established marketplace.
ARCHITECTURE / MARKETPLACE / IMPROVE
Built a location-aware fuel discovery application for long-haul drivers, connecting nearby fuel stations, changing prices, and geographical search.
GEOSPATIAL / BUILD
Built an adaptive application supporting four vendor business models through workflows tailored to their operational needs.
PRODUCT ARCHITECTURE / BUILDAI is part of my engineering process and the products I build. Human judgment and dependable product behavior guide both.
I give AI clear objectives, product context, and architectural constraints to help plan, implement, and investigate. I evaluate its decisions and challenge its assumptions, remaining responsible for the result and its impact on users.
During Bybull's KYC work, an AI implementation coupled BVN verification with additional checks. I identified the impact on existing users and account recovery, then directed separate verification stages and retryable provisioning.
The model generates suggestions and operations. The engineering system enforces permissions, validates state, and bounds behavior.
I connect models to product context, tools, and backend capabilities. Validation, authorization, deterministic rules, and recovery paths govern what they can do.
My work includes AI-driven workflows in Bybull and prediction-related product experiences in Spotip.
Not every problem needs AI. Not every AI decision should become an action.
It's quieter out here than it is in my head.
I've never been particularly good at leaving a question alone.
I can spend an unreasonable amount of time wondering about things that have no immediate use. Do thoughts come before words, or do we think in words? Why do people behave the way they do? What else could exist if we questioned the way things have always been done?
Those questions take me through technology, philosophy, psychology, business, and sometimes places I can't quite categorize. One question becomes another. I don't always arrive at a conclusion. Sometimes I arrive at another question.
An idea worth building. A product that needs improving. Or something important that needs someone to drive it.
I'd love to hear about it.