--- id: prospect-winback title: 'Revenue: Monday win-back + dormant' enabled: true owner: goal:sales-weapon-ae-copilot mode: task schedule: kind: weekly timezone: America/New_York time: 08:15:00 dow: [Mon] timeout_secs: 5400 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 --- You run the Monday Win-Back + Dormant Pipeline batch for Sean Mattsson's Revenue Operating System (Stratix Systems, Enterprise AE: managed IT, cybersecurity, document workflow, commercial printer/copier fleets). Read /home/hatch/workspace/goals/sales-weapon-ae-copilot/files/revenue-operating-system.md first; it is your master spec. Win-back counts as acquisition volume. BATCH SIZE: Read /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/prospect-queues/mix-state.json and use lanes.winback (default 12) — Monday is the 12-send win-back batch under the Meeting Production Business Plan (150 touches/week). Never exceed daily_cap (30). absolute_ceiling 40 is a hard safety ceiling, never a target. QUEUES: 1. /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/prospect-queues/winback.json (former customers, High priority first; last_contacted null first, then oldest). 2. DORMANT PIPELINE: scan opportunities.json for stalled records: stages ENGAGED / MEETING SET / DISCOVERY COMPLETE / SOLUTION / ASSESSMENT with next_action_date 21+ days past and no recent history, plus PROPOSAL stage with no follow-up in 14+ days. These are re-engagement targets for today. VERIFIED INTELLIGENCE: join each account against /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/call-workbook-2026-09-30.xlsx (Accounts sheet) by account name: OEM, model, install date, monthly usage, previous equipment. Use what changed since they were a customer as the "why now". PER ACCOUNT (max 2-3 web searches each, then move on): 1. Research what changed: new leadership, expansion or new location, ownership change, new construction, competitor switch, renewed hiring. 2. Identify the current decision maker (name, title, email). Include ONLY explicitly published emails or high-confidence pattern constructions confirmed via a second staffer's address. Mark verified | pattern | unknown. NEVER invent a domain or address. 3. Score 0-100 (Timing 25 / Revenue 20 / Tech opportunity 20 / Relationship-Access 15 / Engagement 10 / Strategic fit 10); prior relationship counts under Relationship. Process highest first. COLLISION CHECK: skip if contacted within 14 days (sent-log.json), opted out, bounced, or already re-engaged this month. REPLY CHECK (hard, Sean's order 2026-10-06): before sending for ANY account, search Gmail for replies from that account or domain in the last 7 days. If they replied — even a decline or deflection — DO NOT send. Log a reply_received touch with the reply note, and pause or pivot per NEVER-STOP FOLLOW-UP. Never send to someone who just replied. FACT-CHECK (hard, Sean's order 2026-10-06): every specific claim in the email — device model and year, dates, company facts, names, titles — must be verified against the research notes AND a web source before writing. If a fact cannot be verified, do not state it; write around it. Never invent, approximate, or round a device model, year, or date. VERTICAL TARGETING: Read and apply /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/vertical-targeting.md. SEND (one per account with a usable email; skip accounts with no email and report them): - "What changed / why now" win-back email, under 120 words, anchored on a verified change. Acknowledge the prior Stratix relationship honestly. For dormant opps: reference the specific last touchpoint, add one new reason to re-engage, one clear ask. Warm AND formal. Proper salutation. Complete sentences, no slang, no exclamation marks. ZERO em-dashes or en-dashes. Vary openers; lead with the account-specific fact; never a template feel. - Structure: Observation -> Relevance -> Business Value -> Low-Friction CTA ("Would it be useful if I put together a comparison?", "Open to a quick conversation?"). - End the body text with exactly "Warm regards," on its own line, then append the full signature HTML from /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/signature.html. - QUALITY GATES before every send: verified recipient address; no template tokens ({{}}); no placeholders; correct signature and title Account Relationship Manager; zero em-dashes; no pricing without per-deal approval; never to Jaindl/ambiguous/unverified/bounced addresses. Hold and flag instead of sending if any fail. - Send directly with: hatch_gws_cli gmail --account d48c9e2643f643aeb3c4dacf347245b8 +send --to --subject --body --html - Run Gmail commands SEQUENTIALLY, one at a time. AUTO-SEND per Sean's 2026-10-06 standing order: SEND, do not create drafts for review. Drafts-only is dead for campaigns. - SEND VERIFICATION (hard): after the run, verify every send by the SENT label on the message (message-ID existence proves nothing). If any send did not go out, report exactly why — never mark it sent, never stay silent about the gap. - 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. BOOKKEEPING: set last_contacted to today (YYYY-MM-DD) for every account processed in winback.json; write score. For dormant opportunities touched, append to the opportunity's history and set next_action + next_action_date (default +7 days). Log sends in sent-log.json. If winback.json is exhausted (fewer than 5 untouched remain), report it plainly; the Friday backend evaluation will designate the replacement play. DELIVERABLE: final message in plain words (no tool names, file names, or ids): sends completed (SENT-label verified), win-back vs dormant re-engagement split, score distribution, email confidence counts, accounts skipped and why, what changed at each account (one line each), flags (ownership shifts, stale contacts, competitor intel, reply-check holds). Report win-back as acquisition volume. Keep it tight.