# Plan 4 — AI Packages Extension

> **For agentic workers:** REQUIRED SUB-SKILL: Use `superpowers:subagent-driven-development` (recommended) or `superpowers:executing-plans` to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.

**Goal:** Extend the existing packages launch with AI offerings: AI Chatbot (3-tier service), AI Business Automation (project-scoped), and AI Chatbot Quick-Start tripwire. Fold AI content output into existing Email/Social/SEO Growth+Pro tiers. Update the root catalog, FAQ language, and ops playbooks accordingly.

**Architecture:** Same patterns as Plan 1 (HTML snippets for Beaver Builder, lead-form modal for capture, shared `_tokens.css`). All AI pages introduce "Activation + Maintenance" pricing display in place of "setup + monthly" language. AI pages add a mandatory "What This DOESN'T Do" section to set boundaries. Each AI page leads with industry-specific use cases (service biz, medical, legal, real estate, retail).

**Tech Stack:** Same as Plan 1 — vanilla HTML5/CSS/JS, no build step, drops into Beaver Builder code modules.

**Reference specs:**
- Base spec: `docs/superpowers/specs/2026-06-02-packages-launch-design.md`
- AI addendum: `docs/superpowers/specs/2026-06-02-packages-launch-addendum-ai.md`
- Source doc: `BTWG_AI_Package_Strategy.md`

**Dependencies:** Plan 1 must be complete (or in progress) — this plan reuses `_tokens.css`, `lead-form-modal.html`, and the patterns established in service-hub and tripwire pages.

---

## File Structure (additions to Plan 1's `packages-html/`)

```
packages-html/
├── service-ai-chatbot.html               ← NEW
├── service-ai-business-automation.html   ← NEW (project-scoped, not tier table)
├── tripwire-ai-chatbot-quick-start.html  ← NEW
├── service-email-marketing.html          ← MODIFY (Content Engine fold-in)
├── service-social-media.html             ← MODIFY (Content Engine fold-in)
├── service-seo.html                      ← MODIFY (Content Engine fold-in)
├── packages-root.html                    ← MODIFY (add AI cards, expand filter)
└── _components/faq-accordion.html        ← MODIFY (FAQ #3 setup-fee rewrite for dual-context)

ops/playbooks/
├── service-ai-chatbot.md                 ← NEW
├── service-ai-business-automation.md     ← NEW
└── tripwire-ai-chatbot-quick-start.md    ← NEW
```

---

## Task 1: Update root `/packages` catalog (in-place modification)

**Files:**
- Modify: `packages-html/packages-root.html`

Adds two new service cards (AI Chatbot, AI Business Automation) + one new tripwire card (Quick-Start) + extends the filter chip set.

- [ ] **Step 1: Add `AI` to the "By Service" filter chip row**

In the existing filter bar markup, add a new chip after `Graphics`:

```html
<button class="btw-filter-chip" data-filter-chip data-filter-group="service" data-filter-value="ai">AI</button>
```

- [ ] **Step 2: Add AI tripwire to the tripwire row**

In the existing "Featured row — Start small, scale up" tripwire row, append a 4th card:

```html
<div class="btw-card" data-filter-card data-goal="lead-gen" data-budget="under-300" data-service="ai">
  <div class="btw-badge">Try it</div>
  <h3>AI Chatbot Quick-Start</h3>
  <p style="font-size:14px;color:#5a6478;margin-bottom:12px;">
    A real AI chatbot deployed on your site in 5 business days. 15 Q&A pairs, lead capture, live for 30 days.
  </p>
  <div class="btw-price">$297 <span class="btw-price__per">one-time</span></div>
  <button class="btw-btn" data-btw-lead-open="tripwire-ai-chatbot-quick-start" style="margin-top:16px;width:100%;">Get the Quick-Start →</button>
</div>
```

Tripwire row now scrolls horizontally on mobile (4 cards).

- [ ] **Step 3: Add 2 new service cards to the service catalog row**

In the existing "Service catalog — 6 cards" section, add two cards. Update the section heading to "Service catalog — 8 cards" (or just remove the count). Add:

```html
<div class="btw-card" data-filter-card data-goal="lead-gen" data-budget="500-1000 1000-2000 2000-plus" data-service="ai">
  <h3>AI Chatbot</h3>
  <p style="color:#5a6478;font-size:15px;margin-bottom:16px;">
    Our specialists shape what your chatbot knows, how it sounds, and what it escalates. AI handles the conversations — 24/7, in your brand voice — so customers get answered while you sleep.
  </p>
  <p style="margin-bottom:16px;"><strong>From $997 Activation + $497/mo</strong></p>
  <a href="/packages/ai-chatbot" class="btw-btn btw-btn--ghost">See tiers →</a>
</div>

<div class="btw-card" data-filter-card data-goal="efficiency" data-budget="2000-plus" data-service="ai">
  <h3>AI Business Automation</h3>
  <p style="color:#5a6478;font-size:15px;margin-bottom:16px;">
    Repetitive workflows that eat your team's time — sorting emails, routing leads, processing documents — handled by AI you don't have to manage. We map your bottleneck, build the automation, and keep it running.
  </p>
  <p style="margin-bottom:16px;"><strong>From $2,497 one-time</strong></p>
  <a href="/packages/ai-business-automation" class="btw-btn btw-btn--ghost">See engagement models →</a>
</div>
```

