Use cases
Set the approved audience, Gmail sending policy, business purpose, suppression rules, and review threshold before drafting. Judge sequence readiness separately from projected pipeline.
Acceptance question: Can leadership explain who may receive the sequence, why it is relevant, and who approves release?
Control recipient sources, address verification timestamps, field mappings, suppression lists, reply states, and CRM exports. Preserve an explicit unknown state when connected systems disagree.
Acceptance question: Can an operator explain which source changed each CRM field and reverse it?
Review subjects, merge fields, claims, follow-up spacing, unsubscribe language, and mailbox load. Keep generation, approval, launch, and reply handling as separate states.
Acceptance question: Can a representative distinguish fact, inference, and an unsupported personalization claim?
Evaluate package behavior, Gmail authorization scope, secret storage, sending limits, retries, export schema, retention, and deletion. Begin with an internal seed list.
Acceptance question: Can the workflow fail safely without leaking a credential or silently accepting a weak match?
| Requirement | Leadership research | RevOps enrichment | SDR preparation | GTM engineering |
|---|---|---|---|---|
| Recipient verification | Review sample | Hard gate | Required | Schema test |
| Verification recency | Defined window | Stored timestamp | Visible in brief | Expiry rule |
| Provenance | Decision support | Field-level | Claim-level | Logged source |
| Human review | ICP approval | Exception queue | Before send | Release gate |
| Compliance | Market policy | Retention controls | Suppression and opt-out | Secrets and deletion |
Higher send volume can expand reach while increasing bounce, complaint, and sender-reputation risk. Gmail-native operation can simplify drafting while still requiring account permissions, rate-limit awareness, SPF/DKIM/DMARC checks, suppression handling, and human review. The appropriate sequence depends on audience relevance and mailbox health, not a universal daily-send claim.
Install the workflow and judge a small result against the acceptance question for your role.
npx -y @okki-global/okki-go-taroball