Applications
Custom software development
The point where a website stops being enough: people have to sign in, do something that changes data, and come back tomorrow expecting it to still be there. Portals, dashboards, internal tools, and the integrations tying them to what you already run.
after discovery
See this beside everything else →What you get
One engineer, start to finish
Database schema to the last pixel, by the person who took the first call. Nothing gets passed between three companies, so nothing falls into the gap between them.
Working software, not status reports
Deployed to a preview environment from the first week. You click through what exists rather than reading about what is planned.
Fixed price wherever the scope allows
Most defined projects get a number before work starts. Where scope genuinely cannot be pinned down, you get a rate and an agreed ceiling rather than an open meter.
Handover is a supported ending
Documentation and a clean handover to your own team is a normal outcome, not a failure. So is a retainer. Both get quoted honestly.
What this does not cover
- Work that needs more than one pair of hands - this is one senior engineer, so the scope has to fit what one person can deliver properly
- Anything requiring 24/7 on-call. This runs alongside a full-time job, and the timelines you get are honest rather than optimistic
- Desktop and robotic process automation of legacy software
- Work a large agency would genuinely serve better, which gets said on the first call rather than after three meetings
Questions
- What stack do you work in?
- TypeScript and JavaScript across React, Next.js and Angular; Node and Express or Java and Spring Boot behind them; SQL and MongoDB for data. The full list, including cloud and CI, is on the platform page.
- Who owns the code?
- You do, outright - the source, the repository and anything built for you. No licence, no per-seat fee, and nothing that needs our permission to change later. If you want it in your own GitHub organisation from the first commit, that is the normal arrangement rather than a special request.
- You are one person. What if you are not available?
- The right question to ask before hiring one engineer instead of a firm. Three things make it survivable: the repository is yours from the start, documentation is part of the delivery rather than an extra, and the stack is deliberately ordinary - TypeScript, React, Node, plain SQL - so another developer can pick it up without needing anything explained. A clean handover is a supported ending here, not a failure.
- How do we start without committing to a build?
- A paid, fixed-price assessment. You keep the findings and the prioritised list whatever you decide next, and the fee credits toward the build if you go ahead.
Describe the problem, not the solution.
Tell us what people need to do and what is currently in the way. You get an honest read on whether that is a build, a fix, or something you do not need at all.