# MBAC Skill 11: Workshop Engine

| | |
|---|---|
| **Version** | v1.0 (2026-07-27) |
| **Workflow** | B, Outreach & Follow-Up |
| **Lead indicator it moves** | Workshop registrations |
| **Process owner** | James Pullins |
| **Built from (Anthropic plugin)** | `marketing:campaign-plan` |
| **Customized by** | MBAC Context Document + this file |

## Trigger

A workshop or event is scheduled (including the Sept 8 Community Day), ideally 4+ weeks out.

## Inputs / Context needed

- Event basics: topic, date, place, who it is for, what attendees walk away with
- The MBAC Context Document
- The prospect + client lists in the connected store (the invite pool)

## Steps

1. Paste the MBAC Context Document, this file, and the event basics into Claude.
2. Ask for the full promotion kit in one pass:
   - A plain-language event description (the "what you walk away with" version, not the flyer-speak version)
   - A 3-touch invite sequence for the prospect list (announce / value + logistics / last call)
   - Two social posts and one newsletter blurb
   - A day-after follow-up for attendees AND a "sorry we missed you" for no-shows, each routing people to the intake landing page
3. Review the kit (human checkpoint), schedule the sends.
4. Registration data flows into the SAME connected store, so every registrant drops into the right sequence automatically: attendees to intake/booking, no-shows to a nudge.
5. After the event, log attendance and hand the list to Skill 01/07 so nobody who showed up goes dark.

## Rules that never bend

- Every workshop ends by routing people to the intake landing page. Workshops are top-of-funnel, not an end in themselves.
- Registrants enter the one connected store, never a separate spreadsheet.

## Human checkpoint (Zone 2)

James reviews the kit; a counselor sanity-checks the walk-away promise ("would I stand behind this in the room?").

## Safety & disclosure

Registration collects the same minimal fields as intake (including the AI-use consent checkbox) so every registrant enters the connected store cleanly. Email is the reminder channel.

## Output & where it lands

Promotion kit sent on schedule; registrations + attendance in the connected store; post-event routing into Workflow A.

## Customization moves (Adopt, Customize, Rename)

1. **Adopt:** Anthropic `marketing:campaign-plan` plugin skill.
2. **Customize:** MBAC's event flow, the route-to-intake rule, the one-store rule.
3. **Rename & anchor:** "MBAC Workshop Engine," anchored to workshop registrations.