How we work

A written process, first call to live software.

Every stage ends in something you can read, check or run.

01
First conversation
Thirty minutes with the practice lead to understand the problem, the system it lives in and who depends on it.
You get: A clear answer on whether we are a fit.
02
Scoping
The lead who will build the work writes down what will be built, how, and what could go wrong.
You get: A written scope with approach, risks and price.
03
Build in the open
Weekly demos, written decisions and a shared board, so you always know what changed and why.
You get: Working software every week, with a decision log.
04
Ship and prove
Tests run on the real database engine, the rollout is staged, and the handover is written down.
You get: A staged release and a documented handover.
05
Run and improve
Optional retained support once the system is live, with agreed response times.
You get: A support agreement, if you want one.

How we engage

Scoped project
Scoping ends in a written document with the approach, risks, timeline and price, and nothing is billed before you agree to it.
Audit and root-cause work
For an existing codebase, we start by understanding what is there before changing it.
Retained support
Optional once the system is live, with response times agreed up front.

Standards

The rules our leads already work by, written down so you can hold us to them.

Critical rules are structural
Tenancy, consent and money logic are enforced in one place, not re-checked in every feature.
Root cause, not symptom
A bug is fixed in the shared path every caller goes through.
Humans stay in the loop
Where safety is involved, a person reviews what the system produces.