30 Claude Prompts That Build Meeting Agendas

You are a startup COO who prepares tight, decision-oriented board agendas. <context> I need a timed agenda for a quarterly board meeting, returned as a self-contained, ready-to-use document that respects directors' time and drives decisions. </context> <inputs> - Company stage and board size: [STAGE, NUMBER OF DIRECTORS] - Meeting length: [E.G. 90 MIN] - Headline results this quarter: [KEY METRICS VS PLAN] - Decisions or approvals needed: [E.G. BUDGET, HIRES, OPTION POOL] - Strategic topic for discussion: [ONE DEEP-DIVE TOPIC] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Materials). Include: approval of prior minutes and consent agenda, CEO update and results vs plan, financials and runway, the key metrics dashboard, one strategic deep-dive discussion, formal decisions and votes, an executive session note, and action items. Assume pre-read materials were sent; keep the meeting for discussion and decisions, not reading slides. </task> <constraints> - Route routine items through a consent agenda to protect time for the deep-dive. - Clearly mark which items are FYI, discussion, or decision; minutes sum to length. - Reserve time for executive session. </constraints> <format> Return the agenda as a table artifact, then a short note on what to include in the pre-read pack. </format>

You are a chief of staff who runs the weekly executive team meeting. <context> I need a timed agenda for the weekly leadership team meeting, returned as a self-contained, ready-to-use document focused on decisions and cross-functional alignment. </context> <inputs> - Leadership roles present: [E.G. CEO, CPO, CTO, CFO, CMO] - Meeting length: [E.G. 60 MIN] - Company priorities this quarter: [TOP 3] - Metrics we track weekly: [KEY NUMBERS] - Open decisions or escalations: [WHAT NEEDS THE ROOM] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Owner). Include: a quick metrics scorecard review (flag red only), progress against quarterly priorities, a decisions block for escalations that need the leadership team, cross-functional issues and dependencies, a people/hiring pulse, and a crisp action-and-owner close. Write prompts that keep the room on decisions, not departmental status. </task> <constraints> - Only discuss metrics that are off-track; skim the green. - Reserve the bulk of time for decisions and cross-functional issues; minutes sum to length. - Every escalation ends in a decision, an owner, or a scheduled follow-up. </constraints> <format> Return the agenda as a table artifact, then a short note on maintaining a rolling decisions log across weeks. </format>

You are a head of communications who designs engaging company all-hands meetings. <context> I need a timed agenda for a monthly all-hands, returned as a self-contained, ready-to-use document that informs, aligns, and energizes the whole company. </context> <inputs> - Company size and format: [HEADCOUNT, IN-PERSON / REMOTE / HYBRID] - Meeting length: [E.G. 45 MIN] - Wins and news this month: [HIGHLIGHTS] - The one message leadership wants to land: [KEY THEME] - Recognition and new hires: [WHO TO CELEBRATE] </inputs> <task> Build a timed agenda as a table (Time | Segment | Speaker | Purpose). Include: a warm opener and the month's theme, business and progress update tied to company goals, a team or customer spotlight, wins and recognition, new-hire welcomes, a short 'what's next' preview, and a live Q&A with pre-submitted questions. Balance information with celebration and keep energy up. </task> <constraints> - Tie updates back to the company's goals so people see how their work connects. - Protect real time for live Q&A; assign a speaker to every segment; minutes sum to length. - Include recognition; avoid a wall of one-way slides. </constraints> <format> Return the agenda as a table artifact, then a short note on collecting Q&A questions in advance. </format>

You are a strategy facilitator who runs multi-hour leadership planning offsites. <context> I need a timed agenda for a strategic planning offsite, returned as a self-contained, ready-to-use document that moves from reflection to a concrete plan. </context> <inputs> - Planning horizon: [E.G. NEXT YEAR / NEXT QUARTER] - Attendees: [ROLES] - Total length: [E.G. HALF-DAY / FULL DAY] - Big questions to answer: [2-3 STRATEGIC QUESTIONS] - Current context: [MARKET, RESULTS, CONSTRAINTS] </inputs> <task> Build a timed agenda as a table (Time | Block | Activity | Output) with breaks. Include: a look-back on the last period, an honest situation assessment (wins, misses, market), a vision/priorities discussion, structured working sessions on the big questions, converging on 3-5 priorities, drafting objectives and owners, and a commitment-and-next-steps close. Specify the facilitation method for each working block (e.g. silent brainstorm, dot voting). </task> <constraints> - Include breaks and vary the format so energy holds across hours. - End with 3-5 owned priorities and draft objectives, not just discussion; total time sums to the length. - Reserve divergence before convergence in each working block. </constraints> <format> Return the agenda as a table artifact, then a short note on turning the priorities into quarterly OKRs afterward. </format>

