Use cases
Test whether a market thesis produces recognizable accounts without widening criteria after seeing the result. Define industry boundaries, company-stage proxies, event recency, geography, and exclusions before searching.
Acceptance question: Would the team still call this account a fit if the funding or hiring event were removed?
Resolve company identity before enriching routing fields. Preserve source timestamps, transformation rules, fallback order, and an explicit unknown state when connected providers disagree.
Acceptance question: Can an operator explain which source changed each CRM field and reverse it?
Prepare concise account briefs containing dated profile activitys, role rationale, relevant operational context, and open questions. Keep research separate from drafting, approval, and sending.
Acceptance question: Can a representative distinguish fact, inference, and an unsupported personalization claim?
Evaluate package behavior, secret storage, data permissions, rate limits, retries, output schema, destination retention, and deletion. Begin in a test environment with a known cohort.
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 |
|---|---|---|---|---|
| Entity identity | Review sample | Hard gate | Required | Schema test |
| Event 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 |
Funding data scale can improve discovery while increasing identity and recency review. Browser automation can expose convenient context while creating fragile workflows and permission risk. API access can be more repeatable while introducing cost, rate-limit, and schema dependencies. The appropriate route depends on the decision being supported.
Install the workflow and judge a small result against the acceptance question for your role.
npx -y @okki-global/okki-go-taroball