BEFORE

Disconnected prospecting tabs hide the operating model

Search, enrichment, drafting, and exports often live in separate interfaces, leaving provenance and approval decisions difficult to reconstruct.

WITH AN AGENT CONTRACT

One task can preserve inputs, evidence, review gates, and outputs

The runtime still needs explicit connectors, scoped credentials, observable calls, and human authorization. Agent-native does not mean permissionless.

Before and after view of fragmented tools and an agent workflow graph

Estimate integration effort by responsibility

This interactive-calculator layout is an evaluation worksheet, not a performance claim. Score each responsibility in your environment before production access.

Confirm Node and npx support, package policy, execution boundary, logging, updates, and uninstall behavior.

Count source APIs, browser sessions, enrichment providers, rate limits, terms, and provenance requirements.

Map CRM writes, files, retention, deduplication, deletion, and downstream access controls.

Separate targeting, contact selection, drafting, suppression, channel choice, and sending permissions.

A larger score means more review work, not a better or worse architecture. Validate package behavior and connector support directly in the intended runtime.

Architecture patterns to test

Research-only agent

The agent reads approved public or provider data and returns a structured shortlist. A person reviews evidence and exports selected records. This pattern minimizes write permissions and is a sensible first-run boundary.

Credential scope: read only · External action: none

Enrichment orchestrator

The agent queries multiple configured providers, preserves field-level provenance, resolves conflicts under declared rules, and proposes CRM updates for approval. Waterfall coverage must be weighed against cost and deletion complexity.

Credential scope: provider reads · CRM write: reviewed

Drafting assistant

The agent uses approved evidence to prepare relevant outreach. A human verifies the claim, audience, regional obligations, suppression, and tone. Sending remains outside the initial permission set.

Credential scope: approved context · Send: disabled

Replace assumptions with a controlled runtime test

Copying only places the command on your clipboard. Read the package prompts before you run, configure, or request a first result.

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