May 2026 · Gladia Research Report

2026 AI Meeting Assistant Market Map

Aka Gladia’s “Magique Square” for meeting assistants.

With input from

Sequoia Northzone Recall Nabla

What this report is

What is this?

A map of the meeting assistant market in 2026 that explores how products are differentiating, and where the category is heading. Our framework is built around four “moats” of defensibility, and our POV is informed by product testing, survey data, and conversations with the investors and founders shaping the market.

How do we define “meeting assistants”?

Any AI-powered platform that (magically) turns a conversation into an artifact. Notepads, notetakers, operating systems, ambient AI… We don’t really care what they call themselves, so long as voice is the input for some sort of useful output.

Who’s it for?

Primarily founders and product teams operating in (or adjacent to) this space. But honestly? Anyone trying to make sense of the market. That includes investors, enterprise buyers, everyday consumers, and anyone else who cares about how AI is reshaping how work gets done.


01

I’ve always believed that voice is the most underutilized data source in any organization. Not because it’s inaccessible (we’ve been recording conversations for decades), but because we’ve never had the tools to do anything meaningful with what was captured. But if every conversation could be structured and connected to the systems where work actually happens, the AI workplace assistant — one that genuinely understands what’s happening inside an organization and acts on it — stops being a concept and starts being an inevitability.

$1 billion+ in venture funding has been poured into meeting assistant tools in the last 3 years.

Meeting assistants are the wedge into that future.

I use them constantly and it’s remarkable how much has already been solved. Getting a bot into the room. Distilling a messy, hour-long call into three action items someone will actually follow up on. Pushing the right structured data into the right field in Salesforce, or Epic, or Linear. These are genuinely hard engineering problems to solve. But the hardest are still ahead. The teams trying to do this are making consequential bets in a market that’s moving fast. This is especially interesting because what’s unfolding is a classic David and Goliath story.

Zoom has real advantages, like distribution and data. But the startups building in this space have something the legacy players don’t: they were built AI-native from the ground up, and have the speed and flexibility to ship new features faster than any large platform can. As a fellow David — building the infrastructure that many of these tools depend on — we believe some of these products will become more than just useful software.

They’ll become indispensable like Slack, Figma, and Notion. They’ll become tools people can’t imagine doing their job without. And they’ll be powered by voice.

This report is our attempt to understand and celebrate what these builders are doing, the structural bets they’re making, the moats they’re trying to dig, and where this category, which is still very much in its earliest stages, is heading next.

Jean-Louis Quéguiner · Co-Founder & CEO, Gladia

02

Let’s back up. To understand where this market is today — and where it’s going — we have to trace its evolution. Looking at the key players, there are three primary product origin stories.

Origin 01

Tools built from day one as AI-native meeting assistants

Fireflies.ai · Fathom · Granola · Fellow

  • Built for one thing: Every product decision optimizes for the meeting experience, nothing else.
  • Moves fast: No legacy architecture or internal politics slowing things down.
  • Easy to love: Narrow focus tends to produce sharper, more intuitive UX.
  • Starting from zero: Every integration and enterprise relationship has to be earned from scratch.
  • Distribution is hard: No existing user base to grow from; every user has to be acquired.
  • Growth requires expansion: To scale, the product eventually has to become more than a meeting tool.

Origin 02

Evolved from somewhere adjacent

Otter.ai · Gong · Read AI

  • Strong foundations: Deep technical expertise in at least one hard problem already solved.
  • Existing trust: An established user base that already believes in the product.
  • Adjacent leverage: Prior integrations and workflows give them a head start on the stack.
  • Legacy baggage: The original product can be a ceiling as much as a foundation.
  • Identity problem: Convincing users (and the market) to see them differently is slow, hard work.
  • Split focus: Roadmap priorities are always competing with the core product.

Origin 03

Platform players with meeting assistance as a feature inside a much larger product

Microsoft, Google, Zoom

  • Default distribution: Access to millions of users who already live inside their ecosystem.
  • Already embedded: Deep hooks into the tools and workflows people use every day.
  • Enterprise trust: Compliance, security, and procurement relationships already in place.
  • Features, not products: Meeting assistance competes internally with dozens of other priorities.
  • Slow to move: Innovation at platform scale is measured in quarters, not weeks.
  • Good enough is the enemy: “Included in your subscription” sets a low bar that’s hard to push past.

Product origin shapes what a tool can realistically become, but all of these products (regardless of where they started) are navigating the same evolutionary arc.