You are a founder who runs concise, high-trust investor update calls. <context> I need a timed agenda for a monthly or quarterly investor update call, returned as a self-contained, ready-to-use document that builds confidence and gets useful help. </context> <inputs> - Round stage and investors: [STAGE, WHO'S ON THE CALL] - Meeting length: [E.G. 30 MIN] - Key metrics and trajectory: [GROWTH, REVENUE, RUNWAY] - Wins and challenges this period: [BOTH] - Specific asks: [INTROS, HIRES, ADVICE] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Notes). Include: a headline summary (one line: are we on track), key metrics vs last update, wins, honest challenges and how we're addressing them, a strategic topic or decision for their input, and a clear specific-asks block. End with the asks front-of-mind, not buried. Write prompts that keep it candid and efficient. </task> <constraints> - Be transparent about challenges; investors trust founders who name problems early. - Make the asks concrete and specific (names, roles, intros); minutes sum to length. - Metrics compared to the prior update, not just absolute numbers. </constraints> <format> Return the agenda as a table artifact, then a short note on the written update to send alongside the call. </format>

You are a scrum master who facilitates retros that produce real change. <context> I need a timed sprint retrospective agenda, returned as a self-contained, ready-to-use document that ends with committed improvement actions. </context> <inputs> - Team and sprint just finished: [NAME, SPRINT] - Meeting length: [E.G. 45 MIN] - Team mood or recent context: [ANYTHING NOTABLE, GOOD OR BAD] - Prior retro actions: [DID WE FOLLOW THROUGH?] </inputs> <task> Build a timed agenda as a table (Time | Segment | Activity | Output). Include: setting the stage and psychological-safety reminder, reviewing last retro's action items, gathering data (what went well / what didn't / puzzles), generating insights on the top themes, deciding 1-3 concrete improvement actions with owners, and a quick closing pulse. Specify the facilitation technique for the data-gathering block. </task> <constraints> - Start by reviewing whether last retro's actions actually happened. - End with no more than three owned, specific actions; minutes sum to length. - Keep it blameless; focus on the system, not individuals. </constraints> <format> Return the agenda as a table artifact, then a short note on tracking the actions so the next retro can check them. </format>

You are an SRE lead who runs blameless post-mortems. <context> I need a timed blameless post-mortem agenda for an incident or a completed project, returned as a self-contained, ready-to-use document focused on learning and prevention. </context> <inputs> - What happened: [INCIDENT OR PROJECT SUMMARY] - Impact: [WHO/WHAT WAS AFFECTED, DURATION] - Meeting length: [E.G. 60 MIN] - Attendees: [ROLES INVOLVED] - Timeline available: [ROUGH SEQUENCE OF EVENTS] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Output). Include: a blameless-framing opener, a factual timeline walkthrough, impact assessment, root-cause analysis (what happened and why, using 5-whys or similar), what went well in the response, what made it worse, and a prioritized corrective-actions block with owners and dates. Write prompts that keep it about systems, not blame. </task> <constraints> - Strictly blameless; no naming individuals as causes. - Distinguish contributing factors from root cause; minutes sum to length. - Every corrective action gets an owner, a date, and a priority. </constraints> <format> Return the agenda as a table artifact, then a short note on the post-mortem write-up to publish afterward. </format>

You are an engineering manager who runs a broader quarterly retro beyond individual sprints. <context> I need a timed quarterly team retrospective agenda, returned as a self-contained, ready-to-use document that reflects on the whole quarter and resets for the next. </context> <inputs> - Team and quarter: [NAME, QUARTER] - Meeting length: [E.G. 90 MIN] - What we shipped and missed: [HIGHLIGHTS AND GAPS] - Team health signals: [MORALE, ATTRITION, WORKLOAD] - Themes I suspect matter: [E.G. PROCESS, COLLABORATION, TOOLING] </inputs> <task> Build a timed agenda as a table (Time | Segment | Activity | Output) with a break. Include: a look-back on quarterly goals and outcomes, a team-health check-in, structured reflection across themes (process, collaboration, tooling, growth), pattern-finding across the quarter (not one-off issues), agreeing on 2-4 systemic improvements for next quarter with owners, and a forward-looking close. Specify facilitation methods. </task> <constraints> - Focus on recurring patterns and systemic issues, not single incidents. - End with 2-4 owned systemic improvements; total time sums to the length. - Include a genuine team-health check, not just delivery metrics. </constraints> <format> Return the agenda as a table artifact, then a short note on connecting the improvements to next quarter's planning. </format>

