Research method

Clearbit separates a useful match from a plausible guess

Follow a traceable path from ICP criteria to a reviewed account record. This page compares operating methods, previews a sample output, records data behavior, and ends with a controlled installation run.

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

Use a small, representative cohort for the first test.

Layered prospect research method diagram

Checked 20 July 2026

Compare the operating model

This table evaluates methods, not unverifiable performance claims. “Unknown” means public evidence was not sufficient for a conclusion.

DimensionAgent-native researchSeat SaaSManual research
Setup pathInstall in the working agentProvision a separate workspaceDefine a manual checklist
Task modelNatural-language brief with structured outputSaved filters and platform workflowsAnalyst interpretation
Source disclosureRequested per field and taskVaries by providerDepends on analyst notes
Human reviewExplicit gate before outreachConfiguration-dependentInherent but inconsistent
ExportRuntime and destination dependentPlan and integration dependentSpreadsheet or CRM entry
Cost modelRuntime and connected data costsOften seat or credit basedAnalyst time
Security disclosureInspect package and connected permissionsReview vendor documentationReview local handling process

Sample—not a customer record

Read the result from task to evidence

SAMPLE

Candidate account

Northstar Systems
Identity: unresolved sample
Fit: provisional

  • Industry criterion: appears aligned
  • Hiring signal: requires recency check
  • Buying role: RevOps leader to verify

Data behavior ledger

Questions to answer before connecting a source

Data sources

Config-dependent Record which connected source supports each output and whether its terms permit the intended use.

API keys

Verified practice Store credentials in environment secrets; never include them in prompts or export files.

Runtime behavior

Inspect locally Review package output, requested permissions, and network connections in your environment.

Retention and deletion

Config-dependent Document destination retention, access controls, and deletion steps before production use.

Controlled first run

Install with a test plan already written

  1. 01

    Copy

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

    The clipboard state is the only success signal at this stage.

  2. 02

    Run

    Execute in a supported terminal and inspect package prompts.

  3. 03

    Configure

    Connect the minimum source permissions required for your trial.

  4. 04

    First result

    Audit identity, freshness, provenance, and exclusions on a small sample.