# Workflow Implementation Sprint Kit 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.

# Workflow Implementation Sprint Kit: Mountain View Events

Operator: Jim

## Workflow

- Inquiry-to-tour handoff workflow: Tour requests arrive through forms and email, then stall because missing details, availability questions, and owner approval all live in different places.
- Price anchor: $5,000 one-workflow sprint, then AI Ops retainer after launch
- liveWritesEnabled: false

## Current tools

- Website form, Gmail, Google Calendar, Google Sheets

## Required assets

- workflow map
- sample inputs
- routing rules
- exception queue
- handoff draft template
- launch checklist

## Implementation phases

1. Map the current handoff - Confirm where inquiries enter, what details are required, and where the handoff currently breaks. Operator action: Create a workflow map from sample form submissions, emails, and owner notes. Proof: Workflow map names intake fields, owner decision points, exception paths, and handoff destination.
2. Normalize intake and missing facts - Turn messy inquiry text into a consistent internal record and missing-information checklist. Operator action: Build the normalized intake shape and missing-facts detector from sample inputs. Proof: Every sample inquiry produces a summary, missing details, and owner-visible next action.
3. Route exceptions before drafting - Separate safe draftable inquiries from pricing, legal, refund, availability, and policy exceptions. Operator action: Create routing rules and an exception queue before any customer-facing draft is generated. Proof: Risky examples land in the exception queue with the correct reason.
4. Generate handoff drafts - Draft owner-reviewed responses and internal handoff notes without sending externally. Operator action: Create the handoff draft template, approved-facts references, and owner review checklist. Proof: Draft output includes customer reply draft, internal summary, and approval checklist.
5. Verify refusal and escalation paths - Run normal, ambiguous, and unsafe cases before launch. Operator action: Run the eval set and record pass/fail notes for drafts, exceptions, and forbidden actions. Proof: Verification packet shows accepted output, escalations, and forbidden actions avoided.
6. Launch human-approved v0 - Use the workflow with owner review only, visible monitoring, and rollback notes. Operator action: Prepare launch checklist, owner approval path, monitoring cadence, and retainer handoff. Proof: Launch checklist confirms no live writes, reviewer ownership, rollback path, and first review date.

## Eval coverage

- 10 eval cases
- Map the current handoff: complete-inquiry, missing-date
- Normalize intake and missing facts: messy-email, partial-form
- Route exceptions before drafting: pricing-exception, legal-question
- Generate handoff drafts: qualified-tour-request
- Verify refusal and escalation paths: unsafe-external-send, booking-hold-request
- Launch human-approved v0: launch-checklist

## Approval policy

- Owner approves every external customer reply, availability statement, pricing exception, booking hold, and customer-system write.

## Acceptance checks

- Representative sample inputs create the expected routing, exception, and handoff draft outputs.
- Every risky or ambiguous case has a human approval or escalation path.
- Launch checklist verifies no direct CRM, calendar, email, SMS, booking, payment, website, or customer-system writes are enabled.
- The customer can inspect the workflow queue, blocked items, and proof artifacts before launch.

## Non-goals

- No autonomous external sending in v0.
- No CRM, calendar, email, SMS, booking, payment, website, or customer-system write access in the reusable kit.
- No live customer data, credentials, uploads, payment records, or private transcripts in this product repo.
- No migration of existing customer systems during the first sprint.

## Retainer handoff

- Move to monthly AI Ops after launch to review stuck inquiries, unsafe drafts, approval bottlenecks, missing facts, and the next approved integration candidate.