Design the transaction, not just the catalogue
Checkout, logistics visibility, vendor accountability, and dispute handling were treated as first-class product flows because trust is created after discovery.
Selected Product Work
Co-Founder & Technical Product Lead
Shoppergetit — Structured Commerce Marketplace
A live e-commerce marketplace designed to help shoppers buy from verified SMEs through structured checkout, vendor systems, logistics workflows, request sourcing, bundles, community drops, and dispute handling.
Live productVisit live product
Context
Independent SMEs often sell through fragmented social channels, while buyers need confidence that discovery, payment, fulfilment, and issue resolution will hold together. Shoppergetit was built as commerce infrastructure: a marketplace where operational structure becomes the trust layer.
Problem
The challenge was not simply presenting products online. A multi-sided product needed to coordinate verified vendors, shopper intent, checkout, delivery status, request sourcing, promotional bundles, community drops, and dispute resolution without creating operational confusion.
My Role
As Co-Founder and Technical Product Lead, I shaped the opportunity, product model, workflows, priorities, and release decisions. I translated marketplace requirements into experience and system logic, supervised technical execution, and aligned product decisions with capital and launch realities.
Constraints
- Building trust for new marketplace transactions and newly onboarded SMEs.
- Balancing three operating surfaces: shopper, vendor, and admin workflows.
- Shipping under early-stage capital, team, and go-to-market constraints.
- Supporting exceptions such as unavailable inventory, delivery friction, and disputes.
Product Decisions
Build role-specific operating surfaces
Shopper simplicity required structured vendor and admin controls behind the scenes. Each audience received workflows aligned to the decisions they own.
Expand demand capture beyond search
Request sourcing, bundles, and community drops created paths for intent that a standard product listing model would miss.
Treat monetization as system design
Revenue logic and fulfilment realities informed prioritization rather than being postponed until after the interface was built.
Execution Process
- Mapped critical shopper, vendor, admin, logistics, and exception journeys.
- Defined release priorities around transaction confidence and operational control.
- Directed UX architecture and requirements across marketplace workflows.
- Worked with implementation decisions across a Next.js, Node.js, MongoDB, and Redis stack.
- Used analytics instrumentation and launch learning to inform subsequent product decisions.
Technical / System Thinking
A marketplace is a set of linked state transitions: inventory availability, vendor action, shopper payment, fulfilment status, support escalation, and admin intervention. I approached the product as a controlled operations system, defining the interfaces and decision points that make those transitions understandable and manageable.
Outcomes
- Launched a live commerce marketplace serving verified SME participation.
- Established product infrastructure across shopper, vendor, and admin flows.
- Raised ₦10M in early capital to support the business direction.
- Built a foundation for logistics workflows, sourcing requests, bundles, drops, and dispute handling.
Product Screens
Selected product and workflow views from this work.
Lessons Learned
- Marketplace trust is operational: clear resolution paths matter as much as polished acquisition flows.
- Early role clarity across admin and vendor experiences reduces manual firefighting later.
- Product leadership in a constrained startup requires prioritizing system integrity and commercial learning at the same time.
Build Together
Need product clarity that becomes execution?
I help early-stage teams frame the right system, direct the work, and get a credible product shipped.