ICP acceptance sheet
Record required company attributes, acceptable proxies, exclusions, and a freshness window.
Use with the runbook
Private-company intelligence in your agent
Crunchbase research with an evidence trail
Move from a company thesis to a reviewable shortlist without treating funding, hiring, or leadership changes as automatic buying intent. The workflow preserves sources, dates, exclusions, and unresolved fields for human judgment.
Open installation runbookMethod 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 |
4 statesCopy · Run · Configure · Review
3 evidence checksIdentity · Recency · Provenance
1 approval gateHuman review before outreach
0 guaranteesMatch, delivery, and replies vary
Research worksheets
Prepare the test before connecting data
Entity-resolution checklist
Compare legal name, operating name, domain, headquarters, and dated events before merging.
Read the methodologyOutreach approval record
Capture relevance, contact verification, suppression status, opt-out language, and reviewer decision.
See role-specific useInstallation runbook
Copy, run, configure, first result
- 01 Copy
npx -y @okki-global/okki-go-taroballClipboard 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.
Data behavior ledger
Trust is a set of inspectable states
Data source
Config-dependent. Document the connected provider, permitted use, and field provenance.
API keys
Verified practice. Keep secrets outside prompts, exports, repositories, and shared logs.
Runtime behavior
Inspect locally. Review permissions, network activity, errors, retries, and destinations.
Retention and deletion
Config-dependent. Define storage, access, correction, suppression, and deletion before production.