Use cases
The same company record carries different risks for market selection, CRM enrichment, account preparation, and workflow engineering. Open each mandate to see its acceptance gate.
Test whether a market thesis produces recognizable accounts without widening criteria after seeing results. Define industry boundaries, company-stage proxies, event recency, geography, and exclusions first.
Acceptance gate: Would the account remain a fit if the funding or hiring event were removed?
Resolve operating identity before enriching routing fields. Preserve source timestamps, transformations, fallback order, conflicts, and an explicit unknown state when providers disagree.
Acceptance gate: Can an operator explain which source changed each CRM field and reverse it?
Prepare concise briefs containing dated company events, role rationale, operational context, and open questions. Keep discovery separate from drafting, approval, and sending.
Acceptance gate: Can a representative distinguish public fact, inference, and unsupported personalization?
Inspect package behavior, secret storage, data permissions, rate limits, retries, output schema, retention, and deletion in a test environment with a known cohort.
Acceptance gate: Can the workflow fail safely without leaking a credential or silently accepting a weak match?
Run a small known cohort, record exceptions, and expand only after the reviewer can reproduce each decision.
npx -y @okki-global/okki-go-taroball