# AI Implementation Proposal Packet

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

Source: setupyour-consulting-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.

# AI Implementation Proposal: Mountain View Events

Operator: Jim
Source roadmap: AI Implementation Roadmap
Proposal status: draft_requires_human_review

## Human review status

- Draft requires human review before it is sent.
- No payment link is generated from this reusable product repo.

## Business context

- Wedding venue losing momentum when tour requests wait overnight and follow-up depends on owner availability.

## Recommended package

- Tour follow-up agent pilot (agents)
- Quoted range: $7,500-$12,000
- Outcome: Draft qualified tour replies from approved facts with owner approval before send.

## Included scope

- Approved facts and reply boundaries
- Owner handoff packet for qualified tour requests
- Human-approved draft follow-up workflow
- Verification examples for refund, contract, date-availability, and vague-pricing scenarios

## Excluded until separately approved

- Calendar write access
- CRM record creation
- Autonomous external sending
- Payment, booking, website, SMS, or customer-system writes

## Milestones and acceptance

1. Approved facts and escalation boundaries
   - Owner-approved facts are separated from uncertain claims.
   - Pricing exceptions and booking holds escalate to the owner.
2. Draft reply workflow
   - Qualified tour requests create an owner handoff.
   - Every external customer reply is reviewed before launch.
3. Verification and launch decision
   - Risky examples escalate instead of promising availability, pricing, refunds, or legal terms.
   - Launch requires a written owner approval record.

## Approval policy

- Owner approves every external customer reply and every customer-system write before launch.

## Payment terms placeholder

- Deposit or invoice terms are added manually after Jim reviews the proposal.
- Valid for 14 days after human review.

## Next actions

- Review scope with the owner.
- Confirm which integrations stay excluded.
- Send a manually reviewed proposal.

## Acceptance checks

- Proposal names buyer outcome, price range, included scope, excluded scope, milestones, and next actions.
- Draft requires human review before it is sent.
- No payment link is generated from the reusable product repo.
- Every customer-visible action and customer-system write keeps the human approval policy visible.

## Non-goals

- No payment link is generated; invoices, deposits, discounts, and payment terms are added manually after review.
- No autonomous external sending.
- No CRM, calendar, email, SMS, booking, payment, website, or customer-system write access until separately approved and scoped.
- No legal, refund, pricing-exception, contract, or policy answers beyond the reviewed proposal language.
- No live customer data, credentials, uploads, payment records, or private transcripts in this reusable consulting repo.

## Pricing note

- Implementation proposal is a draft sales packet after a roadmap; payment terms and links are added manually after human review.