AI sales prospecting · evidence first

Research the account before your agent drafts a word

ZoomInfo turns a company brief into a reviewable prospect record: entity clues, dated observations, open questions, and a clear human approval gate. It does not treat a funding event, title, or web visit as automatic intent.

See a sample result

Agent research result with evidence and review states

Terminalnpx -y @okki-global/okki-go-taroball

Copy → Run → Configure → First result

Method comparison

Two research paths, one acceptance standard

Control	Agent-native workflow	Manual browsing
Brief	Reusable ICP criteria and exclusions	Analyst interprets notes per search
Entity resolution	Domain, name, location, and event clues compared	Usually resolved tab by tab
Evidence	Requested beside each returned claim	Depends on note-taking discipline
Unknown fields	Remain explicitly unresolved	May be omitted or inferred
Review	Required before any downstream outreach	Built in, but rarely standardized

Auditable preview

Inspect the route from task to evidence

Your task

Find North American B2B firms with a recently announced security hiring program. Keep uncertain identity matches visible for review.

SAMPLE

Prospect result

Entity: Example company · identity pending
Observed change: Security role listing · dated source
Fit hypothesis: Requires reviewer confirmation
Disposition: Do not contact automatically

Research worksheets

Prepare the test before connecting data

ICP acceptance sheet

Record required company attributes, acceptable proxies, exclusions, and a freshness window.

Use with the runbook

Entity-resolution checklist

Compare legal name, operating name, domain, headquarters, and dated events before merging.

Read the methodology

Outreach approval record

Capture relevance, contact verification, suppression status, opt-out language, and reviewer decision.

See role-specific use

Installation runbook

Copy, run, configure, first result

01 Copynpx -y @okki-global/okki-go-taroball
Clipboard success is not installation success.
02 Run
Execute in a supported terminal and inspect the package prompt and completion output.
03 Configure
Store connected API credentials in environment secrets with the minimum required scope.
04 First result
Test known companies; check identity, dates, source context, exclusions, and unknown states.

Questions before a first run

What this command does—and does not—establish

Does copying install the skill?

No. Copying changes only your clipboard. Run the command in a supported terminal, inspect the package prompt, then confirm the completion output.

Where should credentials live?

Use a runtime secret store with minimum scope. Never paste API keys into prompts, exports, shared logs, or a test record.

Can a returned contact be emailed automatically?

No. Check identity, freshness, professional relevance, suppression, opt-out handling, and applicable regional requirements first.

What should a first test include?

Use known companies, one exclusion, and one ambiguous identity. Measure evidence quality and correction work rather than assuming a universal match rate.