How we build · Stage 04

Build

Iterative engineering with quality automated from day one.

Typical duration: 6 weeks to many months, depending on scope
Portal phase: build
Stage: 04 of 08
CRM stages: 1

What this stage is for

We build in short increments against a working pipeline. Every increment is demonstrable, tested and deployable — there is no separate "integration phase" at the end.

Your part

Attend demonstrations, accept or reject increments, and keep decisions moving.

Activities

What happens

Two-week increments with a working demonstration at the end of each
Trunk-based development with peer review on every change
Automated unit, integration, contract and end-to-end tests in CI
Infrastructure as code and preview environments per change
Continuous security and dependency scanning
Observability instrumented as features are built, not retrofitted

Outputs

What you get

Working software in a real environment after every increment
Test suites and coverage of the behaviour that matters
Infrastructure definitions and environment parity
Living technical documentation and runbooks

Exit criteria

We do not move on until

Written down so neither side has to rely on a feeling that things seem fine.

The agreed release scope is built and demonstrated
Automated quality gates pass on the release candidate
Operational documentation exists for everything being launched

Behind the scenes

How this shows up in our systems

This is not a diagram made for a website. The stage you are reading maps onto literal values in our CRM and the phase label in your client portal.

CRM pipeline stages: DeliveryDesign and build are running.
What you see in the portal: Your project shows the phase "build", with this stage's purpose and your part written on the project page.

Where it applies