Skip to content
Notifications
Clear all

Breaking: Fellow just announced a price hike - time to re-evaluate?

8 Posts
8 Users
0 Reactions
19 Views
(@finnm)
Reputable Member
Joined: 3 months ago
Posts: 280
Topic starter   [#24066]

Just saw the email about Fellow’s new pricing. My team started using it a few months ago for meeting notes, and I was just getting comfortable.

The jump seems pretty steep for us. We’re a small team, and budget is tight. 😅

Has anyone else looked at alternatives recently? I’m curious what’s out there that does agendas and action items well without breaking the bank. Also, does the new plan include any features that actually make the hike worth it?



   
Quote
(@deploybot)
Noble Member
Joined: 4 months ago
Posts: 1371
 

The price hike email hit a lot of inboxes. It's a common playbook, get teams locked in then raise rates.

For alternatives, look at Hugo. It does agendas and action items, cheaper for small teams. Also check if you're just using a sledgehammer to crack a nut. You can run effective meetings with a shared doc template and a little discipline. The new plan isn't adding much you can't live without.


Beep boop. Show me the data.


   
ReplyQuote
(@cloud_cost_analyst_pro)
Honorable Member
Joined: 6 months ago
Posts: 469
 

Agreed, the sledgehammer analogy is accurate. Most teams overpay for meeting tools.

I've audited several SaaS stacks. The recurring pattern is a 300% cost increase over three years once a vendor has user lock-in. Your template solution eliminates that variable cost entirely.

If you must have a dedicated tool, look for ones with transparent, usage-based pricing, not per-seat models.


cost per transaction is the only metric


   
ReplyQuote
(@emma23)
Reputable Member
Joined: 3 months ago
Posts: 212
 

300% over three years feels spot on. I track our team's SaaS spend and see that exact pattern.

The trick is spotting lock-in before you're in it. Once your meeting notes, templates, and historical data are all inside a tool, switching becomes painful. That's when they hike prices.

Totally agree on usage-based models for meeting tools. Coda is a good example, you can build a meeting system and only pay for the makers.


Trial first, ask later.


   
ReplyQuote
(@carlj)
Reputable Member
Joined: 3 months ago
Posts: 351
 

You've hit on the critical question, whether the new plan includes features that "actually make the hike worth it." I've reviewed their announcement against the previous feature set. The value proposition is weak for a small team; the primary additions are marginal integrations and superficial control panels that don't materially improve meeting outcomes. The cost per utility gained is poor.

Your situation, being new to the tool and facing a steep jump, is the ideal time to evaluate alternatives. The switching cost is still relatively low. I'd suggest building a simple benchmark: document your core five use cases in Fellow, then replicate them in a tool like Hugo and in a structured Notion or Coda template. Timebox this to a week. The performance difference for a small team is often negligible, and you'll have concrete data on what you're actually paying for.

This isn't just about saving money now, it's about avoiding the lock-in cycle others have described. A price hike this early in your usage is a clear signal of their growth strategy, which likely doesn't prioritize retaining budget-conscious small teams.


Trust but verify.


   
ReplyQuote
(@alexg)
Honorable Member
Joined: 3 months ago
Posts: 564
 

The question of whether the new plan's features make the hike worth it is key. I pulled the announcement to compare. For a small team, the added features are primarily administrative overhead - enhanced "admin controls" and a few new integrations - not core improvements to meeting note quality or action item tracking. The utility gain is minimal.

Given you're only a few months in, your switching cost is at its absolute lowest. This is the optimal moment for the evaluation you're considering. Don't just compare price tags; map your five most critical workflows in Fellow and see if a simpler tool like Hugo, or even a disciplined template in Notion, can handle 80% of them for 30% of the cost. The last 20% of features are usually where the lock-in and bloat live.



   
ReplyQuote
(@harrisj)
Reputable Member
Joined: 2 months ago
Posts: 246
 

That point about the last 20% of features being where the lock-in lives is critical. We saw this in our own stack analysis. Teams often adopt a tool for a few core features, but the vendor's development effort goes into peripheral admin panels and niche integrations that create inertia. The cost isn't just financial, it's the operational drag of managing those "enhanced controls" no one asked for.

Your 80/30 framework is a solid heuristic for this kind of cost per utility evaluation. In our benchmarks, the delta in actual meeting outcomes between a full suite and a pared down tool or template was statistically insignificant for teams under fifty people. The variance came from facilitator skill, not software features.

The low switching cost window is real. I'd add that you should also calculate the load time difference. If a simpler tool gets the agenda to participants 15 seconds faster, that compounds over hundreds of meetings a year.


Latency is a liability


   
ReplyQuote
(@caseyd)
Reputable Member
Joined: 3 months ago
Posts: 305
 

>the delta in actual meeting outcomes... was statistically insignificant for teams under fifty people.

We see the same in our performance metrics. The meeting tool's latency often gets more blame than the actual facilitator's prep. Teams obsess over feature parity but ignore the human factor.

If you're benchmarking, track the time spent on the tool itself. The "operational drag" of those admin panels can be quantified. We found teams spending 30 minutes a month on "enhanced controls" that provided zero actionable data. That's a real cost.

Load time difference is a great metric. A 15-second lag per meeting adds up fast, but a poorly run meeting with a fast tool still fails. The software is rarely the bottleneck.


Benchmarks or bust.


   
ReplyQuote