AnthonyHughes
Veygo 2025 Case study

Scaling design at speed: adopting ShadCN

How we used open-source tooling and tight collaboration to accelerate design and engineering delivery at Veygo.

~30%faster time-to-implementation
2system layers: tokens + components
Scaling design at speed: adopting ShadCN — project imagery (placeholder)

Problem

Looking ahead to 2025, it was clear our existing design infrastructure wouldn't scale with the ambitions of the business. We needed a faster, leaner, more consistent way to build across Veygo's product ecosystem — from quoting journeys to marketing touchpoints. Design was duplicating effort; engineering faced growing friction around component alignment and visual consistency.

My role

I led the product design team in implementing a scalable, token-driven design system built on ShadCN, working closely with engineering stakeholders on structure, priorities, and rollout across web and mobile.

What we did

  • Foundation design system. A central token library defining colour, typography, spacing, sizing, and radii — one source of truth from app UI to landing pages.
  • UI component system. Built with ShadCN and Storybook: reusable, accessible components with web/mobile parity, giving designers and engineers shared building blocks and smoother handoff.
  • Ways of working. Weekly syncs and async audits with engineers; design tokens taught as a foundation-first mindset; component prioritisation workshops sequenced by roadmap velocity; Figma libraries and Storybook run in tandem to kill duplication.

Outcome

By combining ShadCN's flexibility with clear system architecture and tight stakeholder collaboration, we significantly sped up our quoting redesign rollout.
  • ~30% faster time-to-implementation on new quoting screens.
  • Improved visual consistency across web and app experiences.
  • Fewer QA and design-review cycles by aligning tokens and variants up-front.