# Client Delivery Board Packet

Sample buyer-facing packet generated from Setup Your AI private product repositories.

Source: setupyour-workflow-products
Data policy: sample fixture only; no live customer records, credentials, uploads, payment data, or private transcripts.
Approval policy: human approval is required before external sends, customer-system writes, booking holds, pricing exceptions, payment-affecting actions, legal answers, refunds, or policy exceptions.

# Client Delivery Board: Mountain View Events

Operator: Jim

## Snapshot

- Total cards: 8
- Blocked: 1
- Ready for verification: 1
- Ready for launch: 1

## Board lanes

### inquiry

- Inbound AI consulting inquiry (consulting) - Owner: Jim. Next: Confirm the buyer's repeated manual workflow and collect the first sample transcript. Proof: Intake notes with buyer role, business type, and repeated-work candidate.

### diagnostic

- Opportunity Map diagnostic (consulting) - Owner: Jim. Next: Score missed-lead response, tour follow-up, and client handoff candidates for ROI and launch risk. Proof: Opportunity Map scorecard with one recommended first build and no-build calls.

### quote

- Scoped workflow sprint quote (automation) - Owner: Jim. Next: Turn the first-build candidate into a fixed sprint scope with human approval gates. Proof: Quote packet names inputs, outputs, exclusions, approval policy, and acceptance checks.

### build

- Build tour follow-up agent (agents) - Owner: Jim. Next: Create the approved-facts base, draft follow-up sequence, and owner review checklist. Proof: Sample-only prompt packet and test transcript stored in the private product repo.

### verify

- Escalation transcript verification (agents) - Owner: Jim. Next: Run refund, contract, date-availability, and vague-pricing scenarios through the draft workflow. Proof: Verification transcript shows escalation instead of unsupported promises.

### launch

- Human-approved launch checklist (automation) - Owner: Jim. Next: Review launch examples with the owner before turning on any customer-visible workflow. Proof: Owner approval record and launch checklist with rollback contact path.

### retainer_ops

- AI Ops monthly review (ops) - Owner: Jim. Next: Review volume, wins, misses, incidents, and expansion candidates after launch. Proof: Monthly AI Ops report with next approved improvement.

### blocked

- Calendar write integration request (automation) - Owner: Client owner. Next: Keep scheduling manual until the customer approves integration scope, permissions, rollback, and test data. Proof: Approval and permission evidence are missing; no calendar write access is configured.

## Blocked work

- Calendar write integration request: Keep scheduling manual until the customer approves integration scope, permissions, rollback, and test data. Proof needed: Approval and permission evidence are missing; no calendar write access is configured.

## Approval policy

- Owner approves every external customer reply and every customer-system write before launch. Jim reviews launch examples before anything customer-visible changes.

## Acceptance checks

- Every card has an owner, next action, and proof artifact.
- The board separates inquiry, diagnostic, quote, build, verify, launch, retainer, and blocked work.
- Blocked cards are visible instead of buried in notes.
- Launch and external customer actions keep the human approval policy visible.

## Non-goals

- No autonomous external sending in v0.
- No CRM, calendar, email, SMS, booking, payment, website, or customer-system write access until a client-specific integration is approved.
- No live customer data, credentials, uploads, payment records, or private transcripts in this reusable product repo.
- No silent launch; every launch card needs a human approval record.

## Pricing note

- Included inside workflow automation sprints and AI Ops retainers; standalone dashboard customization is scoped separately.