Where it started
Massarat sells its systems to many organizations, yet each one looked and behaved differently: inconsistent screens, a dated interface that didn't reflect the brand, and everyday tasks that were hard to complete. With no shared identity, no shared experience and no ready-made templates, every new product started from scratch.
How I worked on it
I started from Massarat's core identity, chose a new typeface and rebuilt the interface from the ground up: design foundations (colour, type, spacing), then a component library, then screen templates.
I designed the user journeys for the key tasks in two tracks — HR and government warehousing. The template was built as a general foundation; it does not yet cover all of the company's products.
I worked in a team of four and owned the UX and UI end to end, down to every detail in Figma and the developer handoff — 60 screens.
The identity didn't stop at the screens: I also designed the documents the system prints — such as the item control card — in the same language: a clear information hierarchy, colour-coded statuses that read at a glance, and enough white space to stay legible on paper.

What changed
Massarat now builds every screen in one language: a consistent brand, ready-made components and templates for HR and government warehousing. The team starts new screens from a template instead of a blank page, and users meet the same system wherever they go.
Estimated results are marked with “≈”.
