Meeting notes are worth more when they’re multiplayer.
Managers, customers, prospects, PMs, and now platforms.
@readai_ MCP server is turning meetings into multi-platform context, so we’ve shipped a round of updates to lean in.
read.ai/post/new-in-the-read…
Great presentations start with great conversations.
Now @readai_ connects with @gammaapp, so the ideas, decisions, and next steps from your meetings can become the starting point for your next presentation.
The meeting moves the story forward. Your deck should too.
read.ai/post/read-ai-and-gam…
every week someone tells me they’re going to vibe-code their own @readai_ alternative over the weekend.
wish them the best, here’s the backlog of things to make sure to include:
> Join the right meeting, even when the calendar invitation changes five minutes beforehand.
> Know when not to join, because an unwanted guest is a terrible feature.
> Tell everyone in the meeting they’re being recorded, on every platform, because it’s the right thing to do.
> Be in two meetings at once when neither you nor your laptop physically can.
> Handle the meeting that starts late and the one that never ends.
> Keep recording when someone’s Wi-Fi briefly gives up on the conversation.
> Capture usable audio from people with very different microphones and rooms.
> Give people another way to capture calls when a agent cannot join.
> Turn an uploaded recording into something useful, not another file to manage.
> Process a one-hour meeting without making users wait another hour.
> Recognize speech when people interrupt, mumble, or eat lunch beside the microphone.
> Tell speakers apart without confidently assigning everyone else’s commitments to you.
> Keep the transcript synchronized with the moment someone wants to replay.
> Make names, acronyms, and industry jargon survive transcription reasonably intact.
> Know when the audio is unclear instead of inventing a polished sentence.
> Summarize what mattered, not merely what consumed the most airtime.
> Separate decisions from suggestions that sounded briefly popular.
> Extract action items with owners, not just impressive-sounding verbs.
> Distinguish a real deadline from someone saying “maybe next week.”
> Catch the question everyone discussed but nobody actually answered.
> Preserve the nuance that gets lost when a disagreement becomes one bullet.
> Attribute claims to the people who actually made them.
> Organize a long conversation so people can find its turning points.
> Make a recap useful to someone who missed the meeting, or has thirty seconds before the next one.
> Handle the person who leaves early but still owns an action item.
> Show live notes that stay useful as the conversation changes direction.
> Help people notice they have spent half the meeting on one question.
> Measure participation without pretending talk time equals contribution.
> Surface useful coaching without embarrassing someone for saying “um.”
> Make reports easy to skim and easy to investigate further.
> Give users control over which meetings become reports.
> Keep reports private by default when the context calls for it.
> Keep personal notes distinct from what the whole meeting can see.
> Let someone share the useful takeaway without sharing every private aside.
> Search across months of meetings without returning twenty identical weekly syncs.
> Let people search their work without learning a query language.
> Answer with evidence someone can inspect rather than a plausible-sounding guess.
> Admit when the available material does not support an answer.
> Handle follow-up questions without forgetting what “that decision” refers to.
> Connect related conversations without confusing two projects with similar names.
> Notice when a newer decision superseded an older plan.
> Let a user find their own commitments before someone else reminds them.
> Help teams find recurring themes without reading every individual report.
> Make setup simple enough that someone reaches value before reading documentation.
> Make settings understandable before somebody discovers them during an awkward call.
> Give people a sensible experience on the web, desktop, and phone.
> Integrate with Zoom, Teams, Meet, Slack, Gmail, Outlook, Salesforce, HubSpot, and Notion, then keep every one working when they ship updates.
> Make the product useful to the person who never opens a dashboard.
> Make it useful to the person who opens it after every meeting.
> Give administrators control without making every employee file a ticket.
> Support company sign-in rules without turning login into an obstacle course.
> Remove access promptly when someone leaves an organization.
> Keep one customer’s information out of another customer’s answers.
> Limit internal access to customer conversations and account for its use.
> Give organizations a way to inspect important administrative activity.
> Apply retention settings to the data they are supposed to cover.
> Make deletion actually delete what users expect it to delete.
> Don’t train on your users’ data by default.
> Protect recordings in transit and wherever they are stored.
> Design privacy controls for sensitive conversations, not just the easy meetings.
> Document security practices well enough for a real customer review.
> Keep the service responsive when everyone’s meetings end at the hour.
> Detect a broken recording before the customer does.
> Know whether a missing report is delayed, failed, or never recorded.
> Support customers when the answer matters more than the bug report.
> Keep improving accuracy as meeting habits, terminology, and expectations change.
> Maintain all of this while operating systems and meeting platforms change.
Read AI is now Read SI.
Artificial intelligence will now be referred to as “super intelligence,” President Trump said at the U.N. General Assembly.
“All of United States documents, and hopefully the world’s, will be changed to use the much more accurate term ‘super.’” wapo.st/4yKXYHM
If you are building anything in consumer AI, this episode with @petersellis should be added to your context window.
Also Peter is an investor in @ReadAI_ if you are looking for the banana stand of meeting notetakers.
My biggest takeaways from @petersellis:
1. There is always money in the banana stand. The highest-ROI growth move is usually investing in the core product, vs. chasing side quests. At @Snap, after the disastrous 2018 redesign caused DAU to flatten, the team laser-focused on performance for existing users—particularly on Android—and sparked a multi-year growth renaissance. At @Discord, rather than chasing @Midjourney’s moment, the team focused on making Discord the best place to play intentional multiplayer games with friends. The result was some of the fastest growth in history.
2. Great taste is knowing when to stop. Peter spent seven years watching @evanspiegel personally say no to better ideas than most consumer startups ever launch. His take on taste is that the difference between people with it and people without it is that the ones with taste stop one step before everyone else does. They know when a good idea’s time has come, or when it has to sit on the shelf a bit longer.
3. Spend your time on your best people, not the ones struggling. Against human instinct, which is to help whoever looks like they’re drowning, Peter consistently loads up his strongest performers with more responsibility and decisions until he finds the limit of what they can handle.
4. The median PM is bad, and even net negative, because the skills of a great product leader are the skills of a founder or an executive, so top-percentile PMs leave for founder and exec seats. On the other hand, mediocre PMs fight to stay in the job because the job pays well and has status. ZIRP made it worse because it was the most lucrative role in tech for non-technical people, with the most subjective sense of what great looks like. A lot of engineers and designers conclude “PMs suck” because they have mostly met the bottom of that distribution.
5. Great PMs hold three contradictory traits. First: deep confidence bordering on arrogance, paired with genuine humility. Second: extreme organizational discipline, paired with near-pathological comfort with ambiguity. Third: a long-term vision that’s always holding in the background, paired with a day-to-day bias for action.
6. Peter designs product teams like terrorist organizations: a shared ideology and an explicit map of who is trusted with which decision. You will almost never hear a leader tell their team to collaborate less, but coordination makes you as slow as the slowest node, which compounds and slows organizations down. The antidote is a strong shared ideology and clear DRIs who can make confident, founder-quality decisions quickly.
7. Optimize consumer products for daily active use. Days map to real human cycles; weeks and months are weaker. One daily user equals roughly 30 monthly users in simple math, which is why elite consumer products run extremely high DAU/MAU. Moving that ratio a few basis points often beats acquiring a pile of soft monthly actives and hoping they retain. DAU/MAU is next-day retention under another name.
8. Define a “Core Product Value” that's both a memorable phrase and a set of metrics that measure it. Peter built this framework at both Snap and Discord. At Snap, it was “the fastest way to share a moment with the people you care about,” which you could actually decompose into metrics: time to load (fast), camera-open-to-share rate (share a moment), best friends engagement (people you care about). At Discord, it was “the best way to talk and hang out with your friends before, during, and after playing games,” with a corresponding L7 and Lness definition that made its way into the growth playbooks. The phrase without the metrics is a slogan; the metrics without the phrase are a dashboard. You need both.
9. The most important career decision you make as a PM is who you choose to marry. This has compounding effects on your career that no podcast, course, or mentor can replicate. The intellectual sounding board, the support system, the person who challenges you to grow—that relationship shapes your capacity to operate at the highest level in ways that are genuinely hard to quantify but nearly impossible to overstate.
Claude for Financial Advisors is now available, but it has one big gap, meetings.
Meetings are the core of a financial advisors day, talking with clients and prospects to build the right plan.
This gap is filled with @readai_ Claude Connector.
claude.com/blog/claude-for-f…
Read AI's Claude Connector enables Financial Advisors to pull in conversations from Zoom, Teams, Meet, and more directly into Claude.
claude.com/connectors/read-a…
As a system of record for meetings, Financial Advisors are able to pull in online and offline conversations (via the mobile app) to capture a holistic picture on what the client needs and work through @claudeai custom workflows to deliver outcomes.
Introducing @ReadAI_ headless meeting agent.
Meeting notes are a prompt away, your attendence is optional.
Available as a @claudeai connector.
claude.ai/directory/connecto…
Recording meetings without notification is the same thing as using meta glasses with LED light drilled out.
Granola secretly records meeting conversations without consent of participants and uses the recordings to train its AI models, according to a new class action filed yesterday.
Plaintiff says Granola recorded her meeting but was never notified of Granola's presence.
Granola's allegedly said on its website that "other people in the room won't know it's there."
Talking meeting templates = boring
Using meeting templates = productive
Now all users @ReadAI_ can use the standard meeting, pre-built, or custom templates.
To make meetings more valuable, you have to present them in a format designed for circulation.
read.ai/post/live-today-temp…
Argentina acaba de confirmar lo que todo ejecutivo ya sospechaba: nadie agenda reuniones durante el Mundial.
Los datos de Read AI muestran que las reuniones cayeron un 76% durante los horarios de los partidos, comparado con la semana anterior.
Pero aquí está el giro — no desaparecen. Simplemente se mueven. Después del último partido, las reuniones tuvieron un aumento del 52% semana contra semana, mientras todos se ponían al día.
La conclusión: las reuniones no desaparecieron durante el Mundial — simplemente se movieron al pre-partido.
Mexico has materially fewer meetings during their opening World Cup match.
Light Line: Prior Day
Highlight: Game Time
Source: @ReadAI_