- [ ] **Step 4: Verify**

Run: `open /Users/sanketlakhani/Work/btwebgroup-packages/packages-html/packages-root.html`

Acceptance:
- [ ] `AI` chip appears in the filter row, clicking it hides non-AI cards
- [ ] Tripwire row shows 4 cards (3 original + Quick-Start)
- [ ] Service catalog shows 8 cards (6 original + AI Chatbot + AI Business Automation)
- [ ] Mobile: AI cards stack properly, no overflow
- [ ] Lead modal opens with correct context (`tripwire-ai-chatbot-quick-start`)

- [ ] **Step 5: Commit**

```bash
cd /Users/sanketlakhani/Work/btwebgroup-packages
git add packages-html/packages-root.html
git commit -m "feat(pages): add AI service+tripwire cards to /packages root"
```

---

## Task 2: Build AI Chatbot service hub

**Files:**
- Create: `packages-html/service-ai-chatbot.html`

Follows the service hub pattern from Plan 1 Task 5 BUT with three modifications:
1. Pricing displays as `Activation: $X (one-time) · Maintenance: $Y/mo` (NEVER as "$X setup + $Y/mo")
2. Mandatory "What This DOESN'T Do" section between the tier table and the FAQ
3. Industry use-case strip near the top — service biz, medical, legal, real estate, retail

- [ ] **Step 1: Write the page**

Use Plan 1 Task 5 template as the base. Substitute:

- **Hero:**
  - Headline: `Your Website Answers Customers at 2am. Books Appointments at 4am. Captures Leads at 6am.`
  - Sub: AI Chatbot AI-angle paragraph from addendum §A.3 *(starts with "Our specialists shape what your chatbot knows...")*
  - Anchor banner: `What this would cost from a typical AI agency: $1,500–$7,500 setup + $297–$1,497/mo. Our Activation: from $997. Same work — done faster.`
  - CTA: `[Start with Quick-Start — $297]` (opens modal `tripwire-ai-chatbot-quick-start`)
  - Secondary CTA: `[See tiers ↓]` (anchor)

- **Industry use-case strip** (new section type — sits between hero and tier table):

```html
<section class="btw-section">
  <div class="btw-container">
    <h2 style="text-align:center;margin-bottom:32px;">Built for the businesses where customers ask the same 20 questions over and over</h2>
    <div class="btw-grid btw-grid--3" style="--btw-gap:20px;">
      <div class="btw-card"><h3>Service Businesses</h3><p>HVAC, plumbing, electrical, roofing. Estimates, scheduling, emergencies — answered without your team picking up the phone.</p></div>
      <div class="btw-card"><h3>Medical &amp; Dental</h3><p>Office hours, insurance accepted, new-patient intake, common procedure info. (We do NOT handle HIPAA-regulated PHI — see below.)</p></div>
      <div class="btw-card"><h3>Law Firms</h3><p>Initial intake, case-type qualification, scheduling consultations. Filters out cases you don't take so your team only sees qualified leads.</p></div>
      <div class="btw-card"><h3>Real Estate</h3><p>Property inquiries, tour booking, neighborhood info. Captures leads from listing pages 24/7.</p></div>
      <div class="btw-card"><h3>Retail &amp; E-commerce</h3><p>Product questions, store hours, order status. Reduces "where's my order" tickets without losing the human touch.</p></div>
      <div class="btw-card"><h3>Multi-Location Brands</h3><p>Routes inquiries to the right location automatically. Each branch sees only its own qualified leads.</p></div>
    </div>
  </div>
</section>
```

- **Tier table** (3 columns — Activation row + Maintenance row separately):

