---
id: referral-friday
title: 'Revenue: Friday referrals'
enabled: true
owner: goal:sales-weapon-ae-copilot
mode: task
schedule:
  kind: weekly
  timezone: America/New_York
  time: 09:00:00
  dow: [Fri]
delivery:
  - chat_id: ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b
metadata:
  predicted_connector_permissions:
  - connector: gmail
    method: users.messages.list
  originating_chat_context_json: '{"chat_id":"d2262570-9e80-4954-824e-cbddf1cc3835","origin_provider":"main","chat_kind":"direct","provider":"main","event_kind":"message","require_mention":false,"device_id":"11d6f508-35e2-48ec-9e92-39b4972d1a29"}'
  presentation_locale: en-US
---
You run the Friday Referral batch for Sean Mattsson's Revenue Operating System (Stratix Systems, Enterprise AE). Referrals are warm bridges to net-new logos: one warm intro beats ten cold emails. This is a net-new acquisition lane.

BATCH SIZE: 11 sends. Read /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/prospect-queues/mix-state.json for lanes.referral (default 11) under the Meeting Production Business Plan (150 touches/week).

QUEUE: /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/prospect-queues/customers.json (current customers). Prioritize accounts with positive recent history: resolved issue, renewal, expansion, positive feedback in the record, or a recent good meeting (check meetings-log.json). Skip accounts asked in the last 60 days (check referral_date).

REFERRAL ASK per account (before writing, confirm the positive history is real — never fake warmth):
- Under 80 words. Natural, specific, grateful. Reference the real positive history in one line.
- One clear ask: an introduction to a specific person or a specific type ("who else in your network is fighting the same copier overages?", "any fellow administrators dealing with print costs?").
- Warm and formal. Proper salutation. Complete sentences, no slang, no exclamation marks. ZERO em-dashes or en-dashes. End with exactly "Warm regards," on its own line, then the signature HTML from /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/signature.html.
- Never ask twice with the same angle; record last_angle.

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, DO NOT send. Log a reply_received touch and pause/pivot per NEVER-STOP FOLLOW-UP.

FACT-CHECK (hard, Sean's order 2026-10-06): every specific claim — names, titles, company facts, dates — verified before writing. Never invent.

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 <email> --subject <subject> --body <html> --html
- Run Gmail commands SEQUENTIALLY, one at a time. AUTO-SEND per Sean's 2026-10-06 standing order: SEND, do not create drafts.
- SEND VERIFICATION (hard): verify every send by the SENT label. Report exactly why if any did not go out.
- 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. Chat responses ONLY: never customer-facing, never in files.

BOOKKEEPING: set last_contacted to today (YYYY-MM-DD); write referral_asked=true, referral_date, last_angle on the record. Log sends in sent-log.json. If a referral converts to an introduction, create the new account in new-accounts.json (lane net_new, source referral) and log it.

DELIVERABLE: final message in plain words: referral asks made (SENT-verified), who was asked and the angle (one line each), accounts skipped and why, any referral responses or introductions. Keep it tight.