Alright, let's cut through the marketing fluff. You're a small business, which means you're operating on a budget tighter than AWS's default service quotas. You're looking at "free" meeting note tools, and Fellow is at the top of your list. As someone who audits cloud bills for a living, I see this as a classic cost-optimization problem: you're trading capital expenditure (hard cash for software) for operational expenditure (your team's time and data portability).
I spent a week stress-testing the free tiers of Fellow and its main alternatives (Hugo, Hypercontext, even using Notion as a baseline). My primary lens? Long-term cost creep and lock-in. Because nothing is truly free; you pay in data, limits, or future migration headaches.
Here’s the breakdown from a FinOps-obsessed perspective:
* **Fellow (Free Plan):** The big sell is the integration with Google Meet and Zoom for live collaborative notes. It's slick. But the free tier is a classic "gateway drug." You hit the 10 meeting template limit fast, and the 1GB total file storage is a rounding error in S3 terms. The real cost? If you grow, you're looking at $6/user/month. Manageable, but it adds up like unmonitored NAT Gateway charges.
* **Hugo (Free Plan):** Similar vibe, but their free tier is slightly more generous on templates and storage. However, the meeting analytics—where you'd see if your meetings are actually worth their "compute time"—are paywalled. This is like getting CloudTrail logs but being charged extra to analyze them. Unacceptable.
* **The "Just Use Docs/Notion" Contingent:** This is the equivalent of running everything on t2.micro instances to save money. It works at first. The "cost" is fragmentation. You'll have notes in shared drives, Notion pages, and random .txt files. The operational overhead of finding context later is a hidden cost that scales linearly with team size. It's technical debt, but for your processes.
**My sardonic take?** Fellow's free tier is the best *if* your meetings are almost exclusively on Zoom/Google Meet and you have the discipline to treat it as a transient experiment. Use it to prove the value of structured notes. But from day one, **implement a data export policy.**
Set a calendar reminder for every quarter to do a bulk export of your notes. Because if you ever need to migrate, that's your disaster recovery snapshot. Their API is on the Business plan, so on the free tier, you're manually copying. It's a pain, but it prevents vendor lock-in, which is the ultimate cost anomaly.
Treat this tool like a reserved instance: commit only if the usage pattern is predictable and long-term. Otherwise, stay on the free tier and be ready to abandon ship without data loss.
your cloud bill is too high
I'm a database engineer at a 50-person fintech, where I'm also responsible for evaluating and operationalizing internal tooling; we run a hybrid stack with heavy use of Google Workspace and Jira, and I've overseen the deployment of three different meeting/productivity tools in the last two years.
1. **Storage & Data Portability:** Fellow's 1GB cap is a hard, non-negotiable ceiling. Hugo's free tier offers "unlimited" storage but throttles individual file uploads to 25MB, which fails for longer video recordings. Hypercontext is more generous on storage but locks exporting meeting transcripts behind its paid plan. Using a Notion free workspace gives you true control, with a 5MB file limit but no total cap, and data is always exportable via Markdown.
2. **Integration Depth & Meeting Context:** Fellow's direct integration with Zoom and Google Meet to auto-create notes is unmatched in the free tier; clicking the Fellow bot in a call immediately creates a shared doc with the calendar event title and attendees pre-populated. Hugo requires a separate calendar connection. Hypercontext and Notion rely on manual creation or less reliable calendar-to-page automations.
3. **Template Scalability & Lock-in:** Fellow's 10-template limit is reached within a sprint cycle for any team with more than one type of recurring meeting (standup, retro, planning, client call, etc.). Hugo's free plan offers 5 "Workspace Templates," which is functionally similar. Both enforce these limits strictly. A Notion template database, while requiring initial setup, has no inherent limit, and templates are simple page duplicates.
4. **The Real Pricing Cliff:** Fellow's jump is to $6/user/month (billed annually). Hugo shifts to a "per host" model at $7/user/month, which can be cheaper if only leads take notes. Hypercontext is $7/user/month. Notion remains free for the core product, but the operational cost is the ~2 hours of admin time per month to maintain the system and onboard new hires.
For a small business under 10 people that lives in Zoom/Meet calls and needs the absolute lowest friction for collaborative, in-meeting note-taking, Fellow's free tier is viable for about 6-9 months. For any team that prioritizes long-term data ownership, avoids per-user SaaS creep, and has a member willing to configure a Notion workspace, building a custom system there is the financially optimal path. Tell me your team size and whether your meetings are primarily internal syncs or client-facing, and I can narrow it further.
Test it yourself.
Spot on about Fellow's free tier being a gateway. The 10 template limit hits you quicker than most expect, because a small team will naturally create different templates for client calls, sprint planning, one-on-ones, and so on.
Your comparison to unmonitored NAT Gateway costs is perfect. It's not just the $6/user/month headline, it's the fact that you don't feel the lock-in until you've built your workflow around their specific agenda format and comments. Migrating that operational knowledge is the real hidden cost.
Have you seen teams hit the 1GB cap in practice? I'm curious if it's more from uploaded files or from the app's own note history piling up.
Keep it constructive.
Good point on the integration depth. That's actually the main reason we're testing Fellow at our small sales team.
But that unlimited storage claim from Hugo, is it really unlimited? There's always a catch, like throttling or read-only access after a point.
Trying to figure it out.
The point about auto-created notes is huge for me. I'm testing Fellow's free plan now and that automation is the main thing keeping us from just using a shared doc. Having the note already exist when you join the call cuts out that awkward first minute of "who's taking notes?"
But you mentioned the 1GB cap. If the app is auto-creating all these notes and we never delete them, how long do you think it takes to hit that limit? Is it mostly from us uploading our own files, or does the app's own history just keep growing forever?
Still learning.
Totally agree about Fellow being a gateway plan. That 1GB storage feels huge until you realize it includes all your uploaded docs, images, and the app's own note history. For a team of 5 having two meetings a day, you can chew through that in under a year without even trying.
You mentioned the NAT Gateway analogy, and it's spot on. The bigger hidden cost for us was the integration lock-in. Once you wire up those Google Meet auto-created notes, migrating to anything else means rebuilding that automation from scratch, usually with Zapier or Make, which adds its own cost and complexity. The free tier gets your process dependent on their ecosystem.
Have you looked at how their API behaves on the free plan? That's often the first hard limit you hit if you try to build any external reporting or data sync.
Integration Ian
The real issue isn't the $6/user/month. It's the mental overhead.
You're building process around a proprietary format. You're right about the gateway. The jump from "free" to "paid" is easy, but the jump from "paid Fellow" to "anything else" is a massive replatforming project. You'll have years of notes stuck there.
Just use Google Docs. It's free, you own the data, and everyone already knows how to use it.
Simplicity is the ultimate sophistication
You're right about the replatforming cost, but "just use Google Docs" oversimplifies the workflow problem. The value in tools like Fellow isn't the notes, it's the structured process - agenda templates, assigned talking points, and action item tracking that's visible before the meeting even starts.
You can replicate this in Docs, but you're trading a software fee for a process tax. Someone has to build and enforce that template system manually every time. For a small team that's already stretched, that consistency is what you're buying, proprietary format or not.
The real question is whether your team's discipline is cheaper than the software license. In my experience, it usually isn't.
Show me the query.