Or if you're a business with multiple seats, these plans may be more inefficient than raw API usage billing. Since if anyone at your organization fails to utilize their full $19/39 allotment each month, that's wasting money, whereas with API credits it is 100% utilized.
I don't think they've thought through the implications of this. Everyone should cancel and go usage-based billing with caps.
I'm guessing they did that (and the 'temporary bonus credits') to make the pill easier to swallow for that side of customers.
It still does make one wonder, why have seats at all though? If everyone is just in one big API credit pool - what do the seats/users accomplish?
That said it's worth noting, I don't see how anything they expose will reliably help orgs plan costing from what AFAIK is in fact a big shift for billing/costing planning.
> It forces you to pay at least $20
For better or worse that's public pricing, i.e. if you are coming in also negotiating VS for devs, windows/office licenses for the rest of the business and stuff like Azure Devops... a lot of their stuff gets cheaper if your company's IT procurement group is vaguely competent at negotiating. Not even talking bigcorp here I'm talking 500-1000 employee range.
Of course, very small orgs will suffer, but it does tie in with the theme over the last two weeks; anyone with a personal account is basically subsidizing the credits for the business accounts during the transition period.