The studio
Every job starts as a written note and ends as a module you own. Nothing in between is a surprise.
Founded
2025
State
Taking new work
We fix it for 30 days after handover. Your data stays in your own accounts, and we do not use it to train any AI. Before we start, we agree in writing what the job is, who owns the result and how we will know it worked.
Something is being done by hand, it takes a morning a week, and the person doing it is the only one who knows how. We write that job down before we quote it. Sometimes the finding is that nothing needs building, and that is a result rather than a lost sale.
After that it could be a site, a small piece of software with a login and a table in it, a script on a timer, or a model reading documents.
AI tools, directed and checked by a person, are used to speed the work. Nothing reaches a client unread. Every line is reviewed by somebody who is answerable for it, which is the same rule we build into the products.
Based in Walton-on-Thames, Surrey, working remotely across the UK.
From call to handover
5 steps, and you are looking at working software by the third. A module stands on its own, so the one after it is a decision you make later rather than a commitment made at the start.
01
Call
Send a paragraph and we arrange 30 minutes. What the job is now, who does it, and how long it takes them.
02
Scope
A written note: the modules, what each one does, what it does not do.
03
Build
1 module at a time, in the open. A working link while it is being built, not a demo at the end.
04
Handover
Handed over with the code, the hosting and the accounts in your name.
05
After
We fix anything that goes wrong in the first 30 days. Work that needs the studio to survive is work built wrong.
Next
Send the thing that is not working. One paragraph is enough to get a straight answer on whether it is worth building and what it would cost.
Start the intake