Ozan Superapp
Category
Product Design · Design Systems · Visual Design
/
Sole designer for 15 months across Ozan's products: the consumer-facing superapp and Ozan Business, its SMB payment platform covering UX, visual/graphic design, and the design system connecting both.
Project
Multiple products, one designer: Ozan's consumer superapp and Ozan Business, its SMB-facing payment platform, both running on a single design system I built and carried across them as well as company's graphic design and advertisement needs.
The Role
Design lead on Ozan, a neobanking startup my first time having such a responsibility to build everything ground-up rather than iterating on an existing system. That meant building Ozan's consumer superapp and Ozan Business, its SMB-facing payment platform, both running on a single design system I built and carried across them. As well as, onboarding, feature prioritization, and stakeholder alignment as one connected problem, working directly with engineering and leadership rather than inside a larger design org.
One of the sharpest lessons from that ground-up work came out of onboarding a research misdiagnosis that cost real churn before we found the actual fix.
→ Full story on the research failure and the fix: [link to your existing article]
The Products
Ozan Superapp: consumer app covering QR payments, cashback, phone-number-based payments, a virtual card, and Game Mode, a store for game e-pins.
Ozan Business: a payment provider tool for SMBs, with virtual POS, pay-by-link, and a set of custom components built for merchant-specific flows.
Strategic Decisions
Connected consumer and business payments through one QR system
The biggest cross-product decision: designing pay-by-link and QR payment so an SMB using Ozan Business could accept payment directly from anyone using the Ozan superapp, no separate terminal, no separate payment rail. What looked like two products became one payment loop.
Built and carried a single design system across two audiences
Rather than treat the superapp and the business tool as separate visual languages, I designed one system flexible enough for a consumer wallet and a merchant dashboard. Every new feature on either side extended the same component library instead of starting from scratch.
Designed toward a CEO-set vision for a super app
The direction to expand into cinema tickets, events, and bus & flight tickets came from the CEO. My role was translating that vision into a UX and component structure the product could actually grow into, building the scaffolding a super app needs before the individual verticals existed.
Outcome
Enabled SMBs to accept payment without additional hardware, using QR and pay-by-link through the existing Ozan apps
One shared design system supported feature growth across two distinct audiences without a visual or component split
[Add real numbers if available: merchant count on Ozan Business, Game Mode e-pin sales, cashback adoption, virtual card issuance]
Closing Thought
My time in Ozan taught me that the fastest way to solve the wrong problem is to trust the first plausible explanation. I take this lesson to everything I built since.
