| name | debrief |
| description | Turn an investor meeting into structured raise state — pull the meeting note, extract objections, commitments, asks, and signals, propose CRM updates, draft the follow-up, and update the belief state. Use right after any investor meeting or demo day. |
Post-Meeting Debrief
Argument: an investor name, meeting reference, or nothing (then ask which meeting, or run round granola sync --dry-run to see recently captured meetings and pick one).
Gather
- The meeting source: Granola MCP for the specific note (authenticate via
/mcp if needed), or the founder's verbal/typed recap if no note exists.
- The investor's
investors/<slug>.md and round.db record for context on where things stood before.
Extract (be exhaustive — this is where raises leak)
- Objections heard — every doubt, even softly phrased. Capture the investor's actual wording.
- Commitments & soft signals — what they said they'd do, check-size hints, timing hints, "not writing right now" qualifiers.
- Proof asks — anything they asked to see (benchmarks, customers, metrics, references). These are the raise's to-do list.
- Intel — fund timing, new vehicles, who else they mentioned, names worth mapping.
- Status change — did this move them (e.g. Meeting set → Met → Diligence → Term sheet → Committed, or Passed / On hold)?
Propose (everything through the queue, never --yes)
round meeting create --investor <id> --date <date> --title "..." --summary "..."round investors update --id <n> --status <new> --last-contact <date> --next-action "..." and add objections to --notes if material; re-score --fit/--tier if the meeting changed your read on fit (e.g. wrong stage, thesis mismatch).round objections add --investor <id> --text "..." [--category <c>] for each objection heard (the investor MD's ## Objections section renders from these on apply — never hand-edit that section, it regenerates).round tasks add for every commitment WE made and every proof ask (one task each, with due dates — follow-ups within 48h). If an ask maps to a data-room gap, add a task to produce the artifact (check round dataroom status).round outreach draft --investor <id> --kind follow-up --subject "..." --body "..." — reference something specific from the meeting, answer the sharpest objection, deliver or promise the asked proof. The founder sends manually.
Write the debrief file
progress/YYYY-MM-DD-<slug>-debrief.md (follow the most recent debrief in progress/ if one exists):
- In the room / context line
- Q&A themes (numbered, with "answer to sharpen" notes)
- Investor-by-investor (for multi-investor events) or single narrative
- Cross-cutting feedback — especially repeated asks across meetings
- Relationship notes — adjacent people worth tracking
Close the loop
- Run
/observe on the debrief so objections and signals become tracked beliefs (a recurring objection gains evidence weight each time it is heard).
- Chat summary: status change, top objection, the follow-up deadline.
