Desired result
A defined, reviewable outcome
Produce a prioritized prospect list with source context, fit reasoning, required fields, duplicate status, and a clear owner for acceptance or rejection.
Business workflow
Create a repeatable prospecting process that starts with explicit ideal-customer criteria and ends with sourced, deduplicated records ready for sales review.
The problem
Prospecting teams spend time moving between research tools, validating contact data, checking fit, and cleaning records before a seller can act.
Desired result
Produce a prioritized prospect list with source context, fit reasoning, required fields, duplicate status, and a clear owner for acceptance or rejection.
How the workflow works
Set industries, company size, regions, exclusions, personas, and evidence required for a qualified record.
Gather permitted company and role context from approved sources without inventing missing facts.
Complete required fields, preserve provenance, and flag stale or conflicting information.
Apply transparent rules, check duplicates, and place candidates in a review queue before CRM creation.
Agents involved
Agent roles describe possible workflow responsibilities. Final configuration and availability depend on the selected implementation.
Researches accounts and assembles candidate records.
View details →Applies fit and routing criteria.
View details →Checks duplicates and prepares the CRM handoff.
View details →Integrations involved
Approved company and contact research context.
View details →Contact, company, deal, and owner context.
View details →Lead, account, campaign, and assignment context.
View details →Human approval points
Approval design should reflect the actual risk, audience, and permissions of this workflow.
Example workflow
A sales operations lead provides a defined segment. The workflow researches matching companies, records sources, enriches selected roles, removes existing accounts, scores fit, and presents a reviewable import file.
Workflow boundary
This illustrates how roles, integrations, and controls can be arranged. Connection support and final behavior must be confirmed during implementation.
Implementation considerations
Related workflows
FAQ
No. Source data can be incomplete or stale, so records should carry provenance and be reviewed before outreach.
No. Research, CRM creation, and outbound messaging are separate workflow stages with their own permissions and controls.
Bring the outcome, current systems, approval needs, and exception paths you want to design.