Skip to content
Skip to content
Skip to content

Service

Your product's interface, from the first component to the production deploy.

Price
From €9,500
Timeline
4 to 8 weeks
Start this project

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

Scope

I join your team or work from a design file and take the frontend the whole way: architecture, components, state, tests and the release pipeline. You get working software every week, not a big reveal at the end.

Includes

  • Architecture note before any code
  • Typed component library
  • Tests on every critical flow
  • A handover call and written docs

How it runs

  1. Week 0

    Architecture note

    Two pages: routes, data flow, state, what gets tested and what does not. You sign it off before any code exists.

  2. Week 1

    First deploy

    A real screen on a real URL behind a login, with CI, a preview per pull request and the performance budget switched on.

  3. Weeks 2 to 6

    One flow a week

    Each flow is finished before the next one starts: components, empty and error states, tests. A written update every Friday.

  4. Last week

    Handover

    Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.

Questions

  • No. Wireframes and a brand guide are enough. I settle the details in the browser, where they can be tested on a real phone.

  • You do, from the first commit. It lives in your repository and runs in your CI.

  • The quote lists the two or three things that could move it. If one of them happens I tell you the same day, with the new range.

Service

Your product's interface, from the first component to the production deploy.

Price
From €9,500
Timeline
4 to 8 weeks
Start this project

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

Scope

I join your team or work from a design file and take the frontend the whole way: architecture, components, state, tests and the release pipeline. You get working software every week, not a big reveal at the end.

Includes

  • Architecture note before any code
  • Typed component library
  • Tests on every critical flow
  • A handover call and written docs

How it runs

  1. Week 0

    Architecture note

    Two pages: routes, data flow, state, what gets tested and what does not. You sign it off before any code exists.

  2. Week 1

    First deploy

    A real screen on a real URL behind a login, with CI, a preview per pull request and the performance budget switched on.

  3. Weeks 2 to 6

    One flow a week

    Each flow is finished before the next one starts: components, empty and error states, tests. A written update every Friday.

  4. Last week

    Handover

    Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.

Questions

  • No. Wireframes and a brand guide are enough. I settle the details in the browser, where they can be tested on a real phone.

  • You do, from the first commit. It lives in your repository and runs in your CI.

  • The quote lists the two or three things that could move it. If one of them happens I tell you the same day, with the new range.

Service

Your product's interface, from the first component to the production deploy.

Price
From €9,500
Timeline
4 to 8 weeks
Start this project

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

Scope

I join your team or work from a design file and take the frontend the whole way: architecture, components, state, tests and the release pipeline. You get working software every week, not a big reveal at the end.

Includes

  • Architecture note before any code
  • Typed component library
  • Tests on every critical flow
  • A handover call and written docs

How it runs

  1. Week 0

    Architecture note

    Two pages: routes, data flow, state, what gets tested and what does not. You sign it off before any code exists.

  2. Week 1

    First deploy

    A real screen on a real URL behind a login, with CI, a preview per pull request and the performance budget switched on.

  3. Weeks 2 to 6

    One flow a week

    Each flow is finished before the next one starts: components, empty and error states, tests. A written update every Friday.

  4. Last week

    Handover

    Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.

Questions

  • No. Wireframes and a brand guide are enough. I settle the details in the browser, where they can be tested on a real phone.

  • You do, from the first commit. It lives in your repository and runs in your CI.

  • The quote lists the two or three things that could move it. If one of them happens I tell you the same day, with the new range.

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.