Decision Tree
I have X, I want Y — pick the right play for your starting point.
You can enter the pipeline anywhere. Match what you have to what you want, and the table points to the play. Discovery order depends on the job: candidate sourcing is people-first; BD/signal work is company-first.
I have… I want…
| I have | I want | Go to |
|---|---|---|
| A job description / spec | A qualified candidate shortlist | JD → Shortlist |
| An engineering / IT role | Developers with skill proof | IT Sourcing |
| A role + several people-DBs | A deduped, qualified candidate pool | Multi-source Candidate Search |
| A list of companies | Only the ICP-fit ones | Qualify Against ICP |
| A funding event | Hiring managers + a BD sequence | Funding → BD |
| A layoff announcement | Displaced talent to poach (+ BD) | Layoff Signal → Poach |
| A shortlist with contacts | An outreach cadence | Campaign Plays |
| Names but no contacts | Email / phone / LinkedIn | Enrich |
Picking the discovery order
Is the target a person or a company?
Sourcing candidates → people-first (title + location across the people-DBs). BD / signal work → company-first (find the accounts/signals, then the contacts). Don't open a broad people search when the task is really "find the right companies first."
What channel do you need?
Candidate acquisition → personal email + LinkedIn (never work email). BD → work email.
Read the matching doc before any paid call
The recipe encodes validated filter shapes and costs. Skipping it re-discovers solved failures (e.g. mis-nesting a filter and pulling the whole DB).
No recipe matches? State the task to /hyreflow-recruit anyway — the agent greps the recipe
and playbook library and composes a pattern from the base capabilities.