You do not need a 200-component enterprise system. You do need consistent patterns so pages ship faster and stay on-brand.
• Typography, colour, and spacing tokens
• Buttons, cards, forms, and section layouts
• Content rules for headings and CTAs
• Responsive behaviour documented once, reused often
Start with the components you actually use on the homepage, services, and blog. Expand only when repetition appears.
If your team publishes three pages a year, a full atomic system is wasted effort. If you ship weekly campaigns, it pays for itself.
The best systems live in both Figma and the codebase. Shared naming and props reduce “looks right in design, wrong in production” bugs.