Skip to content
filipmusial.com
Properties and stack
client
Revenue Analytics (via MasterBorn)
year
2026
role
Design + prototype
team
Only designer, with a PO, 4 developers and QA

Stack

design
  • Figma
prototype
  • Vue
  • PrimeVue
  • Tailwind CSS
hosting
  • Cloudflare
tools
  • Claude Code

The algorithm suggests the price, the revenue manager decides

Overview

Revenue Analytics, the client, has two apps for hotels. What I’m designing is a mix of the two: one revenue management system (RMS) called N2Pricing. It’s still a work in progress.

Among other things, it lets you track, set and automate room prices. Revenue managers use it to read KPIs, stay on top of their hotels and make strategic calls.

It’s a client tool, so there’s no public link. The data in every shot is made up.

Biggest challenge

The challenge was merging two different products into one solution for clients in the US, Brazil and Portugal. Some features had to be redesigned from scratch. Others had to stay on the backend of one of the legacy apps and still fit the users of the second one.

That’s where I stopped being only the person who cares about good UI and UX. I ran AI-powered audits to check the shape of the endpoints and API contracts, so I knew what was possible and what wasn’t. Delivering a feature as a push to a feature branch on GitHub is bread and butter here.

How I use AI here

AI plays a big role here: the whole design process runs on my AI workflow.

I started in Figma by fitting the app’s theme to the PrimeOne Design System (not my call). With the client’s Lead Designer I prepared the first dashboard screen and a few other details, enough to give the project a thought-through direction.

After that I set up my own Vue repo and moved the theme and the design system from Figma into real code. From then on I designed real features as fully working prototypes, with all the edge cases.

I highly recommend my page about it, How I work. No AI slop there, and you won’t regret it. I promise.

Closer to business than ever

Two products meant that every feature, every new screen and every decision had to be confirmed with both sides. I worked very closely with the account managers, the people who know the clients’ needs inside out: workshops, mapping, and later walkthroughs of my prototypes. Each screen had to pass their test, and if something was missing, we adjusted it.

Did I mention that sometimes we had to stick to another app’s backend? Yes, so not everything was possible. That was my biggest lesson here: finding the middle ground between what’s possible and what’s needed.