Case study · Confidential client · Enterprise OMS
Web App Dev
Zero-to-one design and architecture for an enterprise-grade Order Management System, delivered with a global development team.
Client
Confidential (internal enterprise software)
Industry
Operations · B2B
Services
System architecture, UX/UI design, design system, project management
Engagement
MVP to ongoing iterations

(01) Overview
A custom OMS, from zero to a platform teams run on every day.
We provided a zero-to-one, full-service implementation of a custom Order Management System. Our scope covered everything from scalable system architecture and intuitive UX/UI design to detailed project management and coordination with global development teams.
The project has undergone multiple iterations, continuously adding new features based on evolving needs, proving our ability to deliver and sustain critical, high-efficiency operational platforms.
(02) Challenge
Operational software is where good UX usually goes to die.
An OMS touches every order, every role and every exception in the business. The logic is dense, the users are power users, and the cost of a confusing screen is paid many times a day.
It also had to be built by a development team spread across time zones, which meant the design had to be precise enough to act as the specification.

(03) Approach
Map the system, build the language, then design every screen.
We started with the architecture: entities, roles, states and the flows between them, mapped end to end before any interface work. That map became the shared reference for the client, our designers and the engineering team.
On top of it we built a design system for dense operational UI, from typography and colour to tables, filters, modals and status patterns, and then designed the screens themselves. Terminology was treated as UX: renaming a confusing term can align an interface with the real system logic faster than any redesign.
(What we did)
- System architecture
- Entity & flow mapping
- Role-based UX
- Design system
- Screen design
- Dev specification
- Global team coordination
- Iteration planning


(04) Outcome
From MVP through several iterations in a matter of months.
The platform moved from MVP through several iterations in months and is in daily use. We maintain an ongoing partnership focused on continuous updates and feature enhancement. Due to the internal nature of the software, specific details are confidential and available on request.
01
Fast to MVP
Architecture-first design let engineering start building while screens were still being finalized.
02
Built to evolve
A design system and flow map that absorb new features without a redesign.
03
Ongoing partnership
Continuous updates and enhancements, iteration after iteration.
