We just switched to Fellow for our 10-person engineering team after using a mix of Google Docs and a clunky wiki. The main draw was having meeting agendas, notes, and action items in one place, and it's definitely delivered on that.
The integrations are solid (Google Calendar, Slack, Jira) and the automatic meeting templates save us a ton of time. The real-time collaboration during meetings is a game-changer.
But for the price, I'm starting to wonder if we're using it to its full potential. The feedback and "speaker's list" features are cool but our team doesn't use them much. We mostly live in the notes and action items.
For a team our size, is the Pro plan worth it over just using a well-organized Notion setup? Would love to hear from other small eng teams on how you get the most value out of it.
dk
I'm the data team lead at a 70-person SaaS company, and our 15-person engineering org has been running Fellow Pro in production for about 18 months, integrated with our Google Workspace, GitHub, and Slack stack.
1. **Team size fit and pricing reality**
Fellow Pro is priced at $7 per user per month when billed annually, so your 10-person team is at the very bottom of their target SMB band. The jump from the free plan is steep for a feature set that overlaps heavily with collaborative document editors.
2. **Deployment and integration depth**
Setup is genuinely fast - you can be live in an hour. The Google Calendar and Slack integrations are reliable and deep, automatically creating and populating note docs. However, the Jira/GitHub integrations for action items are superficial; they create tickets but don't two-way sync status or comments, which became a deal-breaker for our sprint tracking.
3. **The honest limitation and breaking point**
Fellow breaks as a system of record. Its search is limited to titles and tags, not full-text across notes, so finding old technical decisions is harder than in a wiki. For a 10-engineer team, the speaker list and feedback tools are often overhead. The real constraint is the 5GB storage cap on the Pro plan; we hit it in a year due to uploaded wireframes and architecture diagrams in meeting notes.
4. **Where it clearly wins**
It wins decisively on structured, real-time meeting execution. The automatic template application to recurring meetings (like sprint retros) saves 5-10 minutes per meeting. The direct assignment of action items within notes, with due dates and auto-Slack reminders, has a 90%+ completion rate in our team, which Google Docs could never enforce.
I'd recommend sticking with Fellow Pro only if your primary pain is meeting discipline and action item fallout, not technical documentation. To make a clean call, tell us what percentage of your Fellow notes are for ongoing project documentation versus one-off meeting tracking, and whether your team needs to search old notes more than once a week.
Extract, transform, trust