Development
React development for web applications
When the thing you need is closer to an application than a website — a dashboard, a customer portal, an internal tool people use all day — React is usually what it gets built in. I build those, and I join codebases that already exist.
When this makes sense
- A spreadsheet or a manual process has quietly become the tool the team runs on
- Customers need to log in and do something, not just read a page
- You have a React frontend and need someone senior on it who will also go into the backend
How it works
- 01
Scope
We agree what it has to do and what it explicitly does not, in writing. That is what makes a fixed price honest rather than a bet.
- 02
Build
Working software in front of you along the way, deployed where you can click it. Changing direction is cheap early and expensive late, so the demos come early.
- 03
Ship
Deployed, documented, and yours — the code and the infrastructure both. You can hand it to another developer whenever you want.
What the work covers
- Frontend and the API behind it, so nothing waits on a second supplier
- Authentication, permissions and the parts that are boring right up until they are wrong
- Accessibility and real-device testing, not just a desktop browser
- Tests where breakage costs money, and a deployment anyone on your side can run
Common questions
- What does a React application cost?
- A defined build starts at DKK 48,000, which is 80 hours at DKK 600 an hour, with the scope, the price and the delivery date agreed before anything is written. Larger applications are the same arithmetic with more hours, and you can always check the sum.
- Do I need a React application, or would a website do?
- If visitors mostly read, a website is cheaper to build and cheaper to keep. The moment people log in and change things, you are building an application whether you call it one or not, and the cost of pretending otherwise arrives later as a rebuild. I will tell you which one you have.
- Do you do the backend as well?
- Yes. I am genuinely full-stack — Node and TypeScript, PHP and Laravel, Python, Go, with Postgres or MySQL underneath. Most of the expensive problems in a web application live at the seam between frontend and backend, which is exactly where handing the two halves to different suppliers hurts.
- Can you take over or join an existing React codebase?
- Yes, and it is a large part of the work. It normally starts with a technical review at DKK 6,000 — I would rather know what is in there than promise a delivery date over code I have not read.
- Which React setup do you use?
- Whatever the project is already on, if it is on something. For new work: TypeScript throughout, a real router, TanStack Query for server state, and Tailwind. This site runs that stack, server-rendered, so you can look at the result before you buy it.
Other stacks I work in
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.