Outbound personalized email at scale

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. recipient_data_source

   REQUIREDREADrequest

   Where the pattern gets facts about each recipient. Without rich recipient data, personalization is fake and the value evaporates.

   DATA SHAPE

   Recipient records: name, role, company, recent activity (job change, funding, product release), account state if existing customer.
   COMMONLY FILLED BY

   • CRM with enriched contact records
   • data enrichment service feeding the CRM
   • internal database with customer activity
   • imported list with structured fields
2. sender_intent_input

   REQUIREDREADhuman

   What this email is trying to do. The sender provides the goal; the pattern produces the words.

   DATA SHAPE

   Structured intent: campaign or trigger, target recipient group, key message, desired CTA, sender persona to write as.
   COMMONLY FILLED BY

   • sales user starts a personalized outreach campaign with stated goal
   • customer success setting up a milestone-triggered email
   • marketer launching a personalized announcement
3. draft_review_surface

   REQUIREDREAD + WRITErequest

   Where humans approve, edit, or reject drafts before send. Non-optional: this pattern only operates with a human in the loop.

   DATA SHAPE

   Draft email with recipient context shown alongside, edit field, approve/reject/edit-and-approve actions.
   COMMONLY FILLED BY

   • review queue inside the sales tool
   • draft folder in the sender's email client
   • dedicated review UI built for the engagement
4. email_send_channel

   REQUIREDWRITErequest

   How the approved email actually reaches the recipient. Critically: the email must look like it came from the human sender, not a marketing automation account.

   DATA SHAPE

   Approved email content, recipient address, sender mailbox identity, optional tracking pixels (only with consent).
   COMMONLY FILLED BY

   • the sender's actual email account via authorized API
   • transactional email service configured to use the sender's domain
   • outbound from the CRM under the sender's identity
5. response_tracking_loop

   RECOMMENDEDREADevent

   Where replies and engagement signals come back so the pattern (and the sender) know what worked. Critical for tuning over time.

   DATA SHAPE

   Reply events, open events (where available and consented), bounce events, unsubscribe events. Per-email and aggregated.
   IF MISSING

   Pattern still sends but can't learn what works. Sender flies blind on which framings resonate; quality degrades over time.
   COMMONLY FILLED BY

   • reply detection in the sender's inbox
   • email tracking module in the CRM
   • transactional email service event stream
6. suppression_list

   REQUIREDREADrequest

   Recipients who should not receive outbound. Includes unsubscribes, current customers under freeze, anyone in a regulated jurisdiction without consent.

   DATA SHAPE

   List of email addresses, domains, or recipient IDs flagged do-not-contact, with reason and date.
   COMMONLY FILLED BY

   • suppression list in the CRM
   • unsubscribe list in the email service
   • compliance list maintained by legal or RevOps