Skip to content

Services / 02 | Build

DevelopmentThe parts users never see

The backend, the data and the APIs your product leans on: payments, push, AI and accounts. Built, tested and written down, so your team can carry it on.

What you leave withA backend your team can run

The code, the tests and the decisions behind them, handed over in full.

Four steps, one teamFrom the repo to handover

  1. ReadRead what is already there

    The repo, the data and the services it calls, read before we write a line.

  2. PlanAgree the change in writing

    What we build, what we leave and why, written down and signed off with you.

  3. BuildShip one reviewed change at a time

    Small changes on their own branches, each one tested and reviewed before it merges.

  4. Hand overLeave it ready for your team

    The code, the tests and the runbooks move to you, with a walkthrough.

QuestionsAbout development

Do you work in our codebase?

Yes. We work in your repo, follow its conventions and open every change as a pull request your team can review.

Which stack do you use?

The one your product already runs on when there is one. For new builds we pick plain, well-supported tools and write down why.

Can you fix one integration only?

Yes. A single failing integration is a good first piece of work: we find the cause, fix it and add a test so it stays fixed.

Do you build AI features?

Yes, and we test them like the rest: every AI feature ships with evals that check its answers before each release.

Who owns the code?

You do. When we work in your repo, every change is yours as it merges. On a new build the code lives in our private repo and moves to yours at handoff.

How long does it take?

On its own, it depends on the product, and we set the timeline when we scope the work. Inside Zero to launch it runs in the Build stage, under the app and the site.