You are an agile coach who facilitates the Start-Stop-Continue format. <context> I need a timed Start-Stop-Continue retrospective agenda, returned as a self-contained, ready-to-use document with a fillable board and clear timeboxes. </context> <inputs> - Team or group: [WHO] - Period being reviewed: [SPRINT / MONTH / PROJECT] - Meeting length: [E.G. 45 MIN] - How we'll capture input: [WHITEBOARD / DIGITAL BOARD / STICKIES] </inputs> <task> Build a timed agenda as a table (Time | Segment | Activity | Output), and include a ready-to-use three-column board template labeled Start / Stop / Continue with example prompts under each. Agenda covers: framing and the format explanation, silent individual brainstorming into the three columns, grouping and discussing themes, dot-voting on top items, and committing to specific actions with owners. Provide the exact prompts to display. </task> <constraints> - Silent generation before discussion to avoid anchoring on the loudest voice. - End with owned actions drawn mostly from the Start and Stop columns; minutes sum to length. - Keep timeboxes visible so no single column dominates. </constraints> <format> Return both the agenda table and the Start/Stop/Continue board template as artifacts, then a short note on running the dot-vote. </format>

You are a product operations lead who runs cross-functional launch retros. <context> I need a timed retrospective agenda for a product or feature launch, returned as a self-contained, ready-to-use document that captures lessons across all the functions involved. </context> <inputs> - What launched and when: [PRODUCT/FEATURE, DATE] - Functions involved: [E.G. PRODUCT, ENG, MARKETING, SUPPORT, SALES] - Meeting length: [E.G. 60 MIN] - Launch results vs goals: [METRICS VS TARGET] - Notable issues during launch: [WHAT WENT SIDEWAYS] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Output). Include: launch results vs goals, a phase-by-phase walkthrough (planning, build, GTM, launch day, post-launch), what each function felt went well and poorly, cross-functional coordination gaps, customer and support feedback, and a prioritized lessons-and-actions block for the next launch with owners. Write prompts that pull honest input from every function. </task> <constraints> - Give each function airtime; don't let one team's narrative dominate. - Translate lessons into a reusable launch checklist update; minutes sum to length. - Compare results to the original goal, not a moved target. </constraints> <format> Return the agenda as a table artifact, then a short note on updating the launch playbook with what you learned. </format>

You are a solutions consultant who runs discovery calls that qualify and impress. <context> I need a timed discovery-call agenda for a first meeting with a prospective client, returned as a self-contained, ready-to-use document that uncovers needs and sets up next steps. </context> <inputs> - Prospect and their business: [COMPANY, INDUSTRY] - What we sell: [PRODUCT/SERVICE] - Meeting length: [E.G. 30 MIN] - What I already know: [ANY CONTEXT FROM OUTREACH] - My goal for this call: [QUALIFY / SCOPE / BOOK DEMO] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Questions). Include: a rapport and agenda-setting opener, discovery questions on their current situation, goals, pain, and impact of not solving it, a light qualification pass (timeline, budget, decision process), a tailored overview of how we can help (only after listening), handling initial questions, and a clear next-step booking. Write specific, open discovery questions per segment. </task> <constraints> - Spend most of the call listening; pitch only after you understand their pain. - End by booking a concrete next step, not 'I'll send some info'; minutes sum to length. - Qualify gently without turning it into an interrogation. </constraints> <format> Return the agenda as a table artifact, then a short note on the recap-and-next-steps email to send after. </format>

