Custom web applications
A prototype is the easy part. I take web applications through real data, access rights, deployment and the release after that — or take over one that is already live and needs someone to own it.
01
What you get
- The working application, not a hand-off of screens
- Accounts, roles and permissions
- Integrations with the systems around it
- Production deployment, monitoring and release checks
- Documentation and a clear ownership path
02
Typical projects
- A customer portal or a client zone
- An internal system replacing spreadsheets
- A dispatch, booking or order-tracking tool
- Taking over an existing app whose original developer has left
03
How it goes
- 01
First conversation
You describe the problem in a sentence or two. I reply with questions — or with a straight answer that it is not work I should take.
- 02
Scope in writing
What gets built, what counts as done and roughly when, agreed before any code is written.
- 03
Build in reviewable steps
You see working software early and often, not a stack of screenshots at the end.
- 04
Launch and handover
Deployed, documented and handed over — with ongoing maintenance if you want it.
04
Questions
- Can you take over an existing application?
- Yes. It starts with a written audit and a prioritised plan, then a first stable release under new ownership.
- Which technologies do you use?
- Mostly TypeScript and React on the front end, with the back end and hosting chosen to fit the project rather than the other way round.
Tell me what you need built.
Start with one sentence