Service
When the website is not the whole problem
Some jobs are not a page. They are a calculator, an integration, a portal, or the manual process somebody repeats forty times a week.
The point where plugins stop
Most business software needs start the same way: there is a plugin that almost does it. It does eighty per cent, the remaining twenty is the part that actually matters, and the workaround becomes somebody's Tuesday afternoon forever.
That is the point where building something is cheaper than continuing to work around it — not because custom software is inherently better, but because the twenty per cent is where the business logic lives, and generic tools cannot hold business logic they have never heard of.
If you have been searching for this, you probably typed custom software — that is exactly what this is. And it has a smaller sibling: when every tool you need already exists and they simply do not talk to each other, that is not a build at all — that is business automation, its own service here, and the honest recommendation whenever it fits. This page is for the thing no plugin ships: the calculator, the portal, the tool that holds your twenty per cent.
How a build is scoped so it does not run away
The failure mode of custom software is not bad code. It is a scope nobody bounded, discovered halfway through, at which point the only options are all expensive.
- 01
Name the manual process
Not the feature — the thing a person currently does by hand, how often, and what it costs when they get it wrong. If that cannot be stated in a sentence, the build is not ready.
- 02
Find the smallest useful version
The version that removes the worst part of the process and nothing else. It ships sooner, it teaches you what the real requirements were, and it is far cheaper to be wrong about.
- 03
Build against the systems you already run
Most of this work is integration rather than invention — the CRM, the scheduler, the payment processor and the spreadsheet that quietly runs the company all already exist.
- 04
Hand it over with the lights on
Software that nobody maintains rots faster than a website, because dependencies move underneath it. It goes onto the same monthly arrangement as everything else.
What this is for — and what to buy elsewhere
The fastest way to a wasted month is a software engagement that should have been something else. So the boundary is stated here, before any call: what this service is built to take on, and the asks that are honestly somebody else's job.
A good fit
- A manual process you can name, done weekly, worth killing
- A plugin ceiling you have actually hit
- An integration between systems you already run
- A calculator, portal or intake tool no product ships
- Software that lives with your website and is maintained with it
Not the right fit
- Native mobile apps for the app stores
- Building a SaaS product for you to resell
- A formal security audit or compliance certification
- Renting engineering hours against your own spec
- A team to absorb into your project
What separates this from hiring an engineer off a marketplace
A freelance engineer sells hours against a specification and is gone once it ships. Nobody is watching eight months later when a dependency updates and quietly breaks the integration, because nobody is still there to notice.
This is written in TypeScript rather than loose, untyped code — the compiler catches a whole class of mistakes before they reach production, not after a customer finds them. Typed end to end, server-rendered, and carrying no third-party scripts: the same standards the instrument further down this page is measuring while you read. And it goes onto the same monthly arrangement as everything else this studio builds, which means the software is maintained on the same terms as the site it lives inside, not shipped once and abandoned the day the invoice clears.
Engineering is not a separate department here
In most agencies the developers are elsewhere, briefed through a document, and the design gets negotiated into whatever the build can take. The same person doing both means the negotiation happens while the thing is being drawn rather than after it is signed off — and it is also why the honest answer is sometimes that you do not need software at all, that the process can be removed or an existing tool configured properly. That answer is much easier to give when nobody is selling engineering hours by the sprint.
You do not have to take any of that on faith. This page, and every page on this site, is the artifact — hand-built rather than assembled from a page builder, and measured below rather than asserted.
Custom software is quoted as a scoped project. Ongoing care is optional, and the exact handover and ongoing-service terms are agreed before work starts.
Measured on this page, in your browser
The build itself, measured while you're on it
- —
- —
- —
- —
These are read from your browser as you look at this, not typed in by us. Open devtools and check them — that is rather the point.