Custom Software
The system nobody sells off the shelf, built to fit how you already work and to connect to what you already run. For internal tools, integrations between systems that were never meant to talk, and data platforms.
Who this is for
- A process run on spreadsheets and email that has outgrown both.
- Two systems that need to share data and were never designed to.
- An unusual requirement that off-the-shelf software gets 80% right and 20% wrong.
- A team that knows exactly what it needs and cannot buy it.
What is included. Tick what you need.
Artefacts, not adjectives. Each is something you can point to at the end. Tick the ones your project needs and send the list with your enquiry; we reply with a written scope.
Technologies we use for this
The relevant slice of our technology matrix. Nothing here that we cannot staff today.
- React
- Next.js
- TypeScript
- Vue
- Nuxt
- Tailwind CSS
- Redux Toolkit
- TanStack Query
- Vite
- Three.js and React Three Fiber
How we deliver it
The five steps every engagement goes through, in the form they take for this service.
Scope
A call with an engineer, then a written scope: what is in, what is out, and what it costs.
Architecture
Data model, API contract, and infrastructure plan, approved before code is written.
Build
Built with the people who will use it, on a staging URL they try every week, so the tool fits the work before it goes live.
Harden
Tests on the paths that matter, error tracking, a performance pass, and a security review.
Launch and hand over
Production deployment, monitoring, documentation, and every repository transferred to you.
From the blog
- LLM application architecture: the layers that don't change with the modelModel, harness, data layer, and product surface: the four layers of a production LLM application, and which ones survive the next model upgrade.
- RAG vs fine-tuning: what should your business use?They get pitched as competitors and usually are not. How to tell which problem you actually have, and the cases where the right answer is both.
- LangGraph vs CrewAI vs AutoGen: a practical comparisonThree popular agent frameworks, compared on what actually differs in production: control over the loop, debugging, and how much they decide for you.
Questions we get asked
We have an unusual requirement. Can you build it?
Almost certainly. The scope call is where we find out, and if something off the shelf would serve you better we say so.
Can you integrate with our existing systems?
Yes, through APIs where they exist and files, databases, or automation where they do not. We tell you which before quoting.
What if we do not know exactly what we need yet?
Start with a short discovery: a week with the people doing the work, ending in a written scope and a prototype. Then you decide.
How do you keep a custom system maintainable?
Standard languages and frameworks, tests, documentation, and your engineers involved from the start if you have them. Nothing exotic.
Do you build desktop software?
Yes, when a browser cannot do the job, for example hardware access or offline field work. Most internal tools are better as web applications, and we say which.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.