Looking at Sembly's site. The "per user per month" price looks simple. But I know how this goes.
What's the real price to actually use it? I need the transcription and AI features. Do I need a separate plan for each team? What are the hidden costs or required add-ons to make it functional for a small team? Just give me the final number.
You've pinpointed the classic SaaS pricing puzzle. The advertised per-user price is rarely the final cost. For a functional small team needing transcription and AI, you're likely looking at the "Business" tier, which starts at $20/user/month billed annually.
However, that base tier typically includes a limited pool of transcription minutes. Exceeding that triggers overage charges or requires upgrading to a higher-capacity plan. The "per team" structure means if you have distinct departments needing separate data silos, you'd need multiple team subscriptions, effectively multiplying your cost. For a team of 10 with ample transcription needs, the true operational cost often lands closer to $30-$35 per user per month once you factor in the necessary minute allocations and potential multi-team setups.
Exactly. The per-team multiplier is what catches organizations as they scale, even if the initial per-user price seems manageable. Your $30-$35 estimate for a team of ten is probably on target, but I've seen it go higher if meetings are long or frequent.
People often overlook the cost of storage for those transcriptions and recordings over time. Many plans include a set amount of storage, but after a year of active use, teams hit that limit. Then you're either purging historical data or paying an additional storage fee, which is another line item that isn't in the initial per-user calculation.
The more insidious cost is the administrative overhead of managing separate team subscriptions and minute pools. You end up needing to monitor usage across silos to avoid overages, which is a soft cost that further increases the total operational expense beyond the invoice amount.
Always check the data transfer costs.
You're spot on about the administrative overhead being a hidden tax. That soft cost of managing minute pools and storage limits across teams often translates into someone spending a few hours a month on license and usage babysitting.
One thing I've seen teams do to avoid the storage fee trap is set up a manual process to export and archive old transcripts to a cloud drive, then delete them from the platform. It's a clunky workaround, but it keeps that line item off the invoice.
The multiplier effect gets brutal when different departments have fluctuating meeting volumes. One team burns through its minutes in two weeks while another has surplus, but you can't share the pool.
Yep, the manual export workaround just shifts the cost from a direct line item to internal labor. I've seen teams burn half a day each quarter on that "free" archive process, which at a fully-loaded salary rate adds a few dollars per user back into the equation anyway.
The rigid minute pools are a real pain. Some vendors offer organization-wide "bank" of minutes that any team can draw from, but that's usually an enterprise-tier feature they won't advertise up front. It's something to push for in negotiations if you're growing.