Sales · Specialized agent role

Lead Generation Agent

The Lead Generation Agent turns a defined ideal customer profile into a researched prospect queue, with source context, duplicate checks, and an explicit sales handoff.

Get StartedReview the workflow

Best for

  • B2B teams with documented segments, territories, exclusion rules, and qualification criteria
  • Revenue operations teams that need consistent enrichment fields and clean CRM ownership

Typical inputs

  • ICP criteria including industry, size, geography, role, technology, exclusions, and account signals
  • Existing account and contact records, territory ownership, required enrichment fields, and source rules

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Translate ICP rules into explicit account and contact research criteria

2

Gather context

Find candidate organizations and retain source links for material facts

3

Prepare the work

Enrich permitted fields, score fit, and check candidates against existing CRM records

4

Review and hand off

Deliver approved candidates with rationale, gaps, and a recommended owner

Actions it can perform

  • Research accounts and decision-maker roles, normalize firmographic fields, and document relevant signals
  • Deduplicate domains and contacts, apply qualification rules, and prepare CRM-ready lead records

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A prospect table with company, contact, role, source links, fit reasons, and missing-data flags
  • A deduplicated CRM import or review queue with score components, territory, owner, and next step

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • lead-generation
  • defined-ideal
  • ideal-customer
  • customer-profile
  • researched-prospect
  • prospect-queue
  • duplicate-checks
  • explicit-sales
  • sales-handoff
  • handoff-give
  • give-sellers
  • reviewable-list
  • relevant-accounts
  • contacts-instead
  • unfiltered-volume
  • criteria-including
  • including-industry
  • industry-size
  • size-geography
  • technology-exclusions
  • account-signals
  • signals-existing
  • existing-account
  • contact-records
  • records-territory
  • territory-ownership
  • ownership-required
  • required-enrichment
  • enrichment-fields
  • rules-translate
  • explicit-account
  • contact-research
  • research-criteria
  • criteria-find
  • find-candidate
  • candidate-organizations
  • material-facts
  • facts-enrich
  • enrich-permitted
  • permitted-fields
  • fields-score
  • check-candidates
  • candidates-against
  • against-existing
  • records-deliver
  • rationale-gaps
  • research-accounts
  • decision-maker
  • maker-roles
  • roles-normalize
  • normalize-firmographic
  • firmographic-fields
  • document-relevant
  • relevant-signals
  • signals-deduplicate
  • deduplicate-domains

Human approval and escalation

Approval boundary

Sales operations approves source policy, scoring thresholds, list acceptance, ownership, and any write into the CRM or outreach sequence.

Escalation rule

Uncertain identity matches, conflicting company data, excluded segments, and ambiguous consent or territory rules return to the list owner.

What remains under human control

  • People define the ICP, lawful research boundaries, exclusions, score weights, territories, and source standards
  • A seller decides whether a prospect is appropriate to contact and what relationship or timing considerations apply

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

ApolloReview integration scopeHubSpotReview integration scopeSalesforceReview integration scopeGoogle WorkspaceReview integration scope

Example workflow

For a mid-market software campaign, the agent researches finance leaders at matching accounts, records cited fit signals, removes CRM duplicates, and submits the remainder for seller review.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

SDR Agent

See the responsibilities, controls, and handoffs for this related specialist role.

Explore SDR Agent

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Questions about this role

Does this role guarantee contact accuracy?

No. It preserves source context and flags gaps, but a person should verify important identity and contact details before outreach.

Design a responsible Lead Generation Agent workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started