Agent-native outbound infrastructure

Turn a sales question into a review-ready prospecting run

Amplemarket coordinates account discovery, contact verification, enrichment context, and draft outreach without forcing your GTM team into another seat-based workspace. Install the skill, state the ICP in natural language, and keep every send decision behind a human review gate.

npx -y @okki-global/okki-go-taroball
Copying is step one. Run and configure the command in your supported agent to begin.
Agent canvas turning an ICP brief into an auditable prospect list
Prospecting agent evidence workspace
One connected research loop

Move from ICP to evidence without losing the reasoning

Find accounts by operating context

Describe market, headcount, geography, and technographic signals in plain English instead of assembling a brittle filter stack.

Resolve the buying committee

Map relevant roles and verify business contact paths while preserving source and freshness notes for review.

Enrich through explicit steps

Use waterfall enrichment when configured, and show which source supplied each field rather than hiding provenance.

Draft, review, then decide

Prepare relevant outreach with SPF, DKIM, DMARC, unsubscribe, and regional obligations in mind; no message is represented as sent automatically.

Prompt to result

Three GTM tasks, each with a visible review gate

For SDR leaders

Build a territory-ready account set

  1. Brief: define firmographic and technographic fit.
  2. Agent actions: discover, enrich, and deduplicate.
  3. Review gate: approve exclusions and contact roles.
  4. Output: a structured list with evidence notes.
For founders

Research a narrow early market

  1. Brief: describe the customer problem and region.
  2. Agent actions: identify companies and likely owners.
  3. Review gate: check relevance before drafting.
  4. Output: prioritized prospects and message angles.
For RevOps

Audit enrichment gaps

  1. Brief: identify missing CRM fields.
  2. Agent actions: compare configured data paths.
  3. Review gate: validate provenance and mappings.
  4. Output: an import-ready correction set.
Auditable preview

See the task, candidate record, and supporting evidence together

SAMPLE

Prospect result

Northstar SystemsIllustrative company · 52 employeesSignal: RevOps role published
Candidate roleFounder / VP SalesEmail status: requires configured verification
Installation runbook

Four distinct states from clipboard to first result

  1. 1. Copy

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

    Success: the exact command is in your clipboard; nothing has been installed yet.

  2. 2. Run

    Paste the command into a terminal with Node.js and npm access. Review the package name before execution. A successful run displays setup guidance rather than silently sending data.

  3. 3. Configure

    Add only the provider credentials and destinations your workflow needs. Keep API keys in your runtime secret store, confirm scopes, and test permissions with non-sensitive sample data.

  4. 4. First result

    Ask for a narrow ICP search, inspect source notes and verification status, then approve or reject the record. Outreach remains under human control.

Install FAQ

Know what happens before you run anything

It invokes the named npm installer, which guides agent-skill setup. Review terminal output and package metadata in your environment before granting credentials.

No. Copy, run, configure, and first result are separate states. Copying only places the command on your clipboard.

Use your agent runtime's secret management, grant minimum scopes, rotate exposed keys, and never paste credentials into prospecting prompts or exported lists.

This site describes a human-in-the-loop workflow. Teams should review targeting, relevance, consent basis, unsubscribe handling, and applicable regional requirements before any send.