Capabilities

A guided path through LinkedIn prospect research

Start with an observable account brief, preserve uncertainty through enrichment, and keep a named reviewer between research and outreach.

Guided LinkedIn prospecting workflow

Four jobs, each with a boundary

01

Resolve the company

Compare operating name, domain, location, and parent relationship before attaching a profile. Shared names and redirected domains remain review cases.

02

Interpret the role

Use function, seniority, current description, and company context. A title alone does not establish responsibility for a buying decision.

03

Check contact status

Keep discovery, verification, and permitted use as separate fields. A found address is not automatically current, deliverable, or appropriate to contact.

04

Prepare context

Draft a concise reason for relevance with cited observations. A person removes unsupported claims and decides whether outreach should proceed.

Questions to answer before scaling

Which source supplies each field?

Document the connected provider, observation date, transformation, fallback order, and whether the value is reported, classified, estimated, or inferred.

What happens when sources disagree?

Preserve alternatives and route the record to review. Do not let a later waterfall source silently erase a better-supported earlier value.

What controls outreach?

Human approval, suppression, opt-out handling, applicable regional rules, platform terms, and SPF, DKIM, and DMARC health remain downstream gates.

Before and after a controlled workflow

Uncontrolled browsing

  • Criteria shift after results appear
  • Sources disappear into notes
  • Unknown fields look blank or complete
  • Research and sending blur together

Reviewable agent workflow

  • Criteria and exclusions written first
  • Evidence and dates travel with claims
  • Unknown is an explicit state
  • Outreach waits for human approval

Run the guide on accounts you already know

Use a small cohort to expose identity errors, stale roles, missing evidence, and unsafe assumptions before connecting any sending workflow.

Include a positive match, an excluded company, a shared company name, a recently changed role, and a record with conflicting contact data. Judge these cases separately. Installation health, data coverage, identity accuracy, contact verification, and outreach relevance are different measures and should not be collapsed into one score.

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