6–16 weeks typical

Build

A Build is the delivery of your frontend against an agreed, versioned spec. It is fixed-fee, runs milestone by milestone, and every milestone ships with a trace report that shows each acceptance criterion, its test and its result.

What a Build is

A Build is the engagement in which we write the code. Senior engineers and supervised coding agents build your frontend from the tasks in the spec, and every change is checked against its acceptance criteria before it merges. The spec sets the scope, so the fee and the dates are fixed against it.

A Build usually follows a Spec Sprint. If you already have a spec of the right quality, from us or another team, we review it first and can start from there.

What we build

We own the frontend end to end. Your backend, APIs and business decisions stay with you. We build the interface on top of them, to the spec.

  • Frontend architecture. Module boundaries, state, routing, the rendering approach for each page, and integration boundaries, with each decision recorded.
  • Design system and tokens. Components and themes built from design tokens, including several brands on one codebase where you need it.
  • Security and privacy UI. Consent and identity flows, data minimisation, sessions and security headers.
  • Performance and accessibility. A Core Web Vitals budget (LCP, INP, CLS) and WCAG 2.2 AA, both measured and enforced in CI.
  • Tests from the criteria. Every acceptance criterion becomes an automated test, so the spec and the test suite can’t drift apart.

How a Build runs

A Build runs as a series of milestones. Each milestone maps to sections of the spec, has a target date and a fee, and ends when you accept it against its criteria.

  1. Kickoff. We confirm access (repository, staging, design files, vendor sandboxes), your decision-maker and the milestone dates.
  2. Milestone work. Tasks are built in parallel by engineers and agents. Every change passes the quality gates and a senior review before merge.
  3. Weekly written update. Every week you receive: done, next, blocked, any proposed spec changes, and any risk to a date.
  4. Milestone delivery. You receive the working software in your repository, a walkthrough, and a trace report showing each criterion, its test and its result.
  5. Acceptance. You have a fixed review window, set in the Statement of Work, to accept or to point to a criterion that fails. We fix what fails and redeliver.

What you receive

At each milestone At final release
Source code in your repository Final trace report: every criterion, its test and its result
Automated tests derived from the criteria Performance and accessibility results
A trace report for the milestone’s criteria An inventory of every third-party request and storage key
Release notes Handover notes your team can run the product from

How changes are handled

Changes are normal, and we handle every one of them in writing. A change is written as a spec delta (ADDED, MODIFIED or REMOVED), priced with its effect on dates, and started only after your written approval. You always know what changed, why, and what it cost.

This keeps the fixed fee honest. The fee covers the spec as agreed, and anything new is visible as a delta rather than buried in a vague estimate.

How agents are used

We use supervised coding agents to deliver faster, under fixed rules. Agents build only from tasks that link to acceptance criteria. A senior engineer reviews every change before it merges. Your code and data are never used to train any model, and only tools you approve in writing can access your code. More detail is in agent-assisted delivery.

What we need from you

Projects slip when inputs arrive late, so we ask for four things up front:

  • One decision-maker who answers questions and approves changes within an agreed number of business days.
  • Access to the repository, staging, design files and vendor sandboxes by kickoff.
  • Your compliance or legal team’s confirmation of the rules for each market.
  • APIs and backend dependencies delivered to the dates in the plan.

When an input is late, the affected dates move by the same number of days, and we say so in the weekly update.

How success is defined

A Build succeeds when four things are true, and we measure and report each of them:

  1. Milestones are delivered on time, or rescheduled in writing before the date.
  2. 100% of acceptance criteria are traced to a passing test in the final trace report.
  3. The Core Web Vitals budget is met on the devices the constitution names.
  4. WCAG 2.2 AA is met, and the frontend makes no third-party request the spec doesn’t list.

We don’t promise outcomes we can’t measure, such as revenue or conversion.

Ownership, warranty and pricing

The code, specs and designs we produce are yours on payment. For 30 days after final acceptance we fix, free, any defect against an accepted criterion. The fee is fixed against the spec and quoted after the Spec Sprint. We don’t publish prices.

Start with a Spec Sprint

One to two weeks to a versioned spec you own, whoever builds it.

Start a Spec Sprint