---
name: raisekit-first-meeting-prep
description: Prepares a founder for a first meeting with an investor using RaiseKit. Finds the meeting (from the founder or upcoming Google Calendar events that match an investor in the pipeline), pulls the investor dossier and fund profile, and writes a one-page brief with thesis, recent portfolio and overlaps, what they pass on, how to pitch them, five likely questions with suggested answers, the ask, and what to log afterwards. Use when the founder says "prep me for my call with", "first meeting with", "investor meeting tomorrow", "brief me on this VC" or "who am I meeting this week".
---

# RaiseKit first meeting prep

A one-page brief the founder can read in five minutes before a first investor call.

## Requirements

- RaiseKit connector (https://raisekit.co/mcp). If a RaiseKit tool reports a sign-in or subscription problem, call `auth_whoami` and tell the founder exactly what it says.
- Optional: Google Calendar connector. If it is not connected and the founder did not name the investor, say "Google Calendar is not connected; who is the meeting with?" and continue from their answer.

## Steps

1. **Identify the meeting.**
   - If the founder named an investor or firm, use that.
   - Otherwise, if Google Calendar is connected, list events in the next 7 days. Call `pipeline_overview` and match event attendee emails (and, as a fallback, the firm name in the title) against pipeline investors. Confirm with the founder before going further: "Is this the meeting: <event>, <date>, with <investor>?"
2. **Pull the RaiseKit record.** Call `pipeline_get_dossier` with the `opportunity_id`, `person_id` or `firm_id`. Note: contacts and emails, current stage, recent touches, any thread, legal next stages and artifacts.
   - If the investor is not in the pipeline, call `search` with their name or firm, confirm the right result, and offer to add them with `pipeline_add_investor` (pass the `vc:` or `fund:` id from search).
3. **Pull the profile.** Call `fetch` with the investor's `vc:<id>` and the firm's `fund:<id>` (from the dossier or from `search`). Use: thesis, check size, stages, recent portfolio, what they pass on, how to pitch.
4. **Check fit against the founder's company.** Use what the founder has told you in this conversation and their deck read if available (`intel_suggest_target_list` shows whether this investor is a match and why). Flag:
   - Overlaps: portfolio companies in the same space (possible conflict or a useful reference).
   - Gaps: stage or check size outside what the founder is raising.
5. **Write the brief** (format below).
6. **Offer the pipeline updates.** Ask: "Want me to mark this as first call scheduled and set a follow-up?" On yes, call `pipeline_update_opportunity` with `stage: "first_call_scheduled"` (only if it is in the dossier's legal next stages; otherwise tell the founder which stages are allowed), `next_action` (for example "Send recap and deck after call") and `due_at` (the day after the meeting).

## Output format

```
## <Investor>, <Firm>: first meeting brief
<date and time if known> · Stage in RaiseKit: <stage>

**Who they are** - 2 to 3 lines: role, firm, check size, stages.
**Thesis** - 2 to 3 lines in their words where the profile has them.
**Recent portfolio** - up to 5 names; mark overlaps or conflicts with your company.
**What they pass on** - bullets from the profile.
**How to pitch them** - 3 bullets tailored to your company.

**Likely questions**
1. <question>
   Suggested answer: <1 to 2 lines from what the founder has shared; write "[fill in]" where you lack facts>
... (5 total)

**The ask** - amount, instrument and the specific next step you want (for example a partner meeting).

**After the call, log**
- Outcome and their stated next step
- Who else should be in the next meeting
- Any data they asked for, with a due date
```

## Guardrails

- Only state facts the tools return. If a profile field is empty, write "Not on file" instead of guessing.
- Never invent the founder's metrics in suggested answers; leave "[fill in]" placeholders.
- Do not contact the investor or send anything. Pipeline changes only after the founder says yes.
- After the meeting, if the founder shares notes, offer to log them with `pipeline_log_interaction` (`channel: "meeting"`, `direction: "out"`, plus `calendar_event_id` when known so re-logging is safe).