What an AI outreach teammate should own
An AI outreach agent should prepare personal, context-aware communication for review and keep the related follow-up responsibility visible. It should not turn a relationship workflow into high-volume sending.
The teammate owns preparation: gather the relevant history, understand the recipient's request, use approved facts, follow the user's voice brief, and return a draft with the sources and assumptions exposed. A draft is not a sent message. The relationship owner still controls the recipient, claims, timing, attachments, and send decision.
Meet your outreach teammate
| Responsibility | Prepare relevant one-to-one outreach and follow-up from current relationship context. |
| Working style | Specific, concise, natural, easy to edit, and respectful of communication preferences. |
| Needs from you | The relationship objective, approved facts and materials, voice brief, recipient rules, and send boundary. |
| Brings back | An unsent draft, the context used, unresolved claims, and a recommended follow-up state. |
| Reports back | In its continuing conversation and the relationship record, with draft, approved, sent, replied, paused, and suppressed kept distinct. |
This role fits inside a wider AI teammate system for private capital. Its purpose is not to maximize message volume. It is to reduce the repeated work of rebuilding context while preserving the judgment that makes a relationship personal.
Start with the relationship, not a writing prompt
Before drafting, the teammate should be able to answer:
- Who is the recipient, and is the identity current?
- Why is this message appropriate now?
- What did the recipient ask for or agree to?
- What has already been sent?
- Which material facts and documents are approved?
- What promise, question, or next step remains open?
- Who owns the relationship?
- What communication preferences, opt-outs, or restrictions apply?
- Does the message require another reviewer?
If the system cannot answer those questions, it should return a blocker or request clarification instead of filling the gaps with persuasive language.
Give the teammate a voice brief
"Sound like me" is hard to review and easy to overclaim. Use a short, explicit voice brief:
| Voice setting | Example instruction |
|---|---|
| Tone | Direct, warm, and professional. Do not manufacture familiarity. |
| Length | Default to 90 to 140 words unless the recipient asked for detail. |
| Opening | Begin with the actual conversation or request, not a generic greeting. |
| Claims | Use only approved facts and label anything that needs verification. |
| Ask | Request one clear next step with room to decline or redirect. |
| Phrases to avoid | "Just bumping this," false urgency, exaggerated traction, and presumed interest. |
| Escalation | Ask the user when recipient, claim, material, or permission is unclear. |
The voice brief is a quality standard, not permission to send.
Generic draft versus context-aware draft
The example below is illustrative.
Generic draft
Hi Alex, I wanted to follow up and share our exciting opportunity. We would love to schedule another call and answer any questions. Let me know when you are free.
The draft is grammatical but does not explain why the message exists. It could go to anyone.
Context-aware draft
Alex, thank you for the questions about the leasing assumptions in Tuesday's meeting. I attached the updated schedule we discussed and highlighted the two changes your team asked us to explain. We are still confirming the renewal option for Suite 410, so I left that item open rather than estimate it. If useful, I can walk through the schedule with you Thursday afternoon. No rush if your team needs time to review first.
The second draft connects the real request, the approved material, the unresolved fact, and one next step. It does not claim enthusiasm, intent, or urgency the recipient did not express.
Illustrative example: a real estate sponsor follows up
The following scenario is synthetic.
Harbor Street Partners is raising capital for a multifamily acquisition. A prospective investor attended a call and asked for the current rent roll, debt terms, and an explanation of the sponsor's downside case.
The outreach teammate receives:
Prepare a follow-up from the meeting record and approved offering materials. Use my direct, concise voice. Attach nothing. Identify the documents I should review before sending. Do not describe the investor as interested or qualified. Nothing should be sent without my approval.
The teammate returns an unsent draft plus a review receipt:
- Sources used: meeting note, current CRM record, approved investment summary, and document index.
- Draft state: ready for sponsor review.
- Missing: the debt-term summary is approved, but the current rent roll is still awaiting internal verification.
- Suggested action: send the approved downside-case explanation now, or wait until the verified rent roll can be included. The sponsor decides.
- Nothing sent: no email or attachment was transmitted.
The sponsor corrects one phrase, chooses to wait, and assigns the rent-roll check to the asset manager. The teammate keeps the open responsibility visible for the next review.
This is separate from underwriting. Finta can support capital-raising relationships and follow-through, but it does not determine whether a property or investment is suitable.
Use a communication-state model
An outreach teammate should distinguish preparation from execution:
| State | Meaning |
|---|---|
| Context needed | A required source, identity, claim, or permission is missing |
| Draft prepared | Text is ready for human review and has not been sent |
| Approved | The required reviewer accepted the recipient, claims, materials, and timing |
| Sent | The message was actually transmitted through a supported action |
| Replied | A response was received and linked to the relationship |
| Waiting | No action is due before the agreed date or event |
| Paused | The relationship owner intentionally stopped follow-up |
| Suppressed | The recipient or policy prevents further communication |
Do not label a draft as outreach completed. Do not label silence as engagement. Do not let a scheduled or queued action appear as delivered without a receipt.
Communication rules still apply
An AI teammate does not remove the sender's legal or professional responsibilities. In the United States, the FTC's CAN-SPAM compliance guide explains that the law can cover commercial email, including business-to-business messages, and addresses accurate headers, non-deceptive subject lines, identification, postal address, and opt-out handling. Whether a particular investor, relationship, transactional, or other message is covered depends on the facts and applicable law.
Fundraising communications can also require securities, broker-dealer, privacy, contractual, or firm-specific review. Use qualified counsel and the organization's current policies. A writing agent is not a compliance reviewer.
Common failures
Treating personalization as a merge field
Adding a first name or company does not make a message relevant. The actual request, prior conversation, approved evidence, and appropriate next step do.
Optimizing for volume
More drafts can create more review burden and reputation risk. Focus the teammate on qualified relationships and open responsibilities.
Smuggling inference into a claim
"You seemed interested" or "your team is moving quickly" can misstate the recipient's intent. Use what the record supports.
Reusing private context
Information available internally may not be appropriate to mention externally. Apply disclosure boundaries before drafting.
Sending with an obsolete attachment
Check approval, version, access, and recipient before including a document or link.
Ignoring a reply or opt-out
Follow-up routines should stop or change when the recipient responds, asks to pause, declines, or opts out.
What still needs a person
The relationship owner decides whether the message should exist, whether the context is appropriate, whether the claims and materials are accurate, and when or whether to send it. Required legal, compliance, or disclosure reviewers remain responsible for their decisions.
Stop when identity is uncertain, the evidence conflicts, the recipient did not authorize the proposed context, the message would disclose sensitive information, or communication preferences cannot be confirmed.
Keep communication personal without rebuilding the context
Aurora can use available Finta context and supported tools to prepare messages and working documents. An outreach teammate makes the working style and recurring responsibility recognizable, while the human owner retains control of consequential communication.
For GP follow-up, use the LP fundraising follow-up workflow. For the context that should arrive before the draft, see the AI meeting-preparation teammate.
Research checked September 27, 2026. This article provides operational education, not legal, compliance, investment, broker-dealer, placement-agent, or communications advice. Verify applicable law, firm policy, recipient preferences, sources, and approval requirements.