Problem
DC extended its SaaS from orders and support into shipping, with the goal of lifting average order value. But the new service didn't look or behave like the ones beside it — there was no brand harmony across the suite, and users lost their footing every time they moved between products.
The cost landed on the team as much as the customer. Designers shared a single component library with no guidelines behind it: they spent significant time hunting for the right component, edited components without publishing back to the library, and applied their own typography and scales. Prototypes shipped with gaps in component states, incorrect hierarchies, and accessibility failures. Developers then coded each screen from scratch instead of reusing one repeated format. The result was an interface that was inconsistent for users and complex for the people building it.
Solution
A scalable, multi-brand design system — one foundation that several brands could theme, rather than one library several brands quietly diverged from.
Five things changed concretely: iconography was rationalised for consistency; the title bar was designed in versions matched to function; typography and type scales were documented in one place; master components were rebuilt with proper variants and states; and visual hierarchy was applied correctly throughout. Guidelines were documented and put through workshops so the system was adopted rather than published and ignored.
Impact: ~20% time saved on design tasks, a 15% increase in average order value across the SaaS services, and a 30-point NPS gain in pilot teams over three months.
Copyright @ 2026 Zara soltani