The ADA build process

Clear before code.
Proof before handover.

A predictable process reduces buying fear and protects both the client and ADA. Scope, responsibilities, major external costs and the expected delivery window are defined before development begins.

01 · Diagnose

Understand the real problem.

We clarify the organisation, audience, current digital position, constraints and desired outcome.

02 · Recommend

Choose the smallest useful solution.

ADA maps the problem to Presence, Visibility, Growth, Systems, Care or a staged combination.

03 · Scope

Make the commercial agreement clear.

Deliverables, responsibilities, cost, external services and expected timing are documented before the build.

04 · Design

Plan the experience and content.

Structure, visual direction, customer journeys and required assets are established before complexity grows.

05 · Build

Develop and integrate.

ADA implements the approved solution and tests it throughout the build instead of waiting until launch day.

06 · Standard

Pass the ADA Web Standard.

Experience, performance, visibility, security, accessibility, contactability, ownership and continuity are reviewed.

07 · Launch

Release with a record.

Launch is accompanied by the relevant access, asset, renewal and handover information.

08 · Care

Keep improving when needed.

Care plans provide a path for monitoring, updates, search improvement and future capability.

ADA Clear Build Promise

No silent scope expansion.

If the requirements change after approval, ADA explains the impact before extra work is added. The goal is not to trap a client inside technical language; it is to keep expectations visible.

ScopeWhat is being built.
CostWhat the approved work costs.
OwnershipWho controls the important assets.
ContinuityWhat happens after launch.