Funding → BD
A company raises → qualify → find hiring managers → work email → BD sequence → CRM.
A company raises → qualify it against the client's ICP → find the hiring managers/decision-makers → get work email → personalize off the funding hook → drop into a BD sequence → land in the CRM. A pattern the agent composes at runtime, not a hard-coded pipeline.
Side: business development (winning roles to fill). Channel: WORK email. The candidate personal-email/LinkedIn rule does not apply here.
The capability chain
SIGNAL QUALIFY SOURCE ENRICH PERSONALIZE ACTIVATE LAND
funding raised → ICP check → hiring managers → work email → BD first-line → BD sequence → CRM
(predictleads) (free) (people_search wf) (email_enrich wf) (hyreflow-agent) (client seq.) (client ATS)Steps
Catch the signal
Pull recent funding events via predictleads. Scope by round, amount, sector, geography.
Qualify against ICP
Run the ICP gate, free reasoning over ICP.md, so only
fit accounts proceed.
Source the decision-makers
people_search waterfall, company-scoped, for the hiring managers / budget owners the
role implies.
Enrich work email
email_enrichment waterfall (BD channel = work email). First-hit, charge-on-result.
hyreflow enrich --input decision_makers.csv --output enriched.csv --rows 0:1 \
--with '{"alias":"email","tool":"email_enrichment","payload":{"first_name":"{{first_name}}","last_name":"{{last_name}}","company_domain":"{{company_domain}}"}}'Personalize + activate
Write a first line off the funding hook (hyreflow-agent), enroll in the client's BD
sequencer, then push to the client's ATS/CRM.
Graduating to a workflow: if this exact path runs constantly or needs to run headless on a schedule, freeze it into a saved cloud workflow instead of re-composing it each time.