---
name: raisekit-weekly-standup
description: Runs a weekly fundraising standup from the founder's RaiseKit pipeline. Summarizes what moved, committed versus target, overdue and stale investors, optionally finds investor replies in Gmail since last week and offers to log them, and ends with the top 3 actions for the week. Use when the founder asks for a weekly raise update, fundraising standup, pipeline review, "where is my round at", "what happened this week with investors" or "what should I focus on this week".
---

# RaiseKit weekly standup

A short, honest weekly review of the founder's raise, built only from RaiseKit data (and Gmail if connected).

## 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: Gmail connector. If it is not connected, say "Gmail is not connected, so I skipped the inbox scan" and continue.

## Steps

1. **Load the board.** Call `pipeline_overview` with `stale_days: 10` and `due_within_days: 7`. If the founder has more than one active round, ask which one (or use the round they named) and pass `round_id`.
2. **Work out what moved.** From the board, collect:
   - Opportunities whose last stage change or last touch is within the past 7 days.
   - Committed amount versus the round target (only if the round has a target; never estimate one).
   - `due` items: next actions due this week or already overdue.
   - `stale` items: no touch in 10+ days, excluding passed and ghosted.
3. **Scan Gmail for investor replies (optional).** If Gmail is connected:
   - Search for messages received in the last 7 days (for example `newer_than:7d -from:me`).
   - For each sender, check whether they are an investor in the pipeline: call `pipeline_get_dossier` for opportunities on the board and match the sender address against the dossier contacts' emails. Ignore senders that do not match. Never guess a match from a name alone.
   - List matched replies (investor, firm, date, one-line gist) and ask: "Log these to RaiseKit?" On yes, call `pipeline_log_interaction` once per message with `email` (the sender), `channel: "email"`, `direction: "in"`, `summary`, `subject`, `occurred_at`, `gmail_thread_id` and `gmail_message_id`. Re-running is safe: RaiseKit dedupes on the Gmail ids.
4. **Pick the top 3 actions.** Rank by: overdue items on late-stage deals first (term sheet, IC, partner meeting), then warm replies that need an answer, then stale investors who were engaged before going quiet. Each action names one investor, one concrete step and a date.
5. **Offer to set them.** Ask: "Want me to set these as next actions in RaiseKit?" On yes, call `pipeline_update_opportunity` per action with `opportunity_id`, `next_action` and `due_at` (ISO date). Do not change stages unless the founder asks.

## Output format

Keep it to one screen.

```
## Raise standup: week of <date>

**Wins**
- <investor / firm>: <what happened> (<stage>)

**Pipeline by stage**
| Stage | Count | Investors |
|---|---|---|
| ... | ... | ... |

Committed: <amount> of <target> (<percent>)   [omit the line if no target]

**Risks**
- Overdue: <investor> (<next action>, due <date>)
- Stale: <investor> (last touch <date>, <stage>)

**Top 3 this week**
1. <investor>: <action> by <date>
2. ...
3. ...
```

If nothing moved, say so plainly in Wins ("No stage changes this week").

## Guardrails

- Only report investors, firms, amounts and dates that the tools return. Never invent a target, a commitment or a reply.
- Never send email. Logging and next-action updates happen only after the founder says yes.
- Keep investor email contents private to this conversation; summarize, do not quote long passages.
- If `pipeline_overview` returns no rounds, say so and suggest creating one with `pipeline_upsert_round` instead of producing an empty standup.