# AI Consulting Sales 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.

# AI Consulting Sales Workflow: Setup Your AI

Operator: Jim

## Workflow

- Lead-to-proposal workflow
- Price anchor: $5,000 sales workflow sprint
- liveWritesEnabled: false

## Lead profile

- Buyer: Mountain View Events (Owner)
- Problem: Missed event inquiries and slow tour follow-up are costing booked weddings.
- Current tools: Website form, Gmail, Google Calendar, Stripe

## Workflow stages

1. Capture qualified inquiry (inquiry) - Turn raw contact-form notes into a clean buyer snapshot and missing-information list. Operator action: Review the intake, classify the buyer lane, and decide whether the next step is a call, Opportunity Map, workshop, or no-fit reply. Proof: Lead snapshot names buyer role, business problem, likely offer lane, and missing facts.
2. Prepare first call (diagnostic) - Give the lead engineer a concise call brief before the discovery call. Operator action: Build a first-call prep brief with buyer context, likely ROI, risk flags, and the top five questions. Proof: First-call prep brief is ready before the call and uses sample-safe facts only.
3. Summarize call notes (diagnostic) - Convert messy notes into the buyer problem, workflow candidates, objections, and next decision. Operator action: Summarize notes into decision records and route to Opportunity Map, proposal, workshop, or wait state. Proof: Call-note summary separates facts, assumptions, objections, and follow-up commitments.
4. Score opportunity (diagnostic) - Choose the highest-ROI first workflow instead of selling a vague AI package. Operator action: Score candidate workflows by ROI, repeatability, data readiness, integration simplicity, approval clarity, risk, and speed to value. Proof: Opportunity scorecard names the first build, no-build calls, and deferred integrations.
5. Draft human-reviewed proposal (quote) - Turn the selected first build into a concrete proposal without generating a live payment link. Operator action: Draft included scope, exclusions, milestones, acceptance checks, price range, and next step for Jim review. Proof: Proposal packet says draft requires human review before it is sent and no payment link is generated.
6. Kick off delivery (launch) - Move an accepted proposal into delivery without losing scope, approvals, or blocked items. Operator action: Create kickoff checklist, required assets, owner approvals, and blocked integration list. Proof: Kickoff packet links proposal scope to delivery board cards and launch acceptance checks.
7. Schedule AI Ops review (retainer_ops) - Turn the first build into recurring improvement rather than one-off support. Operator action: Schedule monthly review topics and expansion candidates for after launch, without changing any customer systems. Proof: AI Ops handoff names reporting cadence, metrics, incidents, improvements, and expansion boundaries.

## Required deliverables

- Qualified lead snapshot
- Missing-information checklist
- First-call prep brief
- Discovery question list
- Call-note summary
- Decision record
- Opportunity scorecard
- First-build recommendation
- Human-reviewed proposal follow-up draft
- Proposal checklist
- Delivery kickoff checklist
- Blocked integration list
- AI Ops handoff
- Monthly review agenda

## Handoff rules

- Inquiry snapshot feeds first-call prep.
- First-call prep and call notes feed the Opportunity Map.
- Opportunity Map feeds the human-reviewed proposal draft.
- Accepted proposal feeds the delivery kickoff and blocked-integration list.
- Launch proof feeds the AI Ops monthly review agenda.

## Approval policy

- Jim reviews every outbound email, proposal, payment term, and calendar step before anything external is sent or changed.

## Acceptance checks

- A sample inquiry creates a qualified buyer snapshot and missing-information checklist.
- First-call prep names buyer problem, likely ROI, risk flags, and the top discovery questions.
- Call notes separate facts, assumptions, objections, commitments, and next action.
- Opportunity scoring names one first build and visible no-build or deferred integration calls.
- Proposal follow-up remains a human-reviewed draft and does not generate a live payment link.
- Kickoff output creates visible blocked items for unapproved CRM, calendar, email, SMS, booking, payment, website, or customer-system writes.

## Non-goals

- No autonomous external sending in v0.
- No CRM, calendar, email, SMS, booking, payment, website, or customer-system write access in the reusable workflow.
- No live customer data, credentials, uploads, payment records, or private transcripts in this product repo.
- No proposal, payment term, calendar step, or customer-visible message is sent without lead engineer approval.

## Pricing note

- $5,000 sales workflow sprint can be sold standalone or bundled into an implementation roadmap.