AI agent team guide
AI SDR Agents: Build a Research-to-Outreach Desk
A small researched prospect batch with substantiated personalized drafts

An AI SDR agent should make a first conversation worth having. Define a specific audience, research a defensible reason for fit and draft an opening that gives the recipient a relevant choice. The best output is not a large pile of names. It is a small, reviewable set of accounts whose inclusion and next step you can explain.
Outbound Prospecting leads the desk, Sales Account Planner frames the conversation, Brand Voice Editor checks the message and CRM Steward protects the record handoff. Work from permitted sources and your actual offer. Keep research, contact readiness, draft approval and a sent message as different states.
Build your four-agent team
| Agent template | Its job on the team | Bring to its setup | Reviewable return | Team |
|---|---|---|---|---|
Outbound ProspectingLead agent | Build the bounded account shortlist and first-touch draft. | Explicit target criteria, exclusions and permitted account sources. | An evidence-led shortlist with a relevant opening for each accepted account. | Add to team |
Sales Account PlannerSupporting agent | Frame the next useful conversation. | Verified account context, known relationships and the actual offer. | A stakeholder hypothesis and specific discovery questions, with unknowns preserved. | Add to team |
Brand Voice EditorSupporting agent | Make the opening sound like the sender. | Approved draft facts, writing samples and communication boundaries. | A concise edit with meaningful changes explained. | Add to team |
CRM StewardSupporting agent | Reconcile existing relationship records. | Authorized account records and record-ownership rules. | Duplicate or stale-record flags and proposed field-level corrections. | Add to team |
Set up your team in Finta
- Add each template individually. Use the Add to team action for each named coworker, review the import setup and complete its Getting Started skill.
- Give each role the right context. State the shared objective, then supply the authorized documents, notes or exports that role needs. Do not assume an unconnected system is available.
- Review the handoff. Accept or correct one return before giving its evidence and open questions to the next coworker. Importing four templates does not itself run a bulk team.
- Make recurrence deliberate. Complete a useful manual pass first. Review any supported routine and enable it only when the scope, inputs and permissions are right.
Prepare the evidence
- A narrow audience definition, explicit exclusions and a research cutoff.
- An actual product or service offer, with claims the sender is allowed to make.
- Permitted account sources and current relationship records.
- The sender, approved outreach route and communication requirements applicable to the work.
Run the workflow
1. Choose a small research unit
Start with one segment and a bounded shortlist. Write what qualifies an account and what would exclude it before collecting names. An impressive logo without evidence of the relevant need is not a research success.
2. Give every account an inclusion reason
Ask Outbound Prospecting for a specific source supporting relevance. Sales Account Planner should distinguish a public company priority from an assumed buying project. Keep unknown stakeholders as research questions rather than invented contacts or authority.
3. Use relationship context without overstating it
CRM Steward checks whether the account or person already appears in authorized records. A mutual connection is not permission to claim an introduction. If a warm route is relevant, prepare the request for the actual connection owner to consider.
4. Review one complete first-touch package
Brand Voice Editor should preserve the evidenced reason, remove empty flattery and make the next step easy to understand. The sender reviews the recipient, factual context and channel requirements. Measure accepted conversations separately from drafts or sends.
A fictional first-touch package for one account
The company and statements below are fictional. They demonstrate source discipline rather than an outreach performance benchmark.
| Desk field | Illustrative entry | Review test |
|---|---|---|
| Inclusion reason | The company publicly describes adding a partner-led sales motion. | Does a dated source actually support this statement? |
| Conversation hypothesis | A shared account handoff may be relevant. | Keep it a question, not a claim about an internal problem. |
| Opening draft | Your partner announcement prompted a question about how account context moves between teams. | No invented compliment, customer result or private knowledge. |
| Next step | Ask whether a short example would be useful. | The person can decline; no meeting or relationship is assumed. |
The useful artifact connects evidence to an honest conversation. It does not treat personalization as a license to invent familiarity.
Copy the team brief
Build a bounded AI SDR desk for [segment] using [fit criteria], [exclusions], [actual offer] and [permitted sources].
Outbound Prospecting: propose accounts with specific inclusion evidence.
Account Planner: frame the relevant conversation and unknown stakeholders.
CRM Steward: flag existing relationships and possible duplicate records.
Brand Voice Editor: edit one first-touch draft in [sender voice] using only accepted facts.
Return source, fit reason, open question, draft, review owner and action state.
Do not invent contacts, scrape private data, claim an introduction, send outreach or enroll anyone in a sequence.Review the return
- Every included account has a relevant, dated source.
- The draft distinguishes a useful hypothesis from a known customer problem.
- A real person owns recipient and channel review before any external action.
Questions before you start
Is this a fully autonomous SDR?
No. This workflow assembles research and first-touch drafts with explicit handoffs. Templates do not automatically authorize contact collection, sending or sequence enrollment.
Should the team start with hundreds of accounts?
Start with a bounded segment you can review carefully. Expand only after the inclusion criteria, source quality and first-touch relevance prove useful to the team.
Sources and next steps
This playbook uses the current published Finta marketplace packages linked in the team table. Open each profile to review its instructions, context, Skills and any routines before importing.