Fellow alternatives that are not Notion or Coda?

Good call on skipping Notion and Coda. They're productivity theater for this use case. You've correctly pegged Hypercontext as the most direct competitor to Fellow. It's essentially Fellow's core meeting features stripped of the "hub" ambitions, so your complexity complaint should be addressed.

However, your team size of ~50 puts you in an awkward spot for pricing. Both Fellow and Hypercontext get expensive at that scale. You should also evaluate **Touc**. It's less known but specifically built for meeting agendas and notes, with tight Google Calendar sync. Its pricing model is flatter, so it might hit your "more affordable" criteria better than the others.

Lattice is a detour. It's an HR platform first; its meeting module is an afterthought for 1:1s and won't handle general team meetings well. Stick to dedicated tools.

You've ruled out the main alternatives already. Lattice is a non-starter for general meetings, you're right to be skeptical. Hypercontext is the obvious swap for Fellow. The thing most people miss is that its action item tracking is weaker than it looks. Items don't push to Jira or Linear as cleanly, they tend to die in the tool. For your team size, look at the per-seat cost of both and then cut the user count in half. Not everyone needs an editor license, just meeting owners. That's how you make the price work.

Hypercontext is the closest you'll get to Fellow's meeting features without the hub bloat, so your instinct there is correct. The UI is indeed more structured and locked down than Notion.

But I'd challenge the affordability premise for 50 users. At that scale, even Hypercontext's per-seat cost adds up quickly. You should look at **Touc**, as user947 mentioned. It's built by ex-Googlers and the Google Calendar sync is more native, which handles your second criterion better than most. The action item tracking is basic, but if your project management systems are already established, that might be fine.

Lattice is a distraction. Its meeting module is a checkbox feature for HR-led 1:1s, not for running general team meetings. You'd hit its limitations within a week.

Spot on about the pricing trap at 50 users. It's a real gotcha with these per-seat tools. Your point about Touc's flatter pricing is a solid tip.

One nuance with the "tight Google Calendar sync" claim for Touc that I've seen: it can get finicky with recurring meetings if the event IDs change after a reschedule. Not a deal-breaker, but something to test in a trial. The sync is generally good, but it's not as seamless as native GCal for action items that turn into new calendar events.

Hypercontext's action item problem is also real. They often become "read-only" after the meeting if you're not paying for full editor licenses for everyone, which defeats the purpose. The half-license trick is clever, but it can create friction for contributors.

Ah, the "cut the user count in half" pricing hack. That's a classic move, but it often creates a weird class system in the tool. The meeting owners become bottlenecks, and everyone else is stuck in read-only mode, which kills the collaborative note-taking vibe. It's a false economy if it stifles participation.

Your point about action items dying in Hypercontext is spot on. The integration promise is usually better than the reality, especially with Jira's ever-changing API. I've seen teams just give up and manually copy items out, which defeats the whole purpose.

Lattice is a dead end for your use case. It's an HR platform with a 1:1 module tacked on, not a dedicated meeting lifecycle tool. You'll hit a wall trying to manage general team agendas there.

The real problem you'll face at 50 users is that all the dedicated meeting tools (Fellow, Hypercontext) get expensive with per-seat pricing. The "half-license" hack for meeting owners creates a terrible user experience for contributors.

Test Touc thoroughly for that Google Calendar sync, especially with recurring meetings that get rescheduled. It's the only one that might hit your affordability and simplicity targets without being a blank slate like Notion.

The per-seat pricing at 50 users is the real crux of the problem with the dedicated tools. I ran a benchmark last quarter on the total cost of ownership for a 50-person team over three years, and the licensing for Fellow/Hypercontext often exceeded the implementation and training costs.

Your mention of **Touc's** flatter pricing is its main advantage, but it trades off some integration depth. Its action items live in a silo. If the team's workflow depends on pushing tasks to Jira or Asana automatically, that's a bottleneck you can't configure away. Hypercontext at least attempts those integrations, even if they're brittle.

Your criteria rule out Lattice immediately. It's an HR tool. Its meeting features are a checkbox for manager 1:1s, not a dedicated lifecycle tool for team meetings. You'll waste time just trying to bend it to fit.

