Levon Saribekyan

Manymore was growing from one service into a suite, but people who signed up for one module rarely discovered the others — and the product still ran on manual invoicing, with no way to pay online.

I led the onboarding design focused on guiding users from the module they came for toward the others. I designed the platform's monetization flow end to end — pricing, plans and online payments through Stripe.

The new modules brought in more customers, and monetization drove the first revenue.

A client wanted to launch a cashback app with an unusually simple promise: connect your card once, then just pay as usual and earn — nothing to activate or click. The challenge was making an invisible mechanic feel understandable and trustworthy.

I won the project by analyzing patterns across 20+ rejected competitor proposals, then owned the full scope — running the client relationship from presale through delivery. The core design work was making the automatic model legible: communicating that earning happens passively after a one-time card connection. To keep users active, I designed engagement features around the loop — curated lists, challenges, tips and tricks. I built one cohesive cross-platform language while respecting native conventions where they mattered — platform-specific interactions and system patterns.

We launched the MVP to test the riskiest part of the concept: the card integration the entire model depended on. While the product didn't continue — in real-world use the card integration didn't work reliably enough to deliver on the automatic-earning promise — it did exactly what an MVP should: it surfaced a fatal technical assumption early, before heavier investment.

Support staff across two teams ran daily work out of four separate admin systems, switching tools to complete a single job. The fragmentation slowed everyone down and complicated daily operations.

I interviewed customer-service agents to map how work actually flowed across the four tools, which exposed the redundant steps and handoffs worth consolidating. I used that to design a single platform with one coherent information architecture for all teams, then grew the design system from its early foundation into a shared library that kept three designers and three developers consistent as the product scaled.

The unified platform let 15+ agents handle roughly 35% more jobs with no added headcount.

Salita's main customer-facing product was already live but had no Figma source and no design system. This was the product pitched in competitive government tenders, and its design directly affected whether bids were won.

I built the design foundation from scratch, used across the web platform and the mobile app, then partnered with the CDO and developers on a facelift — an update to the visual look at minimal development cost. I designed improvements driven by real user feedback routed through the customer-service team and prepared materials for the tender applications.

We won 3 of 10 government tenders, with direct feedback that our platform had the strongest UX among the competing bids.