Alright, let's talk about a real-world cost optimization I've been implementing for clients lately. Fellow is a fantastic tool for meeting culture, but when you're looking at a company-wide rollout, the per-seat pricing can get eye-watering fast, especially for teams that might not live in it daily.
The core insight is this: **The highest leverage users of Fellow are managers, not individual contributors.** The value isn't just in note-taking; it's in agenda building, tracking action items across reports, providing structured feedback, and having a single source of truth for 1:1s and team meetings. An IC might take notes, but a manager *orchestrates* the process.
Here's the practical playbook I'm recommending, born from a few painful, over-budget rollouts:
* **Managers are Full Users.** They get full licenses. They own the meetings, build agendas in Fellow, record talking points, and assign action items. This is their command center.
* **Individual Contributors are "Light Users" via Integration.** Instead of a Fellow license, ICs interact with Fellow *through your existing communication tools*. This is key.
* **Agendas & Notes:** Managers share the Fellow meeting link via calendar invite. ICs can view the live agenda and notes in the browser *without an account*. They can even add topics via the "Suggest" option if the manager enables it.
* **Action Items:** When a manager assigns an action item in Fellow to an IC, it can be configured to automatically send a task to that person's tool of choice—like a Slack DM, a Microsoft To-Do list, or even an email. The IC tracks and completes it there, and the manager marks it done in Fellow. The IC never logs into Fellow.
* **1:1s:** The manager owns the 1:1 doc. They can share read-only notes or key feedback via your existing HRIS or docs platform after the fact. The conversation itself is what matters.
**The Gotchas & Battle Scars:**
* **Culture Pushback:** Some teams feel like "second-class citizens" without logins. You must frame this as a workflow efficiency, not a privilege. It reduces tool fatigue for ICs.
* **Process Discipline:** This model falls apart if managers aren't disciplined. They must be the ones driving the agenda population and action item updates. It requires a bit of change management.
* **Integration Reliance:** You're betting on the stability of the Slack/Microsoft Teams/email integrations. Test them thoroughly. Have a fallback (e.g., a quick screenshot shared in chat) for when they hiccup.
In a recent 200-person company, we cut a proposed 150-license Fellow bill down to 45 licenses for all people managers and above. The savings were massive, and the meeting hygiene actually improved because responsibility was clearly placed on leadership. It's not the right fit for every org (especially if you're using Fellow for collaborative brainstorming sessions), but for structured, recurring meetings, it's a proven cost-saver.
Implementation is 80% process, 20% tool.
This is a solid approach for trimming costs, and I've seen it work well in practice. However, it's crucial to manage the cultural shift carefully. If you're designating managers as "command centers," you need to set clear expectations for them on transparency.
If they're the only ones with full access, they must be diligent about sharing notes and action items promptly through those integrations. Otherwise, ICs can feel left out of the loop, which undermines the tool's purpose of creating a single source of truth. Have you run into any pushback on that front?
Stay constructive
Absolutely love this breakdown. It mirrors exactly what we found when piloting Fellow last quarter.
We actually took the "light user" idea a step further. For team syncs, our managers post the final, cleaned-up notes and action items directly into our main Slack channel right after the meeting, using the Fellow integration. It keeps everyone aligned without needing another app open. The key was getting managers to commit to that 5-minute post-meeting ritual.
Have you seen any specific integrations work better than others for that IC transparency loop? Slack seemed like the natural fit for us.