--- id: cybersecurity-campaign title: Cybersecurity campaign (Wed) enabled: true owner: goal:sales-weapon-ae-copilot mode: task schedule: kind: weekly timezone: America/New_York time: 09:00:00 dow: [Wed] delivery: - chat_id: ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b metadata: originating_chat_context_json: '{"chat_id":"d2262570-9e80-4954-824e-cbddf1cc3835","origin_provider":"main","chat_kind":"direct","event_kind":"message","require_mention":false,"device_id":"11d6f508-35e2-48ec-9e92-39b4972d1a29"}' presentation_locale: en-US --- Cybersecurity Awareness Month campaign for Sean Mattsson (October 2026, Wednesday 9:00am ET). October is Cybersecurity Awareness Month — a natural hook for cyber/IT outreach to the VERIFIED OPPORTUNITY CALL LIST and net-new accounts. AUTO-SEND (Sean's standing order 2026-10-06): campaign emails SEND directly — no drafts awaiting review. Drafts-only is dead for campaigns. FOLLOW-UP PHILOSOPHY (Sean's standing order 2026-10-06, his words: "1 email is not the end its the process that counts sometimes it take 17 emails spread out to get through to someone"): follow-up is the campaign, not an afterthought. Touches NEVER end for non-response — they pivot. Every touch must bring a FRESH angle (new intel via Tavily, new seasonal hook, new value prop, new contact, new channel). Never repeat the same message. Never send a "breakup" or terminal touch. Never mark closed-lost for non-response. The sequence only pauses when they reply or buy. The November 3 follow-up pass keeps the engine running on whatever got attention in October — the campaign evolves, it never terminates. TARGET: ~/workspace/goals/sales-weapon-ae-copilot/hidden_files/campaign-opportunity-list.json. Cyber-relevant angles: municipal (police depts, townships — ransomware risk), healthcare (HIPAA), education (student data), nonprofits. TARGET RULES (hard): - ONLY accounts with emailable=true for email touches. - NEVER email ambiguous/unverified accounts until Sean confirms them. - NEVER email Jaindl Farms (DO NOT CONTACT). - Coordinate with opp-followup-campaign: check the To Do List and account touches[] to avoid emailing the same account twice in 3 days. PERSONALIZATION (Tavily, 2026-10-05+): - Before sending for an account, run the personalization module: `~/workspace/goals/sales-weapon-ae-copilot/hidden_files/personalize.py "" --vertical --location "" --mode news` (Vertical and location come from the campaign JSON entry; default vertical=business, location="".) - Results are cached 7 days — repeat accounts cost nothing extra. - Weave ONE fresh intel point into the email opener where it fits naturally: a recent expansion, leadership change, funding award, or tech initiative. NEVER invent intel — use only what Tavily returned with a source URL. If Tavily returns nothing useful, fall back to the CRM-based opener without forcing it. - CITATION (Sean's standing order 2026-10-06, refined same day): cite the AI model in EVERY chat report to Sean where a model sourced the work — e.g. "angle via Tavily". One parenthetical per line. Chat responses ONLY: never in customer-facing copy (emails, proposals, attachments), never in saved documents/files — record the source fact there without the model tag. QUALITY GATES (check before every send — hold and flag instead of sending if any fail): - Verified recipient address; no template tokens; no placeholders; correct signature and title Account Relationship Manager; zero em-dashes/en-dashes; no pricing/margins/costs without Sean's per-deal approval; never to Jaindl/ambiguous/unverified/bounced addresses. STANDING EMAIL RULES (see MEMORY.md): from sean@seanmattsson.com only; full Stratix signature; title Account Relationship Manager; zero em-dashes/en-dashes; warm and formal, under 120 words. - PRE MEETING FORM (Sean's standing rule 2026-10-05): whenever an email asks a contact to complete the form, call it exactly "Pre Meeting Form" (never "Stratix Pre Meeting IT Form" or variants) AND always attach the PDF at ~/workspace/goals/sales-weapon-ae-copilot/hidden_files/pre-meeting-form.pdf. - PRICING (hard): customers never see pricing, margins, costs, or internal/sensitive info without Sean's explicit per-deal approval. MESSAGING (October): - Hook: Cybersecurity Awareness Month. Angle ideas: ransomware hitting local orgs, backup that was never tested, phishing training, HIPAA/compliance gaps, "when was your last security review?" - Rotate angles across touches — the same account should never get the same hook twice. Check touches[] for which angles were already used and pick a new one. NEVER repeat the same message. - From November 3: the campaign evolves. Shift the hook to year-end: budget-flush, Section 179, "lock in before the holidays," Q1 planning. The engine keeps running — it never terminates for non-response. EACH RUN: 1. Read campaign-opportunity-list.json. For each emailable cyber-relevant account, determine follow-up status: - Check Gmail for replies since the last outbound touch. - A touch is DUE if: 3+ days since last touch AND no reply received. No maximum touch count — the sequence continues with fresh angles per the FOLLOW-UP PHILOSOPHY. - First-touch accounts with no touches yet are due immediately (max 5 new first-touches per run). - SKIP if: a reply is awaiting Sean's action, another cron already has a touch scheduled within 2 days, or today is a holiday blackout (Nov 25-29, Dec 24-Jan 1). 2. Per-run target: 12 sends under the Meeting Production Business Plan (Wednesdays only). For each due account: run personalize.py (news mode), then SEND one contextual follow-up with a FRESH angle: - Open with Tavily intel where one exists; otherwise reference the specific CRM opportunity, stage, and last interaction. - Weave in the Awareness Month hook (Oct) or year-end hook (Nov+). - One clear call to action. Thread as a reply where a thread exists. - Send with: hatch_gws_cli gmail --account d48c9e2643f643aeb3c4dacf347245b8 +send --to --subject --body --html (or +reply --message-id for threads) 3. REPORTING (urgent-only, Sean's order 2026-10-05): stay SILENT on routine runs. Post in the Work chat ONLY when: (a) a reply needs Sean's action, (b) a send failed or bounced, (c) a high-value opp ($10K+) needs his decision. When reporting, cite the model per the CITATION rule. 4. Log every sent touch in the account's touches[] with date, type "sent", and the angle used (so future runs pivot, never repeat). 5. Append a one-line note to ~/memory/YYYY-MM-DD.md (ET date): how many sent, for which accounts. RESULTS FOCUS: every touch must move the account forward. The process is the campaign: keep showing up with something new until they reply or buy.