Deliverables across the lifecycle

The complete list of named deliverables an agency engagement produces, organised by lifecycle phase. Each row points to the page where the deliverable is specified in detail. Use this as a reference when scoping a new engagement, drafting an SOW, or auditing whether an in-flight engagement is on track to produce what it owes.

The list is opinionated — it reflects the deliverables the site treats as load-bearing, not every artefact every agency has ever produced. Engagements smaller than mid-market may collapse several rows into one; engagements in regulated industries may need additional artefacts beyond what is listed here.

Pre-Sales & Business Development

Deliverable	Specified at
Qualified-lead record (BANT outcome, recommended path)	Lead Qualification & Scoping Calls
Written proposal (outcome-oriented sales document)	Proposal Writing
Signed Statement of Work (SOW)	SOW & Contract Drafting
Pricing commitment with documented methodology	Pricing & Estimation
Signed NDA, MSA, and DPA where applicable	NDA / MSA / DPA — the legal stack

Discovery

Deliverable	Specified at
Stakeholder interview synthesis	Stakeholder Interviews
Workshop summary, decisions log, parking lot	Requirements Workshops
Prototype or POC findings (if commissioned)	Prototyping & Proof of Concept
Refined cost estimate with confidence band and commitment path	Estimation & Cost Commitment
Signed discovery deliverables package: prioritised feature list and constraint catalogue, scope statement, risk register, decisions log, handoff package	Discovery Deliverables & Sign-Off

Requirements & Design

Deliverable	Specified at
Numbered, atomic, testable, traceable FR/NFR document	Functional & Non-Functional Requirements
UX design specification: wireframes, design system, component library, interaction patterns, accessibility specification	UX/UI Design
Architecture decision record (ADR) collection, component diagram, data-flow diagram, integration map	System Architecture
Infrastructure design and Day-1 readiness checklist	Infrastructure Design

Delivery

Project Management stream

Deliverable	Specified at
Mobilization document (RACI, sprint cadence, tooling stack, named stakeholders, escalation paths)	Delivery Mobilization & Kickoff
Sprint plans and outcomes (one per sprint)	Sprint Planning & Cadence
Refined and prioritised backlog (always 1–2 sprints ahead)	Backlog Management
Sprint-level estimates and slicing artefacts (vertical INVEST-conformant slices)	Estimation & Sprint Slicing
Status reports at agreed cadence (typically weekly written + monthly steering)	Status Reporting & Stakeholder Communication
Change log: every scope change, impact assessment, client decision, and link to change order	Scope Control & Change Management
Risk register at every sprint boundary	Risk & Issue Management
Retro outputs (one per sprint)	Retrospectives

Development stream

Deliverable	Specified at
Repository structure, branching strategy, commit conventions, mainline protection	Repository Structure & Branching
CI/CD pipeline with documented gates and deployment runbooks	DevOps & CI/CD
Backend implementation: APIs, data model, business logic, observability hooks	Backend Development
Frontend implementation against signed design system, accessibility bake-in	Frontend Development
Unit and integration test suite	Developer Testing
Code-review-before-merge enforced; PR records as the audit trail	Code Review
Secrets hygiene, dependency management, threat modelling, security gates passed	Secure Development Practices
Performance budgets met, regression detection in CI	Performance Engineering
Architecture reference (ADRs), API reference, runbooks, onboarding guide, known-issues log	Technical Documentation

QA / Testing stream

Deliverable	Specified at
Test strategy and test plan tied to FR/NFR set, with traceability matrix	Test Strategy & Planning
Functional and regression test cycles, automation suite, defect log	Functional & Regression Testing
Performance test results against NFR thresholds	Performance Testing
Security test results: SAST, DAST, dependency scan, third-party pen-test where applicable	Security Testing
Accessibility test results, VPAT or accessibility conformance report, accessibility statement	Accessibility Testing
UAT sign-off from named client signatory, deferred-bugs list with sign-off	User Acceptance Testing

Deployment / Launch

Deliverable	Specified at
Provisioned production environments, DNS, certificates, secrets, monitoring connectivity	Infrastructure Provisioning
Migration plan, cutover runbook, rehearsal records, signed reconciliation report	Data Migration & Cutover
Live production system, smoke-test pass record, archived launch evidence	Deployment Execution & Smoke Testing
Operational dashboards, alerts, runbook-linked notifications, baseline metrics	Monitoring & Observability Setup
Signed handoff package: credentials, documentation, training, acceptance	Client Handoff & Launch Checklist

Maintenance & Retainer

Deliverable	Specified at
Signed hypercare close-out, complete hypercare ticket log	Hypercare & Warranty Period
Bug-fix log, patch cadence record, dependency-update history	Bug Fixes & Patch Management
Feature-request intake log, mini-SOWs, change orders for substantial work	Feature Iteration
Severity-classified incident log, post-incident reviews, learning log, tabletop-exercise records	Incident Response
Signed retainer agreement: hours/capacity, SLA tiers, exclusions, renewal calendar	Retainer Structure & SLAs
Signed final acceptance, paid final invoice, lessons-learned artefact, post-implementation review report	Engagement Closeout & Post-Implementation Review

Cross-cutting

These artefacts are produced or maintained at multiple lifecycle phases, not at a single one:

Artefact	Purpose
Risk register	Lives across the engagement; updated at every sprint boundary by PM, surfaced at sign-off events, hands off to retainer at engagement close
Decisions log	Every workshop, ADR, and change order contributes; the long-term record of “why we chose this”
Cross-phase links	Every page on this site links forward and backward to its lifecycle neighbours; the artefact is the readable site itself