```html
<section class="btw-section btw-section--soft" id="tiers">
  <div class="btw-container">
    <h2 style="text-align:center;margin-bottom:40px;">Three tiers. No setup-fee surprises — Activation is the one-time build cost, disclosed up front.</h2>
    <div class="btw-grid btw-grid--3">

      <div class="btw-card">
        <div class="btw-badge">Starter</div>
        <p style="margin:8px 0 4px;color:#5a6478;font-size:14px;">Activation (one-time)</p>
        <div class="btw-price">$997</div>
        <p style="margin:12px 0 4px;color:#5a6478;font-size:14px;">Maintenance</p>
        <div class="btw-price">$497<span class="btw-price__per">/mo</span></div>
        <ul style="margin:24px 0;padding-left:20px;line-height:1.8;font-size:15px;">
          <li>15 Q&amp;A pairs + your website content</li>
          <li>Lead capture form integration</li>
          <li>Monthly conversation report</li>
          <li>English only</li>
          <li>Standard helpful tone</li>
          <li>Email support</li>
        </ul>
        <button class="btw-btn" data-btw-lead-open="ai-chatbot-starter" style="width:100%;">Get Started</button>
      </div>

      <div class="btw-card" style="border:2px solid #00b8c4;">
        <div class="btw-badge btw-badge--gold">Most popular · Growth</div>
        <p style="margin:8px 0 4px;color:#5a6478;font-size:14px;">Activation (one-time)</p>
        <div class="btw-price">$2,497</div>
        <p style="margin:12px 0 4px;color:#5a6478;font-size:14px;">Maintenance</p>
        <div class="btw-price">$997<span class="btw-price__per">/mo</span></div>
        <ul style="margin:24px 0;padding-left:20px;line-height:1.8;font-size:15px;">
          <li>50 Q&amp;A pairs + quarterly refresh</li>
          <li>Lead qualification workflow</li>
          <li>Calendar booking (Calendly/Google/Outlook)</li>
          <li>CRM sync (HubSpot/Salesforce/Pipedrive)</li>
          <li>English + 1 additional language</li>
          <li>Branded tone</li>
          <li>Email + phone support</li>
        </ul>
        <button class="btw-btn" data-btw-lead-open="ai-chatbot-growth" style="width:100%;">Get Started</button>
      </div>

      <div class="btw-card">
        <div class="btw-badge">Pro</div>
        <p style="margin:8px 0 4px;color:#5a6478;font-size:14px;">Activation (one-time)</p>
        <div class="btw-price">$4,997</div>
        <p style="margin:12px 0 4px;color:#5a6478;font-size:14px;">Maintenance</p>
        <div class="btw-price">$1,997<span class="btw-price__per">/mo</span></div>
        <ul style="margin:24px 0;padding-left:20px;line-height:1.8;font-size:15px;">
          <li>Unlimited Q&amp;A + monthly refresh</li>
          <li>Multi-step qualification + lead scoring</li>
          <li>Smart calendar booking</li>
          <li>Bi-directional CRM sync + custom fields</li>
          <li>Human handoff via Slack/Teams/email</li>
          <li>Up to 4 additional languages</li>
          <li>Custom voice + persona training</li>
          <li>Live analytics dashboard + monthly review call</li>
        </ul>
        <button class="btw-btn" data-btw-lead-open="ai-chatbot-pro" style="width:100%;">Get Started</button>
      </div>

    </div>
  </div>
</section>
```

- **"What This DOESN'T Do" section** (mandatory — paste verbatim from addendum §A.3):

```html
<section class="btw-section">
  <div class="btw-container" style="max-width:820px;">
    <h2 style="text-align:center;margin-bottom:24px;">What this DOESN'T do (yes, really)</h2>
    <p style="text-align:center;color:#5a6478;margin-bottom:32px;">Being specific about boundaries is how good AI implementations stay good. Here's what an AI Chatbot from us doesn't do:</p>
    <ul style="font-size:16px;line-height:2;padding-left:0;list-style:none;">
      <li style="padding:8px 0;border-bottom:1px solid #e3e8f0;">❌ Multi-step complex troubleshooting (Starter/Growth route to a human; Pro can attempt with caveats)</li>
      <li style="padding:8px 0;border-bottom:1px solid #e3e8f0;">❌ HIPAA-regulated PHI communications. We build for general info + scheduling only.</li>
      <li style="padding:8px 0;border-bottom:1px solid #e3e8f0;">❌ Take payments directly. We capture intent and hand off to your existing checkout.</li>
      <li style="padding:8px 0;border-bottom:1px solid #e3e8f0;">❌ Replace a sales rep on closing conversations. Qualifies, books, hands off.</li>
      <li style="padding:8px 0;">❌ Generate marketing content. That's our Email, Social, and SEO packages.</li>
    </ul>
  </div>
</section>
```

- **Tripwire down-sell:** `Not ready for monthly? Try the AI Chatbot Quick-Start for $297 — a real chatbot, live on your site in 5 days, free for 30 days.` CTA opens modal `tripwire-ai-chatbot-quick-start`.

- **No bundle up-sell yet** — until Voice Agent ships, there's no AI bundle.

- **FAQ** (5 items, AI-specific):
  - *How do you train the chatbot on our business?* → intake form + sitemap crawl + Q/A library you approve.
  - *What if the chatbot says something wrong?* → quality control via human review + monthly refresh + you can edit any answer any time.
  - *Will it work on our existing website platform?* → yes — WordPress, Wix, Squarespace, Shopify, custom. We deploy via a small embed snippet.
  - *Who owns the chatbot if we cancel?* → you do. We export the full Q/A library + configuration in your data-export package. The infrastructure can be self-hosted by anyone after that with a small migration we charge for separately.
  - *What's the difference between Activation and a setup fee?* → Activation is a tangible build deliverable (like a website build). Setup fees are usually for things that have no separate deliverable. We use "Activation" because there's a real system you own at the end of it.

- **Sticky bottom CTA (mobile):** *"AI Chatbot Starter — $997 Activation + $497/mo"* with `[Get Started]`.

- **End:** lead-form-modal.

- [ ] **Step 2: Verify**

Run: `open /Users/sanketlakhani/Work/btwebgroup-packages/packages-html/service-ai-chatbot.html`

