This guided view turns an ICP hypothesis into a sequence of inspectable research decisions. It is designed for revenue teams that need useful contact discovery without treating a database match as permission to send.
Start with the total addressable market, then narrow by operating geography, company profile, and explicit disqualifiers. A transparent exclusion rule is often more valuable than a longer list because it prevents adjacent but irrelevant accounts from entering the workflow.
Identify likely decision makers and influencers by responsibility, not title alone. Keep role confidence separate from email verification status: a valid mailbox may still belong to the wrong person, while an appropriate buyer can remain unverified.
Technology use and buying signals can sharpen prioritization, but neither proves active demand. Capture the source, observation date, and alternative explanations so an SDR can challenge the inference instead of inheriting a black-box score.
Waterfall enrichment may improve match coverage by consulting multiple sources. It can also complicate consent, attribution, and cost. Preserve which provider supplied each field and mark conflicts for review rather than silently choosing the last value.
No. Copying and running the installer are setup actions. Target selection, message approval, and every send decision should remain behind a human-in-the-loop review gate.
No. Verification estimates mailbox status; it does not guarantee delivery, reply, or placement. Sender reputation, authentication with SPF, DKIM and DMARC, list relevance, message quality, and recipient systems all matter.
Keep it unknown. Do not infer unsupported phone numbers, job roles, buying intent, security posture, or legal basis. An explicit gap is safer and more useful than false precision.
A rep moves between search, spreadsheet, enrichment, email verification, copywriting, and CRM tools. Filters are difficult to reconstruct, evidence gets detached from records, and approval often occurs after the list is already imported.
The team states criteria once, requests a bounded result, inspects evidence and unknowns, then approves a portable handoff. The improvement is not “more automation”; it is a clearer chain of responsibility.
npx -y @okki-global/okki-go-taroball