How a small studio builds a brand system

By Imran Sheikh · 2026-11-12 · Design · 4 min read

Key points

  • Start with one sentence about who you are and what you refuse to do.
  • Keep the system to a few tokens and rules people will remember.
  • Put it in code so it stays true after launch.

Small teams rarely need a hundred-page brand book. They need a system that a new person can learn in an afternoon and that a developer can follow without asking. The goal is consistency under pressure, when there is a launch on Friday and nobody has time to consult a document.

We are a small studio, and we make our own apps with very different moods. We also work with clients on their products. This is how we think about building a brand system that stays small and keeps working.

Start with the idea, not the logo

A brand system starts as a sentence. Who is this for, what does it feel like, and what will it never do. The last part matters most. Refusals give a team something to decide with. A brand that will never use urgency tricks or stock photos has already answered a hundred small questions.

Write three adjectives and then write the opposite of each. If the opposite is something nobody would choose, the adjective is too vague to help. Warm is weak. Warm but not chatty is a decision.

Keep the idea in the first line of every document you hand to a new person. It will shape the work more than any color choice, because it tells them how to decide when the system has no answer.

Then say it out loud to someone outside the project. If they can repeat it back in their own words, you have an idea. If they nod politely, keep working.

Choose a small set of parts

A usable system is mostly a short list of choices. We keep it to six parts and make each one specific.

  • Color: a canvas, a surface, an ink, a line and one brand color.
  • Type: one family, a five-step scale and a rule for weights.
  • Space: a base unit and a short ladder of multiples.
  • Shape: one corner radius family and one border treatment.
  • Voice: three rules for how we write, with examples.
  • Image: what a good picture looks like and what we never use.

Resist adding a seventh. Every part you add is another thing to maintain and another way to be inconsistent. If a new need appears, find out whether an existing part can stretch to cover it.

Use one accent and make it rare

Small brands often try to look big by using many colors. The better move is the opposite. Choose one brand color and use it for the single most important thing on a screen, usually the main action. When color is rare, it works as a signal.

Photography and illustration follow the same logic. Decide on one style and a few rules for it, such as the kind of light, the kind of crop and the kind of subject. A small set of consistent images looks more expensive than a large set of mixed ones.

Keep the neutrals carefully tuned, because they do most of the work. A slightly warm or slightly cool gray family gives the product its temperature. Test the accent on every surface it will meet, in light and dark.

Choose the shape language with the same care. A single corner radius family, used everywhere, gives a product a recognizable face. Mixing sharp and round corners without a reason makes a system look assembled from parts. Pick the radius, apply it to buttons, cards and inputs, and keep it.

Write the rules with examples

Rules without examples are ignored. Show a right version and a wrong version side by side. A rule like keep headlines short becomes useful when it sits next to a headline that ran too long and the fixed version.

Keep the voice rules practical. Use plain words. Lead with what the user can do. Put the number or the name in the first sentence. A team that follows three clear rules will sound more alike than a team that has twenty vague ones.

Include a short list of words you use and words you avoid. It takes ten minutes and saves hours of editing. It also keeps the product copy, the site, the store listing and the support replies sounding like one team.

A brand system is the set of decisions you never have to make twice.

Keep the system in the codebase

The common failure for a small team is a lovely brand file that nobody opens. Six months later the live product has drifted, because the system and the product were kept in different places.

We solve this by putting the system where the product is built. Color, type and space become tokens in the repo. Components use them and nothing else. A styleguide page renders the tokens and the components from the same source, so a change shows up everywhere at once. This is also how the studio works with clients. We design in their codebase, so the brand system and the shipped product are the same thing.

A developer can then answer most brand questions by reading the code. A designer can answer them by opening the styleguide page. Nobody needs to ask for a file.

Review it on a schedule

A brand system is a living thing. Once a quarter, open the product and look for drift. Count the one-off colors. Look for a headline set in a size that is not in the scale. Each oddity is either a mistake to fix or a signal that the system is missing something.

When the system is missing something, add it deliberately and remove something else if you can. The aim is to stay small. A brand system that fits on a few pages will be used. One that needs a table of contents will not.

Journal · Book a call · Home