At one end: a transcription tool that captures what was said.

At the other: a true AI workplace assistant that understands context, takes initiative, and works like a colleague.

The distance between those two things is where the entire market is competing right now.

Phase 1

The first wave solved a simple problem: stop making humans do the work of recording what happened in a meeting. Reactive and isolated, these tools capture, summarize, deliver. Many products are still essentially here.

Phase 1, Capture
97% trust AI-generated
meeting notes
AR-2
Phase 2, Connect
Only 41% use meeting
assistants to trigger workflows
AR-4

Phase 2

The conversation stops being an isolated output and becomes an operational input. CRM fields get updated, tasks assigned, follow-up emails drafted. The AI proposes, the human approves. Most workflow execution stays supervised.

Phase 3A

Conversations don’t just get processed and filed — they get connected. A question today surfaces context from six months ago. A decision in one team becomes visible to another. Over time, it stops feeling like a tool and starts feeling like institutional memory.

The split — Path A and Path B

Phase 3B

The agent is live on the call with you. It listens in real-time, detects a risk or an opportunity, and surfaces the right context, proactively. After the call, it doesn’t wait for instructions — it acts. No manual input. No handoff. Just execution, on the org’s behalf.

Final Destination

Ultimate agentic workplace platform

The destination is a collaborative, autonomous tool people can’t imagine working without. One that’s embedded in how teams think, decide, and act.

Each path there solves different parts of the same puzzle, because a true AI workplace assistant requires both. Memory without action is a better filing system. Action without memory is a faster bot.

The products that figure out how to combine them are the ones that will define this category.

05

The end goal is to become a Platform.

The products that will define this category won’t just do one thing well. They’ll become the layer where work actually happens instead of just an input to another tool. They’ll be the place where decisions get made, actions get assigned, and context accumulates over time. And the key to getting there isn’t just integrations or features. It’s collaboration. A tool that one person uses is always replaceable. A tool that holds shared context across an entire team is a different proposition entirely.

Verticalization is an underrated bet.

If history tells us anything, only a few players will rise to the top of the horizontal enterprise market. While, yes, vertical players face a higher bar — deeper technical challenges, stricter compliance requirements, a more demanding buyer — the reward is real defensibility. Gong already proved that owning a specific function was worth more than being broadly useful, and the same pattern is playing out across industries, functions, and individual workflows too specific for any horizontal tool to serve well.

The freemium era is on borrowed time.

This market got its distribution through free tiers and low-friction sign-ups. That was smart. But individual users who are easy to acquire are equally easy to lose. The products that matter long-term will be bought by teams and organizations, not expensed by individuals. Tools that stay in consumer mode will be forced to compete for individual loyalty, which means running forever on a treadmill of retention and feature releases. The only way off it is to get bought (and embedded) at the organizational level.

English-first is becoming a liability.

Workforces have gone global thanks to remote work and the globalization of talent. Now, multilingual meetings are the new norm, especially for the youngest generation entering the workforce. But most tools are built and optimized for English, and performance drops big time for other languages. This isn’t a niche problem. For any tool that wants to serve modern teams, multilingual performance is table stakes.

Innovation is outpacing awareness.

This category of tools is well understood and adopted in Silicon Valley and in tech start-ups. But outside of these circles, awareness drops fast. Most people can’t even name a vendor beyond the one built into their meeting platform. And even where adoption does exist, use cases remain relatively simple: notes, summaries, the occasional action item. Lightweight use cases like these don’t build the habits or shared context that make a tool truly embedded. The agentic future is real and it’s being built right now, but vendors will need to invest as much in driving feature adoption as they do in shipping them.

03

Not every vendor is playing the same game. These four maps reveal where the market is crowded, where there’s white space, and where the most interesting strategic bets are being made.

Disclaimer: Placement reflects the primary value proposition customers buy, not every capability a product offers.

Moat #1 · Capture

Where products listen, and who decides what gets recorded (and how).

Walled Gardens

The most governed approach to capture, but also the most limited. These tools record what happens inside meeting platforms. Anything that happens outside a scheduled call gets lost. Microsoft Copilot, Google Meet AI, Zoom AI Companion, Fellow AI, Notion AI Meeting Notes

Compliant Ears

The hardest quadrant to build in. These tools capture more ambiently by extending beyond meeting platforms, without sacrificing the governance and compliance controls enterprises require. DAX Copilot, Abridge, Nabla, Freed, Suki

Personal Recorders

