React development
React development
Dashboards, portals and internal tools in React and TypeScript — built so that the next developer can find where things happen, including when the next developer is not me.
From £75/hrAn estimate before any work startsOne developer, start to finish
01
React is the default for a reason, and the default is also how most web applications end up unmaintainable.
The ones that stay workable are not the ones with the cleverest state management. They are the ones where a new developer can find where a thing happens.
02
What actually gets built
Dashboards and admin
The screens a business actually runs on: tables that hold up at real data volumes, filters, permissions and exports.
Customer portals
Accounts, documents, billing and self-service — usually the cheapest support cost a company can buy.
Internal tools
The ones replacing a spreadsheet, which have to be quicker than the spreadsheet or nobody switches.
Rescuing one that has stopped being changeable
A change in one place breaks something unrelated, the build takes minutes, nobody is sure which components are still used. Recoverable, and it starts with finding out what is actually there.
03
How the work runs
You describe it
Two sentences is enough to start. What you are building, who it is for, and where it is stuck if it already exists.
A scope and a price, inside 24 hours
Not a range with a shrug attached: what is in, what is deliberately out, what each stage costs and what it depends on. If something cannot be priced honestly yet, that is said rather than padded.
Built in the open
Your repository from the first commit, deployed somewhere you can see it from the first week. Progress is a working thing you can open, not a status call.
Handed over properly
Your accounts, your keys, your infrastructure, and a README that assumes the reader is not me. Ongoing work can run on a retainer; nothing breaks if it does not.
- Rate
- From £75/hr
- Scope and price
- Inside 24 hours
- Written by
- The person who scoped it
Inherited a React app nobody can change? Getting it building reproducibly and reading what is in it produces an honest view of its state — useful on its own if you are deciding whether to invest or replace.
Start a project →Common questions
React, Next.js, or something else?
Next.js when pages need to be fast on first load or found by search — a marketing site, a public catalogue, anything with SEO at stake. Plain React behind a login, where nothing is crawled and server rendering buys complexity rather than speed. The deciding question is who the audience is, not which is newer.
Can you work on an existing React codebase?
Yes, and a lot of this work is exactly that. It starts with getting it building reproducibly and reading what is there, which also produces an honest view of what state it is in — useful on its own if you are deciding whether to invest in it or replace it.
Do you build the backend too?
Usually, yes — the API, the database and the deployment, so the whole thing is one person's responsibility rather than a boundary to argue across. Where you already have a backend team, the front end is built against their API and the contract between them gets written down.
04
Tell me what you need built
Two sentences is plenty. If it is an existing codebase, tell me what hurts about it — that is usually the fastest way to a useful scope.