What is the Meeting Notes Summarizer?
Meetings produce two things that matter: decisions and action items. Everything else is context. But most people leave a meeting with notes that look like a transcript — a wall of "X said this" and "we talked about that" with no clear signal of what actually needs to happen next.
The Meeting Notes Summarizer turns raw notes, transcripts, or voice-memo text into a structured executive summary. It surfaces decisions, extracts action items with owners and deadlines, highlights the discussion points that mattered, and drafts a follow-up email you can send to attendees. Everything that should be in the post-meeting message is in one output.
It works for any meeting type: standups, client calls, project reviews, one-on-ones, board meetings, discovery calls. You paste in whatever you have (messy notes are fine — the messier the more value the tool adds) and it produces the clean version.
How It Works
Runs on Llama 3.3 70B via Groq with Gemini and OpenRouter fallbacks. Temperature 0.3 — low, because meeting summaries need to be deterministic and accurate, not creative. Max output 2,048 tokens, enough for transcripts of up to about 45 minutes of dense conversation.
The system prompt is structured to produce six output sections: meeting metadata (date, duration), key decisions, action items in table format, discussion highlights, next steps, and a ready-to-send follow-up email draft. The output format is strict because it's meant to be skimmed — the person reading the summary should be able to find the action items in two seconds.
One design decision worth calling out: the tool never invents owners or deadlines. If a task was discussed but no one was named, it writes "Unassigned" rather than guessing. That's a real-world-safe default — a summary that silently assigns work to the wrong person is worse than a summary that says "needs owner."
Who Is This Tool For?
- Project managers — Send a clean summary to stakeholders after every client or internal meeting.
- Team leads — Capture 1-on-1 action items without a dedicated note-taker.
- Account managers — Turn discovery calls into organized next-step documents for clients.
- Freelancers & consultants — Send professional post-meeting summaries that make small teams look bigger.
- Anyone who takes messy notes — Paste the mess; get back something you'd actually send.
- Sales teams — Extract deal-relevant decisions and follow-ups from recorded discovery calls.
How to Use the Meeting Notes Summarizer
- Paste your raw notes, transcript, or a summary of the conversation. Messy is fine — fragments, abbreviations, misspellings all work.
- Include any names, dates, or numbers mentioned. The tool uses these for the action items and next steps.
- Click ✨ Generate. You'll get a structured summary with metadata, decisions, action items, highlights, and a follow-up email.
- Read the action items first — this is the value. Verify owners and deadlines are correct; correct any the model captured differently than the discussion actually went.
- Review the follow-up email draft. Edit it to match your voice (the default is professional but neutral) before sending.
- Send the follow-up email to attendees and, if useful, the full summary as an attachment or thread.
Real Examples
John said we need to finish the landing page by Friday. Sarah mentioned the budget is $5000. We decided to use React. Mike will handle the design. Next meeting is Monday.
📅 MEETING SUMMARY
Date: Not specified (next meeting referenced for Monday)
Duration: Not specified
🎯 KEY DECISIONS:
1. Use React as the framework for the landing page project.
2. Landing page must be completed by Friday.
✅ ACTION ITEMS:
| # | Task | Owner | Deadline |
|---|------|-------|----------|
| 1 | Finish landing page | Unassigned (discussed by John) | Friday |
| 2 | Handle design work | Mike | Not specified |
| 3 | Confirm budget allocation ($5000) | Sarah | Not specified |
📌 DISCUSSION HIGHLIGHTS:
• Budget for the project is $5000.
• Team aligned on React as the technical choice.
• Design will be handled by Mike; development owner still to be confirmed.
⏭️ NEXT STEPS:
1. Confirm the developer who will own the landing page build.
2. Sarah to document the budget breakdown.
3. Reconvene on Monday for progress update.
📧 FOLLOW-UP EMAIL DRAFT:
Subject: Recap — Landing Page Kickoff & Next Steps
Hi team,
Thanks for the quick sync. Here's a recap of what we covered:
Decisions:
• We're building the landing page in React.
• Target completion: Friday.
Action items:
• Mike — design work
• Landing page build — owner to be confirmed
• Sarah — budget allocation ($5000)
Next meeting: Monday.
Best,
[Your Name]Client is Acme Corp, represented by their CTO Linda and PM David. They want a custom analytics dashboard for their sales team of 40. Timeline: they'd like something live in 8 weeks. Budget: flexible but prefer monthly. They currently use spreadsheets and HubSpot. Concerns: data migration and GDPR compliance. We proposed a 3-week discovery phase. They'll review internally and get back by next Wednesday. David will send us their existing spreadsheet templates. I need to follow up with a written proposal by Monday.
📅 MEETING SUMMARY
Date: Not specified (proposal due Monday, follow-up by Wednesday)
Duration: Not specified
🎯 KEY DECISIONS:
1. Proposal will include a 3-week discovery phase as the first stage.
2. Acme Corp will review internally and respond by next Wednesday.
✅ ACTION ITEMS:
| # | Task | Owner | Deadline |
|---|------|-------|----------|
| 1 | Send existing spreadsheet templates | David (Acme) | Not specified |
| 2 | Deliver written proposal | [Your team] | Monday |
| 3 | Internal review and decision | Linda & David (Acme) | Next Wednesday |
📌 DISCUSSION HIGHLIGHTS:
• Acme wants a custom analytics dashboard for their 40-person sales team.
• Target go-live: within 8 weeks.
• Budget preference: monthly billing over one-time purchase.
• Current stack: spreadsheets + HubSpot.
• Key concerns: data migration complexity and GDPR compliance.
⏭️ NEXT STEPS:
1. Prepare and send the written proposal by Monday.
2. Await Acme's internal review; expect their response by Wednesday.
3. Prepare discovery-phase scope in case the proposal is approved.
📧 FOLLOW-UP EMAIL DRAFT:
Subject: Recap — Analytics Dashboard Discovery Call
Hi Linda and David,
Thank you for the time today. Summarizing what we discussed:
What we heard:
• Custom analytics dashboard for your 40-person sales team
• Target go-live within 8 weeks
• Preference for monthly billing
• Concerns around data migration and GDPR compliance
What we proposed:
• A 3-week discovery phase as the first stage of the project
Next steps:
• We'll send a written proposal by Monday.
• David — please share the spreadsheet templates when convenient.
• We'll look for your internal review and decision by Wednesday.
Looking forward to next steps.
Best,
[Your Name]Sprint 14 retro. Went well: shipped the new onboarding flow (2 days early), zero P1 bugs. Didn't go well: two features slipped (search redesign, admin panel), standup ran over time most days, QA bottlenecked on Friday. Ideas raised: move standup to 15-min hard cap, add a second QA reviewer, split search redesign into smaller tickets. Decided to try 15-min standups starting Monday. I'll set up the QA rotation doc. Sam will break down search redesign into tickets by Wednesday. Retro every other week going forward.
📅 MEETING SUMMARY
Date: Sprint 14 retrospective
Duration: Not specified
🎯 KEY DECISIONS:
1. Standup will move to a 15-minute hard cap starting Monday.
2. Sprint retros will run every other week going forward.
3. Search redesign will be split into smaller tickets before the next sprint.
✅ ACTION ITEMS:
| # | Task | Owner | Deadline |
|---|------|-------|----------|
| 1 | Set up QA rotation document | [You] | Not specified |
| 2 | Break search redesign into smaller tickets | Sam | Wednesday |
| 3 | Enforce 15-minute standup cap | Team | Starting Monday |
📌 DISCUSSION HIGHLIGHTS:
• Wins: onboarding flow shipped 2 days early; no P1 bugs.
• Misses: search redesign and admin panel slipped; standups ran over; QA bottlenecked Friday.
• Proposed solutions: 15-min standup cap, second QA reviewer, smaller tickets.
⏭️ NEXT STEPS:
1. Implement new standup timebox.
2. Follow up on admin panel slip in next planning session.
3. Rotate QA responsibilities per the new doc.
📧 FOLLOW-UP EMAIL DRAFT:
Subject: Sprint 14 Retro — Decisions & Actions
Hi all,
Quick recap of the Sprint 14 retrospective.
What went well:
• Onboarding flow shipped 2 days early
• Zero P1 bugs
What didn't:
• Search redesign and admin panel slipped
• Standups ran over time
• QA bottlenecked on Friday
Decisions:
• 15-minute hard cap on standups, starting Monday
• Retros every other week from here
• Search redesign to be split into smaller tickets
Action items:
• [You] — QA rotation doc
• Sam — Break down search redesign by Wednesday
Thanks,
[Your Name]Technical Details
Runs on Llama 3.3 70B via Groq with Gemini and OpenRouter fallbacks. Temperature 0.3 — deliberately low, because meeting summaries must be faithful to what was said. Max output 2,048 tokens, enough for a 30–45 minute meeting transcript.
Notable design: the tool will not invent owners, deadlines, or decisions. If a task is mentioned but unassigned, it writes "Unassigned" rather than guessing. If no deadline is mentioned, it writes "Not specified." That's intentional — silently assigning work to the wrong person is a worse failure than an incomplete action item.
Rate limit: 10 requests per minute per IP. No text stored.
Frequently Asked Questions
Why Use MintAI Tools for This?
Most AI summarizers produce a narrative paragraph that reads like a book report. This tool is built around the two things meetings actually produce — decisions and action items — and structures the output so a manager can scan it in 30 seconds. It also drafts the follow-up email, which is the piece most people dread writing. And it never invents owners or deadlines, because accuracy matters more than completeness.