Skip to content
Skip to content
Skip to content

Service

One set of tokens and components your whole team actually uses.

Price
From €12,000
Timeline
6 to 10 weeks
Start this project

Opens the contact form with this service picked. Nothing is sent yet.

Scope

I build the system with your designers and the teams who will use it: tokens, accessible components, documentation and the process for changing it. Adoption is part of the job, not an afterthought.

Includes

  • Token pipeline for code and Figma
  • Accessible components with usage notes
  • Visual and interaction tests
  • Migration plan for existing screens

How it runs

  1. Weeks 1 to 2

    Inventory

    Every button, input and table that exists today, counted and grouped. The teams see their own drift on one page.

  2. Weeks 3 to 4

    Tokens

    Colour, type and spacing in one file, generated for code and for the design library from the same source.

  3. Weeks 5 to 8

    Components

    Built in the order your teams need them, each with keyboard behaviour, a usage note and visual tests.

  4. Weeks 9 to 10

    Adoption

    Two real screens migrated with each team, a contribution guide and a weekly office hour that outlives me.

Questions

  • Good. I start from it. Most systems need fewer components and better ones, not a rewrite.

  • Tokens export to the common variable formats, so the library and the code stay in step.

  • By making it the fastest option they have, and by sitting with them for the first two screens.

Service

One set of tokens and components your whole team actually uses.

Price
From €12,000
Timeline
6 to 10 weeks
Start this project

Opens the contact form with this service picked. Nothing is sent yet.

Scope

I build the system with your designers and the teams who will use it: tokens, accessible components, documentation and the process for changing it. Adoption is part of the job, not an afterthought.

Includes

  • Token pipeline for code and Figma
  • Accessible components with usage notes
  • Visual and interaction tests
  • Migration plan for existing screens

How it runs

  1. Weeks 1 to 2

    Inventory

    Every button, input and table that exists today, counted and grouped. The teams see their own drift on one page.

  2. Weeks 3 to 4

    Tokens

    Colour, type and spacing in one file, generated for code and for the design library from the same source.

  3. Weeks 5 to 8

    Components

    Built in the order your teams need them, each with keyboard behaviour, a usage note and visual tests.

  4. Weeks 9 to 10

    Adoption

    Two real screens migrated with each team, a contribution guide and a weekly office hour that outlives me.

Questions

  • Good. I start from it. Most systems need fewer components and better ones, not a rewrite.

  • Tokens export to the common variable formats, so the library and the code stay in step.

  • By making it the fastest option they have, and by sitting with them for the first two screens.

Service

One set of tokens and components your whole team actually uses.

Price
From €12,000
Timeline
6 to 10 weeks
Start this project

Opens the contact form with this service picked. Nothing is sent yet.

Scope

I build the system with your designers and the teams who will use it: tokens, accessible components, documentation and the process for changing it. Adoption is part of the job, not an afterthought.

Includes

  • Token pipeline for code and Figma
  • Accessible components with usage notes
  • Visual and interaction tests
  • Migration plan for existing screens

How it runs

  1. Weeks 1 to 2

    Inventory

    Every button, input and table that exists today, counted and grouped. The teams see their own drift on one page.

  2. Weeks 3 to 4

    Tokens

    Colour, type and spacing in one file, generated for code and for the design library from the same source.

  3. Weeks 5 to 8

    Components

    Built in the order your teams need them, each with keyboard behaviour, a usage note and visual tests.

  4. Weeks 9 to 10

    Adoption

    Two real screens migrated with each team, a contribution guide and a weekly office hour that outlives me.

Questions

  • Good. I start from it. Most systems need fewer components and better ones, not a rewrite.

  • Tokens export to the common variable formats, so the library and the code stay in step.

  • By making it the fastest option they have, and by sitting with them for the first two screens.

Start a project

Three quick picks so the first reply is useful. You finish the message on the contact page.

What do you need?

Rough budget

brief.tsdraft, not sent

Brief so far: nothing picked yet

or write to hello@sorenhale.dev

Nothing is sent from this page. Your picks are kept in this browser tab and wait for you on the contact form.

Start a project

Three quick picks so the first reply is useful. You finish the message on the contact page.

What do you need?

Rough budget

brief.tsdraft, not sent

Brief so far: nothing picked yet

or write to hello@sorenhale.dev

Nothing is sent from this page. Your picks are kept in this browser tab and wait for you on the contact form.

Start a project

Three quick picks so the first reply is useful. You finish the message on the contact page.

What do you need?

Rough budget

brief.tsdraft, not sent

Brief so far: nothing picked yet

or write to hello@sorenhale.dev

Nothing is sent from this page. Your picks are kept in this browser tab and wait for you on the contact form.

Footer

Local time, Oslo

Footer

Local time, Oslo

Footer

Local time, Oslo

Create a free website with Framer, the website builder loved by startups, designers and agencies.