Backend and API work for a front end you already have
You have the front end. What is missing is the system behind it. I build the database, the admin and the figures page that tells you how the business is doing, and hand over documentation and tests somebody else can pick up.
This is for you if any of this sounds familiar
You have a site or app, but the real data lives in spreadsheets
The front looks finished and the back is a file being passed around. Two people edit at once and nobody knows which copy is true.
You are an agency or a design-side freelancer
You can deliver the front end but the system behind it needs someone else. I subcontract and sign an agreement not to approach your client.
The old system still runs, but nobody dares touch it
No documentation, no tests, and whoever wrote it has left. Every change is a gamble on what breaks.
Money or another system is involved
Getting this wrong costs money rather than looking wrong. It needs somebody thinking about repeated calls, floods of traffic, and work lost halfway through, from the start.
Three packages. Pick the one that matches what you actually need
These are full project prices, not starting points that grow later. If anything falls outside the scope, I tell you the number before I start on it.
- A schema designed from what you really hold, not from guesswork
- Up to 8 kinds of record and 15 requests, named in the spec on day one
- Your front end reads the very same records, with sign-in built in
- A figures page with the four numbers that matter, open any day
- Documentation and automated checks, in English, so your team can carry it on
- A full dashboard: historical charts, date ranges, month on month
- An admin a non-developer can use, up to 6 screens
- Roles controlling who sees and changes what
- Import and export as Excel or CSV
- An audit trail of who changed what and when
- If the bank reports the same payment twice, nobody is charged twice
- Bursts and floods held off, so the system stays up for everyone
- Heavy work runs in the background, so nobody sits watching a screen
- The monthly summary sent to you, and an alert when a figure looks wrong
- Logging and alerting, plus a security review of what is handed over
How it works, from first message to launch
Send me what already exists
The front end you have built, the spreadsheet you run on, or the old system still in production. Any one of those is enough to start scoping.
We agree the data shape before code is written
You get the data structure and the list of what the system will do, to review first. Changing it as a document takes ten minutes. Changing it halfway through the build takes three days.
Your team uses the real thing while it is still being built
The system and its documentation open up in stages, so front-end work runs alongside rather than discovering a mismatch at the end.
Handover somebody else can pick up
Source code, API documentation, tests, deploy instructions and an admin manual, plus support after delivery.
Questions people ask about this service
We already have a front-end team. How do we connect?
You get an API with documentation you can fire test calls from in a browser, so your team works without asking me one question at a time. We agree the shape of the data in one round before anything is written, so neither side has to rework later.
How is this different from your booking or stock systems?
Those are finished products that arrive with a front end, for owners who want something they can switch on. This is the back end only, for people who already have a front end or a team building one. If you have nothing yet, I will point you at those first because they finish sooner and cost less.
We are an agency. Will you approach our client?
No, and I sign an agreement saying so. The work ships under your name and the documentation is written so you can hand it straight to your client, with my name nowhere in it if you prefer.
What is it written in?
TypeScript and Node primarily. PHP with Laravel and Python are both fine, and if your existing system is one of those I continue in it rather than making you switch to what suits me. Sample code in all three is public and readable before you commit.
How do I know the code is any good?
Judge it on three things you can check: tests that run and pass in front of you, documentation somebody else can work from, and the security review included in Harden. Security work is my main line, so I review my own work before it ships.
Often booked together
Send me what already exists
The front end you built, the spreadsheet you run on, or the old system still in production. Any one of those is enough.
A written reply within one working day. No call required.