Click Business
The B2B side of one of Uzbekistan's biggest payment apps: merchant onboarding, POS infrastructure, and a token system that won engineering over.
Role
Senior Product Designer
Duration
6 months
Company
Click
Context
One payment app, three platforms, every size of business
Click is one of the country's dominant payment apps. Click Business is its B2B mode: a merchant can register a business directly in the app, then order and configure POS infrastructure — from a single terminal for an individual entrepreneur to fleets for national supermarket and electronics chains.
I owned the design of the B2B merchant experience while also evolving the design system that served the B2C app, the B2B mode, and the web — three platforms whose styles had drifted apart.
Research
The most profitable users were the hardest to reach
Large merchants brought most of the revenue, but you cannot hallway-test a supermarket chain. I pushed for dedicated research — and when the company formed its first UX research team, I scoped and commissioned deep-dive merchant studies through it: pains, needs, tools, and how the app actually fits into their day.
The defining insight: merchant size completely changes who the user is. An individual entrepreneur personally watches every incoming payment. In a large chain, the app is operated by an accountant — often serving several companies at once — who needs almost nothing from the interface except one thing: exporting reports to Excel. The shape of that report decides whether the product works for them.
That reframed the priorities: reporting and export became first-class features rather than an afterthought, and the interface stopped assuming one kind of merchant.
Design system
Winning engineering over to tokenization — with a tool, not a debate
In parallel, I was unifying the visual system across the three platforms. The codebase was full of hardcoded values; Figma had styles, but unsystematized and applied uncontrollably — which gave engineers every reason to keep hardcoding.
When I proposed full multi-level tokenization, engineering pushed back: they expected an ongoing maintenance burden. Arguing didn't move things. A tool did: I built a Figma plugin that let developers export the current tokens themselves, at any moment, in a paste-ready format for the project.
Manual token sync disappeared from the workflow entirely. The same engineers who resisted tokenization started praising the token system and proactively aligning the codebase with the design system.
Outcome
Strategy informed by hard-to-reach users, and a system engineers wanted to keep
- Merchant research reshaped product priorities for the highest-revenue segment — built around how large merchants actually operate, not how we imagined them.
- Styles unified across B2C, B2B, and web; manual token sync eliminated from the design-to-code workflow.
- Engineering shifted from resisting the design system to actively maintaining alignment with it.
- Helped establish UX research as a practice in the company — the research team and the habit of commissioning studies outlived my tenure.
