Design systems and component libraries
I’ve built design systems for multi-module enterprise platforms and for 15+ startup products. They make every new screen faster to design and build, and stop a product drifting apart as it grows. Several of them are rebuilt in code on the project pages, with every variant and state.
What this involves
- 01Component library in Figma with variants and states
- 02Design tokens and variables for colour, type and spacing
- 03Usage documentation and Dev Mode handoff
- 04Alignment with code components in Storybook
Where I’ve done it
- 01Plinth CRM: tokens, 34 table cell types, filters and pipeline components
- 02Multi-module enterprise platforms that had drifted apart
- 03Light systems for 15+ startup products that grew with them
How I work
A design system is worth it when it matches how the product is really built. It starts from what already exists.
- 01AuditCollect the colours, type, spacing and components already in use
- 02FoundationsTokens for colour, type and spacing, named so designers and developers mean the same thing
- 03ComponentsThe pieces every screen repeats, with their variants and states
- 04Document and adoptUsage notes and handoff so the team uses the system in new work
Related work
All projects →What clients say
5.0 from 73 reviews on Upwork ↗
Connor B. · Mobile app and web app for an eCommerce site · May 2025“It has been a pleasure working with Florin, and we’re happy he said “yes” to our project. He was our #1 pick based on other feedback we read, and our experience was fantastic. Florin is talented, patient, a good listener, and is highly qualified to take on any project. He has become a true partner and is an excellent collaborator. He’s a seasoned pro!”
Case studies
Questions
What is a design system?
A shared set of components, rules and tokens that designers and developers both use, so the product stays consistent and new features ship faster.
How do you work with existing components?
I usually audit what exists, keep what works and turn it into a documented system.
When does a startup need a design system?
As soon as more than one person designs or builds screens, or the same component starts showing up in slightly different versions. For an MVP, a light system of colours, type and core components is enough; it grows with the product.
Other areas
- UI/UX designResearch, user flows and interface design for SaaS platforms, dashboards and consumer apps.→
- MVP designScoping MVPs to the flows that prove the idea, launch-ready UI and an interactive prototype developers can build from.→
- Rapid prototypingInteractive prototypes for apps and SaaS: clickable in Figma and Framer, or functional in code with AI tools, ready for user testing in days.→
- Embedded product designWorking embedded in product teams: design leadership, hands-on UI/UX and a design system the whole team builds with.→
- App designMobile app design from first idea to App Store-ready screens, for telehealth, education, events, fintech and commerce.→
- AI product designAI UX and user interface design for AI apps, chatbots, assistants and agents: showing model results, confidence and next steps so people can act on them.→
- UX auditUX audits: heuristic evaluation, usability testing and a prioritised list of fixes.→
Let’s talk it through
30 minutes on Google Meet, at a time that suits you.

