How it works
Move from a bounded ICP to sourced context, reviewed drafts, and explicitly authorized action. Each stage exposes uncertainty instead of hiding it behind activity volume.
Define firmographic and technographic criteria, geography, exclusions, purpose, and acceptable sources. The output should show why an account fits and when each public signal was checked. A likely role is not a verified identity, and visible activity is not proof of private buying intent.
Draft a concise connection note and follow-up from context a recipient would reasonably recognize. Avoid sensitive inference, fabricated familiarity, and generic praise. Check suppression, regional obligations, current platform terms, sender authentication, and whether LinkedIn, email, or CRM actions require different permissions.
Make target, text, channel, timing, export, and send separate decisions. A reviewer can approve, revise, reject, or pause each record. Record sent, delivered, replied, and opted-out states independently; none guarantees pipeline, account safety, deliverability, or legal compliance.
Name the audience, business question, evidence threshold, prohibited sources, and owner. A narrow brief is easier to falsify and safer to review than “find everyone.”
Collect account and person context with provenance, retrieval timing, and confidence. Preserve unknown values and conflicting evidence for human resolution.
Create channel-appropriate text without sending. Review relevance, tone, pacing, suppression, opt-out, SPF/DKIM/DMARC readiness for email, and platform-policy risk.
Let the responsible operator decide whether any external action is permitted. If a connector, source, policy, identity, or region changes, return the record to review.
Copying changes only your clipboard. Inspect the package, run it in an approved environment, configure narrow permissions, and review a small first result before exports or external action.
npx -y @okki-global/okki-go-taroball