Why no client name
Some of our product work happens under non-disclosure agreements – especially MVPs competing in young markets. We respect that absolutely. So we show the process and the design decisions without revealing the client, because the process says the most about how we work.
Context
A B2B service company was managing a growing client base with spreadsheets and email. The processes worked but did not scale: knowledge was scattered, manual-entry errors were costly, and onboarding new employees took too long.
Challenge
Build a tool that brings order to the processes without forcing a revolution in how the team works, and one that can, over time, become a product offered to other companies in the industry (the SaaS model).
What we did
- Product workshop: process mapping with the client's team; separating critical features from nice-to-haves. Out of dozens of ideas, the MVP covered those that solve 80% of everyday problems.
- Prototype and testing: a clickable mock-up of the key flows tested with employees before a line of code existed. Two flows were overturned after testing: they looked right on paper and failed in practice.
- Design system: a component library that makes every next module faster to build and consistent in look.
- Iterative development: releases every two weeks; the client's team worked in the system long before the official "launch".
Outcome
The company moved its core processes from spreadsheets into a dedicated tool, and the owners gained the foundation of a SaaS product with an architecture ready for external customers. The collaboration continues and the product grows in iterations.
