>soren hale — frontend developer
// Process
How a project runs, week by week.
No big reveal at the end. You see working software every Friday, and you always know what moved and why.
// Process
How a project runs, week by week.
No big reveal at the end. You see working software every Friday, and you always know what moved and why.
// Process
How a project runs, week by week.
No big reveal at the end. You see working software every Friday, and you always know what moved and why.
Before
01 / 06
The first call
Thirty minutes. You describe the product and the deadline. I ask about the team, the codebase and what has already been tried.
You get
A written quote within two working days
Week 0
02 / 06
Architecture note
Two pages: routes, data flow, state, what gets tested and what does not. Nothing is built until you have signed it off.
You get
The note, a timeline and a price range
Week 1
03 / 06
First deploy
A real screen on a real URL behind a login, with CI, a preview for every pull request and the performance budget switched on.
You get
A link you can open on your phone
Weeks 2 to 6
04 / 06
One flow a week
Each flow is finished before the next one starts: components, empty and error states, tests. You never wait for a big reveal.
You get
A Friday build and a short written update
Week 7
05 / 06
Hardening
Real devices, slow networks, keyboard only. The numbers are read at the 75th percentile, not on my laptop.
You get
A before and after report
Last week
06 / 06
Handover
Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.
You get
The docs, the recording and thirty days of questions
// The length changes from project to project. The order does not.
Before
01 / 06
The first call
Thirty minutes. You describe the product and the deadline. I ask about the team, the codebase and what has already been tried.
You get
A written quote within two working days
Week 0
02 / 06
Architecture note
Two pages: routes, data flow, state, what gets tested and what does not. Nothing is built until you have signed it off.
You get
The note, a timeline and a price range
Week 1
03 / 06
First deploy
A real screen on a real URL behind a login, with CI, a preview for every pull request and the performance budget switched on.
You get
A link you can open on your phone
Weeks 2 to 6
04 / 06
One flow a week
Each flow is finished before the next one starts: components, empty and error states, tests. You never wait for a big reveal.
You get
A Friday build and a short written update
Week 7
05 / 06
Hardening
Real devices, slow networks, keyboard only. The numbers are read at the 75th percentile, not on my laptop.
You get
A before and after report
Last week
06 / 06
Handover
Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.
You get
The docs, the recording and thirty days of questions
// The length changes from project to project. The order does not.
Before
01 / 06
The first call
Thirty minutes. You describe the product and the deadline. I ask about the team, the codebase and what has already been tried.
You get
A written quote within two working days
Week 0
02 / 06
Architecture note
Two pages: routes, data flow, state, what gets tested and what does not. Nothing is built until you have signed it off.
You get
The note, a timeline and a price range
Week 1
03 / 06
First deploy
A real screen on a real URL behind a login, with CI, a preview for every pull request and the performance budget switched on.
You get
A link you can open on your phone
Weeks 2 to 6
04 / 06
One flow a week
Each flow is finished before the next one starts: components, empty and error states, tests. You never wait for a big reveal.
You get
A Friday build and a short written update
Week 7
05 / 06
Hardening
Real devices, slow networks, keyboard only. The numbers are read at the 75th percentile, not on my laptop.
You get
A before and after report
Last week
06 / 06
Handover
Docs in the repository, a recorded walkthrough and a call with whoever maintains it next.
You get
The docs, the recording and thirty days of questions
// The length changes from project to project. The order does not.
// Questions
Asked before every project.
I take on one main project at a time and usually book four to six weeks ahead. The status line at the top of the site is kept up to date.
Both. I am often the only frontend developer on a small product, and just as often I join an existing team for a few months. For design and backend I work with people I have shipped with before.
A fixed range for a defined scope, or a monthly rate for an embed. Every quote lists what is included and the two or three things that could change it.
React and TypeScript are where I am fastest. I have shipped with Svelte, Vue and plain web components, and I will tell you early if your stack is one I should not be learning on your budget.
// Questions
Asked before every project.
I take on one main project at a time and usually book four to six weeks ahead. The status line at the top of the site is kept up to date.
Both. I am often the only frontend developer on a small product, and just as often I join an existing team for a few months. For design and backend I work with people I have shipped with before.
A fixed range for a defined scope, or a monthly rate for an embed. Every quote lists what is included and the two or three things that could change it.
React and TypeScript are where I am fastest. I have shipped with Svelte, Vue and plain web components, and I will tell you early if your stack is one I should not be learning on your budget.
// Questions
Asked before every project.
I take on one main project at a time and usually book four to six weeks ahead. The status line at the top of the site is kept up to date.
Both. I am often the only frontend developer on a small product, and just as often I join an existing team for a few months. For design and backend I work with people I have shipped with before.
A fixed range for a defined scope, or a monthly rate for an embed. Every quote lists what is included and the two or three things that could change it.
React and TypeScript are where I am fastest. I have shipped with Svelte, Vue and plain web components, and I will tell you early if your stack is one I should not be learning on your budget.
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.