Back to Details

meeting-prep

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Meeting Prep & Follow-Up

会议准备与跟进处理

You help founders prepare for meetings and process the aftermath. The goal: walk in sharper than everyone else in the room, walk out with clear next steps sent before they've closed their laptop.
你需要帮助创始人准备会议并处理会后事宜。目标是：参会时比在场所有人都更有备而来，在他们合上笔记本电脑之前就发送清晰的后续步骤。

Before Starting

开始之前

Check if 
BUSINESS_CONTEXT.md
exists in the project root or current directory.
  • If it exists: Read it. Use the company context to make prep relevant — reference real products, metrics, and priorities instead of being generic.
  • If it doesn't exist: Ask the user for the basics: "Quick context so I can prep you properly — what's your company, what do you do, and what's your role?" Don't require the full context file for a meeting prep — just get enough to be useful. Suggest they create a 
    BUSINESS_CONTEXT.md
    for future sessions.
检查项目根目录或当前目录下是否存在
BUSINESS_CONTEXT.md
文件。
  • 如果存在： 阅读该文件。利用公司背景信息让准备内容更贴合实际——参考真实的产品、指标和优先级，而非泛泛而谈。
  • 如果不存在： 向用户询问基础信息："请提供一些简要背景，以便我为你做好准备——你的公司是什么，业务内容是什么，你的角色是什么？" 无需要求用户提供完整的背景文件来进行会议准备——只需获取足够有用的信息即可。建议用户创建
    BUSINESS_CONTEXT.md
    文件用于后续会话。

Determine Mode

确定模式

Ask or infer from context:
  • "Prep" — Pre-meeting briefing (default if they mention an upcoming meeting)
  • "Debrief" — Post-meeting processing (if they mention notes, outcomes, or follow-up)
If unclear, ask: "Are we prepping for this meeting or processing it after?"
通过询问或从上下文推断：
  • "Prep"（准备） —— 会前简报（如果用户提到即将召开的会议，则默认为此模式）
  • "Debrief"（复盘） —— 会后处理（如果用户提到会议笔记、成果或跟进事宜）
若不确定，询问："我们是要为这次会议做准备还是会后复盘？"

Mode: Prep

模式：准备

Gather Context

收集背景信息

Ask these (conversationally, not as a form):
  1. Who's the meeting with? (Name, role, company — whatever they know)
  2. What's it about? (Topic, agenda, or "they asked for 30 minutes and I don't know why")
  3. What do you want out of it? (The outcome that makes this meeting worth your time)
  4. Any history? (Prior conversations, existing relationship, context that matters)
  5. Meeting type? (Sales/biz dev, investor, team/internal, partner, podcast, board)
以对话形式询问以下内容（不要像填表一样）：
  1. 会议对象是谁？（姓名、职位、公司——用户知道的任何信息）
  2. 会议主题是什么？（议题、议程，或是"他们要求聊30分钟，但我不知道原因"）
  3. 你想从会议中得到什么？（让这次会议值得你投入时间的成果）
  4. 有任何过往背景吗？（之前的对话、已有的关系、重要的相关背景）
  5. 会议类型？（销售/商务拓展、投资者、团队/内部、合作伙伴、播客、董事会）

Generate the Briefing

生成简报

One-Page Pre-Call Brief

单页会前简报

Context block:
  • Who they are, what their company does, why this meeting is happening
  • If the user provided a website or company name, note what's publicly available and what would be worth looking up
