This is driving me crazy. We evaluated Camunda last year, got a quote, built our business case around it, and now they’ve restructured their licensing. Our original estimate assumed per-instance pricing, but apparently that’s changing, and now they’re talking about different tiers based on throughput or execution time or something.
I can’t even budget properly because the goalpost keeps moving. By the time we finish the RFP process and negotiation, the actual cost could be 30% higher or lower depending on how they’ve restructured things by then.
I get that enterprise vendors need to evolve their pricing, but how do other people actually handle this uncertainty when building financial projections? Do you just add a big buffer to your estimates? Build in quarterly reconciliation? Or is there a better way to lock in costs or at least understand the formula well enough to predict where things are heading?
I’m leaning toward looking at platforms where the pricing is more predictable from the start. Has anyone actually managed to forecast multi-year costs with a vendor that’s historically shifted their model?
I’ve dealt with exactly this. The vendors don’t like to admit it, but their pricing moves around because they’re trying to extract more value from longer-term customers once you’re locked in.
What we started doing is getting the pricing formula in writing as part of the contract, not just the current rates. So instead of a flat price, we negotiated a structure: base cost X plus Y per execution unit, with a maximum annual increase of 5%. That protects you for at least a few years.
The other thing is to explicitly ask during RFP what’s actually changing and why. Sometimes they’ll tell you if you’re direct about it. We found out Camunda was shifting to throughput-based because their old per-instance pricing didn’t capture value the way they wanted. Once we understood that, we could actually forecast based on our expected throughput instead of trying to guess at future per-instance costs.
Build your financial model around actual usage metrics that won’t change, not around tiers that they’ll reshape.
One thing that helped us: get at least three years of their pricing history if possible. Look at what actually changed, by how much, and when. Most enterprise vendors follow a pattern. If Camunda’s been shifting every 18 months, you can probably predict that trend and bake it into your forecast.
The real issue with traditional enterprise platforms is that they optimize for lock-in, which means pricing can move after you commit. Instead of trying to predict their moves, some teams I know shifted to platforms with transparent usage-based pricing from the ground up. Those vendors built their entire model on simplicity, so changing it would hurt their competitive position. You get more stability when the vendor’s model is fundamentally built on clarity rather than opaque enterprise negotiation.
Ask for historical pricing data and any public roadmap around licensing changes. If they won’t give you either, that’s a signal. We’ve found that vendors transparent about their pricing strategy are way less likely to shock you later. Also negotiate a price-hold clause for at least 2-3 years, not just contract duration. Some vendors will agree because it locks you in, but it protects you from mid-cycle surprises.
Yeah, this is exactly why we moved away from enterprise vendors with shifting models. The constant repricing is a tax on your business continuity.
When we switched to a unified subscription model, the pitch was simple: pay one price, get 400+ models, no surprise restructurings later. It’s not sexy enterprise positioning, but it’s predictable. We could actually build a multi-year budget without guessing what the vendor would change.
The best part? Because the platform isn’t trying to extract value through opaque licensing tiers, they don’t have incentive to keep reshuffling the model. Your cost per execution is locked in.
If you’re frustrated with the moving goalpost on Camunda, look at platforms where the pricing is transparent by design, not just by negotiation. You’ll spend way less energy on financial forecasting and more on actual automation.