Custom software development
Custom web and backend systems, built to be handed over — with tests, documentation and a deployment path.
The challenge
Software that was built once by someone who has since left, with no tests and no documentation, so every change is a risk nobody wants to take.
The system still works. Nobody dares touch it.
How we approach it
Read before proposing
We understand the existing system before recommending anything.
Test around the change
Establish a safety net before modifying what works.
Ship in increments
Reviewable changes, deployed continuously.
Document as a deliverable
Not as a final task nobody funds.
The same four phases, whatever we are building.
- 012–3 weeks
Discovery
We map your current process, users and constraints, then define scope in writing.
- 022–4 weeks
Design
Interface and data design, reviewed with the people who will use the system daily.
- 036 weeks+
Build
Delivery in two-week increments, each one testable, with progress visible throughout.
- 04Ongoing
Launch & support
Deployment, training and documentation, then optional support at a level you choose.
What you get
- Written, with the alternatives we rejected and why.
- In your repository, from the first commit.
- Automated coverage on the logic that matters.
- Build, test and deploy without manual steps.
- How to operate, monitor and recover the system.
- A phase with your team, not an email at the end.
What changes
Safe to change
Tests make the next team's work possible.
No key person
Documentation removes the single point of failure.
You own it
Code, accounts and infrastructure are yours throughout.
Often looked at together.
AI solutions
Custom models where they earn their cost, established providers where they do not.
Web development
Accessible, fast web applications with a performance budget agreed up front.
Enterprise & custom business software
Custom operational systems for companies that have outgrown spreadsheets and disconnected tools.
About this work specifically.
General questions about scope, ownership and timelines are answered on the resources page.
Often, yes. We start with a short assessment of the code and the servers it runs on. You then get a straight answer on whether the system should be kept, repaired or replaced — including when the answer is that it is fine as it is.
Yes, from day one. It lives in your repository, under your account. This is not a deliverable at the end of the project; it is where the work happens.
Tell us what you need built.
We reply within two working days with honest scope and next steps — including when we are not the right fit.