Use cases
The useful workflow changes with the team’s market knowledge, data boundaries, channel authority, and responsibility for replies and opt-outs.
Test a narrow segment without turning exploration into a mass campaign. Define firmographic and technographic criteria, exclusions, and geography; then collect a small set with public evidence and checked dates. Compare accepted targets, research time, provider cost, and meaningful replies. Keep external action manual while the market thesis changes.
Give representatives an evidence checklist before drafting. Confirm account fit, role, source recency, suppression, and suitable context. Managers set daily pacing, working hours, message limits, escalation, and stop conditions. Profile activity does not prove intent, and personalization never guarantees a reply.
Map sources, runtime, CRM, engagement tools, credentials, exports, logs, retention, and deletion. Prefer documented APIs when available; browser automation can be fragile and harder to govern. Separate research, drafting, approval, export, and sending permissions. Measure overrides, opt-outs, delivery, and account incidents with productivity.
Keep each client’s ICP, credentials, suppression, templates, evidence, and reports isolated. Document client authorization, applicable regions, approved channels, and the named send approver. Reports should distinguish researched, approved, sent, delivered, replied, and opted-out states rather than compressing them into one activity count.
These are operating states, not performance claims. Coverage, match rate, bounce rate, and inbox placement depend on selected sources, configuration, sender infrastructure, market, and measurement method; test them in your own environment.
Copying the command does not run software or authorize outreach.
npx -y @okki-global/okki-go-taroball