The "minimum floor" is why we started budgeting for the second-highest tier from day one. Treat the advertised starter price as fictional.
Your third variable point is spot on. Even if you lock down user and collection definitions, they'll meter something else later. We got hit with "API calls per collection per day" after our first renewal. The real cost is always hidden in the metrics you aren't tracking yet.
It's both limits, and you'll be charged for whichever dimension you exceed first. With 3 users and 10 collections, you pay for the 3 user licenses. The system will simply prevent the creation of an 11th collection until you upgrade your plan's collection cap.
The real cost complexity isn't in the interaction, but in the vendor's definition of a "collection". For marketing, a temporary campaign sandbox or each major competitor's folder will likely count as one. That's how teams routinely underestimate their needed tier.
Ask support to classify 3-4 specific workspace types you'll create, and get that in writing. Their answer often doubles the initial forecast.
infrastructure is code
Completely feel this. The "metered plan disguised as a tiered one" is the perfect description. We saw the same with temporary project spaces - each one counted, so our usage was always spiky.
It turns the pricing from a predictable cost into an operational tax, where you're constantly having to clean up or re-architect just to avoid a surprise invoice. Did you find any vendors that handle this gracefully, like offering true rolling windows or a pooled credit system?
Cheers, Henry
That's a really good way to put it, the annual commitment being the real trap. Once you're forced over the cliff to get that one extra collection, you're suddenly locked into paying for all those extra seats you don't need for a whole year. It feels less like buying software and more like accepting a loan.
Does anyone know if these companies ever make exceptions for that? Like, if you exceed your collection cap by one, would they ever let you pay a small overage fee for just that resource instead of forcing the full tier upgrade? Or is the jump always mandatory?
That's exactly what I'm trying to figure out too. I thought I understood it until I read the fine print. The replies here are making me think it's not a simple 'either/or' but that both limits apply at the same time.
So for your team, you'd pay for the three users, but if your plan only allows five collections, you'd hit a wall. The confusing part is how they define a collection for that limit. Is a folder of bookmarks for one competitor a collection? Is a draft campaign a collection?
I'm leaning towards what user1193 said. You have to ask support for specific examples from your own workflow before you can even guess at the real cost.
Still learning.
Yep, you've got the interaction right. Pay for the users, but get blocked by the collection cap. That "folder of bookmarks for one competitor" example is the exact kind of thing that will get you. In my experience, if it has a unique name and can be shared or archived independently, it's almost always billed as a collection.
The only thing I'd add is to test their export/deletion policy too. Sometimes "archiving" a collection still counts against your cap, forcing you to fully delete it to stay under your limit. Really changes how you think about temporary workspaces.
ship it
Your point about the support agent's examples is exactly right. In my experience, that's the only way to get a reliable mapping between their terminology and your actual data model.
The trouble is, those interpretations can shift. You'll get one answer from pre-sales engineering, and a stricter one from the billing team six months later when they audit your account. I now ask for written confirmation that the provided examples are the definitive billing logic for the term of the contract. It doesn't always work, but it creates a paper trail.
Without that, their broad definition of a collection as a "top-level entity" becomes a backdoor for metering every project phase and client silo.