Agentic outbound research pipeline
Turn a research brief into checked candidates, outreach drafts and follow-up tracking with approval before sending.
This example explains a workflow design and its controls. It does not represent verified client results. Tooling and benefits must be validated in each project's context.

Solution example
Agentic outbound research pipeline
Turn a research brief into checked candidates, outreach drafts and follow-up tracking with approval before sending.
The design connects these steps: Brief intake → Missing-info loop → Search creation → Candidate pool → Account validation → Deep research → Company score → Discover contacts → Score contacts → Suppression → Draft queue → Approve/send/follow-up. Rules, exceptions and approvals are defined before external actions are connected.
Workflow map
Three independent workflows in one outbound pipeline
Each workflow has its own trigger. They can run one after another, but they can also be used separately for intake, research, or approved sending.
Main database: Supabase
The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.
Tool icons
Pipeline rationale
This is not an outbound bot. It is a controlled sales operating system.
The agentic part is not a model sending messages on its own. It is the system breaking an ambiguous commercial job into smaller decisions: ask for context, research, discard, score, draft, wait for approval, send and record what happened.
Workflow 0 exists because human briefs rarely arrive perfect.
The system can ask for market, geography, company size, buying signals, exclusions and goal before spending research effort.
Workflow 1 exists because researching is not the same as sending.
This is where the pool is built, customers/duplicates are blocked, company/contact fit is scored and a review queue is prepared.
Workflow 2 exists because sending is an external action.
It only starts after human approval, rechecks suppression, then syncs HubSpot, sends and stores follow-up state.
Why the gates matter
- Complete brief before investigation starts.
- Customers, duplicates and owned accounts blocked before deep research.
- Company must qualify before contacts are discovered.
- Each contact must qualify before drafting.
- Suppression checked before draft and again before send.
- HubSpot and Resend touched only after human approval.
Add-ons that fit on top
The scenario
Design scenario: Turn a research brief into checked candidates, outreach drafts and follow-up tracking with approval before sending. The starting point is a workflow with scattered information, manual steps and responsibilities that need to be made explicit.
Before implementation, we review available data, responsible owners and decisions that need approval. Understand the workflow first.
The approach
The design connects these steps: Brief intake → Missing-info loop → Search creation → Candidate pool → Account validation → Deep research → Company score → Discover contacts → Score contacts → Suppression → Draft queue → Approve/send/follow-up. Rules, exceptions and approvals are defined before external actions are connected.
AI can help classify, extract or draft; sensitive actions retain human review. Clear controls at each step.
What was used
Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.
In practice, the build combined Supabase, Python/FastAPI, OpenRouter, Tavily, HubSpot, Resend. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.
Workflow design
Manual approach and proposed workflow
Manual approach
Proposed workflow
Visible artifacts
- Search brief record
- Candidate company table
- Account-status validation event
- Company research summary
- Contact score rationale
- Outreach draft queue
- Approval log
- HubSpot activity
- Resend message id
- Follow-up status
Controls
- Brief must be complete before search starts
- Existing customers, owned accounts and duplicates are blocked before deeper research
- Company must qualify before contacts are discovered
- Each contact must qualify before drafting
- Suppression is checked before draft and again before send
- Human approval required before HubSpot or Resend
- Every score keeps source evidence
- Follow-up timing is tracked instead of relying on memory
What this aims to improve
The aim is to reduce manual coordination and make records, exceptions and the next action visible. Any improvement must be validated against the project's own data and operating conditions.
Project scoping establishes a baseline and success criteria so proposed improvements can be tested. Validate the benefit in context.
The workflow in one line
Tooling and boundaries
The design shows how Supabase, Python/FastAPI, OpenRouter, Tavily, HubSpot, Resend can work together. Final tooling, scope and controls are agreed for each project.
Integrations need appropriate permissions, run logs and a way to review exceptions. The team should be able to understand and operate the workflow.
What this example demonstrates
- Brief intake workflow
- Candidate pool creation
- Account-status validation
- Company/contact research
- Company/contact scoring
- Draft approval queue
- HubSpot/Resend send
- Follow-up tracking
- Brief must be complete before search starts
- Existing customers, owned accounts and duplicates are blocked before deeper research
- Company must qualify before contacts are discovered
- Each contact must qualify before drafting
- Suppression is checked before draft and again before send
- Human approval required before HubSpot or Resend
- Every score keeps source evidence
- Follow-up timing is tracked instead of relying on memory