Avoma

What it is

Avoma records sales calls, transcribes them in 75+ languages, writes notes and action items, and pushes the result into Salesforce, HubSpot or Pipedrive. That part is Fireflies or Fathom with a revenue skin on it.

The part that isn’t: Avoma also sells the meeting before the meeting. Scheduler and Lead Router — booking pages, group scheduling, inbound form qualification and routing to the right rep — ship inside the same product, on the same seat. No other conversation-intelligence vendor in this catalog does that. Gong, Chorus, Attention and Sybill all start at the recorder and work forward. Avoma starts at the calendar.

The product is four modules: AI Meeting Assistant, Scheduler & Lead Router, Conversation Intelligence, Revenue Intelligence. The first is the base plan. The other three are separately priced. Reading Avoma as “the cheap Gong” is the mistake that runs the evaluation off the road — the base seat is a notetaker, and the Gong-shaped job is three line items.

Why it shows up in RevOps stacks

Consolidation, and it is a defensible reason for once. A 30-rep team running one vendor for booking, another for inbound routing, a third for notes and nothing at all for coaching is carrying four renewal dates for one funnel. Avoma collapses that into one contract and one admin surface, and it is the only vendor here that can.

The second reason is the MCP server. Avoma publishes one for Claude and ChatGPT: an admin publishes the org connector, then each user connects their own account over OAuth 2.0, with no API keys to manage. The read side covers transcripts, notes, summaries and action items, meeting search by participant, topic, date or outcome, and call-scoring and coaching metrics. The write side is deliberately narrow — set a meeting purpose (Discovery, Demo, QBR, Renewal), log a deal outcome (Closed Won, Lost, Renewal, No Show), enforce privacy settings. Set that against Attention’s 68 tools and a write scope that includes delete_user: Avoma’s connector cannot damage anything outside meeting metadata. If you want the assistant reading call history without holding write access to your system of record, that narrowness is the feature, not the gap.

Pricing reality

Published per seat, and checked 5 September 2026:

• Startup — $19/seat/month annual, $29 monthly. Hard cap of 25 paid seats. Meeting Assistant, 1:1 scheduling, recording, transcription, summaries.
• Organization — $24/seat/month annual, $39 monthly. Hard cap of 100 paid seats. Adds custom AI templates, group scheduling, limited conversation intelligence, smart playlists.
• Enterprise — $39/seat/month, annual billing only, 10-seat minimum. Adds SSO, HIPAA handling, custom data retention, concierge onboarding, a named success manager.

Add-ons price per seat on top of any tier: Conversation Intelligence $29 annual / $35 monthly (AI coaching, call scoring, custom scorecards), Revenue Intelligence $29 annual / $35 monthly (deal risk alerts, forecasting, win-loss), Lead Router $19 annual / $25 monthly (advanced routing, form qualification, handoff). Viewers and collaborators are free and do not consume a paid seat. There is no permanent free plan — the entry point is a 14-day Organization trial with add-ons enabled and no card.

The number that matters is the one for the job you are actually buying. Recording plus coaching plus CRM-aware deal tracking — the Gong-equivalent scope — is Organization + CI + RI, which is $82/seat/month annual, about $984/seat/year. Twenty reps in that configuration is roughly $19,700/year.

Against the comparables that sets up honestly. Gong runs approximately $1,400-$2,000 per seat/year on standard-tier deployments, plus a mandatory platform fee reported in the $5,000-$50,000 range, with a practical 15-25 seat floor. Avoma at full scope is about half of Gong per seat with no platform fee — not a tenth of it, whatever the comparison blogs say. At the other end, Fathom Business is $25/seat/month annual and includes CRM field sync, so Avoma fully configured costs over 3x a competent notetaker. The $19 base seat is priced against Fathom; the $82 configuration is priced against Gong. Those are two different purchases and only one of them is on your quote.

Best for

A RevOps or sales leader on a 10-60 seat revenue team running Salesforce, HubSpot or Pipedrive who owns inbound meeting booking and call coaching and wants one vendor for both. The scoped case where Avoma wins outright: a team already paying separately for a scheduling tool and a notetaker, where inbound demo requests need routing to the right AE and those same calls need scorecards. Avoma is the only vendor in this segment that prices both on one seat.

