Multinet is one of Turkey's leading fintech companies, providing meal card and employee benefit solutions to businesses across the country. Their platform handles a significant share of Turkey's meal card transactions, serving corporate clients of all sizes.

Multinet had been running a core internal operations platform for nearly ten years. The platform was desktop-based, deeply embedded in daily workflows across the entire operations team, and built on a foundation that predated modern web development practices. As the product grew and the team's ambitions grew with it, Multinet made the decision to move this platform to the web.

The Challenge

Moving a decade-old desktop application to the web is not a straightforward rewrite. The scope of the platform, the number of teams depending on it, and the complexity of the workflows it supported meant that the new system had to be built on a foundation that could carry the product for the next decade, not just the next release.

Two things needed to exist before a single screen of the new platform could be built properly: a design component library that defined the visual language across every part of the product, and a frontend component library that developers could build with consistently at scale. Neither existed.

What We Built

We partnered with Multinet's engineering team to build both foundations from scratch and establish the architecture the new platform would run on.

We designed and developed a comprehensive frontend component library in Vue.js and TypeScript, covering every component type the platform would require. Forms, tables, navigation patterns, data visualization, modals, notifications. Each component was built to be composable, documented, and tested. The library gave Multinet's engineers a shared language: the same button, the same input, the same card, everywhere across the product.

We structured the platform on a micro frontend architecture. Given the scale of the operations team and the breadth of workflows the platform needed to support, a monolithic frontend would have created the same maintenance burden the desktop application had accumulated over ten years. With micro frontends, each domain of the platform could be owned, developed, and deployed independently. Teams could ship without coordinating across the entire codebase.

Alongside the build work, we provided architectural consulting throughout the process. Technology decisions at the foundation level have long consequences. We worked closely with Multinet's team to make sure those decisions were made deliberately and with the full picture in view.

The Outcome

With the component library and micro frontend architecture in place, Multinet's development velocity increased by 81%. New screens and features that would have required building from scratch could now be assembled from a shared, tested foundation.

The operations platform that had run on desktop for nearly ten years now runs on the web, built on a foundation designed to scale with the product for years to come.