Lindy meeting prep alternative that posts the brief in Slack

What the split actually is

A Lindy meeting prep alternative that posts the brief in Slack is a standing pre-call brief in the channel you already work in. Lindy's meeting prep covers attendees, LinkedIn for externals, and past meetings, and lands by email or iMessage.

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. LinkedIn research delivered by email or text is Lindy meeting prep. A morning Slack DM of your day is Lindy's daily brief. Asking Lindy in a thread after a recorded call is still notes. A standing brief from calendar, last emails, and open promises, posted in Slack without you asking, is a different product. 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. Prep versus a bot on the call is on Fireflies vs a meeting prep tool that doesn't join.

Which job each one wins

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

What Lindy meeting prep is, from its own pages

Lindy is an AI teammate that lives in Slack. Meeting prep is a built-in personal routine, not a workspace routine. On the Routines page, open Personal, find the Meeting prep card, and toggle it on. You choose which meetings get prep, when it arrives, and the format.

The meeting prep docs list five built-in sections: time, meeting name, attendees, attendee context for externals (job title, current company, LinkedIn), and a summary of previous meetings with the same people. You can write custom prep instructions for tone, structure, and detail. The built-in table does not list last emails or Slack threads. Delivery is email or SMS/iMessage. You can enable a daily digest, minutes before each meeting, or both. Scope is all meetings, or external only.

Daily brief is a different personal routine. It can land as a Slack DM, a text, or Lindy chat, once each morning. You prompt what it covers: schedule, who you are meeting, industry news, priorities. It is one morning summary of the day. It is not a five-line brief in the 10 minutes before you join.

Recording is a third routine. When it is on, Lindy sends a notetaker that joins visibly as a named participant on Google Meet, Zoom, or Teams. Recaps can go to email, SMS, Slack DM, or Lindy chat after the call. Follow-up actions can include a Slack DM of outstanding action items. That is notes after, not prep before. Work across apps with a send gate is on Lindy vs an AI employee in Slack.

What a Slack-posted brief is

The job is a few lines in Slack before you walk in, not a LinkedIn bio in your inbox, and 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.

Lindy can be @mentioned in Slack and asked for a brief. Setup docs use that as an example. That still needs you to ask. Daily brief is the Slack delivery Lindy names, and it is morning-wide. Granola writes 2-3 bullets overnight in the notepad, for external meetings on Business or Enterprise with Google Calendar. 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 walking in cold, then hunting Gmail and Slack while the client waits. 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. Last meeting's transcript is a record of that hour. The promise you typed in email later is outside that transcript unless someone said it on the recording.

Lindy lives in Slack. That does not make meeting prep a Slack post. The Meeting prep routine's delivery channel is email or SMS/iMessage. Daily brief is the routine that names Slack DM, once in the morning. An @mention is on-demand. If the leak is the 10 minutes before the fourth call, a morning digest and a text you might miss are different delivery jobs from a ping in the channel you already have open.

A second caveat is a bot on the call. Lindy's recorder joins as a named participant. Fireflies' default path is a visible notetaker. Granola listens on the device. Concrete never joins, records, or transcribes. Prep does not require a bot on the call.

A third caveat is where the brief posts. People in a Slack Connect channel can see messages from bots and apps. A half-right list of what you still owe, in the shared client channel, is an unchecked send. Keep the brief off the thread the client can read. Safety of putting an agent in that channel is on the shared-channel page.

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. LinkedIn research, a morning digest, last-call notes, and a standing brief from last emails are different products. Fund research if you do not know who they are. Fund the Slack brief if you walk in cold on a client you already talk to.
• Do not confuse Lindy's three meeting routines. Meeting prep is email or iMessage, with LinkedIn for externals. Daily brief is a morning Slack DM of the day. Recording joins visibly and can Slack-DM the recap after. Ask which one you turned on.
• Decide if a bot may join. A visible notetaker is a notes product. If the client would get stiff, skip recording or pick device audio. 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 notepad, an email you might miss, a morning Slack DM, and a ping on this meeting 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.