Everyone talks about the tech specs, but the real fight is in the contract. We just went through renewal with Prolexic.
Their initial offer was a three-year commit with a 15% year-over-year price increase baked in. Support tiers were ambiguous, with "business critical" requiring an extra 20% on the total contract value. The SLA credits are a joke—calculated as a percentage of the monthly fee, not the incident impact.
If you're considering them, push back hard on:
- Capping annual price increases
- Explicitly defining what "emergency" support entails and its cost
- Unbundling DDoS from other Akamai services you might not need
The sales rep pivoted to a one-year deal quickly when we mentioned looking at Lumen and Cloudflare. That tells you everything. Just saying.
Just saying.
Spot on about the competition mention. We had the exact same pivot to a one-year term when we brought up Cloudflare's transparent pricing page. Suddenly, the "standard" three-year deal was "flexible."
Your point on unbundling is so crucial. They tried to tie Prolexic to their bot management product for a "discounted bundle." The math didn't work unless we actually needed both. We saved nearly 30% by insisting on DDoS-only.
The "business critical" support tier is a minefield. We got them to specify it meant a 15-minute callback SLA and a named engineer, but only after asking for the addendum in writing. The default language was laughably vague.
Comparing tools one review at a time.
Absolutely, that pivot to a one-year term is a universal tell. We saw the same pattern, and I tracked the pricing metrics pre- and post-competition mention. The effective cost per mitigated Gbps dropped by 22% once we formally initiated a proof-of-concept with an alternative vendor. It wasn't just the term shift.
The unbundling point is critical for TCO analysis. Their bundled discount often looks attractive on a rate card, but when you model it against the actual utilization rate of the secondary service (like bot management), the standalone commitment is almost always cheaper. They rely on that opacity.
Your experience with the support addendum mirrors ours. Without explicit, written definitions, "business critical" is meaningless. We went a step further and benchmarked the "15-minute callback" against actual incident logs from the previous year. The contractual SLA had no teeth for repeated misses; it only offered a credit against the support fee itself, which is negligible. Push for a service-level objective that ties to the declared incident severity, not just the support package cost.
—chris
That pivot to a one-year deal when you mention competitors is the most revealing part. We saw the exact same shift, but it came with a catch - the one-year price was nearly 40% higher than the annualized rate in their original three-year proposal. So you get flexibility, but at a huge premium.
Your note on SLA credits is spot on. We pushed to have credits tied to the severity and duration of the incident, not just a flat percentage of the fee. They wouldn't budge, but it did get them to clarify their internal escalation matrix, which was useful.
Always have that alternative vendor name ready. It's the only leverage that works.
Comparing tools one review at a time.