# Client Delivery Workflow 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 Workflow: Mountain View Events

Operator: Jim

## First build

- Tour follow-up agent: Qualify tour requests and draft fast venue replies with owner approval.

## Current tools

- Gmail, Google Calendar, Squarespace

## Delivery stages

1. Inquiry intake and fit check (inquiry) - Capture the buyer problem, current tools, urgency, budget signal, and owner approval needs before promising integrations. Proof: Qualified intake summary and recommended first lane.
2. Opportunity Map diagnostic (diagnostic) - Score candidate workflows by ROI, repeatability, data readiness, integration simplicity, approval clarity, risk, and speed to value. Proof: Opportunity Map names the first build and at least one no-build call.
3. Scoped quote and approval policy (quote) - Turn the first build into a bounded scope, price range, timeline, non-goals, and explicit approval gates. Proof: Quote packet names included systems, excluded systems, human approval rules, and acceptance checks.
4. Build Tour follow-up agent (build) - Build the deterministic intake, routing, queue, or reporting path before adding AI drafting or classification. Proof: Representative sample input creates the expected internal handoff without external side effects.
5. Verify risky and high-value examples (verify) - Run happy-path, ambiguous, risky, and escalation examples before any launch decision. Proof: Verification log shows useful output, refusal paths, escalation behavior, and owner approval points.
6. Human-approved launch (launch) - Launch only the approved v0 path with visible monitoring, rollback notes, and no silent expansion into new channels. Proof: Launch checklist names owner approval, monitoring, rollback, and the first post-launch review date.
7. Retainer handoff and improvement loop (retainer_ops) - Review handled volume, misses, incidents, improvements, and expansion candidates monthly. Proof: Monthly report separates improvements from risky expansion and repeats approval boundaries.

## Handoff rules

- Inquiry handoff feeds the Opportunity Map.
- Opportunity Map feeds the quote and sprint blueprint.
- Sprint verification feeds launch approval.
- Launch proof feeds the monthly AI Ops retainer.

## Approval policy

- Owner approves every external customer reply and every customer-system write before launch. Jim reviews the first production examples.

## Acceptance checks

- Every external send, customer-system write, payment-affecting action, legal answer, refund, pricing exception, and policy exception has a human approval gate.
- The first launch path can be demonstrated with sample input before any real customer-system access is requested.
- The customer can see what is in scope, what is excluded, what is waiting on them, and what proof marks the stage complete.
- Retainer work starts from launched workflow telemetry, not vague ongoing support.

## Non-goals

- No autonomous external sending in v0.
- No CRM/calendar/email write access until the customer explicitly approves that integration path.
- No live customer data, credentials, uploads, payments, or private transcripts in product templates.
- No silent migration of existing customer systems during the first sprint.

## Commercial path

- Quote: $5,000-$7,500 for the first workflow sprint
- Retainer: AI Ops retainer after launch, starting around $1,000/month.