What an AI meeting-preparation teammate should own
An AI meeting-preparation agent should make sure an important conversation begins with current context, a clear objective, and the unresolved items that actually matter. It is not a generic company-summary generator and it is not merely a meeting recorder.
The teammate owns preparedness. The person attending the meeting still decides what to ask, what to disclose, and what outcome to pursue.
Meeting preparation is one responsibility in the broader AI teammates for private capital model, not a substitute for the relationship owner's judgment.
Meet your meeting-preparation teammate
| Responsibility | Prepare the right person for the right conversation using current, authorized context. |
| Working style | Brief, chronological, source-aware, and centered on the decision or next step. |
| Needs from you | Verified participants, the meeting purpose, authorized sources, and the desired outcome. |
| Brings back | A concise brief, what changed, open commitments, likely questions, and a proposed meeting objective. |
| Reports back | Before the meeting in its continuing conversation, then hands the open work into follow-through. |
A useful brief lets someone enter the conversation without reopening five systems. It should also show what the teammate could not verify.
The same brief structure supports different mandates
The preparation framework can remain stable while the substantive questions change.
| Meeting | What matters before the call | What the brief must not assume |
|---|---|---|
| GP meeting an LP | LP mandate evidence, prior fund discussion, requested materials, diligence state, relationship owner | Appetite, allocation authority, commitment, or meeting outcome |
| Family office meeting a manager | Strategy relevance, manager history, prior questions, team changes, approved research | Investment quality, suitability, or a decision to proceed |
| Sponsor meeting a prospective investor | Offering context, approved materials, questions asked, access state, next decision | Investor intent, accreditation, subscription, or commitment |
This distinction is why meeting preparation should start from the job and the relationship, not a standard web-research prompt.
Build the brief around one conversation outcome
Ask: what should be clearer when the meeting ends?
Possible outcomes include:
- understand an LP's process and unresolved diligence questions;
- confirm whether a manager's strategy changed;
- decide which approved material addresses an investor's request;
- determine whether a potential co-investor wants a deeper review;
- agree on ownership and timing for one open item.
"Have a good meeting" is not an operational objective. Neither is "convince them." A preparation teammate needs an outcome that can guide source selection and question design without predetermining the other person's answer.
Use a relationship-aware brief
A compact brief can include:
- Meeting frame: participants, roles, time, purpose, and named internal owner.
- Why now: the event, request, deadline, or relationship change that makes the meeting timely.
- What happened before: prior conversations and decisions in chronological order.
- What changed: new public facts, new material, role changes, or completed work since the last interaction.
- Still open: questions, promised documents, decisions, or unclear ownership.
- Meeting objective: one realistic result the attendee can pursue.
- Questions to ask: a small number tied to the open items.
- Boundaries: information that is unverified, private, restricted, or not approved for sharing.
The Finta investor meeting-prep template uses CRM context first, then available web, inbox, and calendar context when accessible. It instructs Aurora to flag uncertainty rather than fabricate portfolio details, thesis information, or relationship history.
Check identity before synthesizing context
An impressive brief about the wrong person is still wrong. Before assembling the narrative:
- verify the person's current organization and role;
- distinguish people with similar names;
- confirm which fund, vehicle, property, company, or mandate is involved;
- reconcile the calendar attendee with the CRM and email identities;
- use the current approved version of a document;
- separate the meeting organizer from the actual decision participants.
If identity remains ambiguous, the teammate should return a blocker instead of merging records.
Illustrative example: a GP prepares for an LP meeting
The following example is synthetic.
Meridian Ventures has a second meeting with the investment team at Harbor Foundation. The calendar title says "Fund III follow-up," but the useful context is spread across an email thread, a CRM record, a prior meeting note, and two versions of the track-record schedule.
The GP assigns:
Prepare a one-page brief for tomorrow's Harbor Foundation meeting. Confirm the attendees and their current roles. Use the latest approved fund materials and our authorized relationship history. Show what they asked last time, what we promised, and what remains open. Do not infer allocation interest or prepare a send.
The teammate returns:
Why now: Harbor requested a follow-up after reviewing the strategy deck.
What changed: The GP uploaded the approved current track-record schedule after the last meeting. One calendar attendee moved to a different investment role, which the GP should confirm before the call.
Still open: Harbor asked how reserves are allocated and whether the new partner is a voting member of the investment committee. The prior note contains no confirmed answer.
Prepared objective: Clarify Harbor's remaining review process and leave with owners for the two diligence questions.
Questions: Which part of the strategy needs the most clarification? Who else participates in the next review? What evidence would be most useful before that step?
Boundary: The relationship record contains no allocation amount or commitment. The brief does not label Harbor as likely to invest.
The output prepares the GP to have a better conversation. It does not script the meeting or decide what the LP means.
Connect the meeting to what happens afterward
Preparation and follow-through should share one open-item record. The pre-meeting brief predicts what may matter. The post-meeting handoff records what actually changed.
Before the meeting, an item may read:
Open question: Does the LP need an operating-reference call before committee review?
After the meeting, it might become:
Confirmed request: LP asked the GP to propose two operating references by Friday. Owner: Maya. External sharing requires reference approval.
Do not let a preparation hypothesis survive as if the meeting confirmed it. The meeting-preparation workflow can organize the source-backed brief. The handoff should then capture decisions, commitments, and next actions from the real conversation.
Common failures
Producing a public-profile summary
Background can help, but the relationship history, open questions, and current purpose usually determine what matters now.
Treating a prediction as a fact
Likely objections or questions are preparation hypotheses. Label them that way.
Including everything the system can find
More context can bury the decision. Keep the brief short enough to use five minutes before the meeting.
Mixing private and shareable context
Information useful for internal preparation may not be appropriate to mention or send externally.
Failing to show freshness
Role, mandate, fund, property, and transaction information can change. Date the material claims and expose stale sources.
What still needs a person
The attendee remains responsible for the meeting objective, disclosure choices, investment or fundraising judgment, and any promise made during the conversation. A teammate cannot know every offline interaction, political sensitivity, or confidential restriction.
Stop when an attendee cannot be identified, required context is inaccessible, sources conflict materially, or the meeting involves advice or decisions beyond the reviewer's competence and authority.
Give preparedness a recognizable owner
Aurora can assemble available CRM, inbox, calendar, document, and public context into a reviewable brief when the relevant sources and tools are accessible. An Aurora teammate makes that responsibility easier to return to: the user can refine the instructions, correct the emphasis, and keep the handoff with the same role.
Start with the meeting-preparation workflow, then use the AI outreach teammate when the next job is preparing a personal, reviewed follow-up.
Research checked September 27, 2026. This article provides operational education, not investment, legal, tax, compliance, or fundraising-outcome advice. Verify identities, sources, permissions, and material claims before using a brief.