Easy to adopt and built for the individual. These tools tend to be botless and invisible, and they operate on the user’s terms, not the organization’s. But that freedom only stretches so far because these products are built primarily for online meetings (for now). Fireflies, Claap, Fathom, BlueDot, Granola

Open Mics

The broadest reach of any quadrant, and the least governed. These tools (mostly on-device or portable) push furthest toward true ambient capture, following users beyond scheduled, online meetings into the rest of their day. Spoiler alert: NOT enterprise-friendly. Plaud, HeyPocket, Wispr Flow, Limitless (acq. Meta)

Strategic Insight

The two axes of this moat are in tension with each other. Broader capture creates more value, but governance is what makes that capture enterprise-safe. So far, only healthcare has been forced to solve both at once. The products that crack this combination in horizontal enterprise contexts will define what this category is ultimately able to become.

“A tool that captures 80% but misses the critical 20% isn’t 80% as valuable. It’s a fundamentally weaker product.”

Julien Bek, Partner at Sequoia

Capture Deep Dive: Q&A With Recall.ai CEO, Amanda Zhu

To dig into what modern capture actually involves at the infrastructure level, we sat down with Amanda Zhu, Co-Founder of Recall.ai, a simple API for recording meetings that’s built for teams who don’t want to maintain their own capture infrastructure.

Q: How do you think about capture’s role in the broader AI stack?
A: AI systems need context. If you ask ChatGPT “write me an email,” it can’t do it. It needs to know what the email is about and who it is for. 99% of the context that AI needs is in conversations that are never written down. And with meetings, once the meeting is done, it’s not happening again. If meeting data is lost, it’s catastrophic. That’s why reliability is really important in meeting capture, and why the quality of capture directly shapes what’s possible downstream.
Q: What makes modern capture genuinely difficult?
A: As a user, recording a meeting is pretty straightforward. The difficulty is on the infrastructure side. You need to integrate with multiple platforms — Zoom, Google Meet, and Microsoft Teams — each with different APIs, some with no APIs at all. There are edge cases that are hard to solve, like getting speaker names so that transcripts are accurately labeled. And if you’re trying to build a low-friction experience with high adoption, simply integrating with what the platforms offer creates a lot of dependencies on the user: they need to remember to click record, be on a specific tier, be the host of the meeting, and have certain settings configured by an admin.
Q: Do you see bot-less capture as the future?
A: For enterprises that care a lot about user consent and low friction in adoption, the meeting bot is typically what they opt for. For more PLG productivity apps, they may opt for the desktop recording SDK because they prioritize invisible recording, and user consent and compliance isn’t as big of a focus. Ultimately, in our customer base, we see different use cases for meeting bots and different use cases for a more invisible capture system. And we serve both. We have a meeting bot API, if you want a bot to record your meeting, as well as a desktop recording SDK, if you want to build a bot-less, Granola-style recording.
Q: When a startup decides to just build their own meeting capture, what do they almost always underestimate?
A: The level of work to maintain the infrastructure for meeting capture and keep it working reliably is immense. It is easy to build a proof of concept that works on your laptop for yourself 80% of the time. It’s much more difficult to build something that works for even just a hundred people 99.9% of the time. We estimate that it’d take a team of 3-5 engineers to maintain a solution like this in perpetuity. Additionally, teams often underestimate how hard it is to get the data they need. It’s easy to get a transcript with machine diarization with speaker 1 and speaker 2, but it’s hard to get perfectly diarized transcripts with real speaker names and speaker emails. It’s one of the hardest and unique edge cases we’ve solved. Several companies who have built in-house meeting bots or a desktop app — Fireflies, Cluely — switch to Recall.ai, because even after years of running their own in-house infrastructure, at the end of the day, it’s not worth it to spend engineering time on undifferentiated infrastructure. That engineering time can be better spent on building differentiating features for your product.

Moat #2 · Intelligence

What products do with what they’ve captured, and when those insights are delivered.

Knowledge Graphs

These tools win through accumulation. By synthesizing across conversations, documents, and systems over time, they start to map the tribal knowledge that lives inside an organization. This is the most ambitious quadrant in the map, and the hardest to build. Tana, Sana, Read AI, Gong, Avoma, Supernormal, Glean

Live Coaches

The only quadrant where timing is the whole point. These tools are built to surface intelligence during the conversation so users can influence outcomes in the moment. But real-time means less context to reason over, and teams must optimize for sub-200 ms latency across their entire stack, which adds significant build complexity. Winn AI, Cluely, Attention, Fireflies Live Assist, Otter Sales Agent

