Custom software

The system you need does not come in a box.

When a process is the thing that makes your business different, off-the-shelf software makes you average at it. We build the applications, APIs and integrations that encode how you actually work.

When this makes sense

Signs you have outgrown the tools you have

  • A spreadsheet has become load-bearing, and only one person understands it.
  • Two systems hold the same data and disagree about it.
  • Your differentiator is a process no product on the market supports.
  • Staff spend hours re-keying between applications that should talk to each other.
  • An internal tool works but no one can safely change it any more.

Typical engagements

Internal business application
Operations, planning or back-office tooling that fits the process instead of bending it. Usually 2–4 months to first production release.
Customer-facing product
A portal, a booking flow, a SaaS product. Built to be handed to your own team or to keep growing with ours.
Integration layer
Making the ERP, the CRM, the warehouse and the shop agree. Often the highest-return work we do.
Rescue and modernisation
An inherited codebase no one wants to touch. We stabilise it first, then change it.

What is included

Everything that makes software last

Discovery and design

We map the process before we model the database. Wireframes and a data model you can argue with, early, while changing them is still cheap.

Build

Boring, well-supported technology. Tests around the logic that matters, code review on everything, and a deployment that runs from a single command.

Integration

APIs, webhooks, file drops and the occasional stubborn legacy protocol — with retries and reconciliation, because networks fail.

Security and compliance

Authentication, role-based access, audit trails and GDPR-aware data handling designed in rather than retrofitted.

Operations

Monitoring, alerting, backups and restore drills. You find out about problems from a dashboard, not from a customer.

Handover

Documentation written for the next engineer, and time budgeted to walk your team through it properly.

Technology

Deliberately unexciting choices

We pick tools with long support horizons and a deep hiring pool, so that in three years you can still find someone to work on this. Novelty is a cost paid by whoever maintains the system next.

Python FastAPI Java Spring Framework PostgreSQL Redis
TypeScript React Vite
Docker Terraform GitHub Actions AWS Azure

Questions

Before you ask

Both, for different things. A well-understood phase can be fixed price. Open-ended work is time and materials with a capped monthly budget — a fixed price on a vague scope just moves the risk into padding and change requests.

You do, from the first commit, in your own repository. No licence-back arrangement and no proprietary framework you would have to keep paying us for.

Often the best arrangement. We take a workstream your team does not have capacity or specific experience for, work in your repositories and your process, and review each other's changes.

Most clients move onto a support retainer covering dependency updates, monitoring, incident response and a budget of development days each month. If you would rather take it fully in-house, we plan the handover instead.

Have something specific in mind?

Send us the shape of the problem — a spec, a spreadsheet you have outgrown, or just a description. We will tell you what we would build and roughly what it takes.