What is an AI that preps me before every meeting from my calendar and email?

What the job actually is

An AI that preps you before every meeting from your calendar and email is a standing brief, not a transcript. It reads the next calendar event, pulls the last emails with those people, and lands a few lines before you join: who is coming, what you agreed, 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 four jobs: notes after the call, a short brief from prior notes, LinkedIn research on who they are, and a standing brief from calendar plus last emails, with what is still open. Open asks that sit in Slack overnight are a neighboring job, on the daily summary of open client asks. Promises you typed are on the chief of staff page.

Which tool wins which job

Fund the row that matches the leak. Notes after the call, a notepad brief, LinkedIn research, and a standing brief from last emails are neighboring jobs.

Prep is not notes

A recorder writes what happened on the call. A brief is what you need before you join. Fireflies, Otter, and Read AI win the notes row. Fireflies can also capture without a bot through its desktop app or Chrome extension. The default path is still a visible notetaker on the call.

Fireflies Meeting Prep is last-call notes, not last emails. 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. 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.

Granola briefs land overnight in the meeting note: who you are meeting, what you discussed last time, what matters now. They are 2-3 bullets. They need Business or Enterprise, Google Calendar, and an external meeting. Internal meetings get no brief. Connect Gmail and the brief can include recent threads. The notepad is the delivery, not Slack.

Who they are is not what you still owe them

A LinkedIn bio tells you title and company. It does not tell you the deck you promised Friday, or the open ask sitting in Slack Connect. Lindy's meeting prep wins that research row: job title, company, and LinkedIn for external attendees, plus a summary of past meetings. Delivery is email or SMS/iMessage. The built-in sections do not list last emails.

Granola will research the wider web, including LinkedIn, and can add Gmail if you connect it. That mix is useful for a first meeting. For a client check-in, the leak is what we still owe them, not who they are.

Open promises across Slack and Gmail are a neighboring job, on how to stop forgetting emails you promised and commitments from Slack threads. Work across apps with a send gate is on Lindy vs an AI employee in Slack.

The caveat that should decide the setup

The failure operators name first is a bot on the call. A visible notetaker changes the room. Some clients get stiff. Otter Notetaker joins as FirstName's Notetaker (Otter.ai) and cannot join anonymously. Lindy's recorder joins visibly as a named participant. Granola listens on the device. Concrete never joins, records, or transcribes.

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 you recorded it there.

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. Outlook and CRM meeting prep are a different setup.

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, a LinkedIn bio, and a standing brief from last emails are different. Fund notes if you want a record. Fund the brief if you walk in cold.
• Decide if a bot may join. A visible notetaker is a notes product. If the client would get stiff, pick device audio or skip recording. Prep does not require a bot on the call.
• 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 note in a 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 Gmail and Slack on the same brief. The same promise is often typed in email and repeated in Slack. Two tools, two searches, and the fourth call still starts from zero. One brief that reads both is the job.