Structured Summarizers

Reliable and easy to love, but limited in their outputs. These tools deliver clean post-meeting summaries and structured notes from a single conversation. What they don’t do is connect the dots across meetings. Each conversation is treated as its own isolated event. Otter.ai, tl;dv, MeetGeek, Microsoft Copilot, Google Meet AI, Zoom AI Companion, Notion AI, Timeless, Circleback

Verbatim Recorders

Where the category started. These tools prioritize capturing what was said over understanding what it meant. They’re fast and accurate…but increasingly low-utility and easy to replicate. Tactiq, Voicenotes, Notta

Strategic Insight

When insights arrive is largely a product design choice, and both real-time and post-meeting have genuine use cases. But it’s the accumulation of context and conversation history that creates real lock-in. Products that treat each meeting as an isolated event will remain easy to replace. The ones that build knowledge over time won’t.

“The most interesting company would surface information when you need it. Actually, when you don’t even know that you need it. We’re not there yet. It needs to proactively surface things. Today it’s very, very reactive.”

Naseem Moumene, VP at Northzone

Read the full Q&A

Moat #3 · Integrations

How deeply a product embeds itself into the tools a business runs on, and how well it connects the people who use it.

The Utilities

Wide reach, shallow roots. These tools connect to the apps people already use, but mostly in one direction. They’re also adopted by individuals, not deployed across teams. Fireflies, Otter.ai, tl;dv, Read AI, Circleback, Fyxer, Grain, Granola, Timeless

The Fortresses

The hardest quadrant to displace. These tools combine deep, bi-directional integrations with wide team adoption. The product becomes the place where outputs live and where teams build shared context. Hard for product teams to build, hard for buyers to replace. Gong, Microsoft Copilot, Google Meet AI, Zoom AI Companion, Fellow AI, Avoma, Notion

Focused Transcribers

Built for the individual, not the organization. These tools do one thing well — capturing and exporting meeting content — but they don’t attempt to deeply embed themselves in broader workflows or connect the people around them. Jamie, Tactiq, HappyScribe, Krisp, Notta AI, Plaud, Wispr Flow, BlueDot

Specialized Assistants

Narrow by design, but deeply embedded within their niche. These tools integrate tightly with the systems of record that matter most in their domain — CRM, EHR — but the data they handle is sensitive by nature. Used by many, shared by few. Steno, Abridge, DAX Copilot, Claap, Chorus, Momentum, Attention, Winn AI, Clari Copilot, Sybill

Strategic Insight

Integrations aren’t just a feature. They’re what determine whether a product stays a tool or becomes a platform. That’s true on two dimensions: how deeply a product connects to the tech a business runs on, and how many people are connected through it. Get both right, and you become something a business can’t easily remove.

“For these meeting assistant companies to become really big, they need to crack collaboration. That’s the next stage where they can really become systems of work. For that same reason, the top player will be significantly larger than number two and number three. Network effects from collaboration features are strong.”

Julien Bek, Partner at Sequoia

Moat #4 · Market Strategy

How a product reaches its users, and what that relationship is ultimately worth.

Vertical Giants

Specialized tools sold to enterprise buyers within a specific vertical. The technical complexity is high, user expectations are exacting, and that’s reflected in the price tag. These products grow by going deeper. More workflows, more integrations, more of the stack owned within the niche they already dominate. Abridge, DAX Copilot, Nabla, Steno, Winn AI, Momentum, Sybill, Claap

Enterprise Giants

The biggest contracts and the broadest deployments. These tools typically arrive through existing platform relationships or dominant distribution (for now). Lower price per seat than their vertical counterparts, but what they lack in depth they make up for in scale. Gong, Microsoft Copilot, Clari, Google Meet AI, Zoom AI Companion, Chorus, Glean

B2B Boutique

These tools are built for specific, smaller audiences (investors, financial advisors, recruiters), and note-taking is often just one feature of the overall product. The total addressable market is limited by definition, which raises a real strategic question: do you go deeper into the niche like a Vertical Giant, or broader like a PLG Mover? Freed, Metaview, Zocks, Saturn

PLG Movers

Where the energy is right now. Low friction and often free to start. But not all PLG tools are heading in the same direction. Some are actively moving upmarket: expanding into team deployments, adding governance, chasing enterprise contracts. Others are settling into an App Store tier. PLG Movers (Fireflies, Otter.ai, Granola, Read AI, Fellow AI, tl;dv) to App Store Tier (Fathom, Voicenotes, Krisp, Tactiq).

