Research specification

Dux-Soup turns profile activity into testable research questions

Funding rounds, acquisitions, executive appointments, and hiring signals create useful hypotheses. They do not prove budget, urgency, or fit. This methodology keeps each observation attached to a date and asks a reviewer to accept or reject the inference.

LinkedIn prospect event research method

Structured research specification

Company discovery

Input
Industry thesis, geography, size proxy, event window, exclusions.
Output
Candidate domains with match rationale and unresolved fields.
Boundary
Classification and headcount estimates can differ by source.

Event analysis

Input
Funding, acquisition, leadership, or hiring event type.
Output
Dated event context and a separate relevance hypothesis.
Boundary
An event is not equivalent to buying intent.

Decision-maker research

Input
Buying function, seniority, responsibility clues.
Output
Role candidates with verification status and evidence.
Boundary
Titles vary; responsibility must be reviewed.

Outreach preparation

Input
Approved account evidence and message constraints.
Output
A restrained draft for human editing.
Boundary
No automatic sending or response guarantee.

Numbered methodology

  1. Write observable criteria.

    Replace “promising startup” with industry, operating region, company stage proxy, dated change signal, and disqualifiers.

  2. Resolve the entity.

    Compare legal name, operating name, website domain, location, and event participants before combining records.

  3. Separate fact from inference.

    Store the source-supported event independently from the commercial interpretation your team wants to test.

  4. Review the smallest cohort.

    Measure false positives, unresolved fields, source freshness, review time, and downstream correction work.

  5. Approve outreach separately.

    Verify professional contact data, suppression status, applicable regional rules, and human-edited relevance.

Run the method on accounts you already know

A known cohort reveals whether identity, event timing, and role interpretation meet your internal acceptance policy.

Score each candidate against a written rubric: correct entity, event inside the stated window, source available, required role supported, exclusions respected, and reviewer decision recorded. Report unresolved fields separately from rejected matches so coverage gaps do not disappear inside a single accuracy percentage.

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