Full narration of the briefing. Click a section heading to jump the player to that moment.
Many enterprise buyers quietly overpay at their Datadog renewal. They focus their energy on arguing over the rate card, but the actual invoice is driven by something else entirely. Overspending happens because of billing mechanics like the ninety ninth level host watermark, tag explosions, and new SKUs that sit outside your existing commit pools. To secure a fair deal, you must negotiate the mechanics, not just the rate.
Let us walk through the five key points that define your Datadog spend. Point one is the high watermark mechanic. This is perhaps the most significant driver of infrastructure costs in a modern cloud environment. This mechanic prices your entire infrastructure at the peak hourly host count.
It does not look at your average usage or your typical workload. It happens because the system is designed to capture the maximum footprint you ever touch. Even if that footprint only exists for a single hour in a thirty day period. Consider a concrete example.
Imagine you have a standard production environment of five hundred hosts. Everything is running smoothly and predictably. Then, a single autoscaling event or a scheduled load test pushes that count to fifteen hundred for just two hours. That spike sets the billing for the entire month.
You are now paying for fifteen hundred hosts for all seven hundred and twenty hours of that month, even though you only used them for two. The counter move is to negotiate for demand smoothing or averaging language. This is a common contractual lever that many procurement teams overlook. You should explain that these spikes do not represent your true infrastructure footprint.
Ask for the monthly bill to be based on an average of your daily peaks. This costs the vendor very little in terms of actual resources, but it removes your worst, most inflated invoice. It creates a more predictable and fair cost structure. Point two involves custom metrics and the phenomenon known as tag explosions.
This is where costs can quietly compound without anyone noticing. Custom metrics bill on every unique name and tag combination beyond your standard allotment. Every time you add a new dimension to your data, you are adding cost. It happens because cardinality compounds.
If you have ten metrics and you add ten tags, you suddenly have one hundred unique data streams to pay for. For example, a developer might add a unique user ID or a container ID as a tag to a custom metric to help with troubleshooting. If you have thousands of users or ephemeral containers, that single tag can create millions of unique combinations. The resulting bill can be staggering.
When we analyze renewals, we often find that a third of the growth is not due to real workload increases. It is simply a billing artifact of poor tag hygiene. The counter move is to audit tag explosions sixty days before your renewal. You must clean the estate before you begin the process of pricing it.
Look for metrics with high cardinality that are rarely used in dashboards. By removing these unnecessary tags, you can significantly reduce the baseline for your next contract. Point three covers new AI offerings like LLM Observability and Bits AI. These are powerful tools, but they carry specific billing risks.
These new SKUs are often deliberately launched outside your existing commit pools. This means your current discounts may not apply to them at all. By keeping them separate, the vendor can convert your adoption of new technology into undiscounted spend. It is a way to increase the effective rate you pay.
Consider a team that starts experimenting with LLM Observability. They assume it is covered under their broad infrastructure agreement. They soon realize that every token monitored is billed at a premium rate with no volume discount. The cost of innovation suddenly becomes a budget crisis.
You must realize that your leverage is highest before you become dependent on these tools. Unit prices are only truly negotiable at the start. The counter move is to pool these SKUs at the time of signature. Demand that new products be included in your overall commitment and benefit from your tiered discounts.
Negotiate for a future proofed contract that allows you to draw from your commit for any new product in the catalog. This protects your budget from sudden shifts in technology. Point four is about consolidation bundles. These are often presented as a way to simplify your billing, but they can hide significant costs.
These bundles blend a generous infrastructure discount with very thin discounts on logs and other high growth areas. It is a classic shell game. It happens because the vendor wants to show you a big headline discount on your most visible spend, while the real money moves to the less scrutinized line items. For instance, you might see a deep discount on your host count, but find that your log management costs are rising at double digit rates every quarter.
Without benchmarking each product individually, you cannot see if you are actually getting a good deal on the services that will drive your future growth. The counter move is to demand per product pricing. Benchmark every single line item against its own industry standard band. Do not accept a single blended rate.
Furthermore, use options like Flex Logs or a credible OpenTelemetry pilot to create competition. Showing a viable path to alternative solutions gives you leverage to reprice indexing. Even if you do not plan to switch, having a documented pilot of an alternative stack makes your demand for lower log pricing much more credible during the renewal. Point five addresses the trade off between on demand flexibility and contractual commitment.
This is where many buyers leave money on the table. Staying on demand for the sake of flexibility sounds prudent, but it often means you are paying significantly above the committed rates for every unit. It happens because you are essentially buying an expensive insurance policy against low usage. The premium for that policy is often higher than the cost of a slight over commit.
Imagine keeping a portion of your estate uncommitted to avoid being locked in. Over a year, the extra you pay in on demand rates could have funded an entire extra month of service. Do not buy options by staying uncommitted. Instead, you should seek to build flexibility directly into your commitment through pooling and true down rights.
Timing is also a critical factor. You should aim to close your deal at a quarter end, particularly at the end of the calendar year. A credible threat to let the deal slip past December thirty first can reliably move several points in your favor as sales teams scramble to meet their annual targets. We have covered a lot of ground today.
But if you remember only one thing from this briefing, let it be the importance of preparation. The most effective thing you can do is pull your own usage data sixty days before your renewal date. Do not wait for the vendor to provide their report. Find the specific fifth of SKUs that are driving the vast majority of your spend.
Identify where the tag explosions and peak watermarks are occurring. Cleaning the estate before you price it beats the entire first round of discounting every single time. It puts you in control of the conversation. Negotiate the mechanics, not just the rate.
Good luck with your next renewal. We hope this briefing has been helpful for your procurement strategy.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded.
Talk to a Datadog negotiator