Strategic Insight

Some of today’s most popular tools are adopted by individuals, but the products with the most room to grow are those that can move up: from individual users to organizational deployment. That’s true for both horizontal and vertical players, but vertical has an edge: there are more niches to own, less competition, and higher contract values up for grabs.

“Many of [these products] have captured that core behavioral loop: join a meeting, get notes, retain users. But now it’s becoming a question of who’s going to build out the rest of the features. And that’s still all to play for.”

Naseem Moumene, VP at Northzone

Read the full Q&A

Market Strategy Deep Dive: Q&A With Nabla Co-Founder & COO, Delphine Groll

The decision to go vertical is one of the most consequential a founder can make. To understand what that choice actually looks like in practice, we spoke with Delphine Groll, Co-Founder and COO of Nabla — an ambient AI assistant purpose-built for clinical workflows.

Q: What made healthcare a compelling vertical for Nabla, as opposed to building something more broadly applicable across industries?
A: Healthcare was a deliberate choice from day one. We saw an opportunity to apply large language models to one of the most meaningful and underserved use cases. Clinicians spend up to 40 percent of their time on documentation, often outside of patient hours. That administrative burden directly impacts both clinician well-being and patient experience. Generative AI offered a clear path to change that. This focus has proven to be well timed. Healthcare is now one of the fastest growing and highest impact verticals for AI, with ambient clinical documentation having emerged as a leading use case due to its immediate ROI and measurable impact on burnout, efficiency, and care quality.
Q: What does it actually take to build something that clinicians will genuinely adopt and use?
A: Healthcare is one of the most challenging industries to build in, and healthcare users are among the most demanding in any industry. It is often said that there is a “graveyard” of companies that underestimated its complexity. The stakes are fundamentally different. This is not about productivity gains alone. It is about patient safety, clinical accuracy, and trust. For an ambient AI assistant to be truly useful, clinicians need near-perfect accuracy… even small errors can have clinical consequences. Notes must be ready immediately after the visit. And the product must integrate seamlessly into existing systems, especially EHRs. Clinicians cannot afford to switch between tools or disrupt their workflow. On top of that, the experience has to be intuitive, fast, and invisible. Ambient AI must feel like a natural extension of the clinical workflow, not another system to manage. If clinicians need to spend time correcting outputs, the value disappears. Ultimately, clinicians are not looking for a generic AI tool. They need an assistant that fits into clinical workflows and meets the standards of patient care. The bar is high.
Q: How did your go-to-market strategy evolve as you scaled?
A: Nabla initially grew through a product-led approach, offering freemium access to clinicians. This allowed us to observe real-world usage at scale and rapidly iterate based on feedback. That grassroots adoption led to strong word-of-mouth, with clinicians introducing Nabla into their organizations. Over time, this translated into inbound interest from major health systems, including Children’s Hospital Los Angeles, The University of Iowa Health Care, CVS Health, Denver Health, and Carle Health. But building in healthcare requires earning trust at every level. That requires consistently high-quality outputs across diverse scenarios, from primary care to highly specialized fields.
Q: As you look ahead, how do you think about growth? Does it come from going deeper within healthcare, or expanding into adjacent areas?
A: The space is vast, and it is easy to try to solve too many problems at once. Nabla made a deliberate decision to focus on one of the most urgent and universal pain points: clinical documentation burden and the burnout it creates. That focus is what allowed us to build something clinicians genuinely rely on. But that’s just the starting point. We are evolving from ambient documentation into contextual clinical intelligence, operating at the center of every patient encounter to unify documentation, coding, and workflow execution into a single intelligent system. The goal is to support clinicians seamlessly before, during, and after care is delivered. We’re building towards a platform that can reason, assist, and safely execute tasks within clinical workflows, enabling health systems to move beyond fragmented tools toward scalable, system-wide impact.
04

We couldn’t map this market without hearing from the people actually using these tools. What do they prioritize? How much do they trust what gets produced? Are they getting value beyond basic note-taking? We surveyed 2,100 meeting assistant users across the US, UK, France, Germany, Spain, and Italy to find out. Here’s what we learned.

59%Likely to switch in 12 months
97%Trust AI meeting notes
33%Chose their meeting assistant themselves
48%Participate in multilingual meetings regularly

Brand is the first battle

The market is flooded with new entrants, but brand awareness remains a real challenge. Case in point: Only 1 in 7 respondents had heard of specialized new entrants like Granola and Fathom. Fewer still have actually used them. When you compare that to platform players like Teams, used by more than 50%, it’s clear that most people simply use the note-taker that’s built into their default work suite.

