Shape Seeds
Menu

ServicesDesign Systems & Branding

A design system your product and brand share.

I turn scattered screens and brand assets into one documented system: colours, type, spacing and components with all their states. Your team builds new screens faster and they look like they belong.

Best for
Growing products, multiple teams
Typical length
4–8 weeks
Built in
Figma, with code tokens
Ends with
Component library + guidelines

Who it’s for

Book this when…

01

Every screen looks slightly different

Five shades of the same blue, three button styles, and nobody knows which is right.

02

Design and code have drifted apart

What is in Figma is not what ships, and developers rebuild the same parts each sprint.

03

The brand stops at the website

Marketing looks one way, the product another, and customers notice.

The offer

What’s included.

The scope is fixed in writing before we start. This is what a typical project covers.

Not included

  • Naming and brand strategy
  • Coding the full component library
  • Illustration and photography production
  • Inventory of current screens and assets
  • Colour, type, spacing and grid foundations
  • Design tokens ready for developers
  • Core component library (buttons, inputs, tables, navigation…)
  • All states: hover, focus, disabled, error, loading
  • Components applied to your real screens
  • Usage guidelines with do and don't examples
  • Handover session with design and dev
  • Brand touchpoints aligned with the product

How it runs

Four steps, each with a clear output.

  1. 1Week 1

    Inventory

    I collect every screen, colour, font and component you use today and show where they conflict.

    Your part
    Access to Figma, the product and brand files.
    Output
    Visual inventory
  2. 2Weeks 2–3

    Foundations

    We agree colour, type, spacing and how they combine. Existing pieces that work are kept.

    Your part
    Two review calls.
    Output
    Foundations and tokens
  3. 3Weeks 3–6

    Components

    I build the components with every state and test them on your real screens.

    Your part
    Weekly review; developer input.
    Output
    Component library
  4. 4Final week

    Guidelines

    I document how to use the system and walk your team through it.

    Your part
    A handover session.
    Output
    Guidelines and handover

What you get

What you walk away with.

Figma

Component library

Published components with all their states and variants, ready to use in new screens.

JSON

Design tokens

Colours, type and spacing as tokens your developers can bring into code.

Figma

Applied screens

Your key screens rebuilt with the system, as proof it works in real flows.

Docs

Usage guidelines

When to use which component, with examples, so the system stays consistent.

Questions

Before you ask.

How is the price set?

A fixed quote based on the number of components and screens in scope.

Do we have to start from zero?

No. I keep what already works and replace only what conflicts.

Will developers be able to use it?

Yes. Tokens and component specs are made for handover, and I review the first implementation with them.

We only need a logo. Is this for us?

Probably not. This service is about how the product looks and behaves, not standalone logo design.

Tell me what you’re working on.

A few sentences is enough. I reply within 24 hours and, if it’s a fit, we book a free 30-minute call to agree the scope.

Start the conversation