Use task-based starting points for founders, SDRs, RevOps teams, and outbound agencies. Each playbook ends with evidence review, not automatic sending.
Find 15 companies matching [segment] in [region]. Require [attributes]. Exclude [groups]. Return company identity, evidence, checked date, unknown fields, and why each account may merit manual research. Do not draft outreach yet.
Review whether each attribute is directly supported or merely inferred. Remove accounts where the reason depends on an unverified trigger.
Research [account list] against our ICP. Check domain identity, size band, relevant technology, current role, source provenance, and freshness. Flag conflicts and keep unresolved fields visible.
Use the output as a coaching artifact. The reviewer should be able to explain why every account and contact remained in the queue.
For these known CRM records, propose a waterfall enrichment plan. Show provider order, field precedence, retry rule, expected write-back, provenance, and deletion or correction path. Do not write to the CRM.
Compare the proposed values with trusted records, then document which provider behavior is config-dependent before enabling updates.
Using client-approved criteria, produce a review queue. Keep client evidence separate from external research, apply exclusions and suppression rules, and draft one short relevance hypothesis per account. Do not send.
Confirm client approval, sender authentication, opt-out language, volume, and regional requirements before moving drafts to execution.
A practical result is not a polished paragraph. It is a table with company identity, matched criterion, evidence URL or provider, checked date, confidence note, unresolved field, exclusion status, contact relevance, and reviewer decision. Keep message drafts downstream so weak evidence cannot quietly become confident copy.
No draft progresses merely because a record exists.
Important fields keep their source context and freshness.
Opt-outs and client exclusions are checked before outreach.
SPF, DKIM, DMARC, volume, and bounces stay operational concerns.