LinkedIn prospecting tasks, organized by reviewer

Brief the agent with an industry boundary, operating geography, observable stage proxy, relevant functions, and exclusions. Review whether the account remains useful when a funding or hiring event is removed.

Gate: the company matches the written thesis; profile identity and role relevance are separately supported.

Request approved accounts, target functions, current profile context, and explicit unknowns. Keep email discovery and verification distinct, then compare each record with suppression and existing-customer lists.

Gate: a representative can explain every personalization claim and edit the draft before sending.

Define source priority, freshness windows, fallback rules, accepted values, exception queues, and rollback behavior. Waterfall enrichment may improve fill rate while increasing disagreement that needs review.

Gate: every changed CRM field has provenance, a timestamp, and a reversible transformation.

Use a test environment, minimum-scope credentials, known records, rate-limit handling, sanitized logs, an approved destination, and a deletion plan. Browser automation and APIs carry different reliability and policy constraints.

Gate: failure does not leak a secret, bypass an exclusion, or silently accept a weak identity match.