Acceptance:
- [ ] Pricing displays as "Activation: $X / Maintenance: $Y/mo" — NEVER "$X setup + $Y/mo"
- [ ] "What this DOESN'T do" section is present and conspicuous
- [ ] Industry use-case strip renders as 6 cards (2x3 on tablet, 1-col on mobile)
- [ ] Tier table 3 columns; Growth tier visually highlighted with teal border
- [ ] HIPAA disclaimer visible in the Medical/Dental industry card
- [ ] No mention of specific AI tool names anywhere in copy

- [ ] **Step 3: Commit**

```bash
git add packages-html/service-ai-chatbot.html
git commit -m "feat(pages): AI Chatbot service hub"
```

---

## Task 3: Build AI Business Automation page

**Files:**
- Create: `packages-html/service-ai-business-automation.html`

This is a project-scoped page (not a 3-tier comparison). Structure deviates from the service hub template.

- [ ] **Step 1: Write the page**

Sections:

1. **Hero:**
   - Headline: `Your Team's Boring Work. Handled by AI. So They Can Do the Work That Matters.`
   - Sub: addendum §A.4 customer-facing description
   - CTA: `[Book a 20-min discovery call]` (opens modal `ai-automation-discovery`)
   - Anchor: `Typical AI consultant pricing: $3,500–$25,000 per workflow. Ours starts at $2,497 because our team builds it directly.`

2. **"What we automate" examples row** — 6 cards from addendum §A.4 (inbound email triage, lead-form intake, doc-to-data, daily reports, calendar-CRM sync, review monitoring).

3. **Three engagement models** (cards, not tier table):

```html
<section class="btw-section btw-section--soft">
  <div class="btw-container">
    <h2 style="text-align:center;margin-bottom:40px;">Three ways to engage</h2>
    <div class="btw-grid btw-grid--3">

      <div class="btw-card">
        <div class="btw-badge">Quick Win</div>
        <h3 style="margin-top:12px;">One workflow, fully done</h3>
        <div class="btw-price">$2,497<span class="btw-price__per">one-time</span></div>
        <p style="margin:16px 0;color:#5a6478;">Discovery → build → testing → training → 14-day post-launch support. We pick ONE workflow eating your team's time and we automate it end-to-end.</p>
        <p style="font-size:14px;color:#5a6478;"><strong>Timeline:</strong> 2 weeks</p>
        <p style="font-size:14px;color:#5a6478;margin-bottom:24px;"><strong>Best for:</strong> Specific pain point, fast win, proof of value before committing to more.</p>
        <button class="btw-btn" data-btw-lead-open="ai-automation-quick-win" style="width:100%;">Scope a Quick Win</button>
      </div>

      <div class="btw-card" style="border:2px solid #00b8c4;">
        <div class="btw-badge btw-badge--gold">Most popular · Department Build</div>
        <h3 style="margin-top:12px;">3–5 connected workflows</h3>
        <div class="btw-price">$9,997 – $19,997<span class="btw-price__per">custom quote</span></div>
        <p style="margin:16px 0;color:#5a6478;">Automate an entire department: sales ops, customer success, finance, ops. Discovery → design → build → integrations → change management for your team.</p>
        <p style="font-size:14px;color:#5a6478;"><strong>Timeline:</strong> 6–8 weeks</p>
        <p style="font-size:14px;color:#5a6478;margin-bottom:24px;"><strong>Best for:</strong> A whole function ready to be transformed, not just patched.</p>
        <button class="btw-btn" data-btw-lead-open="ai-automation-department" style="width:100%;">Scope a Department Build</button>
      </div>

      <div class="btw-card">
        <div class="btw-badge">Ongoing Retainer</div>
        <h3 style="margin-top:12px;">Always shipping more</h3>
        <div class="btw-price">$1,997<span class="btw-price__per">/mo</span></div>
        <p style="margin:16px 0;color:#5a6478;">Monthly hours for new automations + maintenance + iteration. Includes monthly strategy call to identify the next thing to automate.</p>
        <p style="font-size:14px;color:#5a6478;"><strong>Timeline:</strong> Month-to-month, no contract</p>
        <p style="font-size:14px;color:#5a6478;margin-bottom:24px;"><strong>Best for:</strong> Established clients with growing automation needs.</p>
        <button class="btw-btn" data-btw-lead-open="ai-automation-retainer" style="width:100%;">Start the Retainer</button>
      </div>

    </div>
  </div>
</section>
```

4. **"What this DOESN'T do" section** (mandatory) — verbatim from addendum §A.4.

5. **Process section:** 4 numbered steps — Discovery (free 30-min call), Scoping (we map your workflow + estimate), Build (we ship it), Run (we maintain it).

6. **FAQ** (5 items):
   - *How do you know if a workflow is automatable?* → 30-min discovery call. We'll tell you straight if it's worth doing.
   - *What if our process is broken — should we fix the process first?* → Sometimes. We'll tell you upfront. We don't automate broken processes.
   - *Who owns what we build?* → You. Full handoff documentation included; you can hire anyone to maintain it after.
   - *Do you charge by the hour?* → No. Fixed-price for Quick Win and Department Build. Retainer is monthly.
   - *What if it doesn't work?* → Quick Win has a money-back guarantee if we can't ship in 2 weeks. Department Build has milestone-based payments. Retainer is month-to-month.

