Software built to be handed over.

We build the tool that fills the gap between two products you already own, or the data product you want in front of your own customers.

not in scope · connecting systems you already run · Automation & Integration

The next step

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses


Handover boundary — what stays in your repository A repository, a CI pipeline, an environment and a runbook sit inside a boundary licensed and owned by the client. Build leads to deploy, and deploy leads to hand over, when the inheriting team receives all four artefacts. Connecting systems you already run is out of scope — that work is Automation and Integration. Build, deploy, hand over Your licence, your repository Repository CI pipeline Environment Runbook Inheritingteam build deploy hand over Everything inside stays in your repository. Out of scope Connecting systems you already run — that is Automation & Integration. Build, deploy, hand over Your licence, your repository Repository CI pipeline Environment Runbook Inheritingteam build deploy hand over Everything inside stays in your repository. Out of scope Connecting systems you already run — that is Automation & Integration.
Repository, pipeline, environment and runbook — inside your licence, your repository, handed to the team that inherits them. Connecting systems you already run is out of scope: that is Automation & Integration.

Platforms over your own data

What we build on

We build on Python and .NET as the core, with C#, Java and T-SQL where the estate calls for them, FastAPI services, and React/Next.js or Streamlit front ends over those APIs. Docker and CI/CD are the delivery mechanism rather than an add-on, on the assumption that we will not be the ones maintaining what we build in three years — which is also why we build it the way the method below describes, rather than the way that is fastest to walk away from.

company delivery history · founder-asserted ·

What this silo does not cover, stated in full rather than left to the rail: connecting two systems you already run is Automation & Integration. Custom Software & Data Products is for the system that does not exist yet.

What we build

The handover standard

handover standard · six commitments, all six required

When you should not build

Sometimes the right answer is not to build. If a product already does what you need, we will point you at it instead of billing for a worse version of it. If the real problem is a process, not a missing system, fixing the process is often cheaper and faster than software — and we will say so.

What you can inspect before hiring us

This website is built and deployed exactly the way we build for clients: source control from the first commit, code review, and an automated deployment pipeline. The Static Web Apps case study walks through the architecture, the CI gates and the real monthly run cost — the one part of our work you can inspect before hiring us.

The shapes this usually takes: a lender that needs branch staff to see one customer view instead of three; a grocery group whose ordering tool lives in a spreadsheet; a 3PL whose client portal is six emails a day. These are illustrations of shape, not clients — we have no client work we are permitted to describe, and /case-studies/ publishes none.

illustrations · shape only — no client named

How we build

  1. Review on every change. Nothing ships without a second pair of eyes on the diff.

  2. Automated deployment. A pipeline builds and deploys the same way every time — the same pipeline this site itself ships through.

  3. Tests where a defect costs money. Coverage is targeted at the parts of the system where being wrong is expensive, not a percentage target for its own sake.

Who this is for

Built for

  • The tool that fills the gap between two products you already own — a gap nothing off-the-shelf handles.
  • An internal application running a process specific enough that a generic product does not fit.
  • A data product you want to put in front of your own customers.
  • A team that wants to own the result afterward — the code, the pipeline, and the decisions behind them.

Not a fit

  • What you need already exists as a product — we would rather tell you that than build a worse version of it.
  • You want a body shop adding headcount to your team indefinitely, with no handover in view.
  • The real gap is a connection between two systems you already run, not a new one — see Automation & Integration.
  • You need a large, multi-year platform build — a different shape of engagement than this team is set up for.

Source control, review and access practices for this work follow the same standard as the rest of our work.

Continue

Start with a call about the tool nothing off the shelf provides.

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses