If you're using a dedicated tool (Fathom, Otter) the prompt is mostly hidden. If you're using Claude or ChatGPT directly, the prompt IS the product. Bad prompt = bad summary, every time. This is the library of prompts that actually produce useful output, organized by meeting type.
Three principles for every meeting summary prompt: (1) specify the meeting type, (2) name the audience, (3) ask for structured output (decisions, action items, unresolved questions) — not 'a summary.' Templates below for sales calls, board meetings, customer interviews, 1:1s, and decision meetings.
Every good meeting summary prompt does three things:
1. Specifies meeting type. 'Sales discovery call' produces different output than 'board meeting' than 'cross-functional sync.' Tell the AI which it is.
2. Names the audience. A summary for attendees is different than a summary for someone catching up. 'Write for [audience who wasn't there]' radically changes what gets included.
3. Asks for structured output. Don't say 'summarize this.' Name the sections you want: decisions, action items with owners and deadlines, unresolved questions, key context.
Use for strategy meetings, planning sessions, budget discussions, roadmap reviews.
You are summarizing a decision meeting for people who weren't there.
Read the transcript below and produce:
1. Headline (1 sentence) - the single most important decision
2. Decisions made - what was decided, by whom, with what context
3. Action items - task, owner, deadline. Bullet list.
4. Unresolved questions - what got raised but didn't get answered
5. Risks or red flags - anything that should be escalated
Skip greetings, scheduling chat, and tangents. Maximum 300 words. Transcript: [paste]
Use for new customer conversations, qualification calls, intro meetings.
You are summarizing a sales discovery call for the account executive's CRM record and for cross-functional alignment.
Read the transcript below and produce:
1. Prospect company + role of person on call
2. Their stated problem (in their words)
3. Their stated success criteria
4. Budget and timeline indicators (direct or implied)
5. Decision process they described (who else is involved, what's the next step)
6. Objections or concerns raised
7. Competitive context (what else they're evaluating)
8. Next steps committed to on the call
Capture quotes verbatim where they're memorable. Maximum 400 words. Transcript: [paste]
Use for product research, user interviews, customer success conversations.
You are summarizing a customer interview for the product team. The audience is product managers and designers who weren't on the call.
Produce:
1. Customer profile (role, company stage, use case)
2. Their current workflow (in their words)
3. Specific pain points described
4. What they wish existed (quote where possible)
5. What they've tried and rejected
6. Any feature requests, with the underlying problem
7. Quotes worth sharing (verbatim, with context)
Be precise about what they said vs what they meant. Don't speculate. Transcript: [paste]
Use for board meetings, investor updates, executive committee reviews.
You are producing the official board meeting summary. Audience: board members and senior executives who attended, plus key staff who didn't.
Produce:
1. Attendees (board + management)
2. Quorum confirmation if applicable
3. Key reports presented (CEO update, financial, departmental)
4. Decisions and votes taken (with motion, mover, seconder, vote count)
5. Action items assigned (owner, deadline)
6. Issues tabled for next meeting
7. Date of next meeting
Maintain formal tone. Maximum 600 words. Transcript: [paste]
Use for performance discussions, career conversations, decisions about people. Skip for routine weekly 1:1s.
You are summarizing a 1:1 conversation for the manager's personal record. This is private — not shared.
Produce:
1. Topics discussed (high level)
2. Commitments made (by manager, by report)
3. Concerns raised (by either party)
4. Career or development discussion notes
5. Follow-up needed before next 1:1
Be discrete. Note tone if it shifted notably during the conversation. Maximum 250 words. Transcript: [paste]
Use for projects spanning multiple teams (marketing + sales + product + CS).
You are summarizing a cross-functional sync for everyone on the project team plus their managers.
Produce:
1. Project status (in 1 sentence)
2. What each team committed to before next sync
3. Blockers raised and who owns unblocking
4. Decisions made on open questions
5. New open questions raised
6. Date and agenda for next sync
Be precise about ownership — don't let action items have no owner. Transcript: [paste]
Every team has its own vocabulary, KPIs, and context. Two ways to make the templates above more useful:
1. Add company context. 'Our ICP is mid-market healthcare SaaS, our top competitor is X' helps the AI flag the right things.
2. Add output preferences. 'Format action items as: @owner — task (due date)' produces output your team can copy into your task system without reformatting.
Save the customized version in a Claude Project so you don't reconfigure every time.