Datadog Negotiation, Part 1: Talking Points on Twenty Meters and the High Water Commit

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

Twenty meters 0:00

Datadog built the best observability product of its generation and wrapped it in the most sophisticated metering machine in software. More than twenty separately priced products, each with its own unit: hosts, gigabytes ingested, events indexed, sessions, invocations, custom metrics, each growing on its own, and several engineered so that ordinary engineering behavior inflates them quietly. The renewal conversation this produces is the most predictable in modern software: your usage has grown, the overage rates are punishing you, and the merciful answer is a bigger commit. I am Tom, Claire is with me, and this is part one of the VendorBenchmark Datadog playbook.

Engineering first, commerce second 0:48

The buyer's counter is engineering first and commerce second. Most of what a Datadog bill contains is not observability. It is ungoverned telemetry: indexed noise, unmanaged cardinality, staging environments monitored at production fidelity. The difference between an estate as found and an estate as engineered is routinely thirty to fifty percent of the bill before any negotiation begins.

Then the commercial layer: commits sized to the optimized baseline rather than the panic peak, overage priced at contracted rates instead of the list premium, spend fungible across the twenty meters, and true down rights so the estate can shrink as the engineering improves.

What changed since you signed 1:29

What changed since you signed. The platform became a portfolio of meters: what landed as infrastructure monitoring for one team is now APM, logs, security, RUM, synthetics, serverless, and a dozen more, each its own SKU and its own growth curve. The billing mechanics reward your worst month: host products measure toward upper percentile peaks, so autoscaling bursts, migrations, and incidents get memorialized into the baseline your commit is sized against. The overage premium sells the commits: usage above commit bills at on demand rates, and that premium is the renewal pitch's engine.

And their calendar ends thirty first December, and generosity peaks into the fourth quarter.

The meter map 2:18

Where the bills hide. Custom metrics: every tag combination is a billable series, and cardinality compounds silently as engineers add labels; the fix is the audit, retirement of unqueried series, and linting in the pipeline. Log indexing: ingest and indexing bill separately, and indexing everything ingested is the default and the majority of most log bills, for data rarely searched; exclusion filters become the default, with cheaper retention for the archive. Host high water marks: know each SKU's percentile and window, and never commit to a number an outage created.

Containers and churn, sessions, tests, and invocations: each gets an owner, a budget, and a dashboard.

The estate math 3:04

The estate math, worked. An illustrative three million dollar estate, where the renewal pitch says usage supports three point four. The census decomposes it: logs are one point two million, ninety percent of it indexed and mostly never queried; custom metrics are four hundred thousand of unmanaged cardinality; and dev and staging sit inside the host lines at production fidelity. Exclusion filters and tiered retention take logs down around forty five percent.

Cardinality governance saves another quarter million. Right sizing and peak shaping take three hundred thousand more. The held baseline lands near one point nine million, and the commercial layer builds on that.

Open instrumentation 3:49

The structural lever this category uniquely offers is open instrumentation. Telemetry collected through open standards can be routed to any backend, which turns agent lock in into an ordinary commercial relationship. The migration is incremental: new services on open standards by policy, high volume movable tiers first. It pays twice: directly, where cheaper backends absorb the low value tiers, and structurally, because the vendor's pricing discipline tracks your demonstrated ability to leave with remarkable precision.

An estate on proprietary agents asks for discounts; an estate on open standards sets prices. Part two walks the runway and the December close. More briefings at redresscompliance dot com slash research videos.