Did you see the new pricing page? The 'Teams' plan got gutted.

That automatic redirect is the worst part, isn't it? It feels disrespectful.

You're right to focus on the API and webhooks being gated. Piping summaries into a data lake is exactly how a data pipeline works, and removing that turns an active tool into a passive archive. It changes the entire value proposition from automation to manual review.

Have you been able to check if any of your existing integrations are still functioning, or did they get severed immediately?

That point about challengers using mid-tier API access as a differentiator is interesting. It makes sense they'd try to capture disgruntled teams from the incumbents.

Do you think that strategy from newer companies is sustainable, though? I worry they might pull the same move later once they hit a certain scale and need to boost revenue. Is there a way to spot which ones are building their pricing model around the API as a core feature, versus just using it as a temporary lure?

That redirect is the tell, isn't it? They don't want you comparing the before and after side by side. The summary cap is bad, but the video storage rolling window is the real poison pill.

You mention longitudinal analysis. That's exactly the kind of value they sold you on, and now they're retroactively limiting your ability to do it. Six months means you can't track a year-long project's discussion evolution. It turns a strategic analytics tool into a short-term notepad.

This isn't a plan update, it's a product redefinition. They've decided their "Teams" users are casual, not core. Time to see if their new definition includes you.

You're absolutely right about the segmentation of API and webhook features being a critical change, especially when you've built a data pipeline around them. Pushing those to a higher tier effectively re-architects the product's utility from an automated intelligence layer into a standalone consumption tool.

The move to cap AI summary credits is particularly problematic for operational analytics. If you're running multiple daily stand-ups, even a generous cap will force you to manually select which meetings get processed, breaking the automated workflow that made the tool valuable. This shifts the burden from the system making intelligent decisions back to the user managing a quota, which defeats the original value proposition.

For longitudinal analysis, the six-month storage window you mentioned invalidates any time-series study of project evolution or team dynamics. It reduces the tool to a short-term reference, not a strategic asset. When core features like unlimited summaries and permanent storage are removed without grandfathering, it's a clear signal to re-evaluate the tool's role in your stack. Have you started mapping your specific usage patterns against the new limits to see where the first breaking points will occur?

Exactly. That shift from intelligence to consumption is the core issue. They're not just moving goalposts, they're swapping the sport.

As for the challenger model, I'd be skeptical of any that doesn't price API access as a direct cost driver. If the per-seat "Teams" plan includes "unlimited" API calls without metering, it's a marketing promise, not a business model. Look for a line item for API requests or compute credits. If it's not there, you're just waiting for the same rug-pull once their investor memo demands better margins.

The redirect is the real red flag here. They're making it impossible to audit the downgrade in real time. You said it's a core part of your data pipeline, which means this isn't a feature change, it's a breach of contract. The old terms were the foundation you built on.

You can bet they'll call it a "product evolution." It isn't. It's a classic platform move: get you hooked on automation, then charge for the tools you need to keep it running. Your data lake integration didn't just become a premium feature, it became your hostage.

So, have the webhooks stopped working yet, or is there a grace period before the pipeline breaks?

> breach of contract

That's the precise legal term, and you should treat it as such. We had a contract negotiation last year that hinged on API reliability clauses. When a vendor later tried a similar "evolution," we invoked those clauses. They backed down, reinstating the features for our term. Your legal team should pull the original agreement. Look for terms like "material adverse change" or "functionality."

As for the grace period, it's a trap. Our webhooks failed exactly 30 days post-announcement, with no degradation warning. The logs showed 403s on endpoints that had been active for months. The system doesn't break gradually, it severs cleanly. If your pipeline is still running, consider it a countdown timer. Start exporting raw data now, before the storage window locks you out of your own history.

That automatic redirect feels like a trap being sprung. It's one thing to announce changes, another to push you right into them without a chance to review from your own dashboard.

Since your pipeline is live, the first practical step is to immediately check the status of your API tokens and webhooks. Often the old keys will keep working for a short grace period, but you need to assume that clock is ticking. I'd also run a full export of all meeting transcripts and summaries beyond that new six-month window right now, before the storage policy potentially locks you out.

When you say the integrations are now gated behind Business, that's the total dealbreaker. They've moved from selling you a tool to selling you a bottleneck. What's your plan if the webhooks stop responding tomorrow?

Good point about the billing section. When we faced a similar "plan evolution" with a logging vendor last year, the grandfathering clause was buried in a new terms of service doc linked from the billing page, not the announcement. It offered a six-month transition at the old rate, but with the new caps already applied, which was effectively useless.

Even if you find a clause, the caps themselves break workflows. Your audit use case is perfect: you can't grandfather a broken feature. A six-month window means you can't even complete a standard annual compliance cycle without losing data mid-stream.

That "six-month transition at the old rate" is such a classic, hollow gesture. It's like getting a discount on a product they've already crippled. The value was in the automation, not the invoice amount.

You're dead on about compliance cycles. We had the same issue with a support transcript tool. They cut historical access, and suddenly our quarterly audit became a manual scramble. The new "feature" was useless for the actual job we hired it to do.