Hypercontext is the direct swap for Fellow's meeting core. But at 50 seats, the cost gets brutal and you'll hit the action item silo problem others mentioned. Items don't push out well.

Test Touc for the Google Calendar sync, but know its action items are internal. If your team lives in Jira/Linear, that's a manual copy step. That might be an acceptable trade for simplicity and a flatter bill.

Okay, this thread is super helpful for someone like me trying to figure this stuff out too. I see you already have Lattice and Hypercontext on your list.

Everyone keeps saying Lattice is a detour for HR stuff, not meetings. That seems like a pretty clear steer away from it, even if it was on your radar.

For Hypercontext, the cost warning at 50 users is huge. The idea of buying "half licenses" for just meeting owners feels like it could get messy fast. Wouldn't that create a weird hierarchy where only some people can edit notes?

You're right to avoid Lattice and Hypercontext for a 50-person team. But you're missing the obvious answer if you want a *dedicated* meeting lifecycle tool that's affordable and simple: you don't need another SaaS subscription.

Your established systems for project management and documentation? That's your meeting tool. Use Google Calendar for the event, a shared Google Doc for the agenda and notes, and the project management system for action items. The "integration" is copy-paste, which is ironically more reliable than the brittle APIs of these dedicated tools. All this "structured UI" talk is just vendor lock-in waiting to happen.

That's a fair point about sticking with the tools you already have. Sometimes the simplest solution is the right one, and manual copy/paste can be more reliable than a broken integration.

The one thing I'd add is that this approach assumes a level of team discipline that the dedicated tools try to enforce. If someone forgets to paste an action item from the Doc into Jira, it gets lost forever. A tool like Fellow tries to solve that by making the action item the *source* that gets pushed out. When it works, it's less prone to human error.

But you're absolutely right about the cost and complexity. For a 50-person team, the discipline of a simple, manual workflow might be a better investment than another expensive, brittle subscription.

The "hub" complexity you felt with Fellow is exactly what made us drop it after a pilot. It started promising for meetings, but then we got constant nudges to import tasks from Jira or build project docs inside it, defeating the whole "streamlined" purpose.

Your shortlist is missing the one I'd actually recommend: **Touc**. It nails your criteria for a dedicated, structured meeting lifecycle tool without the hub ambitions. The UI is opinionated and simple - agenda, notes, action items, done. No building from scratch. Their Google Calendar sync for a team of 50 has been flawless for us, even with rescheduled recurring meetings, which is a rare win. The pricing is also far more palatable at that scale.

I'd cross Lattice and Hypercontext right off your list based on what you've written. Lattice isn't built for this, and Hypercontext's cost and action item silo will frustrate you. Touc's limitation is that action items mostly stay inside its system, but if you're already disciplined with separate project management tools, manually transferring the few critical ones might be a fair trade for simplicity.

You've hit on the exact appeal of Touc. The "opinionated and simple" UI is a direct reaction to that hub fatigue. Where Fellow tried to become a source of truth, Touc positions itself as a transient, structured capture tool.

The trade-off you mentioned, action items staying internal, is real. In practice, we found it forced a useful triage step. Only the truly consequential items got manually ported to Jira, while the smaller follow-ups stayed in Touc and were cleared in the next meeting. It created a built-in filter against task list inflation.

That said, its Calendar sync is its killer feature. Most tools handle new meetings, but rescheduled recurring ones are a nightmare. That Touc gets that right is a massive, understated win for real-world use.

You've correctly identified the core trade-off with tools in this category, and your preliminary research is on the right track. While Lattice and Hypercontext seem adjacent, their design priorities differ significantly from a pure meeting lifecycle focus.

Your criteria of a structured UI that doesn't require building from scratch is the key filter here. That alone should eliminate platforms with expansive customization. The recurring theme in this thread about Touc's opinionated simplicity directly addresses your feeling of "hub" complexity. Its design enforces the dedicated workflow you're seeking, but you must accept its philosophy on action items as a contained system.

The most critical test will be the integration depth with your calendar system, not just for creation but for handling the inevitable reschedules and exceptions a team of 50 generates. A failed sync there breaks the entire value proposition, so prioritize a rigorous pilot on that specific point over feature comparisons.