Prospecting workflow

OKKI Go structures research before outreach begins

Give your agent a bounded ICP brief. OKKI Go helps organize company discovery, contact context, evidence checks, and an approval-ready output without turning a research request into an automatic send action.

Inspect the result model
npx -y @okki-global/okki-go-taroball
  1. Scope the brief
  2. Research candidate accounts
  3. Review evidence and gaps
  4. Approve the export
Copying is not installation. Run and configure the skill in your own environment.

Task-based capabilities

Four jobs, each with an explicit input and output

Capability boundaries make the workflow easier to evaluate. They also show where your data providers, review standards, and regional obligations still matter.

01

Find companies

Input
ICP attributes, exclusions, territory, and a business trigger.
Agent action
Translate the brief into firmographic and technographic research criteria.
Output
A candidate account table with match reasons and unresolved fields.

Limit: coverage and recency depend on configured sources.

02

Develop contact context

Input
Approved accounts, target functions, seniority, and decision context.
Agent action
Organize available role, company, and professional contact evidence.
Output
A review queue, not a guaranteed or automatically actionable address list.

Limit: verify freshness, lawful basis, and provider terms.

03

Prepare relevance notes

Input
Business hypothesis, account evidence, and approved messaging boundaries.
Agent action
Summarize why a company may fit without inventing private facts.
Output
Concise research context for a human-written or human-approved next step.

Limit: a relevant note does not guarantee interest or response.

04

Build the review packet

Input
Candidate results, source context, confidence cues, and policy checks.
Agent action
Separate accepted, rejected, and unresolved items with reviewer notes.
Output
A controlled export set for your CRM, spreadsheet, or downstream process.

Limit: downstream writes require your chosen integration and permissions.

Auditable preview

Keep the question beside the answer

The preview below is an illustrative schema. It is marked SAMPLE and does not represent a real customer, verified provider, or performance claim.

SAMPLE

Candidate result

Northstar SystemsReviewFit reason: workflow and role evidence align; trigger requires confirmation.
Clearpath LabsHoldFit reason: segment matches; target-role evidence remains incomplete.
Harborline DataRejectExclusion reason: service model conflicts with the supplied brief.

Operating controls

Define the rules before scaling the task

OKKI Go can sit inside a broader data and outreach stack. Your team remains responsible for selecting providers, limiting credentials, documenting retention, and deciding whether a researched record can move into another system.

Config-dependent

Source selection

Record which provider or public source supplied each important field and how source conflicts are resolved.

Config-dependent

Credential scope

Use separate, least-privilege API keys where providers allow it, and rotate them through your secret-management process.

Verify locally

Runtime logging

Inspect what the chosen agent runtime stores in logs, histories, caches, and generated files before using production data.

Config-dependent

Export approval

Require a named review state before an item enters a CRM, outreach tool, shared document, or customer workspace.

Start with a narrow brief

Install OKKI Go, then validate the workflow in four states

Copy: put the exact command in your clipboard. Run: execute it in a terminal you control. Configure: add only required connections and scoped secrets. First result: test a small brief and have a person explain every retained item.

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

After copying, you still need to run, configure, and review.