Custom Software & Platforms
Software built for one business rather than licensed to thousands: SaaS platforms, ERP and operations systems, internal tools, client portals, and the APIs that connect them to what you already run.
What we build
Bespoke SaaS platforms
Multi-tenant products with accounts, roles, subscription billing, and an admin side for your own team to run it.
ERP and operations systems
Inventory, orders, procurement, finance, and fulfilment in one system, with the reporting that sits on top of them.
Internal tools
Admin panels, dashboards, approval flows, and workflow engines for the screens your staff use all day.
Client portals
Authenticated areas where customers submit, track, pay, and download, instead of emailing your team for it.
APIs and integrations
REST and GraphQL APIs, webhooks, and connections to accounting, CRM, payment, shipping, and legacy systems.
Data migration
Moving records out of the spreadsheets and old systems being replaced, with reconciliation before anything is switched off.
How the engagement runs
1. Discovery
Sitting with the people who do the work, mapping the current process step by step, and writing down the requirements, the integrations, and the scope.
2. Architecture
Data model, system design, stack choices, and hosting, all agreed before code is written.
3. Build
Two-week iterations on a staging environment, with the priority order open to change between each one.
4. Migration and testing
Existing data moved across, run in parallel with the old system where that's practical, and tested against real cases.
5. Rollout and support
Training for the people using it, documentation, deployment, and a support window after go-live.
How it's built to change
Documented architecture
Written setup, data model, and deployment notes, so another developer can pick it up without a call.
Standard stack
Widely used languages and frameworks with a hiring pool, not something only we know.
Tests around the risky parts
Coverage on billing, permissions, and anything that touches money or personal data.
Your accounts
Repositories, hosting, and third-party services in your organisation's name from day one.
Who this is for
Operations-heavy businesses running on spreadsheets and manual re-keying. Founders building a SaaS product. Teams whose packaged software no longer covers how they work, and who are paying for the gap in staff hours.
Frequently asked
How long does a typical build take?
A focused internal tool can ship in a few weeks. A full ERP or a multi-tenant SaaS platform runs months. Discovery tells you which one you're actually asking for, and that's when you get a date.
What do you build with?
TypeScript across the stack for most projects — React or Next.js on the front end, Node on the back, Postgres for data. Python where the work is data or machine learning heavy. If your team already maintains a stack, we'll use it.
Custom software sounds expensive. Is it?
It costs more up front than a licence and less over time if it removes manual work. Price both sides properly: the subscription and per-seat fees on one, the build and its maintenance on the other, plus the hours currently spent moving data between systems. Sometimes off-the-shelf wins that comparison, and we'll say so.
Can you integrate with the systems we already use?
Usually. Anything with an API — accounting, CRM, ERP, payment processors, shipping carriers. Older systems without one can often be reached through their database or scheduled file exchange.
What happens when our process changes six months in?
It's built on the assumption that it will. We document as we go and keep the parts most likely to change configurable, so a revision is a change rather than a rewrite.
Can you take over a build someone else started?
Often, yes. We read the code and the infrastructure first and tell you what's salvageable. Sometimes the answer is to keep the data and rewrite the rest, and it's cheaper to hear that in week one.
What if we want to bring it in-house later?
Everything is documented and the stack is a common one, so a new engineer can pick it up. Repositories and accounts are already yours, so there's nothing to transfer.
Who owns the code?
You do, once it's paid for. The one exception: pre-existing open-source or third-party components stay under their own licences. Everything written for you is yours.