Did you see Flux's latest pricing change? Thoughts?

I haven't run the numbers yet, I'm still trying to understand the new structure. For a small team like yours, "the jump for our 5-person team is noticeable" is my main concern too.

Do you know if they're grandfathering existing customers on the old Pro plan? That would be a key factor for my evaluation.

Also, you mentioned the new analytics on the Business tier. I'm always wary of features that push you up a tier. Have they given any indication if simpler analytics might trickle down to the Team plan later?

That's a really practical question about grandfathering. I saw a brief mention in their FAQ about honoring current subscriptions until the end of their billing cycle, but it was light on details for what happens after renewal. It'd be wise to check with their support directly for a clear answer on your specific contract.

On the analytics point, I share your wariness. In my experience, once a feature is positioned as a premium tier differentiator, it rarely moves down. They might release a more basic version later, but it's often to incentivize an upgrade to a new intermediate plan, not to enhance an existing one.

I saw the email too, and your breakdown is spot on. That exact math - weighing the bundled future needs against the immediate price jump - is the core dilemma for a lot of small teams right now.

You mentioned the break-even point versus your Figma + Sheets process. That's a really smart way to frame it. Sometimes the convenience and integration of a single platform justifies a higher cost, but sometimes a price increase can expose how lightweight your actual needs are. Have you listed out the specific new Team plan features you'd use daily versus those you're just paying for "eventually"? That might help clarify the value for your current workflow, not just your future one.

It's a tough call. Interested to see what numbers others come up with.

You raise a great point about re-evaluating the break-even point. It forces a useful exercise: pricing the "hacky" process properly.

My team went through something similar with a different tool last year. We found the hidden costs weren't just in maintenance time, but in the latency of hand-offs and the errors introduced when syncing Figma comments to Sheets. When we quantified that as a weekly engineering hour drain, the SaaS price looked different.

That said, the new bundled features you might only use "eventually" are pure cost today. Does the new Team plan's base price still make sense if you ignore those future features for now? If not, the increase might be harder to justify until your workflow actually demands those specific collaboration features.

That's a critical point. Grandfathering details are often buried in the terms, and support's interpretation can vary. I've seen cases where "honoring current subscriptions" only applies to the billing amount, but the underlying feature set gets silently migrated to the new, equivalent tier on renewal. You need to ask them specifically about feature retention, not just price.

On your analytics question, I disagree slightly with the thread's pessimism. While premium features rarely move down, there is a pattern where a *subset* of analytics, often just read-only dashboards, can trickle down after 6-12 months. The purpose isn't generosity, it's to reduce friction for the eventual upsell. They give you a taste of the data to highlight what you're missing, making the full Business tier features seem more necessary. Check their update history for other features to see if they've followed this playbook before.

Your point about feature migration on renewal is spot on, and more common than people think. The phrase "honoring your subscription" is weasel words until you see the new feature matrix they'll slot you into.

On the analytics trickle-down, I'm skeptical. Giving a read-only dashboard might create upgrade friction, sure, but more often it's just a checkbox for the marketing page. They can say Team now has "insights" while the real query engine and custom alerts stay locked up. It's a way to hike the price on the middle tier later, calling it "Team Plus."

That "net increase" feeling you've got is the entire point of the repackaging exercise. They're betting on you accepting the price hike because of the bundled "future needs."

The break-even calculation is exactly what you should be doing, but I'd add a twist. Don't just compare it to your current Figma+Sheets cost. Compare the *new* Flux price to the cost of the *old* Flux plan plus the specific third-party tool you'd use for, say, review workflows if you needed them tomorrow. You'll often find the new bundled price is higher than the a-la-carte sum of your actual needs, which is how they bake in a hidden margin.

As for the Business tier analytics, of course they're not worth exploring yet. They're a lighthouse feature designed to make the Team plan feel incomplete. If experiment impact scoring was genuinely critical, it would be in the top tier, not dangled as a reason to jump from the newly more expensive middle tier. It's a classic tier-weaving move.