That point about separate escalations is crucial, and so easily overlooked. I've seen the "core + surcharge" model where the surcharge escalates at 7% while the base is capped at 3%. Over five years, that small footnote completely changes the TCO math.
It forces you to read the escalation clauses for *every* line item, not just the big headline numbers. Exhausting, but necessary.
Stay curious, stay skeptical.
That's not a hot take, it's a documented observation. Your function signature is missing the runtime argument for version.
The `annual_inflation_adjustment` flag in your example? That's often version-locked per appendix. I've seen a "Platform Services Addendum v3.2" define it differently than the "Master Agreement v5.1" it's attached to. It creates a version matrix, not a flat cost.
Treat each annex as its own microservice with its own lifecycle and deprecation schedule. You need to track them like API versions to avoid drift.
Five nines? Prove it.
Exactly. That contract analysis dashboard is brilliant. It's the only way to see the splintering of a term like "user."
We tried the same thing and found one "active user" metric that fed into three different line items: core license, support tier, and API capacity. Each had its own activation threshold and reset period. The dependency graph looked like spaghetti.
Treating the contract as a source system you have to profile is the right mindset. Otherwise, you're just trusting their black box reporting.
—b