It is also the right pick for a smaller team that needs a published number and no platform fee. Ten reps on Organization plus Conversation Intelligence is $53/seat/month on a card. Gong is not a customer conversation at that size.

Not for

Teams past roughly 100 reps whose mandate is coaching depth and cross-market intelligence. Organization caps at 100 paid seats, which forces the Enterprise conversation, and at that scale you are weighing Gong’s deal inspection and market intelligence against a base plan with three add-ons attached. Gong’s economics improve exactly where Avoma’s advantage runs out.

It is also the wrong pick when the deliverable is the follow-up email sent and the CRM field written rather than the summary produced. Avoma’s MCP write scope covers meeting metadata; it does not fill your opportunity fields. Attention and Sybill sell that write-back directly and Avoma does not.

And if the honest requirement is notes for eight people, the base seat is not competitive with a $0 Granola or Fathom tier.

Versus the alternatives

• Gong — the share leader and the name your buying committee already knows, at a roughly $55,000 median annual contract. Pick Gong when 40+ quota-carrying reps and coaching is a funded program with a named owner. Pick Avoma under 60 seats, when the budget has no room for a five-figure platform fee, and when booking and routing are half the reason for the purchase.
• Attention — the fastest-growing entrant in the segment, $30M Series B on 24 June 2026 with ARR up 4x, quote-only and estimated in the $70-140/seat/month band. Its MCP server exposes 68 tools with a real write scope against Avoma’s read-heavy set. Pick Attention when agents taking the action is the deliverable. Pick Avoma when you want a price you can read on a website and a connector that cannot touch the CRM.
• Sybill — the other published-price pole, $90/user/month on Business, CRM Autofill capped at 10 fields, no seat minimum. Pick Sybill when CRM hygiene is the single measured problem. Pick Avoma when scheduling and inbound routing are in scope, because Sybill does not sell them at all.
• Fathom, Granola and Fireflies — $0-25/seat/month. Pick any of them when the requirement really is notes. Fathom’s catch is that CRM sync on Team and Business is capped at 3 users per domain, so a 12-rep writeback rollout lands on an Enterprise quote and the gap to Avoma closes fast.

If none of these fit, the tell is usually that meetings are not the constraint. Buy a $20 notetaker, spend the difference on the process problem, and revisit next quarter.

Watch-outs

• Add-on stacking is where the budget goes. Modeling on the $19 headline and then finding that coaching is a second $29 line and forecasting a third is the most common Avoma surprise. Guard: build the seat count for each of the four modules separately before the first demo, price that grid yourself, and make the vendor quote a discount against the whole grid rather than against the base plan. A discount on the cheapest line is not a discount.
• The seat caps are hard product limits, not negotiating positions. Startup stops at 25 paid seats and Organization at 100. A team that hires past a cap is not asking for a better rate; it is migrating tiers mid-contract. Guard: if your 12-month hiring plan crosses 25 seats, start on Organization even though Startup is cheaper today. If it approaches 100, get Enterprise pricing written into the first paper — the tier change is a repricing event and you have nothing to bargain with in month eight.
• The recorder joins as a participant. Avoma’s notetaker enters Zoom, Google Meet and Teams calls as an attendee, which means it is visible to your prospect and subject to their meeting policy. Some enterprise buyers block external bots outright. Guard: run the trial against your noisiest recurring call and one known-hard call — heavy accents, dense product jargon — and read the raw transcript before signing, not during onboarding. Confirm the bot is admitted in at least one target account’s environment during the trial.
• MCP access has no published tier. The connector is an org-level publish followed by a per-user connect, and the assistant sees whatever that user can see in Avoma. The vendor’s MCP page states the setup flow but does not name which plan or add-on carries the entitlement. Guard: get MCP access named in the order form by plan, and set meeting privacy defaults before publishing the connector rather than after — the write scope includes privacy enforcement, so the ordering matters.

Related: the conversation intelligence stack prices the surrounding layers, and alternatives to Gong covers the wider replacement set.