Software your own team can run and change after handover.

How this works

We work on the software around a product: a web app and its backend, the API between a device and the cloud, a mobile or desktop app, or the internal tools a team uses to test and ship.

Before any code, we agree in writing what goes in and what comes out, what it depends on, who owns the code, how much testing is included and how long support runs. It is the least expensive time in the project to catch a misunderstanding.

At handover you get the repository, the tests, build and deployment notes, and a short record of the decisions we made and why. After that, we can stay on for updates and support if that's useful.

Project checkpoints
CheckpointWhat your team can expect
Scope and stageThe next defined stage is written before larger work begins, so you can decide what to fund next.
HandoverSource files, tests and decision notes are part of the handover, so your team can continue from a known version.
Procurement and buildWhen hardware is involved, you can buy the parts directly or have us source them at itemised cost; alternates and first checks are recorded before any order.

Discuss a software project

Pages in this section

Frequently asked questions

Can you work alongside our in-house developers?

We usually work in your repository and follow your code review, so your developers see every change as it lands. We can take a module, a service or a whole app.

Who owns the code when the project ends?

We agree that in writing before work starts, along with how the source, tests and decision notes are handed over. Custom work and our reusable components can be licensed differently, so the agreement spells out which is which.

How do you estimate the cost of a software project?

We price the step we can see. When the unknowns are still large, Paid Discovery turns them into a written scope and estimate before a larger build begins.

What do you need from us to get started?

A description of what you're building, what already exists and what's worrying you. Access to code and documents can wait until an NDA is in place.

We're in a different time zone. How does that work day to day?

Much of the work happens in writing: scope, decisions and test results go into documents you can read when your day starts. Calls get booked at a time that suits both sides.