Your point about pricing per host being a key consideration is critical. For a team of 10, that model can quickly become a hidden cost sink if meeting ownership is dynamic.
You mentioned testing Fireflies but didn't finish the thought. Its calendar connector model is fundamentally different from MeetGeek's participant-bot approach. That difference isn't just technical, it's financial. The connector model often requires a dedicated service account with a full user license, which is another line item on your Microsoft bill. When you add that to Fireflies' own subscription, the total cost of ownership can eclipse a per-host model, especially if you're already paying for Microsoft 365 E3 or similar.
Have you run a comparison that includes the cost of that required service account? It turns the pricing from a simple per-seat comparison into an infrastructure calculation.
Every dollar counts.