As Lentune’s range of tools expanded across invoice automation, approvals, and job management, fragmented UI patterns began slowing down team velocity. Engineers were rebuilding existing components, and designers lacked a single, scalable source of truth.

​

I identified the lack of a shared UI foundation as a scaling constraint and led the creation of Lentune’s design system from the ground up - defining the token architecture, component model and reusable patterns used across the product.

The goal wasn’t simply visual consistency; it was to reduce repeated design decisions and give product and engineering teams a common foundation for shipping faster.

To speed up layout creation and ensure consistency across data-dense workflows, I established standardised UI patterns and master page templates.

• Master Page Templates: Built reusable Figma template components for complex invoice processing views, approval queues, and data tables -allowing designers to drop in pre-structured layouts and quickly assemble new screens.
• Consistent Component Behaviours: Standardised interactive states, validation logic, and edge-case behaviours for form fields and table cells.
• Figma-to-Code Parity: Structured component properties, variant logic, and auto-layout rules.