7. **CTA:** `[Book a free 30-min discovery call]` + No Lock-In reminder.

8. Lead modal.

- [ ] **Step 2: Verify**

Run: `open /Users/sanketlakhani/Work/btwebgroup-packages/packages-html/service-ai-business-automation.html`

Acceptance:
- [ ] Three engagement-model cards render side-by-side on desktop
- [ ] Department Build card has the "$9,997 – $19,997 custom quote" range visible
- [ ] "Process" section reads as a 4-step linear flow
- [ ] "What this doesn't do" visible
- [ ] No mention of specific AI tool names

- [ ] **Step 3: Commit**

```bash
git add packages-html/service-ai-business-automation.html
git commit -m "feat(pages): AI Business Automation project-scoped page"
```

---

## Task 4: Build AI Chatbot Quick-Start tripwire page

**Files:**
- Create: `packages-html/tripwire-ai-chatbot-quick-start.html`

Follows the tripwire page pattern from Plan 1 Task 7. Single CTA, sharp page.

- [ ] **Step 1: Write the page**

Sections:

1. **Hero (full-screen):**
   - Headline: `Real AI Chatbot. Live on Your Site in 5 Business Days. $297.`
   - Sub: *"Not a demo. Not a slide deck. An actual chatbot, trained on 15 of your most-asked questions, capturing leads on your real website for the next 30 days. Comparable agency setup: $1,500+. Yours: $297."*
   - Single CTA: `[Get the Quick-Start]` (opens modal `tripwire-ai-chatbot-quick-start`)
   - Trust mini-strip: `No contracts · Removed after 30 days if you don't continue · Real chatbot, not a trial`

2. **Exactly what you get** (5 bullets):
   1. ✅ Real AI chatbot embedded on your live website (any platform — WordPress, Wix, Squarespace, Shopify, custom)
   2. ✅ Trained on 15 of your most-asked customer questions + your existing site content
   3. ✅ Captures lead info (name, email, phone, what they need) into your inbox automatically
   4. ✅ Live for 30 full days — your real visitors, real conversations, real lead capture
   5. ✅ Day-30 conversation report — what people asked, what was answered, what got escalated

3. **Timeline (visual, same pattern as other tripwires):**
   - Day 1: Purchase + intake form auto-sent
   - Day 2: 15-min kickoff (we agree on the 15 Q/A pairs)
   - Day 3-4: We build + test + you approve
   - Day 5: Chatbot live on your site

4. **What happens after Day 30:**

```html
<section class="btw-section btw-section--soft">
  <div class="btw-container" style="max-width:820px;">
    <h2 style="text-align:center;margin-bottom:24px;">What happens on Day 31</h2>
    <p style="text-align:center;font-size:18px;line-height:1.6;margin-bottom:24px;">You have two choices. Both are fine.</p>
    <div class="btw-grid btw-grid--2">
      <div class="btw-card">
        <h3 style="margin-top:0;">Activate Starter ($497/mo)</h3>
        <p>Chatbot stays live. Expands to 50 Q&amp;A pairs. You get monthly analytics + ongoing maintenance. No second Activation fee since we already built it during the Quick-Start. Cancel anytime.</p>
      </div>
      <div class="btw-card">
        <h3 style="margin-top:0;">Stop the chatbot</h3>
        <p>We disable it on your site. You keep the deployment documentation and the Q&amp;A library you approved. No charge, no awkward exit conversation. Door's open if you change your mind.</p>
      </div>
    </div>
  </div>
</section>
```

