How Delivery Works

Six stages, with your approval between each one.

Nothing is configured before the design is approved, and nothing goes live before it is tested against scenarios you agreed.

01

Discovery

A structured conversation about one recurring process: what triggers it, who touches it, what it produces and where time is lost.

What we need
  • Someone who runs the process end to end
  • A general view of volumes and systems involved
What you receive
  • Written summary of the process discussed
  • A view on whether AI assistance is appropriate
02

Assessment & mapping

We map the current state, identify decision points and exceptions, and record the controls the workflow would need.

What we need
  • Access to the people who perform the process
  • Non-sensitive sample documents or records
What you receive
  • Current-state workflow map
  • Exception and risk register
  • Suitability assessment
03

Design

We propose a future-state workflow with instruction design, output structure, confidence handling and the points where a person must approve.

What we need
  • Decisions on which outputs require human approval
  • Written approval of the design before build
What you receive
  • Proposed future-state workflow
  • Human-review checkpoint design
  • Assumptions and dependencies
04

Configuration

The approved design is configured in the agreed environment, including exception routing and review queues.

What we need
  • Access to any systems named in the scope
  • A named point of contact for questions
What you receive
  • Configured workflow
  • Configuration summary
05

Testing & acceptance

The workflow is tested against scenarios agreed with you, including the exception cases, before anyone relies on it.

What we need
  • A named reviewer for acceptance testing
  • Timely feedback within the acceptance period
What you receive
  • Test results against the agreed scenarios
  • Defect list and resolution record
06

Handover & support

Your team is walked through operation, reviewer responsibilities and escalation. Continuing support is optional and quoted separately.

What we need
  • Attendance at the handover session
  • Notification of later process or system changes
What you receive
  • Operating guide
  • Handover session
  • Support arrangement if purchased

Timelines

Delivery timelines depend on the process, the systems involved and how quickly reviews and approvals come back. We do not publish a fixed duration for implementation work; the schedule is agreed in the written scope before the engagement begins.