Capture first, automate later

The vast majority of users rely on their meeting assistant for the most basic use case: summaries/notes. Fewer than half use on-call prompts or workflow triggers, the features that start to make these tools genuinely embedded in how work gets done. That gap narrows with age, though: younger workers are meaningfully more likely to use the “advanced” stuff.

Which features do you use?

71%

Meeting summaries

51%

Full transcripts

49%

On-call assistance

48%

Action items

41%

Triggering workflows

34%

Compliance records

97 % Trust Notes

No trust issues here

For AI meeting assistants to fulfil their potential, users need to trust what they produce. Overwhelmingly, they do. 97% of respondents trust AI-generated meeting notes to at least some extent. 10% trust them completely, while less than 1% say they don’t trust them at all.

The user rarely decides

Despite an influx of free, consumer-grade tools marketed directly to individuals, only 1 in 3 people chose their meeting assistant themselves. The majority arrived at their tool through an employer, IT team, or a bundle, meaning the real buying decision is still overwhelmingly an organizational one.

How was your current assistant chosen?

33% I chose it myself 24% Employer or IT 17% Chosen by my team 16% Bundled (e.g. Meet, Zoom) 10% influenced by me, not final call

Security is the silent priority

Accuracy tops the list of what users want, which isn’t a surprise. What is a surprise? Data privacy ranks third, ahead of speed, integrations, and multi-speaker transcription. In a category where the product is always in the room, users have clearly decided that trust in the tool extends beyond the output to the infrastructure behind it.

What users prioritize (ranked)

Accurate summaries — 39%

Accuracy of key details — 36%

Strong data privacy — 33%

Fast output — 29%

Speaker identification — 26%

Integrations — 26%

Multilingual transcription — 22%

Industry/company terminology — 22%

Action item extraction — 19%

Botless assistants16%

The botless paradox

Bot fatigue has spurred a new generation of invisible capture tools. And if a true ambient workplace assistant is the end state, local capture without a visible bot is likely how we get there. But appetite in our dataset appears limited: only 1 in 6 users cite botless capability as a top priority today.

Younger users want different things

The oldest respondents are twice as likely to cite accurate summaries as a top priority compared to the youngest. Younger workers are also less concerned about privacy. So, what do they care about? Accurate transcription in multiple languages. Our take: this is unsurprising for a cohort that entered the workforce during remote work, collaborates globally by default, and has never known a world without ambient data collection.

Top Feature by Age Group

Feature 18–24 55–64
1. Accurate summaries of discussions 26% 43%
2. Botless assistants 24% 12%
3. Multilingual transcription 30% 24%

Expectations vs. reality

On the whole, users are satisfied with product performance today. But there are some gaps that have big implications. Domain terminology and non-English transcription score lowest, and in both cases, the stakes are high. For vertical tools, accurate domain language isn’t a nice-to-have, it’s the entire value proposition.

48% participate in multilingual meetings frequently or at every meeting

Sticky by design, not by default

In a category where a new tool launches every week, loyalty is low. 59% say they’ll switch in the next 12 months. For vendors, the imperative is clear: get embedded, get integrated, become indispensable.

Switching intent (12 months)

21% Very likely 38% Likely 22% Unlikely 8% Very unlikely 12% Not sure
06

This report was informed by a survey of 2,100 meeting assistant users across the US, UK, France, Germany, Italy, and Spain via OnePoll and interviews with investors and founders.

Our research started with 100+ vendors, selected based on market relevance and product differentiation across the category.

Once the axes and criteria for each moat were established, vendors were shortlisted to ~50 against rubrics defined per moat. Placements are based on product testing and publicly available information gathered between February and April 2026. Not every vendor appears in every moat; inclusion reflects standout positioning rather than exhaustive coverage.

We’re not analysts. Placements reflect a point-in-time view based solely on what was publicly available. There were no vendor briefings, and this space moves fast. That means some of this will date quickly.

hand-drawn with care — May 2026
thanks for reading all the way down here
Gladia Research

A letter to meeting assistants

Jean-Louis Quéguiner · Co-Founder & CEO, Gladia

How the market has evolved (and where it’s going)

Q&A With Nabla Co-Founder & COO, Delphine Groll

Q&A With Recall.ai CEO, Amanda Zhu

TLDR: 5 market insights

The four moats of defensibility

What 2,100 users want from AI meeting assistants

Methodology