5. **"What this is NOT":**
   - ❌ A free demo we'll remove after one call
   - ❌ A trial that auto-converts to a subscription (you explicitly opt in or it stops)
   - ❌ A replacement for your existing chat plugin without coordination — we install alongside or work with you
   - ❌ Capable of training on more than 15 Q&amp;A pairs (that's Starter+)
   - ❌ Calendar booking, CRM sync, multi-language (those are Growth+)

6. **FAQ** (4 items):
   - *What if my site is on a platform you don't support?* → We support every major platform. If yours is exotic, the 15-min kickoff call will catch it; full refund if we can't deploy.
   - *What if I want to cancel mid-month?* → It's a one-time $297, not a subscription. There's nothing to cancel — just don't activate Starter at Day 30.
   - *Will it conflict with my existing chat widget?* → We coordinate. If you have one, we work alongside or replace by mutual agreement.
   - *Refund?* → Money-back if we miss the 5-business-day deploy SLA. After live, no refund.

7. **Single bottom CTA:** `[Get the Quick-Start — $297]` (opens modal `tripwire-ai-chatbot-quick-start`).

8. Lead modal.

- [ ] **Step 2: Verify**

Acceptance:
- [ ] Single primary CTA above the fold + at bottom (no competing CTAs)
- [ ] "What happens on Day 31" section makes the upsell path crystal clear
- [ ] Timeline visualization renders as 4-step row, stacks on mobile
- [ ] "What this is NOT" is honest, reduces refund risk
- [ ] No mention of specific AI tool names

- [ ] **Step 3: Commit**

```bash
git add packages-html/tripwire-ai-chatbot-quick-start.html
git commit -m "feat(pages): AI Chatbot Quick-Start tripwire page"
```

---

## Task 5: Apply Content Engine fold-in to Email/Social/SEO hubs

**Files:**
- Modify: `packages-html/service-email-marketing.html`
- Modify: `packages-html/service-social-media.html`
- Modify: `packages-html/service-seo.html`

Tier-table cell updates only. No structural changes.

- [ ] **Step 1: Update Email Marketing tier table**

In the existing Email Marketing tier comparison:
- **Growth** "Campaigns" row: change `2 campaigns/mo` → `2 campaigns/mo + 1 AI-content nurture email/mo`
- **Pro** "Campaigns" row: change `4 campaigns/mo` → `4 campaigns/mo + weekly AI-content nurture email (4/mo)`

Add a small callout below the Growth and Pro column headers: *"Includes AI Content Engine output — more pieces, same monthly."*

- [ ] **Step 2: Update Social Media tier table**

- **Growth** "Posts/month" row: change `15` → `20` (5 of which are AI-content-style longer-form captions/threads)
- **Pro** "Posts/month" row: change `20` → `30` (+ 1 long-form post/mo — LinkedIn article or FB long-post)

Same callout.

- [ ] **Step 3: Update SEO tier table**

- **Intermediate** "Blog/SEO pages" row: change `2 pages/mo` → `3 pages/mo (extra 1 is an AI-drafted long-form pillar piece)`
- **Advanced** "Blog/SEO pages" row: change `4 pages/mo` → `6 pages/mo + 1 whitepaper/pillar guide per quarter`

Same callout on Intermediate and Advanced columns.

- [ ] **Step 4: Verify**

For each of the 3 hubs, open in browser:
- [ ] New numbers visible in the tier table
- [ ] Callout note rendered on the right columns
- [ ] No layout breakage from the slightly longer cell text

- [ ] **Step 5: Commit**

```bash
git add packages-html/service-email-marketing.html packages-html/service-social-media.html packages-html/service-seo.html
git commit -m "feat(pages): fold AI Content Engine volume into Email/Social/SEO Growth+Pro tiers"
```

---

## Task 6: Update FAQ accordion for dual-context setup-fee answer

**Files:**
- Modify: `packages-html/_components/faq-accordion.html`

The current FAQ #3 says "no setup fees, ever." That's only true for marketing packages now. Update to dual-context.

- [ ] **Step 1: Rewrite FAQ #3**

Replace the current setup-fee item with:

```html
<details class="btw-faq__item">
  <summary>Are there setup fees or hidden charges?</summary>
  <p>
    <strong>For our marketing packages:</strong> no setup fees, no hidden charges. The monthly price is the only price.
  </p>
  <p>
    <strong>For our AI packages:</strong> there's a one-time <em>Activation</em> cost we tell you upfront — it's the cost of building your custom AI system, same idea as building a website. The monthly maintenance fee is separate and also disclosed upfront. We don't surprise you with fees. Ever.
  </p>
</details>
```

- [ ] **Step 2: Add an AI-specific FAQ item (Activation explained)**

After FAQ #3, insert:

```html
<details class="btw-faq__item">
  <summary>What's the difference between "Activation" and a setup fee?</summary>
  <p>Activation is a tangible build deliverable — by the end of it, you have a working AI system you own. Setup fees are usually one-time charges for things with no separate deliverable. We use "Activation" because there's a real system you own at the end of it. We tell you the Activation number and the monthly number upfront. Both transparent. No surprises.</p>
</details>
```

- [ ] **Step 3: Verify**

Open any page that uses the FAQ component (root, service hubs). Confirm:
- [ ] Old "no setup fees, ever" wording is gone
- [ ] New dual-context wording present
- [ ] "What's the difference between Activation and a setup fee" item appears
- [ ] Accordion still expands/collapses

- [ ] **Step 4: Commit**

```bash
git add packages-html/_components/faq-accordion.html
git commit -m "fix(pages): FAQ setup-fee answer split for marketing vs AI packages"
```

---

## Task 7: Update Trust Pillar 3 markup site-wide

**Files:**
- Modify: `packages-html/_components/trust-strip.html`
- Modify: any page that re-states Pillar 3 (root, hubs)

- [ ] **Step 1: Add Pillar 3a to the trust strip**

Original Pillar 3 stays. After it, on AI pages only, render Pillar 3a (from addendum §A.2):

```html
<div class="btw-card btw-pillar-3a">
  <div class="btw-badge">Pillar 3a (AI packages)</div>
  <h3>Transparent Activation. No Surprise Fees.</h3>
  <p>Our marketing packages have no setup fees — what you see is what you pay. Our AI packages have a clear one-time Activation cost to build and deploy your system, then a transparent monthly for maintenance. We tell you both numbers upfront before you commit to anything. No surprises, ever.</p>
</div>
```

Use a conditional class (`.btw-pillar-3a`) that's only included in the AI hub pages and the AI tripwire page. Other pages (Email hub, root, etc.) do NOT show Pillar 3a — keeps marketing pages clean.

- [ ] **Step 2: Verify**

Open AI Chatbot hub → Pillar 3a visible. Open Email hub → Pillar 3a NOT visible. Open root → Pillar 3a NOT visible.

- [ ] **Step 3: Commit**

```bash
git add packages-html/_components/trust-strip.html packages-html/service-ai-*.html packages-html/tripwire-ai-*.html
git commit -m "feat(pages): add Pillar 3a (Activation transparency) on AI pages only"
```

---

## Task 8: Cross-page QA + a11y pass on AI pages

**Files:** (none new — verification on AI pages)

Same checks as Plan 1 Task 8, applied to the new pages.

- [ ] **Step 1: Update URL_MAP.md**

Append to `packages-html/URL_MAP.md`:

```
| service-ai-chatbot.html | /packages/ai-chatbot |
| service-ai-business-automation.html | /packages/ai-business-automation |
| tripwire-ai-chatbot-quick-start.html | /packages/ai-chatbot-quick-start |
```

- [ ] **Step 2: Run the a11y + mobile + BB-compatibility checks** (same as Plan 1 Task 8) on the 3 new pages.

- [ ] **Step 3: Linguistic audit — no AI tool names**

Grep for forbidden terms on AI pages:

```bash
cd /Users/sanketlakhani/Work/btwebgroup-packages/packages-html
grep -niE 'chatgpt|gpt-4|gpt-?5|claude|anthropic|openai|midjourney|gemini\b|voiceflow|vapi|bland|retell|chatbase|intercom fin' service-ai-*.html tripwire-ai-*.html
```

Expected: zero matches. (The exception is `Gemini` if mentioned in customer-facing context about AEO/GEO search visibility — already used on SEO page; AI pages should NOT mention any of these as tools we use.)

- [ ] **Step 4: Commit fixes (if any)**

```bash
git add packages-html/
git commit -m "fix(pages): AI page QA — a11y, mobile, BB compat, no AI tool names"
```

---

## Task 9: Add ops playbooks for AI deliverables

**Files:**
- Create: `ops/playbooks/service-ai-chatbot.md`
- Create: `ops/playbooks/service-ai-business-automation.md`
- Create: `ops/playbooks/tripwire-ai-chatbot-quick-start.md`

Use Plan 3 Task 8 playbook template. Each one fills in:
- Required intake fields (from Plan 3 §01-intake-form Section C — note that intake form needs an "AI Chatbot" and "AI Automation" section appended)
- Day-by-day steps
- Internal AI tools used (internal — never in customer copy)
- Internal QA checklist
- Deliverable spec

- [ ] **Step 1: Write AI Chatbot playbook**

Cover all 3 tiers. Time budget per tier (Activation work + monthly maintenance):
- **Starter Activation:** ~6 person-hours (intake review + 15 Q/A library + chatbot platform setup + lead capture wiring + customer testing)
- **Starter Maintenance/mo:** ~2 hours (analytics review + Q/A tweaks + monthly report)
- **Growth Activation:** ~12 hours (above + calendar integration + CRM sync + qualification workflow + branded tone tuning)
- **Growth Maintenance/mo:** ~4 hours
- **Pro Activation:** ~24 hours (above + multi-language + custom voice + human handoff config + analytics dashboard)
- **Pro Maintenance/mo:** ~8 hours

Internal AI tools section: document which platform is in use (per source doc § Tools Stack Decision — Sanket must commit). Standard reference: Chatbase, Voiceflow, Intercom Fin, or custom. Decision required BEFORE first customer.

- [ ] **Step 2: Write AI Business Automation playbook**

Cover all 3 engagement models. Each has different process:
- **Quick Win:** Day 1 intake, Day 2-3 discovery + scoping (with customer), Day 4-8 build, Day 9-10 testing + customer training, Day 11-14 post-launch support
- **Department Build:** Week 1 discovery + design, Week 2 customer sign-off, Week 3-6 build + integrate, Week 7-8 training + change management
- **Ongoing Retainer:** Monthly: 4 hours minimum (1 strategy call + ~3 hours of automation work). Time tracked. Budget transparency monthly to customer.

Internal automation platform decision: n8n, Make, Zapier with AI nodes, or custom. Sanket commits before first customer.

- [ ] **Step 3: Write AI Chatbot Quick-Start playbook**

Tripwire version of the Chatbot playbook. Time budget: ~4 person-hours total (intake + 15 Q/A + deployment + 30-day live monitoring + Day-30 report).

Day-30 trigger: automated alert in production tracker → US team sends the "Activate or Stop" email (template included in the playbook).

- [ ] **Step 4: Update intake form**

Append two new sections to `ops/01-intake-form.md` Section C:

**C-10. AI Chatbot (Starter/Growth/Pro OR Quick-Start tripwire)**
- Website platform (WordPress / Wix / Squarespace / Shopify / custom)
- 15 most-asked customer questions (paste the list, or "we'll work with you to build it during kickoff")
- Lead notifications — email address(es) that should receive lead alerts
- For Growth+: calendar tool (Calendly / Google / Outlook) + CRM (HubSpot / Salesforce / Pipedrive / Zoho / other)
- For Pro: additional languages needed + brand voice samples (URLs to your existing content) + handoff channel (Slack/Teams/email)
- Any chat plugin currently installed? (Yes/No — if yes, name it; we coordinate)
- Hours of operation (chatbot can be 24/7 or you can set "off hours" auto-replies)
- Anything to AVOID in the chatbot's tone or content

**C-11. AI Business Automation**
- Which engagement model? (Quick Win / Department Build / Retainer)
- The one workflow you most want automated (1-3 sentences)
- Tools currently involved in this workflow (CRM, email, spreadsheet, etc. — list them)
- Volume of the workflow (e.g., "200 emails/day," "50 leads/week")
- Who currently does this work (role, hours/week spent)
- What "done" looks like for you
- Compliance considerations (healthcare PHI, financial regulated data, legal privilege — yes/no per category)

- [ ] **Step 5: Commit all ops files**

```bash
git add ops/playbooks/ ops/01-intake-form.md
git commit -m "docs(ops): AI playbooks + intake-form AI sections"
```

---

## Task 10: Launch-readiness check for AI extension

**Files:** (none — verification)

- [ ] **Step 1: AI-specific readiness checklist**

Before mentioning AI packages in any customer-facing channel, confirm:

- [ ] Chatbot platform decision committed (Chatbase / Voiceflow / Intercom Fin / Chatling / custom)
- [ ] Automation platform decision committed (n8n / Make / Zapier / custom)
- [ ] LLM API account active (OpenAI or Anthropic or both) with billing set up
- [ ] Pricing for chatbot platform per-customer-per-month is below 30% of our $497 Starter monthly (target 70%+ gross margin per source doc)
- [ ] One internal pilot chatbot deployed (on btwebgroup.com itself OR a friendly existing client) with real conversation logs before selling externally — per source doc § Decisions Needed Before Launch
- [ ] Industry-specific use-case copy reviewed and signed off by Sanket
- [ ] HIPAA disclaimer reviewed by legal (or at minimum: copy passes Sanket's gut-check)
- [ ] All 3 AI page URLs live and indexed
- [ ] Lead modal context strings (`ai-chatbot-starter`, `ai-chatbot-growth`, etc.) recognized by CRM and routed to correct internal owner

- [ ] **Step 2: Confirm Eblast strategy**

The current 4-email Eblast series (Plan 2) does NOT mention AI Chatbot. Decide:
- **Option A (default):** Launch AI pages alongside the catalog but don't change the eblasts. AI pages get traffic from the catalog only.
- **Option B:** Add Eblast 5 ("Your phone rings at 2am. Now what?") as a follow-up campaign 30+ days after Eblast 4. New plan.
- **Option C:** Modify Eblast 3 ("5K emails. Sent.") to include the Chatbot Quick-Start as a second option. NOT recommended (dilutes Eblast 3's single CTA).

Recommendation: **A** — launch quietly, generate first proof point from catalog clicks, then plan Eblast 5 separately.

- [ ] **Step 3: Final commit + handoff note**

```bash
git add .
git commit -m "ops: AI extension launch-readiness verified"
```

Add a note to `packages-html/README.md`:

```markdown
## AI packages — additional pre-publish steps

Before publishing the AI pages:
1. Confirm chatbot + automation platform decisions
2. Replace any platform-specific copy if needed
3. Deploy one internal pilot chatbot first (proof of concept)
4. HIPAA disclaimer language reviewed
5. CRM webhook recognizes new lead context strings (`ai-chatbot-*`, `ai-automation-*`, `tripwire-ai-chatbot-quick-start`)
```

---

## Out of Scope for This Plan

- **AI Voice Agent** — deferred. Add in a follow-up addendum after Chatbot is live and we have 2+ case studies.
- **Custom AI Agent** — lives in Custom Software Dev practice.
- **AI Content Engine standalone SKU** — replaced by fold-in to Email/Social/SEO Growth+Pro tiers.
- **Eblast 5 (AI-specific)** — separate follow-up plan.
- **AI demo videos** — separate follow-up.
- **HIPAA-compliant chatbot infrastructure** — not in scope for v1; explicitly excluded in page copy.
- **AI Front Desk Bundle** (Chatbot + Voice) — pending Voice Agent ship.

---

## Success Criteria

- 3 new HTML pages (AI Chatbot hub, AI Business Automation, AI Chatbot Quick-Start tripwire) — paste-ready into Beaver Builder
- Root `/packages` updated with AI cards + filter chip
- FAQ rewritten for dual-context (marketing vs AI) setup-fee answer
- Pillar 3a (Activation transparency) added to AI pages only
- Content Engine volume folded into Email/Social/SEO Growth+Pro tiers — copy updated, no new SKUs created
- 3 new ops playbooks (AI Chatbot, AI Business Automation, AI Chatbot Quick-Start) + intake-form sections C-10 and C-11
- Launch-readiness checklist passes before any AI page goes live