Case study: building a product system that scales
The Problem
Nextpoint’s product experience had evolved over years of feature growth, technical constraints, and shifting priorities. The platform solved genuinely complex problems, but the UI reflected the reality of many mature SaaS products: repeated patterns, inconsistent behaviors, and interfaces that had been designed in isolation over time.
As the product expanded, the same interaction problems were being solved repeatedly across teams:
Toolbars behaved differently depending on the screen
Forms used inconsistent spacing, hierarchy, and validation patterns
Data grids — the core surface of the product — relied on one-off implementations instead of shared logic
Engineering teams were often rebuilding similar UI behaviors from scratch
The result wasn’t just visual inconsistency. It created friction across the entire product development lifecycle:
Slower iteration
More ambiguity during implementation
Increased maintenance overhead
Harder onboarding for both users and developers
At the same time, the product itself was becoming more ambitious. Nextpoint was moving toward a unified “One Nextpoint” experience, combining historically separate workflows into a more cohesive platform. That shift exposed an important reality:
The company didn’t just need redesigned screens.
It needed a shared UI foundation capable of scaling across the product.
Traditional design deliverables alone weren’t enough to solve this. Static mockups could describe interfaces, but they couldn’t reliably encode behavior, implementation logic, or system-level consistency.
The challenge became larger than feature design:
How do you create consistency across complex, evolving workflows?
How do you reduce repeated decision-making?
How do you make design scale operationally, not just visually?
How do you shorten the distance between concept and production?
That became the foundation for building TuscanyDS: a live, component-driven design system implemented directly in React and Storybook.