You are a customer success director who runs QBRs that renew and expand accounts. <context> I need a timed QBR agenda for an existing client, returned as a self-contained, ready-to-use document that proves value and shapes the next quarter. </context> <inputs> - Client and their goals: [ACCOUNT, WHAT THEY'RE TRYING TO ACHIEVE] - Meeting length: [E.G. 60 MIN] - Results and usage this quarter: [OUTCOMES, ADOPTION, ROI] - Open issues or risks: [SUPPORT TICKETS, CHURN SIGNALS] - Expansion or renewal context: [UPCOMING RENEWAL, UPSELL POTENTIAL] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Owner). Include: alignment on their business goals, a value-and-ROI review against those goals, adoption and usage insights, open issues and how we're resolving them, a roadmap or new-capabilities preview relevant to them, a forward plan for next quarter with success metrics, and next steps (including renewal or expansion where relevant). Write prompts that keep it about their outcomes, not our features. </task> <constraints> - Lead with their goals and the value delivered, not a product update. - Tie every roadmap item to one of their stated goals; minutes sum to length. - Address risks openly rather than avoiding them. </constraints> <format> Return the agenda as a table artifact, then a short note on the QBR summary deck to leave the client with. </format>

You are an account executive who runs tailored product demos that advance deals. <context> I need a timed agenda for a sales demo meeting, returned as a self-contained, ready-to-use document that keeps the demo tied to the buyer's needs and drives to a next step. </context> <inputs> - Prospect and use case: [COMPANY, WHAT THEY WANT TO SOLVE] - Attendees and roles: [WHO'S ON THE CALL] - Meeting length: [E.G. 45 MIN] - Their known priorities and pain: [FROM DISCOVERY] - Desired next step: [PROPOSAL / TRIAL / STAKEHOLDER MEETING] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Owner). Include: a recap of their priorities to confirm alignment, an agenda check with attendees, a tailored demo mapped only to their stated pains (feature -> their outcome), handling questions and objections, discussion of pricing/process at a high level, and a mutual-next-step close with dates. Write prompts that keep the demo problem-led, not a feature tour. </task> <constraints> - Demo only the capabilities that map to their stated pain; skip the feature tour. - Confirm their priorities before demoing anything; minutes sum to length. - End with an agreed, dated mutual next step. </constraints> <format> Return the agenda as a table artifact, then a short note on the follow-up and mutual action plan to send. </format>

You are an account manager who runs efficient recurring client status meetings. <context> I need a timed agenda for a recurring client status or check-in meeting, returned as a self-contained, ready-to-use document I can reuse each time. </context> <inputs> - Client and engagement: [ACCOUNT, WHAT WE'RE DELIVERING] - Cadence and length: [E.G. BIWEEKLY, 30 MIN] - Current workstreams: [WHAT'S IN FLIGHT] - Open items and decisions needed: [FROM CLIENT OR US] - Any concerns to address: [SATISFACTION, SCOPE, TIMELINE] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Owner). Include: a quick recap of action items from last time, progress on active workstreams against the plan, decisions or inputs we need from the client, upcoming milestones and any risks, an open-floor for client concerns, and a next-steps-and-owners close. Write prompts that keep the client informed and surface issues early. </task> <constraints> - Start by closing out last meeting's action items so nothing slips. - Explicitly ask what the client needs from us and vice versa; minutes sum to length. - Keep it concise; this is a check-in, not a full review. </constraints> <format> Return the agenda as a table artifact, then a short note on the brief recap email to send after each session. </format>

You are a customer success manager who runs renewal and expansion conversations. <context> I need a timed agenda for a contract renewal or upsell conversation with an existing client, returned as a self-contained, ready-to-use document that reinforces value before discussing terms. </context> <inputs> - Client and current contract: [ACCOUNT, PLAN, RENEWAL DATE] - Meeting length: [E.G. 30 MIN] - Value delivered so far: [OUTCOMES, ROI] - Expansion opportunity: [NEW SEATS, MODULES, TIER] - Any renewal risk: [BUDGET PRESSURE, COMPETITOR, LOW USAGE] </inputs> <task> Build a timed agenda as a table (Time | Segment | Purpose | Owner). Include: a warm opener, a recap of value and outcomes delivered, a check on their goals for the coming period, a natural bridge to how expanded usage supports those goals, the renewal terms and any expansion proposal, handling of objections or budget concerns, and a clear next-step-and-timeline close. Write prompts that lead with value before price. </task> <constraints> - Establish delivered value before mentioning renewal or price. - Frame any upsell around their goals, not our quota; minutes sum to length. - Address renewal risks directly with a plan, not avoidance. </constraints> <format> Return the agenda as a table artifact, then a short note on the renewal proposal or summary to send afterward. </format>