Cross-Company Talent Flow & Competitor Poaching Intelligence avatar

Cross-Company Talent Flow & Competitor Poaching Intelligence

Pricing

from $10.50 / 1,000 results

Go to Apify Store
Cross-Company Talent Flow & Competitor Poaching Intelligence

Cross-Company Talent Flow & Competitor Poaching Intelligence

Build source-to-destination talent-flow intelligence between competing companies from recurring employee datasets.

Pricing

from $10.50 / 1,000 results

Rating

0.0

(0)

Developer

Rafael Barreto Haddad

Rafael Barreto Haddad

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 hours ago

Last modified

Share

Build source-to-destination talent-flow intelligence between competing companies from recurring employee datasets.

Why use this Actor

Employee datasets show who works where, while competitive strategy needs the direction and concentration of talent moving from one rival to another. This Actor sits above raw extraction: supply a current dataset, optionally add a previous snapshot, and receive an aggregated report built for recurring monitoring and AI-agent workflows.

Key features

  • Explicit source-to-destination competitor flow network.

  • Poaching-cluster detection rather than generic hires/departures.

  • Seniority-weighted talent movement.

  • Cross-company flow actions.

  • Reads inline JSON rows or Apify Dataset IDs with limited READ permission.

  • Writes one auditable report to the default Dataset and INTELLIGENCE_REPORT.

Example

Use the prefilled example or replace currentItems with rows from an upstream Actor. On recurring runs, provide the prior period in previousItems or previousDatasetId. The Actor normalizes common aliases, compares snapshots, ranks the strongest entity changes and emits agentAction.

Use cases

  • competitive intelligence.
  • executive recruiting.
  • workforce strategy.

Pricing

One primary pay-per-event outcome: one decision-ready intelligence report. Base price USD 0.015 before Apify tier discounts. The 256 MB data-first architecture is designed for strong unit economics.

Limitations

  • Analyzes supplied public or appropriately licensed data and does not bypass restricted sources.
  • Scores are decision-support signals, not predictions or guarantees.
  • Keep stable identifiers across snapshots for best change detection.
  • Zero-direct-competition status is rechecked before publication because the Store changes continuously.

Workflow

upstream dataset -> current snapshot -> optional previous snapshot -> normalization -> entity aggregation -> change scoring -> ranked signals -> agentAction.

Input

Provide currentItems as normalized JSON rows or select a cloud Dataset with currentDatasetId. For change analysis, add previousItems or previousDatasetId. The Actor reads Datasets with limited READ permission. Keep identifiers stable across periods and normalize source fields where possible. The prefilled example is intentionally small so the first run can be validated before scaling.

Output

The default Dataset receives one decision-ready intelligence report with record counts, snapshot additions and removals, ranked entity signals, secondary-dimension breadth, a bounded signal score, and agentAction. The same report is stored as INTELLIGENCE_REPORT for downstream automation. Results are designed for Tasks, schedules, webhooks, dashboards, and agent workflows rather than as a replacement for source evidence.

Gen2 decision intelligence

This Actor preserves its original analysis and adds a decision layer with baseline awareness, regression detection, confidence, GO/WARN/BLOCK executive output, and an optional economic-impact estimate. Economic estimates are produced only when the user supplies valuePerImpactUnitUsd; the result states the calculation basis instead of inventing monetary value.