# AI Workflow Profile Brief 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 Workflow Profile Brief: Northside HVAC

Operator: Jim

## Business snapshot

- Company: Northside HVAC
- Owner role: Owner
- Service area: Loveland, CO
- Website: https://northside.example
- Business type: home-services
- Customer channels: Website form, phone, Google Business Profile
- Current tools: Gmail, Google Calendar, Housecall Pro

## Workflow signal

- Bottleneck: Lead follow-up slows down when the owner is in the field.
- AI goals: Speed up lead follow-up and quote prep without sending anything automatically.
- Monthly lead volume: 31-100
- Preferred contact path: email
- Approval preference: Owner approves every customer-facing reply.

## Buying signals

- Lead volume can support a revenue-linked first build.
- Repeated lead follow-up friction is a strong agent or workflow candidate.
- Current tools are named, so the Opportunity Map can separate manual workflow from future integrations.
- The AI goal already points toward approval-first drafting instead of risky autonomous action.

## Recommended next step

- Recommended next step: AI Opportunity Map
- Pricing anchor: AI workflow profile brief is first-call prep from account metadata; quote the paid Opportunity Map before implementation work starts.

## First-call questions

- Which lead sources produce the highest-value jobs?
- What currently happens when a lead arrives while the owner is unavailable?
- Which replies may AI draft, and which cases must stay human-only?
- What existing tool data is acceptable to review during the diagnostic?
- What would make the first 30 days clearly worth the build cost?

## Acceptance checks

- Brief summarizes the account workflow profile without claiming integrations are already wired.
- Recommended next step is a paid diagnostic, not an implementation promise.
- First-call questions identify ROI, approval boundaries, and safe input sources.
- Human approval and no-write boundaries are visible before any build conversation.

## Guardrails

- Human approval is required before external sends, customer-system writes, booking holds, pricing exceptions, payment-affecting actions, legal answers, refunds, or policy exceptions.
- No CRM, calendar, email, SMS, booking, payment, website, or customer-system write access until separately approved and scoped.
- No autonomous external sending.
- No use of live customer records, credentials, uploads, payment data, or private transcripts in this reusable consulting repo.
- No implementation scope starts until the Opportunity Map names acceptance checks, risks, and owner approval gates.