Stage 7: Client Delivery and Handoff

Stage 7: Client Delivery and Handoff

Owner: Dana (Delivery Manager) Blueprint stage: Stage 7 -- Client Delivery and Handoff

Trigger

Deployment verified by Diego (Stage 6 gate passed).

Inputs

Source What
Diego (Stage 6) Deployment manifest and verification log
Pablo (Stage 4/G) Client documentation (user guide, config guide, skill reference)
Camille (Stage 1) Client contact information and stakeholder map
Work order Demo scenarios, product-specific feedback questions

Activities

7.1 Schedule Handover Session

Schedule 1-2 hour session. Identify attendees (users, technical leads, admin). Prepare agenda and demo scenarios relevant to the product type. Consult the work order for recommended demo scenarios. If the work order doesn't specify, demo three skills representing: intake/input processing, core analysis/generation capability, and output/publication.

7.2 Conduct Handover Session

  1. What the talent does -- overview of capabilities (10 min)
  2. How to start a new request -- create request folder, provide inputs (15 min)
  3. Live demo: run 3 skills -- demonstrate core capabilities (30 min)
  4. End-to-end workflow -- orchestrator demo if applicable (15 min)
  5. Configuration and customization -- updating templates, adding references (10 min)
  6. Q&A -- address client questions (20 min)

7.3 Customer Acceptance Testing (UAT)

After the handover demo, the customer formally tests the product against the acceptance criteria defined in the work order. This is the customer's opportunity to verify the product meets their needs before signing off.

Process:

  1. Dana provides the customer with a copy of the work order's acceptance criteria
  2. Customer walks through each criterion, testing independently (with support available)
  3. Customer marks each criterion: PASS / FAIL / N/A
  4. Customer provides an overall verdict:
Verdict Meaning Next Step
ACCEPT All criteria met or minor cosmetic issues only Proceed to 7.4 (sign-off)
CONDITIONAL Minor issues exist but product is usable Delivery proceeds; fix plan agreed with deadline. Pablo implements fixes.
REJECT Blocking issues prevent acceptance Loops back to Pablo (N-046). Re-enters at Stage 4 or 5 depending on severity.

Remediation on REJECT:

  • Dana documents specific failures and routes to Pablo
  • Pablo fixes and re-submits through QA (Stage 5) if structural, or directly back to UAT if cosmetic
  • Max 2 rejection cycles before escalation to Clara (CTO)
  • Iteration count tracked in process/uat-results.md

Template: workflows/templates/uat-results-template.md

7.4 Deliver Documentation

User guide (client language), configuration guide, skill reference card, quick-start cheat sheet.

7.5 Confirm Client Operational Capability

Client demonstrates invoking 3+ skills independently. Client creates a new request correctly. Client understands any halt/approval checkpoints.

7.6 Establish Feedback Channel

Dana explains how the customer can submit feedback, bugs, and feature requests post-delivery:

  • Repo-based products: feedback/ folder in the deployed repo — one file per issue using the feedback template
  • Standalone products: Shared delivery folder (e.g., OneDrive/agents/{client}/feedback/) or email
  • Dana confirms the customer knows the channel and has submitted a test entry

7.7 Collect Initial Feedback

First impressions, missing capabilities, usability issues, confidence level (1-5). Supplement generic feedback questions with product-specific questions from the work order (look for a feedback questions section, typically Section 12 or equivalent).

Outputs

Deliverable Format Destination
UAT results Markdown Filed in order process/
Delivery confirmation Markdown (signed by client) Triggers billing (Stage 8)
Handover session notes Markdown Filed in order records
Initial client feedback Markdown Sent to Fiona (Stage 9)

Quality Gate

Gate: Client accepts product (UAT ACCEPT or CONDITIONAL) and confirms operational capability. Criteria: UAT completed, handover completed, client demonstrated independent use, documentation delivered, feedback channel established, confirmation signed. Evidence: UAT results + signed delivery confirmation + handover notes.