Built for the second year of use.
Anyone can ship a first version. We design for what happens afterwards — when the data has grown, the team has changed, the requirements have moved, and the system still has to be correct on a Monday morning.
Software engineering, page by page
Ten disciplines, one team
Most systems draw on several of these at once. A platform needs a backend, an API, an interface and somewhere to run.
Web applications
Responsive interfaces built for daily use — accessible, fast on mid-range devices and real connections.
Web applicationsMobile applications
Native and cross-platform apps, including offline-first designs for field and site work.
Mobile applicationsFrontend engineering
Component systems, performance budgets and accessibility treated as requirements rather than a later pass.
Custom software development
Line-of-business systems with role-based access, approval flows, audit trails and reporting built in — designed so both an auditor and a new starter can find what they need.
Discuss a buildSaaS & product engineering
Multi-tenancy, subscription billing, self-service onboarding and the operational tooling required to support customers you have never met.
Our productsEnterprise software
Systems that carry operational weight, with the permissions and audit trails that implies.
API development
Versioned contracts, idempotent operations, sensible retries and errors that say what went wrong.
API developmentBackend engineering
Data modelling, transactional correctness and services sized for the load they will actually carry.
Legacy modernisation
Replacing a system that still runs the business is a sequencing problem, not a rewrite. We move it in slices behind a stable interface, so nothing stops working while it happens.
Discuss modernisationSystem integration
Making an existing estate behave as one system rather than several that disagree — with explicit rules about which source is authoritative for each field.
Integration & automationTrue of every build we ship
These are the baseline, not premium options — because the alternative costs more later and we are usually the ones still there.
- Reviewed code. Nothing reaches the main branch without another engineer reading it.
- Automated tests. Unit and integration coverage on the paths where being wrong is expensive.
- Infrastructure as code. Environments reproducible from a repository, not from memory.
- Migrations, not manual edits. Schema changes versioned and reversible.
- Secrets managed properly. Never in the repository, never in a config file emailed around.
- Documented decisions. The reasoning behind the architecture written down, so the next engineer inherits context rather than archaeology.
What we build with, and why
We are deliberately conservative about technology choice. New is not the same as better, and you inherit whatever we pick.
-
01Backend
.NET and ASP.NET Core for strong transactional and reporting requirements. Node.js and TypeScript where the workload is I/O-bound. Python and FastAPI for data and AI services.
-
02Frontend
React for most interfaces, Angular where a team already runs it, Blazor when the organisation is committed to .NET end to end.
-
03Data
SQL Server and PostgreSQL for systems of record, MySQL where the estate already uses it, vector databases where retrieval is part of the product.
-
04Mobile
Cross-platform where a shared codebase genuinely fits, native where device capability or performance demands it.
-
05Cloud & delivery
Azure and AWS, containerised with Docker, released through automated pipelines with environments defined in code.
-
06Quality
Automated testing in the pipeline, static analysis, dependency scanning and load testing against the volumes you actually expect.
Custom development, answered
A focused internal tool is typically six to twelve weeks. A platform replacing a core business system is usually four to nine months, delivered in releases rather than one launch. Discovery gives you a defensible range before you commit to the full build.
Yes. Intellectual property transfers to you on completion of payment. Code lives in your repositories from day one, along with infrastructure definitions, tests and documentation.
Often. We begin with a code and architecture review that tells you honestly what is salvageable, what should be rewritten and what each option costs before anyone commits to continuing.
By what fits the problem and what your team can maintain, not by what is new. We default to established tools with long support horizons — you inherit whatever we pick, and a framework with a large community is worth more in year three than a novel one was in week two.
Tell us what it has to do
Bring the process, the constraints and the systems it has to live alongside. We will come back with an approach and a range you can plan against.