What a design system actually is
Principles, tokens (colour, type, space), components with states, and documentation a developer can use without pinging you. If any of those is missing, say “UI kit,” not “system.” Words on invoices should match files.
A system that only exists in Figma still helps designers. A system that also exists in code helps velocity. SMEs often need the first in year one and the second when a second product starts.
When 12 screens do not need one
A landing, a few service pages, a form, a success state. Shared buttons and type are enough. Spending weeks on atom/molecule taxonomy delays bookings. Ship the path: UI vs UX.
You can still name colours once. That is hygiene, not a system programme.
Tokens vs a Figma sticker sheet
Tokens pay off when the same values must survive web, app, and email. A sticker sheet pays off when one designer and one developer share a file. Do not buy tokens for a single brochure.
Signals you have outgrown one-off screens
Third landing this month looks unlike the first. Dashboard tables each have a different filter. Dark mode was bolted on and broke contrast: visual noise. New hires invent buttons.
Multiple vendors touching UI is another signal. A kit is cheaper than arguing in screenshots.
Cost of a system vs cost of chaos
A real system is a product: it needs grooming. Chaos is slower shipping and inconsistent trust. Pick the cheaper pain. For many SMEs, a half-day Figma cleanup beats a six-week system launch.
Quote it as extra screens and docs, not as magic. See cost in India.
Who maintains it after launch
Name a person. Monthly: add the new component or delete the unused one. If no one owns it, freeze the kit and accept drift — that is an adult choice.
Developers should not invent a second button because Figma was outdated. Process: handoff.
Handoff to developers
Variants, spacing, and states in the file. In Next.js, a small component folder that matches Figma names is the SME version of Storybook. Full Storybook when the team is large enough to open it.
SME alternatives that are not “Atomic Design”
A one-page UI contract: type scale, 8pt spacing, two button types, form anatomy, do/don’t screenshots. Plus brand PDF. That bundle prevents 80% of drift on a small site.
Template-led website builds already have a system (the theme). Customising without a kit is how themes become unique messes.
How Brevia decides
We look at screen growth, not at whether a competitor’s career page mentions a system. Pack default is a kit. Product teams get a scoped system slice after the first 12 screens work.
Talk it through: consultation or contact from Thousand Lights.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.