Delivery process

A custom software delivery process built around scope, risk, and ownership.

Move from diagnosis and definition through prototype, build, assurance, deployment, and clear operational ownership—with the important decisions recorded.

Six stages, with decisions recorded.

  1. 01

    Diagnose

    Understand the workflow, failure, constraints, and desired outcome before choosing a build.

  2. 02

    Define

    Agree the scope, acceptance criteria, data model, integrations, risks, and decision owners.

  3. 03

    Prototype

    Test the highest-risk workflow early so the important assumptions become visible.

  4. 04

    Build

    Work in visible increments with documented decisions and a clear path through change.

  5. 05

    Assure

    Exercise security, accessibility, testing, AI evaluation, and the operational controls the system needs.

  6. 06

    Deploy and hand over

    Train the people who own the system, document it, and agree how support and measurement continue.

Change control

Fixed scope requires visible choices.

Acceptance criteria, decision owners, assumptions, and excluded work are documented before build commitments are made.

A bounded build and an embedded relationship require different capacity and decision rhythms. Those boundaries are agreed before delivery starts, and major implementation work within an embedded relationship may be scoped separately.