Fireflies vs a meeting prep tool that doesn't join the call

What the split actually is

Fireflies is an AI notetaker that joins Zoom, Meet, or Teams as a visible participant and writes a transcript after the call. A meeting prep tool that doesn't join is a standing brief before you walk in: who is coming, last emails and Slack threads, and what is still open.

Founders, account leads, and CS leads run back-to-back check-ins. By the fourth call the prep is gone, and the first minutes are a search through Gmail and Slack for what was said and promised. Walking in cold is the leak. A QBR and a 15-minute client call have the same gap.

The buying prompt collapses two jobs. Notes after the call are a recorder. A standing brief from calendar, last emails, and open promises is prep. Fireflies also ships Meeting Prep from prior transcripts, and a desktop path that captures with no bot. Those are still notes products. The standing brief from calendar and email is on AI that preps you before every meeting. The owed list for a client check-in is on how to prepare for a client check-in.

Which job each one wins

Each row names the job, the product that wins it, and why. Fireflies still wins the rows it actually wins.

What Fireflies is, from its own pages

Fireflies is an AI notetaker. The default path is a bot. Auto-join is set to all meetings with a web-conf link. It appears as Fireflies.ai Notetaker, may wait to be admitted, and you cannot hide it in the participant list. Paid plans can rename the bot; visibility stays. Invite fred@fireflies.ai, or it joins from the calendar.

The desktop app can skip the bot. Take Notes captures system audio. Nothing joins the call. You get a transcript and summary, not speaker labels and not a saved audio or video file. Sales Assist is bot-only. The Chrome extension captures Google Meet without a bot. Desktop Take Notes still records the room. It is notes without a participant, not a prep-only product.

Meeting Prep sits on Personal Assistant, Pro and above. It pulls key points and open action items from previous meetings with the same attendees. The prep email is 1 hour before a recurring meeting. You turn it on; it is not on by default. It uses AI credits. If you have never met them, you get the attendee list and the calendar agenda. Promises that live in Gmail or Slack after the call are outside that brief.

What a no-join prep tool is

The job is a few lines before you walk in, not a transcript after you hang up. Who is coming. The last emails and Slack threads with them. What was promised and is still open. You should be able to read it between back-to-back calls. LinkedIn bios and web research are a different job. Last meeting's notes are a record of that hour.

Granola is the closest neighbor that never puts a bot on the call. The notepad is the product. Briefs land overnight in the meeting note, 2-3 bullets, for external meetings when you are on Business or Enterprise with Google Calendar. Gmail is optional. Internal meetings get no brief. Delivery is the notepad, not Slack.

Concrete is an AI employee that works in existing Slack channels. Before each Google Calendar meeting it posts a brief in Slack or Telegram: who is attending, the last emails and Slack threads with them, and what was promised to them and is still open. It does not join, record, or transcribe the meeting. It does not research attendees on LinkedIn or the web. It is in design-partner preview. The longer thesis is on the vision page. Open promises across Slack and Gmail are a neighboring job, on how to stop forgetting emails you promised and commitments from Slack threads.

The caveat that should decide the shortlist

The failure operators name first is a bot on the call. A visible notetaker changes the room. Some clients get stiff. Fireflies' own FAQ says you cannot hide the bot's presence; it stays in the participant list for compliance. Lindy's recorder joins as a named participant. Granola listens on the device. Concrete never joins, records, or transcribes.

Skipping the bot does not skip capture. Desktop Take Notes still writes a transcript from your computer's audio. Fireflies asks for consent notifications. The Chrome extension still transcribes Google Meet. If the leak is that anyone is recording, a no-bot notetaker is the same job with a quieter entrance. A prep tool that never joins also never records.

The quieter failure is the next call with the same client starting from zero. Last meeting's transcript is a record of that hour. The promise you typed in email later, or the open ask in Slack Connect, is not in that transcript unless someone said it on the recording. Fireflies Meeting Prep is last-call notes. Keep a pre-meeting brief off a Slack Connect thread the client can see.

What each one costs (October 2026)

Every figure below is from the vendor's own pricing page or docs, read 12 October 2026. Concrete has no public price.

A practical setup for back-to-back calls

This is the boring version that holds when the founder or account lead still owns the check-in. Pin it before the next back-to-back block.

• Name the leak. Notes after the call and a standing brief from last emails are different products. Fund notes if you want a record. Fund the brief if you walk in cold.
• Decide if a bot may join. A visible Fireflies.ai Notetaker is the default. If the client would get stiff, switch auto-join to only when you invite fred@fireflies.ai, use Take Notes, or skip recording. Prep does not require a bot on the call.
• Know which Fireflies capture is on. Notetaker in the participant list means bot capture, with saved audio and speaker labels. Take Notes means device audio, no bot, no saved recording. Meeting Prep is last-call notes emailed 1 hour before a recurring meeting.
• Put the brief where you will see it. A 5-line brief only helps if it lands in the 10 minutes before you join. An overnight notepad, an email you might miss, and a Slack ping are different delivery jobs.
• Ask for what is still open. Who they are is research. What we agreed and what is still open is the check-in. Last emails and Slack threads beat a bio when you already know the person.
• Keep the brief off Slack Connect. People in a shared client channel can see bot messages. Post the owed list in an internal channel, not in the thread the client is on.