AI agent team guide
Coordinate Investor Reference Checks With an AI Team
A permission-aware investor-reference process and evidence comparison

Investor reference checks become more useful when the research, conversations and follow-through stay connected. Use an AI team to prepare a source-led brief, draft respectful requests and reconcile what people actually said. Keep the founder’s decision separate from the team’s summary, particularly when accounts conflict or the evidence is sparse.
Researcher leads the brief, Communicator prepares requests, Meeting Follow-Through reconciles commitments and Decision Red Team tests the conclusion. The templates help organize the work. They do not certify an investor, establish private access or replace the founder’s own judgment and appropriate advisers.
Build your four-agent team
| Agent template | Its job on the team | Bring to its setup | Reviewable return | Team |
|---|---|---|---|---|
ResearcherLead agent | Prepare the source-led reference brief. | Official firm context, founder criteria and permitted reference evidence. | A fact pack, gaps and questions tied to the founder’s decision. | Add to team |
CommunicatorSupporting agent | Draft requests and conversation follow-ups. | A legitimate relationship route, accepted context and approved request. | Respectful drafts that do not claim an introduction or endorsement. | Add to team |
Meeting Follow-ThroughSupporting agent | Reconcile reference-work commitments. | Permissioned conversation notes, accepted requests and existing tasks. | An open-loop register with actual owners, evidence and follow-up state. | Add to team |
Decision Red TeamSupporting agent | Challenge the resulting assessment. | Attributed reference evidence, contradictions and founder priorities. | Counterevidence, remaining questions and limits on any conclusion. | 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
- The founder’s actual fit criteria and the decision the references should inform.
- Current official firm information, distinct from personal reference accounts.
- Legitimate introduction routes and permissioned notes with attribution limits.
- A record of who agreed to what and which conversations actually occurred.
Run the workflow
1. Define what the references should clarify
Researcher links each question to a founder concern, such as communication during difficulty or working style. Use the established reference-check guide for question design instead of creating another generic checklist here.
2. Prepare requests through real relationships
Communicator drafts a specific request to the appropriate person. A network path is not a completed introduction, and a public portfolio entry does not establish willingness to speak. Respect confidentiality and the recipient’s choice.
3. Keep accounts and action states separate
Meeting Follow-Through distinguishes a proposed call, accepted request, completed conversation and received follow-up. Attribute subjective experiences rather than convert them into universal facts about a person or firm. Preserve source dates and limits.
4. Challenge the conclusion before the founder decides
Decision Red Team looks for selection bias, conflicting accounts and questions not yet answered. A positive reference is useful evidence about an experience, not a guarantee of the founder’s future outcome. The founder decides what weight to give it.
A fictional reference-work register
The people, firms and accounts in this original example are fictional. No statement evaluates a real investor.
| Reference-work item | Recorded state | Next decision |
|---|---|---|
| A founder requests an introduction to a portfolio operator. | Request drafted; connection owner has not agreed. | Review and ask through the legitimate route. |
| One operator describes supportive communication. | Attributed account under the stated permission. | Explore which circumstances made that support useful. |
| Another account raises a conflicting experience. | Both accounts remain in the evidence pack. | Ask what context differs rather than discard the inconvenient source. |
| A follow-up promises a source document. | Promised, not received. | Keep the question open until evidence arrives. |
The team improves diligence by preserving provenance and unresolved work. It should not flatten nuanced accounts into an unsupported investor rating.
Copy the team brief
Coordinate reference work for [founder decision and criteria].
Researcher: prepare official context and source gaps.
Communicator: draft requests through legitimate routes without claiming access or endorsement.
Meeting Follow-Through: reconcile proposed, accepted and completed conversations and promises.
Decision Red Team: challenge conclusions using contradictions and coverage limits.
Use only [permitted sources and permissioned notes].
Return a source-confidence brief, open-loop register and questions for the founder.
Do not contact references, expose confidential accounts, rate personal traits or certify an investment decision.Review the return
- Reference accounts remain attributed and within their permission limits.
- Requested, agreed, completed and received work are distinct.
- The founder can see contradictory evidence and unresolved questions.
Questions before you start
Is this a substitute for investor due diligence?
No. It organizes a specific reference-work process. The founder remains responsible for broader diligence and any appropriate professional advice.
Can the team publish what a reference said?
Not without suitable permission and review. Keep private reference evidence private and preserve any attribution or use limits in the working brief.
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.