↑ Top

Case study · 2025 to now · Live · qomodo.me ↗

Qomodo

Paying in instalments at a shop counter should feel as simple for the merchant as it does for the consumer. That’s the concept. I lead the design of both sides of that moment, and of everything behind it.

Role
UX Lead, the only designer
Scope
Merchant app, consumer app, payments, risk, collections, internal tools
Context
Fintech, instalments and pay now, in physical shops in Italy
Status
Live, evolving

What is Qomodo

Qomodo lets shops take a payment at the counter, in one go or in instalments. The dentist, the beauty centre, the vet: places where the bill is bigger than a card tap.

The merchant gets paid. The consumer pays over time. Qomodo carries the payment, the checks in between and, when an instalment fails, the collection. Two apps face the public: one for the shop, one for the person paying. Behind them sit the payment system, risk, identity verification, and four internal tools for the people who run it all.

My responsibilities

I own the end-to-end service and UX, from the counter to the collections desk.

I joined in 2025 as UX Lead and I’m the only designer. That means the merchant app, the consumer app, the payment flow between them, and the internal tools for support, sales, risk and collections, plus the admin that holds them together. I set the UX roadmap with the product owner, run discovery with merchants and consumers, own the design system, write the product copy, design the AI features for merchants, and mentor our design intern.

How I work

Six habits. Everything below the line is made with them.

  • Data before designI size a problem in the warehouse, with SQL, before I design for it. It replaced the clusters we assumed about merchants with profiles we could see.
  • Map the service, then the screenWho acts, who waits, what can fail, who holds the money. A blueprint of one purchase is how I start every piece of this product.
  • Code is the source of truthI explore in code as much as in Figma, lately more in code. I build the screen in React or HTML, review it running, ship it, and go back and forth with Figma to refine the details and the UI. Nobody guesses what is live.
  • Legal, Risk and Ops from the first sketchThe rules are material, not a review at the end. I read the regulation myself so the conversation is between peers.
  • Write the copyIn sensitive moments the words carry more than the layout. Who you pay first, a right stated without pressure, no clause paraphrased.
  • AI, with judgmentA small team of agents I built does research, critique and regulatory checks with me. It never writes what a consumer reads without me.

Brasil mix tape

Tap to play