Eze / Marketplace · Product & engineering
A B2B marketplace connecting electronics businesses across 30+ countries. Built from the ground up as co-founder and CTO.
The challenge
Build a marketplace where electronics businesses can trade across borders, with the pricing, bidding, and operational systems needed to support a growing global customer base.
My contribution
The outcome
Eze generated more than $70M in GMV and $6M in revenue, serving 12,000+ business customers across 30+ countries. The company raised $3.7M in venture capital following Y Combinator W20.
My ownership
As co-founder and CTO, I owned technical direction, marketplace architecture and building the engineering organization. My role grew from building the product to leading the people and systems behind it.
The wider team & tools
Eze was a team effort: more than 60 people across engineering, operations and business development, including 20+ engineers. The commercial results below belong to that company and team. I moved into an advisory role in July 2025.
How it fits together
A Next.js interface for inventory, buying and marketplace interactions.
Shared cart state, shipping choices, invoices and explicit payment steps.
Order APIs connect the experience to payment and fulfillment systems.
Currency, language and country restrictions are part of the product flow.
Simplified view of the archived marketplace. Next.js, shared state, order APIs and payment integrations are visible in the frontend source. NestJS and MongoDB are the backend stack reported in my résumé.
Engineering & product judgment
The enterprise frontend separates shipping, payment selection, payment execution and confirmation. Orders and invoice purchases share the checkout experience.
That structure makes the stages visible, while creating a responsibility to keep shared order, address and payment state consistent.
The archive includes localized interfaces, currency conversion, shipping offers and country restrictions. These are connected to the buying journey.
More markets expand the product surface. A payment choice or shipping rule has to make sense in the buyer’s actual context.
My scope included architecture, integrations and leading an engineering organization of 20+ within a broader company of 60+ people.
As the team grows, technical direction has to be clear enough for other people to make good decisions and own delivery.
Inside the implementation
An international electronics order can involve an invoice, store credit, a shipping restriction and several payment methods. Treating all of that as a single happy path hides important product states.
The archived implementation models separate checkout stages and integrates shipping, billing, invoice and payment data. It shows the operational depth behind the marketplace interface.
My leadership lens: the edge cases customers encounter repeatedly deserve a place in the roadmap.
Outcomes, with context
Company-wide cumulative figure reported in my September 2026 résumé; distinct from revenue.
Reported company outcome. The source does not specify the measurement window.
Reported customer count across 30+ countries; not a monthly active customer metric.
Role, team size and business figures: September 26, 2026 résumé. Technical detail: original Eze frontend archives. The commercial figures have not been independently audited for this portfolio.