We Brought the Full Power of an ERP to the Pocket
If a business's accounting, sales, inventory, and finance are gathered in one place on a desktop, that integrity is only useful while the user is sitting in the office. Yet, decisions are often made in the field, on the road, or at the counter. When VBT Yazılım wanted to close this gap by bringing its web-based ERP Flerpi to mobile, it brought Phexum on board for the development and architecture of the mobile side. We set to work with a single goal: the user should access the exact same integrity they see on their desktop from their phone, without feeling any disconnection.
Featured Results
We released Flerpi's mobile application for both Android and iOS from a single code base and ensured that the platform worked in full integrity with its web ecosystem. Beyond development, we established the technical foundation with VBT for the product to behave consistently across different devices and environments. This work is a good example of Phexum working as a technical solution partner that adds a mobile wing to a mature platform, rather than building a product from scratch.
Who the Client Is and the World They Live In
VBT Yazılım A.Ş. is an established company founded in 1993, providing software, hardware, and consultancy in the field of information technologies. Today, with over 300 employees, it serves many sectors from banking to retail, from energy to the public sector. Names like İş Bankası, Akbank, Garanti BBVA, THY, and SGK are among its clients. The company has been traded on Borsa Istanbul since 2021. Flerpi is a commercial, web-based ERP product where VBT offers this accumulated experience for use across all sectors; it manages accounting, sales, purchasing, material management, and finance with fully integrated modules.
ERP, or enterprise resource planning, is the idea of bringing all a business's fundamental processes together in a single data integrity; issuing an invoice should simultaneously update inventory, current accounts, and accounting, and no record should be disconnected from another. Establishing this integrity on a desktop is an achievement, but preserving it while moving to mobile is a separate engineering feat. When a user enters a sale from their phone, the same rules must apply, and the same data must remain consistent everywhere at the same time. The problem we focused on solving was exactly this.
Cross-Cutting Concepts and Architecture
The most critical issue in this project was cross-platform integrity. Flerpi's value comes from its modules being fully integrated with each other, and the mobile application's task was to carry this integrity to the user's pocket without weakening it. This is the fundamental tension of cross-platform development: releasing rapidly to two platforms while simultaneously preserving data consistency and native user experience. The reason we chose Flutter was exactly because it strikes this balance; while a single code base speeds up development and makes it manageable from one place, the compiled app remains fluid and native on each platform. For VBT, the practical equivalent of this was a single mobile wing capable of evolving at the same speed as the web product, rather than maintaining two separate mobile teams and two separate code bases.
The second critical issue was integration. The mobile app is not an independent island, but an endpoint connecting to Flerpi's existing services; therefore, we designed the mobile architecture from the start to be compatible with the platform's data and session flow. The value of the consultancy side materialized here: by making decisions together with VBT—such as how the mobile side would talk to the existing system and where certain responsibilities should stop—we ensured that the mobile side would remain sustainable in the future as well.
How the Collaboration Began
VBT had a mature product with a solid web foundation; what they needed was a team that could build the mobile wing of this product with the same quality. As Phexum, we joined the project at this stage. Our role in the project was not to design a product from scratch, but to develop the mobile side of an already strong platform in complete harmony with its architecture and ecosystem. That is why we started by first listening and understanding Flerpi's existing structure and data flow; we designed the mobile app to be a natural extension of this structure.
How the Story Was Built
We approached the mobile application with a cross-platform mindset from the start. This meant feeding both platforms from a common code base rather than writing two separate applications for Android and iOS. We brought this decision to life with Flutter; we built an app that outputs to both Android and iOS from a single code base, preserving its native feel on both platforms. As development progressed, we continuously tested the harmony of the mobile side with the web ecosystem: we worked on it until every screen and every flow spoke the same language as its desktop counterpart.
There was also a second track running parallel to development: technical consultancy. We conducted evaluations with VBT on mobile architecture and integration approaches, guiding the overall technical structure so the platform would run smoothly in different environments. We became a partner that didn't just write code, but also shared the engineering logic behind the decisions.
The same rules, the same data, everywhere at once — the desktop's integrity, carried to the pocket.
The Impact We Created
Flerpi's users now carry the power of the desktop in their pockets; they access processes ranging from accounting to sales from their phones with the same consistency as on the web. For VBT, the result was a mobile wing whose architecture was built sustainably from the start, capable of growing at the same rhythm as the web product. New features can be rolled out to both platforms simultaneously from a single place. This work demonstrated how Phexum operates not only on products it develops for its own brand, but also as a technical partner adding engineering power to a mature platform.
