
A small business rarely needs a full design system. Almost every one needs a written-down version of the one it already has. A single page with your colours, type sizes, buttons and form fields, plus a small file of design tokens, gives you most of the benefit for a fraction of the cost. Build more only when several people or several products start drawing from it.
That small version is a design job in its own right, part of UX and UI design, and one of the smallest spells a growing business can order. The guides that rank for this question mostly come from agencies and tool vendors, and they split into two camps: "every business needs one" and "only big companies need one". Both skip the part a business owner can act on, which is how small the first version can be and how to tell when it has outgrown itself.
What is a design system, in plain terms?
Nielsen Norman Group defines a design system as "a complete set of standards intended to manage design at scale using reusable components and patterns." In practice that means a style guide, a library of ready-made parts such as buttons and cards, rules for how they combine, and the people who keep all of it current. The last part is the expensive one.
The same article is blunt about the cost: creating and maintaining a design system "is a time-intensive activity which requires a dedicated team." Even in large companies those teams are small. A 2026 Nielsen Norman Group article, drawing on five years of zeroheight's design-system reports, says most design-system teams have just two to five people, and that in organizations of 5,000 employees or more they average about 9 to 11. A ten-person business can't fund that, and it doesn't have to.
You already have one, it just isn't written down
Every live website runs on design decisions: a brand colour, a heading size, a button shape. On a site built with WordPress, Framer or Webflow, many of them sit inside the theme or template settings. On a site built in code, they live in a stylesheet. The trouble starts when nobody can say where they live, and each new page, landing page or social post re-decides them.
Brad Frost described a quick way to see the damage back in 2013. An interface inventory means taking screenshots of every distinct version of each component on your site, buttons with buttons, headings with headings, and laying them side by side. His example was his own bank's website, whose button styles he called "all over the place." On a small business site that has passed through a few freelancers, buttons are a good place to start the same exercise.
How small can a design system start?
Start with one page and one file. The page shows your colours with their names and uses, three to five text sizes, your button states, form fields and the spacing steps you allow. The file holds the same decisions as design tokens. That is enough for a freelancer, a new hire or an AI tool to produce work that looks like yours.
The idea isn't new. In a 2018 Sparkbox article, Bryan Braun asks "Do you really need a design system, or do you just need better documentation?" and suggests that a strong variables file may cover most needs. He quotes Kaelig Deloumeau-Prigent of Shopify, who recommends starting with "super small abstractions around your color system, your typography" and growing them only if the company grows.
For a small business, a useful first page covers:
- Colours: primary, secondary, text, background, error and success, each with the pairs that are allowed together. Check every text pair against the WCAG ratios; our article on colour contrast for websites has the numbers.
- Type: one or two typefaces, three to five sizes, and which size each heading level uses.
- Buttons: one main style, one secondary style, and how each looks when hovered, pressed and disabled, sized so a thumb can hit them (the details are in our piece on tap target size on mobile).
- Form fields: a text field, an error message and a label, shown once.
- Spacing: four or five steps, used everywhere.
Leave out the rest for now: illustration rules, motion, a component for every edge case. Each extra page is something someone has to keep true.
Why a design tokens file is worth having in 2026
A design token is a named design decision, such as "primary colour" or "body text size", stored as data instead of being buried in one tool. Since October 2025 there is a stable, vendor-neutral format for these files. That makes the decisions you pay for portable between design tools, website builders and code.
The Design Tokens Community Group, a W3C community group, announced the first stable version of its specification, 2025.10, on 28 October 2025. The announcement describes it as "a production-ready, vendor-neutral format for sharing design decisions across tools and platforms," with support for light and dark themes and modern colour spaces. The group's site lists adopters including Figma, Framer, Penpot, Sketch, Tokens Studio and Style Dictionary.
This matters more to a small business than to a large one. A small company changes suppliers: a new designer, a different agency, a move from a website builder to custom code. When your colours and type scale sit in a standard file, the next team can import them instead of measuring your old site with a colour picker. The small-business guides that rank for this question don't mention the format, though it changes what a minimal design system costs to carry from one supplier to the next.
When is a full design system worth building?
When the one-page version keeps breaking. The signs are concrete: several people or teams design and build at the same time, you run more than one product or site, you keep re-explaining the same rules in reviews, or a rebrand is coming. Before that, a written page, a tokens file and one person who owns them are enough.
Braun's warning applies here. He calls a design system built for a small, well-connected team "a premature abstraction," and points out that a system shows its value during active development, so a site that is mostly finished gains little from one. Nielsen Norman Group makes the same point about prototypes that are still likely to change. If your site gets a new page twice a year, keep the one-pager. If you are launching a customer portal next to a marketing site, with an outside developer on each, that is when shared components start paying for themselves.
Whatever the size, give it an owner. The 2026 Nielsen Norman Group article warns that small teams become fragile when knowledge stays in people's heads, which is true of a two-person design team and even more of a one-person business.
What to ask for when you hire someone
If you commission a new site or a redesign, ask for the one-page guide and the tokens file as deliverables, in writing, before the work starts. Ask that the tokens use the 2025.10 format, and that buttons and form fields in the finished site come from the same definitions. Both are far easier to produce during a project than to reconstruct from a finished site.
onlyspell designs and builds websites and complex systems. If you want to work out how much of a system your business actually needs, talk to us about your project.
Frequently asked questions
What is the difference between a style guide and a design system?
A style guide records visual rules such as colours, fonts and logo use. Nielsen Norman Group describes a design system as a larger set that usually includes a style guide, a component library and a pattern library, plus the people who maintain them. Most small businesses need the style guide part first.
How long does it take to set up a minimal design system?
It depends on how consistent the existing site is. A small business can start by taking screenshots of every button, heading and form field on its site, choosing one version of each, and writing those choices on a single page with a matching tokens file.
Can I use a public design system instead of making my own?
You can borrow structure and components from public systems or from a good theme, and many small sites do. You still need your own page that records your colours, type and buttons, because those are what make the result look like your business and not like the template.
Sources
- Nielsen Norman Group: Design Systems 101 (Therese Fessenden)
- Nielsen Norman Group: Small by Design, the strength of lean design-system teams (Huei-Hsin Wang, 2026)
- Sparkbox: When NOT to Use a Design System (Bryan Braun, 2018)
- Brad Frost: Interface Inventory (2013)
- W3C Design Tokens Community Group: Design Tokens specification reaches first stable version
- Design Tokens Community Group: specification and adopters
If you still need additional help in developing and designing your website, our magic is here to help. Contact us today, and our wizards will help you immediately with your digital marketing needs!