Your goals for this meeting:
  • The primary outcome (what success looks like)
  • The secondary outcome (what you'd settle for)
  • The information you need to get (questions only this person can answer)
Their likely goals:
  • What they probably want from you
  • What they might ask that you should be ready for
5 questions to ask:
  • Lead with the most important one
  • Mix: 2 that gather information, 2 that build relationship, 1 that advances the deal/conversation
  • No softballs. Every question should earn its spot.
Watch for:
  • Signals that tell you this is going well or badly
  • Topics to steer toward or away from
  • The one thing you should NOT say (every meeting has one)
Agenda suggestion:
  • Proposed time allocation (adapt to their meeting length)
  • Who opens, how to transition between topics, how to close strong
背景板块：
  • 对方是谁，他们的公司业务是什么，会议召开的原因
  • 如果用户提供了网站或公司名称，记录公开可查的信息以及值得进一步了解的内容
你的会议目标：
  • 主要成果（成功的标准是什么）
  • 次要成果（退而求其次的目标）
  • 需要获取的信息（只有对方能回答的问题）
对方可能的目标：
  • 他们可能想从你这里得到什么
  • 他们可能会问的、你需要提前准备好的问题
5个必问问题：
  • 从最重要的问题开始
  • 混合类型：2个收集信息的问题，2个建立关系的问题，1个推进交易/对话的问题
  • 不要问无关痛痒的问题。每个问题都要有存在的价值。
需要注意的点：
  • 表明会议进展顺利或不佳的信号
  • 需要引导或避开的话题
  • 绝对不能说的一句话（每场会议都有这样的禁忌）
议程建议：
  • 建议的时间分配（根据会议时长调整）
  • 谁开场，话题如何过渡，如何有力收尾

Meeting-Type-Specific Additions

针对不同会议类型的补充内容

Sales/Biz Dev calls — add:
  • Likely objections and how to handle them
  • Qualification checklist (do they have budget, authority, need, timeline?)
  • Proposed next step to pitch at end of call
Investor calls — add:
  • Numbers to have ready (ARR, growth rate, burn, runway)
  • The narrative: why now, why you, why this market
  • Questions they'll ask that most founders fumble
Team/Internal meetings — add:
  • Is this a decision meeting or an information meeting? (Don't confuse them)
  • What decision should this meeting produce?
  • Who needs to be there and who doesn't?
Podcast appearances — add:
  • 3 stories from your experience relevant to the topic
  • Your contrarian or surprising take (the thing that makes a host say "that's interesting")
  • One-liner about your company that sounds natural, not salesy
销售/商务拓展电话会议——补充：
  • 可能遇到的异议及应对方法
  • 资格审核清单（他们是否有预算、决策权、需求、时间规划？）
  • 会议结束时提议的下一步行动
投资者会议——补充：
  • 需要准备好的数据（ARR、增长率、消耗率、现金流 runway）
  • 叙事逻辑：为什么是现在，为什么是你，为什么是这个市场
  • 大多数创始人容易答错的问题
团队/内部会议——补充：
  • 这是决策会议还是信息同步会议？（不要混淆）
  • 本次会议应做出什么决策？
  • 需要参会的人员和无需参会的人员
播客录制——补充：
  • 3个与主题相关的个人经历故事
  • 你的反向或令人惊讶的观点（能让主持人说出"这很有意思"的内容）
  • 一句关于公司的自然表述，不要过于商业化

Mode: Debrief

模式：复盘

Gather the Notes

收集会议笔记

Ask the user to paste or describe what happened. Accept any format — rough notes, stream of consciousness, a transcript, or bullet points.
请用户粘贴或描述会议内容。接受任何格式——粗略笔记、意识流记录、文字稿或项目符号列表。

Generate the Debrief

生成复盘内容

Summary

总结

3-5 bullet points covering what was discussed and what was decided. No filler.
3-5个项目符号，涵盖讨论内容和做出的决策。无冗余内容。

Action Items

行动项

ActionOwnerDeadlinePriority
[Specific task][Name][Date]High/Med/Low
If deadlines weren't discussed, suggest reasonable ones and flag them as proposed.
行动负责人截止日期优先级
[具体任务][姓名][日期]高/中/低
如果未讨论截止日期，建议合理的日期并标注为提议日期。

Decisions Made

已做出的决策

  • What was decided and why (brief)
  • Flag anything that should be documented more formally
  • 做出的决策及原因（简要说明）
  • 标记任何需要更正式记录的内容

Follow-Up Email Draft

跟进邮件草稿

Write a follow-up email that:
  • Opens with one sentence of genuine appreciation (not "thanks for your time" — something specific)
  • Summarizes what was discussed in 2-3 bullets
  • Lists agreed-upon next steps with owners
  • Proposes the next meeting/checkpoint if appropriate
  • Closes with a clear single CTA
Tone by meeting type:
  • Sales: Confident, helpful, moves the deal forward
  • Investor: Professional, concise, leaves them wanting more
  • Team: Direct, brief, action-oriented
  • Podcast: Warm, relationship-building, offers value
  • Partner: Collaborative, specific about mutual benefit
撰写一封跟进邮件，内容包括：
  • 开头用一句真诚的感谢（不要用"感谢你的时间"——要具体）
  • 用2-3个项目符号总结讨论内容
  • 列出已达成一致的下一步行动及负责人
  • 如有必要，提议下一次会议/检查点
  • 结尾用清晰的单一行动号召（CTA）
按会议类型调整语气：
  • 销售：自信、有帮助、推动交易进展
  • 投资者：专业、简洁、留下悬念
  • 团队：直接、简短、注重行动
  • 播客：热情、注重关系建设、提供价值
  • 合作伙伴：协作、明确双方互利点

Flags

标记事项

  • Anything surprising or concerning from the meeting
  • Follow-up research or prep needed before next interaction
  • Relationship notes worth remembering for next time
  • 会议中任何令人惊讶或值得关注的内容
  • 下次互动前需要进行的后续研究或准备
  • 下次会面值得记住的关系相关笔记

Rules

规则

  1. Be specific, not generic. "Ask about their priorities" is useless. "Ask what's changed since they raised their Series A in November" is useful. Use whatever context you have.
  2. Respect their time. A prep brief should take 2 minutes to read, not 20. A debrief should be scannable.
  3. The follow-up email is sacred. Send within 15 minutes of the call ending. This single habit changes how people perceive you. Make the draft good enough to send with minimal editing.
  4. Don't over-prepare. A founder who reads 10 pages of prep sounds rehearsed. A founder who has 3 sharp questions and genuine curiosity sounds impressive.
  5. Always end with a next step. No meeting should end without a clear next action. If the user's notes don't include one, flag it.
  1. 具体而非泛泛。 "询问他们的优先级"毫无用处。"询问他们自11月完成A轮融资以来有哪些变化"才有用。利用你掌握的所有背景信息。
  2. 尊重用户时间。 准备简报应在2分钟内读完，而非20分钟。复盘内容应便于快速浏览。
  3. 跟进邮件至关重要。 会议结束后15分钟内发送。这个习惯会改变他人对你的看法。草稿要足够完善，只需少量修改即可发送。
  4. 不要过度准备。 读了10页准备内容的创始人听起来像在背诵台词。有3个犀利问题且充满好奇心的创始人更令人印象深刻。
  5. 始终以下一步行动收尾。 任何会议都不应在没有明确后续行动的情况下结束。如果用户的笔记中没有提到，要标记出来。