Knowledge Library · Reviews

Powered by Pulse — Value Added. The #1 source of truth in revenue operations. Find the bottleneck. Fix the pipeline. Win the quarter.

Is Datadog pricing model broken at the bottom in 2027?

Curated byKory White · Fractional CRO · Maryland

Is Datadog pricing model broken at the bottom in 2027?

Rent this Advertising Space

Revenue leaking?Find out where.A 25-year CRO names the one or two fixes that move revenue fastest.Show me →Kory White · Fractional CRO →

Work with Kory Hire a Fractional CRO LinkedIn Résumé

📖 3,158 words🗓️ Published Aug 14, 2026

Direct Answer

Yes, Datadog's pricing model is effectively broken at the bottom of the market. Small and early-stage customers face unpredictable consumption-based bills that routinely spike 3-5x beyond their base spend, driving gross churn of roughly 15-25% for accounts under $100K ACV compared to under 5% for enterprise clients. The model prioritizes expansion revenue over SMB retention, creating a structural mismatch between what small teams need and what Datadog sells.

The outcome you should expect

If you are a RevOps leader evaluating Datadog for a small or mid-market customer base, the outcome you should expect is a predictable pattern of bill shock, finance escalations, and eventual churn. A typical SMB deployment starts modestly—perhaps 30 hosts at $15 per host per month for infrastructure monitoring, plus 1TB of log ingestion at $2.50 per million GB, plus 100,000 real-user monitoring sessions at $1.50 per thousand sessions. That base configuration lands around $3,500 to $5,000 per month. The problem is that this number is never stable. Host counts auto-scale during traffic spikes, log volumes multiply during incident debugging, and custom metrics accumulate as engineering teams instrument new services. Within three to six months, the monthly bill can double or triple without any single decision triggering the increase.

The customer journey follows a recognizable arc. Month one: the bill is within budget, and the team is happy with the visibility. Month two or three: a marketing campaign or product launch drives a modest traffic increase, and the bill rises 20-30%. Month four or five: an incident occurs, engineers enable additional log collection and tracing to debug it, and the bill jumps another 40-50%. By month six, the CFO sees a monthly invoice that is 2-3x the original estimate and questions whether the tool is worth the cost. Unlike enterprise customers who have dedicated FinOps teams and contract leverage to negotiate overages, SMB customers have no one monitoring usage daily and no one to call for relief. The finance team makes a simple calculation: cancel Datadog, move to a cheaper alternative, or accept the unpredictable cost. In many cases, they cancel.

Is Datadog pricing model broken at the bottom — figure 1

The net retention math explains why Datadog tolerates this. Customers under $100K ARR show net revenue retention around 117%, meaning expansion from existing small customers is a meaningful growth lever. But this expansion comes at a cost: for every customer that expands 2x, another churns from bill shock. The gross churn rate of 15-25% in the sub-$100K segment means Datadog must continuously acquire new small customers just to keep the segment flat. This is a treadmill, not a growth engine. The enterprise segment, by contrast, has gross churn under 5% and net retention above 130%, making it far more valuable per dollar of revenue. The rational business decision for Datadog is to focus on enterprise, which they do—but that leaves the bottom of the market structurally underserved and ultimately broken for the customers who live there.

What drives that outcome

The root cause of Datadog's broken pricing at the bottom is the consumption-based model applied uniformly across all customer sizes. Datadog's pricing page lists infrastructure monitoring at $15 per host per month, APM at $36 per host per month for premium languages like Java and Python, logs at $2.50 per million GB ingested plus $1.70 per million GB indexed, RUM at $1.50 per thousand sessions, network performance monitoring at $5 per host per month, cloud SIEM at $0.20 per GB ingested, and database monitoring at $70 per database per month. Each line item is individually reasonable. The problem is that they compound unpredictably. A small team using five products across 30 hosts can easily see a monthly bill of $5,000 or more, with no single component dominating and no clear way to reduce costs without losing visibility.

The unpredictability is the killer. Consumption pricing works for enterprises because they have the scale to absorb variance and the teams to manage it. A company spending $1 million annually on Datadog can absorb a 20% monthly fluctuation without changing behavior. A startup spending $3,000 per month cannot. When a Black Friday traffic spike or a viral product launch pushes usage 3x beyond normal, the startup's bill jumps from $3,500 to $10,500 in a single month. The CFO does not see the traffic spike; they see a $10,500 invoice for a monitoring tool. The decision to cancel is made in minutes.

Is Datadog pricing model broken at the bottom — figure 2

Datadog's own product design amplifies the problem. The platform has 700+ integrations, each of which adds a small amount of data when enabled. A small team setting up Datadog for the first time will enable integrations for their web server, database, message queue, and CI/CD pipeline—each one adding hosts, logs, or custom metrics to the bill. Within a quarter, the team is paying for data they do not fully understand and cannot easily audit. The 80/20 rule applies: roughly 80% of observability value comes from 20% of the data, but Datadog charges for all of it equally. Small customers lack the operational maturity to identify and suppress the noisy 80%, so they pay for noise.

Benchmarks and realistic ranges

The competitive landscape shows that flat-tier pricing at the bottom is not only possible but proven. New Relic restructured its pricing in 2022 under CEO Bill Staples, moving from consumption-based to flat tiers: Free, Standard at $49 per user per month, Pro at $349 per user per month, and Enterprise at $1,500 per user per month, with unlimited data ingestion within each tier. The result was a dramatic reduction in bill shock for SMB customers, with churn dropping from roughly 20% to about 8% in the year following the change. New Relic was later acquired by Francisco Partners and TPG in 2023 for $6.5 billion—a modest outcome that suggests flat-tier pricing alone does not guarantee success, but it does solve the bill-shock problem.

Is Datadog pricing model broken at the bottom — figure 3

Grafana Cloud offers a free tier with 10,000 metric series, 50GB of logs, and 50GB of traces, then a usage-based plan with a monthly spend cap that customers set themselves. When the cap is hit, Grafana stops collecting data and sends an alert. This gives SMB customers full control over their spend without requiring them to monitor usage continuously. Grafana's SMB segment grew roughly 40% year-over-year in 2023, suggesting that spend caps and predictable pricing resonate with smaller buyers.

SigNoz, an open-source observability platform, offers a completely free self-hosted option with unlimited data, and its cloud tier starts at $199 per month for 10,000 spans per second and 100GB of logs, with no overage billing. SigNoz's GitHub stars grew from 5,000 to 18,000 during 2024, indicating strong SMB adoption driven partly by pricing transparency.

Is Datadog pricing model broken at the bottom — figure 4

Datadog's response has been limited. They introduced Flexible Consumption in 2023, which offers annual commit with overage protection, but only for customers spending $50,000 or more per year. The bottom segment—customers in the $5,000 to $25,000 annual range—still gets the raw consumption model with no caps, no alerts, and no flat-tier option. This creates a competitive vulnerability that rivals are actively exploiting.

Realistic pricing benchmarks for a fixed SMB tier would look something like this: a Starter tier at $500 per month covering up to 10 hosts, 100GB of log ingestion, and basic APM; a Standard tier at $2,000 per month covering up to 30 hosts, 500GB of logs, APM, and RUM; and a Pro tier at $5,000 per month covering up to 100 hosts, 2TB of logs, full APM, and Cloud SIEM. These tiers would bundle the most commonly used products into a predictable monthly fee, eliminating the line-item anxiety that drives churn. The revenue impact on Datadog would be modest—SMB customers in this range are already spending $3,500 to $5,000 per month on average, so a $2,000 or $5,000 flat tier is not a major discount. It is a predictability upgrade.

Is Datadog pricing model broken at the bottom — figure 5

The churn math supports the fix. If Datadog could reduce SMB gross churn from 20% to 10% through flat-tier pricing, the segment would retain roughly 10% more customers annually. For a segment generating, say, $500 million in annual revenue, that is $50 million in retained revenue per year—more than enough to justify the operational complexity of running a dual pricing model.

Risks, edge cases, and failure modes

The counter-arguments to fixing Datadog's pricing at the bottom are worth taking seriously. The first is that consumption pricing is a structural advantage, not a bug. Customers pay for what they use, which aligns with cloud economics and ensures Datadog's revenue grows with customer usage. The fix is not to abandon consumption pricing but to offer a tier option for SMB customers while keeping consumption for enterprise. This hybrid approach is what PagerDuty does with its combination of per-user tiers and consumption-based event volumes.

The second risk is cannibalization. Mid-market customers currently spending $80,000 per year on consumption might downgrade to a $30,000 flat tier, reducing revenue. This is a real concern, but the mitigation is straightforward: design the tier-to-enterprise ladder so that usage above the tier threshold triggers consumption pricing. A customer on the $5,000 per month Pro tier who exceeds 100 hosts or 2TB of logs naturally graduates to enterprise consumption pricing. The tier is an entry point, not a ceiling.

Is Datadog pricing model broken at the bottom — figure 6

The third risk is operational complexity. Running two pricing models means two sales motions, two billing flows, and two support paths. This is a legitimate burden, but it is one that New Relic, Grafana, and SigNoz have all managed successfully. The tier can be self-serve product-led growth, while consumption remains enterprise sales-led. The billing systems that Datadog already operates can handle both.

The fourth risk is that flat-tier pricing did not fully save New Relic. The company was acquired at a modest valuation despite the successful restructure. This suggests that pricing is necessary but not sufficient—product quality, go-to-market execution, and competitive positioning matter equally. Datadog should not expect a flat-tier SMB option to solve all its problems, but it would solve the specific bill-shock problem that drives churn at the bottom.

Is Datadog pricing model broken at the bottom — figure 7

The fifth risk is that the SMB segment may not be worth fixing. If SMB revenue is less than 15% of Datadog's total, the operational complexity of a dual pricing model might exceed the benefit. In that case, the rational strategy is to let the SMB segment shrink naturally while focusing on enterprise growth. This is a valid triage decision, but it means accepting that Datadog's pricing model is broken at the bottom and choosing not to fix it. For RevOps practitioners advising customers, the implication is clear: if you are a small team, Datadog is likely the wrong choice unless you have the operational maturity to manage consumption spikes.

Edge cases also matter. A startup that ingests 10GB of logs daily at $2.50 per million GB faces $750 per month just for ingestion, before retention costs. If they need 30-day retention for compliance, that adds another $1.70 per million GB, pushing the total past $1,200 per month. For a team with 10 hosts and 100 custom metrics, the bill can jump from $150 to over $500 per month without any infrastructure change. These are not hypothetical scenarios; they are the standard experience for small Datadog customers.

Is Datadog pricing model broken at the bottom — figure 8

A practical rollout plan

For Datadog leadership contemplating a fix, the rollout should follow a phased approach. Phase one is an audit of the current SMB cohort: segment customers by ACV, identify churn causes, and quantify bill-shock incidents. This requires analyzing billing data to find customers whose monthly bills spiked 2x or more without a corresponding increase in usage. The audit will confirm the magnitude of the problem and provide the business case for change.

Phase two is designing the flat-tier bundles. The Starter, Standard, and Pro tiers should be priced to be revenue-neutral against current average SMB spend, not discounted. The goal is predictability, not charity. Each tier should bundle the most commonly used products—infrastructure monitoring, APM, log ingestion with retention, and RUM—into a single monthly fee. Usage above the tier limit should trigger either a pause in data collection or a clear upgrade path, not an automatic overage charge.

Is Datadog pricing model broken at the bottom — figure 9

Phase three is implementing usage caps and alerts. Customers should be able to set a monthly budget cap in the Datadog UI, receive alerts at 50%, 75%, and 90% of the cap, and have data collection automatically throttled or stopped when the cap is reached. This eliminates the anxiety of surprise bills and gives SMB customers control without requiring them to monitor usage continuously. Grafana Cloud has proven this model works.

Phase four is launching annual commit discounts. A customer who commits to $25,000 in annual spend should receive a 15-25% discount, locking in predictable revenue for Datadog and a lower effective price for the customer. This aligns incentives: Datadog gets upfront cash and reduced churn, and the customer gets a predictable budget line item.

Phase five is measuring the impact. The key metrics are SMB gross churn, net revenue retention, and time-to-value. The target should be reducing SMB gross churn from 15-25% to 8-12% within 12 months of launch. If the tiers are working, net revenue retention in the SMB segment should stabilize or improve even as gross churn declines.

Is Datadog pricing model broken at the bottom — figure 10

Phase six is iteration. The initial tier boundaries will not be perfect. Datadog should analyze usage data to see where customers cluster and adjust tier limits and pricing accordingly. The goal is a self-serve product-led growth motion for the bottom of the market that feeds customers into the enterprise consumption model as they scale.

For RevOps practitioners, the practical takeaway is that Datadog's pricing model is broken at the bottom, but the fix is well understood and proven by competitors. If you are advising a small customer evaluating Datadog, the recommendation is to demand a flat-tier option, usage caps, and annual commit discounts before signing. If Datadog cannot offer these, the customer should evaluate New Relic, Grafana Cloud, or SigNoz, all of which have solved the bill-shock problem. If you are advising Datadog, the recommendation is to treat the SMB segment as a strategic investment in future enterprise customers, not a revenue extraction opportunity. The customers who churn from bill shock today are the enterprise buyers of tomorrow—and they will remember the experience.

FAQ

Why is Datadog's pricing considered broken for small businesses?

Datadog's consumption-based model leads to unpredictable costs, often resulting in bill shock for smaller customers. Usage can spike unexpectedly, causing monthly bills to far exceed budgets. This unpredictability drives churn rates of 15-25% for sub-$100K ACV accounts, compared to under 5% for larger clients.

What is bill shock in Datadog's context?

Bill shock happens when a customer's actual usage outpaces their expected spend, leading to surprise overage charges. For example, log ingestion or APM host counts can double without warning, inflating the invoice. This is especially painful for SMBs with limited budgets and no FinOps team to monitor usage.

How does Datadog's churn compare between small and large customers?

Small customers under $100K ACV churn at roughly 15-25% annually, while those spending $100K+ have churn under 5%. The gap stems from pricing unpredictability: smaller buyers lack the leverage or resources to manage consumption spikes, while enterprise customers have contract protections and dedicated teams.

What pricing model would fix the issue for SMBs?

A flat-tier structure, like New Relic's, bundles infrastructure, APM, and log retention into predictable monthly fees such as $500, $2,000, and $5,000 per month. This eliminates surprise overages and simplifies budgeting for smaller teams. Grafana Cloud's spend caps and SigNoz's flat tiers also solve this problem.

Are usage caps and alerts part of the solution?

Yes, automated overage protection—such as hard caps or real-time alerts—can prevent runaway costs. Customers can set limits on hosts, logs, or spans, and get notified before hitting thresholds. This gives SMBs control without requiring constant monitoring, as Grafana Cloud has demonstrated.

Would annual commit discounts help smaller customers?

Offering 15-25% discounts for annual commitments as low as $25,000 would incentivize longer-term relationships. This reduces churn by locking in predictable spend, while Datadog gains upfront revenue and lower acquisition costs. It aligns incentives for both parties.

Sources

Datadog Pricing: https://www.datadoghq.com/pricing/
New Relic Pricing: https://newrelic.com/pricing
Grafana Cloud Pricing: https://grafana.com/pricing/
SigNoz Pricing: https://signoz.io/pricing/
PagerDuty Pricing: https://www.pagerduty.com/pricing/
Datadog Investor Relations: https://investors.datadoghq.com/
AWS CloudWatch Pricing: https://aws.amazon.com/cloudwatch/pricing/

flowchart TD S["Is Datadog pricing model broken at the"] S --> N0["The outcome you should expect"] N0 --> N1["What drives that outcome"] N1 --> N2["Benchmarks and realistic ranges"] N2 --> N3["Risks, edge cases, and failure modes"]

flowchart LR C["Is Datadog pricing model broken at the"] C --> H0["What drives that outcome"] C --> H1["Benchmarks and realistic ranges"] C --> H2["Risks, edge cases, and failure modes"] C --> H3["A practical rollout plan"]

Related on PULSE

Download:

## Direct Answer

Yes, Datadog's pricing model is effectively broken at the bottom of the market. Small and early-stage customers face unpredictable consumption-based bills that routinely spike 3-5x beyond their base spend, driving gross churn of roughly 15-25% for accounts under $100K ACV compared to under 5% for enterprise clients. The model prioritizes expansion revenue over SMB retention, creating a structural mismatch between what small teams need and what Datadog sells.

## The outcome you should expect

```mermaid
flowchart TD
  S["Is Datadog pricing model broken at the"]
  S --> N0["The outcome you should expect"]
  N0 --> N1["What drives that outcome"]
  N1 --> N2["Benchmarks and realistic ranges"]
  N2 --> N3["Risks, edge cases, and failure modes"]
```


If you are a RevOps leader evaluating Datadog for a small or mid-market customer base, the outcome you should expect is a predictable pattern of bill shock, finance escalations, and eventual churn. A typical SMB deployment starts modestly—perhaps 30 hosts at $15 per host per month for infrastructure monitoring, plus 1TB of log ingestion at $2.50 per million GB, plus 100,000 real-user monitoring sessions at $1.50 per thousand sessions. That base configuration lands around $3,500 to $5,000 per month. The problem is that this number is never stable. Host counts auto-scale during traffic spikes, log volumes multiply during incident debugging, and custom metrics accumulate as engineering teams instrument new services. Within three to six months, the monthly bill can double or triple without any single decision triggering the increase.

The customer journey follows a recognizable arc. Month one: the bill is within budget, and the team is happy with the visibility. Month two or three: a marketing campaign or product launch drives a modest traffic increase, and the bill rises 20-30%. Month four or five: an incident occurs, engineers enable additional log collection and tracing to debug it, and the bill jumps another 40-50%. By month six, the CFO sees a monthly invoice that is 2-3x the original estimate and questions whether the tool is worth the cost. Unlike enterprise customers who have dedicated FinOps teams and contract leverage to negotiate overages, SMB customers have no one monitoring usage daily and no one to call for relief. The finance team makes a simple calculation: cancel Datadog, move to a cheaper alternative, or accept the unpredictable cost. In many cases, they cancel.

![Is Datadog pricing model broken at the bottom — figure 1](/assets/qa/q1707-b1.jpg)



The net retention math explains why Datadog tolerates this. Customers under $100K ARR show net revenue retention around 117%, meaning expansion from existing small customers is a meaningful growth lever. But this expansion comes at a cost: for every customer that expands 2x, another churns from bill shock. The gross churn rate of 15-25% in the sub-$100K segment means Datadog must continuously acquire new small customers just to keep the segment flat. This is a treadmill, not a growth engine. The enterprise segment, by contrast, has gross churn under 5% and net retention above 130%, making it far more valuable per dollar of revenue. The rational business decision for Datadog is to focus on enterprise, which they do—but that leaves the bottom of the market structurally underserved and ultimately broken for the customers who live there.

## What drives that outcome

```mermaid
flowchart LR
  C["Is Datadog pricing model broken at the"]
  C --> H0["What drives that outcome"]
  C --> H1["Benchmarks and realistic ranges"]
  C --> H2["Risks, edge cases, and failure modes"]
  C --> H3["A practical rollout plan"]
```


The root cause of Datadog's broken pricing at the bottom is the consumption-based model applied uniformly across all customer sizes. Datadog's pricing page lists infrastructure monitoring at $15 per host per month, APM at $36 per host per month for premium languages like Java and Python, logs at $2.50 per million GB ingested plus $1.70 per million GB indexed, RUM at $1.50 per thousand sessions, network performance monitoring at $5 per host per month, cloud SIEM at $0.20 per GB ingested, and database monitoring at $70 per database per month. Each line item is individually reasonable. The problem is that they compound unpredictably. A small team using five products across 30 hosts can easily see a monthly bill of $5,000 or more, with no single component dominating and no clear way to reduce costs without losing visibility.

The unpredictability is the killer. Consumption pricing works for enterprises because they have the scale to absorb variance and the teams to manage it. A company spending $1 million annually on Datadog can absorb a 20% monthly fluctuation without changing behavior. A startup spending $3,000 per month cannot. When a Black Friday traffic spike or a viral product launch pushes usage 3x beyond normal, the startup's bill jumps from $3,500 to $10,500 in a single month. The CFO does not see the traffic spike; they see a $10,500 invoice for a monitoring tool. The decision to cancel is made in minutes.

![Is Datadog pricing model broken at the bottom — figure 2](/assets/qa/q1707-b2.jpg)



Datadog's own product design amplifies the problem. The platform has 700+ integrations, each of which adds a small amount of data when enabled. A small team setting up Datadog for the first time will enable integrations for their web server, database, message queue, and CI/CD pipeline—each one adding hosts, logs, or custom metrics to the bill. Within a quarter, the team is paying for data they do not fully understand and cannot easily audit. The 80/20 rule applies: roughly 80% of observability value comes from 20% of the data, but Datadog charges for all of it equally. Small customers lack the operational maturity to identify and suppress the noisy 80%, so they pay for noise.

## Benchmarks and realistic ranges

The competitive landscape shows that flat-tier pricing at the bottom is not only possible but proven. New Relic restructured its pricing in 2022 under CEO Bill Staples, moving from consumption-based to flat tiers: Free, Standard at $49 per user per month, Pro at $349 per user per month, and Enterprise at $1,500 per user per month, with unlimited data ingestion within each tier. The result was a dramatic reduction in bill shock for SMB customers, with churn dropping from roughly 20% to about 8% in the year following the change. New Relic was later acquired by Francisco Partners and TPG in 2023 for $6.5 billion—a modest outcome that suggests flat-tier pricing alone does not guarantee success, but it does solve the bill-shock problem.

![Is Datadog pricing model broken at the bottom — figure 3](/assets/qa/q1707-b3.jpg)



Grafana Cloud offers a free tier with 10,000 metric series, 50GB of logs, and 50GB of traces, then a usage-based plan with a monthly spend cap that customers set themselves. When the cap is hit, Grafana stops collecting data and sends an alert. This gives SMB customers full control over their spend without requiring them to monitor usage continuously. Grafana's SMB segment grew roughly 40% year-over-year in 2023, suggesting that spend caps and predictable pricing resonate with smaller buyers.

SigNoz, an open-source observability platform, offers a completely free self-hosted option with unlimited data, and its cloud tier starts at $199 per month for 10,000 spans per second and 100GB of logs, with no overage billing. SigNoz's GitHub stars grew from 5,000 to 18,000 during 2024, indicating strong SMB adoption driven partly by pricing transparency.

![Is Datadog pricing model broken at the bottom — figure 4](/assets/qa/q1707-b4.jpg)



Datadog's response has been limited. They introduced Flexible Consumption in 2023, which offers annual commit with overage protection, but only for customers spending $50,000 or more per year. The bottom segment—customers in the $5,000 to $25,000 annual range—still gets the raw consumption model with no caps, no alerts, and no flat-tier option. This creates a competitive vulnerability that rivals are actively exploiting.

Realistic pricing benchmarks for a fixed SMB tier would look something like this: a Starter tier at $500 per month covering up to 10 hosts, 100GB of log ingestion, and basic APM; a Standard tier at $2,000 per month covering up to 30 hosts, 500GB of logs, APM, and RUM; and a Pro tier at $5,000 per month covering up to 100 hosts, 2TB of logs, full APM, and Cloud SIEM. These tiers would bundle the most commonly used products into a predictable monthly fee, eliminating the line-item anxiety that drives churn. The revenue impact on Datadog would be modest—SMB customers in this range are already spending $3,500 to $5,000 per month on average, so a $2,000 or $5,000 flat tier is not a major discount. It is a predictability upgrade.

![Is Datadog pricing model broken at the bottom — figure 5](/assets/qa/q1707-b5.jpg)



The churn math supports the fix. If Datadog could reduce SMB gross churn from 20% to 10% through flat-tier pricing, the segment would retain roughly 10% more customers annually. For a segment generating, say, $500 million in annual revenue, that is $50 million in retained revenue per year—more than enough to justify the operational complexity of running a dual pricing model.

## Risks, edge cases, and failure modes

The counter-arguments to fixing Datadog's pricing at the bottom are worth taking seriously. The first is that consumption pricing is a structural advantage, not a bug. Customers pay for what they use, which aligns with cloud economics and ensures Datadog's revenue grows with customer usage. The fix is not to abandon consumption pricing but to offer a tier option for SMB customers while keeping consumption for enterprise. This hybrid approach is what PagerDuty does with its combination of per-user tiers and consumption-based event volumes.

The second risk is cannibalization. Mid-market customers currently spending $80,000 per year on consumption might downgrade to a $30,000 flat tier, reducing revenue. This is a real concern, but the mitigation is straightforward: design the tier-to-enterprise ladder so that usage above the tier threshold triggers consumption pricing. A customer on the $5,000 per month Pro tier who exceeds 100 hosts or 2TB of logs naturally graduates to enterprise consumption pricing. The tier is an entry point, not a ceiling.

![Is Datadog pricing model broken at the bottom — figure 6](/assets/qa/q1707-b6.jpg)



The third risk is operational complexity. Running two pricing models means two sales motions, two billing flows, and two support paths. This is a legitimate burden, but it is one that New Relic, Grafana, and SigNoz have all managed successfully. The tier can be self-serve product-led growth, while consumption remains enterprise sales-led. The billing systems that Datadog already operates can handle both.

The fourth risk is that flat-tier pricing did not fully save New Relic. The company was acquired at a modest valuation despite the successful restructure. This suggests that pricing is necessary but not sufficient—product quality, go-to-market execution, and competitive positioning matter equally. Datadog should not expect a flat-tier SMB option to solve all its problems, but it would solve the specific bill-shock problem that drives churn at the bottom.

![Is Datadog pricing model broken at the bottom — figure 7](/assets/qa/q1707-b7.jpg)



The fifth risk is that the SMB segment may not be worth fixing. If SMB revenue is less than 15% of Datadog's total, the operational complexity of a dual pricing model might exceed the benefit. In that case, the rational strategy is to let the SMB segment shrink naturally while focusing on enterprise growth. This is a valid triage decision, but it means accepting that Datadog's pricing model is broken at the bottom and choosing not to fix it. For RevOps practitioners advising customers, the implication is clear: if you are a small team, Datadog is likely the wrong choice unless you have the operational maturity to manage consumption spikes.

Edge cases also matter. A startup that ingests 10GB of logs daily at $2.50 per million GB faces $750 per month just for ingestion, before retention costs. If they need 30-day retention for compliance, that adds another $1.70 per million GB, pushing the total past $1,200 per month. For a team with 10 hosts and 100 custom metrics, the bill can jump from $150 to over $500 per month without any infrastructure change. These are not hypothetical scenarios; they are the standard experience for small Datadog customers.

![Is Datadog pricing model broken at the bottom — figure 8](/assets/qa/q1707-b8.jpg)



## A practical rollout plan

For Datadog leadership contemplating a fix, the rollout should follow a phased approach. Phase one is an audit of the current SMB cohort: segment customers by ACV, identify churn causes, and quantify bill-shock incidents. This requires analyzing billing data to find customers whose monthly bills spiked 2x or more without a corresponding increase in usage. The audit will confirm the magnitude of the problem and provide the business case for change.

Phase two is designing the flat-tier bundles. The Starter, Standard, and Pro tiers should be priced to be revenue-neutral against current average SMB spend, not discounted. The goal is predictability, not charity. Each tier should bundle the most commonly used products—infrastructure monitoring, APM, log ingestion with retention, and RUM—into a single monthly fee. Usage above the tier limit should trigger either a pause in data collection or a clear upgrade path, not an automatic overage charge.

![Is Datadog pricing model broken at the bottom — figure 9](/assets/qa/q1707-b9.jpg)



Phase three is implementing usage caps and alerts. Customers should be able to set a monthly budget cap in the Datadog UI, receive alerts at 50%, 75%, and 90% of the cap, and have data collection automatically throttled or stopped when the cap is reached. This eliminates the anxiety of surprise bills and gives SMB customers control without requiring them to monitor usage continuously. Grafana Cloud has proven this model works.

Phase four is launching annual commit discounts. A customer who commits to $25,000 in annual spend should receive a 15-25% discount, locking in predictable revenue for Datadog and a lower effective price for the customer. This aligns incentives: Datadog gets upfront cash and reduced churn, and the customer gets a predictable budget line item.

Phase five is measuring the impact. The key metrics are SMB gross churn, net revenue retention, and time-to-value. The target should be reducing SMB gross churn from 15-25% to 8-12% within 12 months of launch. If the tiers are working, net revenue retention in the SMB segment should stabilize or improve even as gross churn declines.

![Is Datadog pricing model broken at the bottom — figure 10](/assets/qa/q1707-b10.jpg)



Phase six is iteration. The initial tier boundaries will not be perfect. Datadog should analyze usage data to see where customers cluster and adjust tier limits and pricing accordingly. The goal is a self-serve product-led growth motion for the bottom of the market that feeds customers into the enterprise consumption model as they scale.

For RevOps practitioners, the practical takeaway is that Datadog's pricing model is broken at the bottom, but the fix is well understood and proven by competitors. If you are advising a small customer evaluating Datadog, the recommendation is to demand a flat-tier option, usage caps, and annual commit discounts before signing. If Datadog cannot offer these, the customer should evaluate New Relic, Grafana Cloud, or SigNoz, all of which have solved the bill-shock problem. If you are advising Datadog, the recommendation is to treat the SMB segment as a strategic investment in future enterprise customers, not a revenue extraction opportunity. The customers who churn from bill shock today are the enterprise buyers of tomorrow—and they will remember the experience.

## Related questions

### Does Datadog offer any flat-rate pricing plans for small teams?

Datadog does not offer a flat-rate SMB tier. All pricing is consumption-based per host, per GB, or per session. Customers under $50K annual spend receive no overage protection or usage caps, making bills unpredictable. New Relic and Grafana Cloud offer flat tiers with unlimited ingestion within limits.

### What is the typical monthly cost for a small team using Datadog?

A small team with 30 hosts, 1TB of log ingestion, and 100K RUM sessions typically pays $3,500 to $5,000 per month. Usage spikes can push this to $10,000 or more. Custom metrics and additional integrations compound costs further.

### How does Datadog churn compare between SMB and enterprise customers?

SMB customers under $100K ACV churn at roughly 15-25% annually. Enterprise customers above $100K churn at under 5%. The gap is driven by bill shock and lack of pricing predictability at the bottom of the market.

### What alternatives offer better pricing for small teams?

New Relic offers flat tiers from free to $1,500 per month with unlimited ingestion. Grafana Cloud offers a free tier plus usage-based plans with spend caps. SigNoz offers a free self-hosted option and cloud tiers starting at $199 per month.

### Can customers negotiate Datadog pricing?

Enterprise customers above $50K annual spend can negotiate annual commit discounts and overage protection through Flexible Consumption. SMB customers have no negotiation leverage and receive standard consumption pricing with no caps or guarantees.

## FAQ

**Why is Datadog's pricing considered broken for small businesses?**

Datadog's consumption-based model leads to unpredictable costs, often resulting in bill shock for smaller customers. Usage can spike unexpectedly, causing monthly bills to far exceed budgets. This unpredictability drives churn rates of 15-25% for sub-$100K ACV accounts, compared to under 5% for larger clients.

**What is bill shock in Datadog's context?**

Bill shock happens when a customer's actual usage outpaces their expected spend, leading to surprise overage charges. For example, log ingestion or APM host counts can double without warning, inflating the invoice. This is especially painful for SMBs with limited budgets and no FinOps team to monitor usage.

**How does Datadog's churn compare between small and large customers?**

Small customers under $100K ACV churn at roughly 15-25% annually, while those spending $100K+ have churn under 5%. The gap stems from pricing unpredictability: smaller buyers lack the leverage or resources to manage consumption spikes, while enterprise customers have contract protections and dedicated teams.

**What pricing model would fix the issue for SMBs?**

A flat-tier structure, like New Relic's, bundles infrastructure, APM, and log retention into predictable monthly fees such as $500, $2,000, and $5,000 per month. This eliminates surprise overages and simplifies budgeting for smaller teams. Grafana Cloud's spend caps and SigNoz's flat tiers also solve this problem.

**Are usage caps and alerts part of the solution?**

Yes, automated overage protection—such as hard caps or real-time alerts—can prevent runaway costs. Customers can set limits on hosts, logs, or spans, and get notified before hitting thresholds. This gives SMBs control without requiring constant monitoring, as Grafana Cloud has demonstrated.

**Would annual commit discounts help smaller customers?**

Offering 15-25% discounts for annual commitments as low as $25,000 would incentivize longer-term relationships. This reduces churn by locking in predictable spend, while Datadog gains upfront revenue and lower acquisition costs. It aligns incentives for both parties.

## Sources

- Datadog Pricing: https://www.datadoghq.com/pricing/
- New Relic Pricing: https://newrelic.com/pricing
- Grafana Cloud Pricing: https://grafana.com/pricing/
- SigNoz Pricing: https://signoz.io/pricing/
- PagerDuty Pricing: https://www.pagerduty.com/pricing/
- Datadog Investor Relations: https://investors.datadoghq.com/
- AWS CloudWatch Pricing: https://aws.amazon.com/cloudwatch/pricing/

## Related on PULSE

- [Is Salesloft pricing model broken at the bottom?](/knowledge/q1826)
- [Is Outreach pricing model broken at the bottom?](/knowledge/q1767)
- [Is ServiceNow's pricing model broken at the bottom?](/knowledge/q1647)
- [Datadog NRR 2026](/knowledge/q1681)
- [Datadog moat vs New Relic and Dynatrace](/knowledge/q1689)
- [Datadog protect ARPU from churn in recession](/knowledge/q1712)

Was this helpful?

Sources cited

datadoghq.comhttps://www.datadoghq.com/pricing/newrelic.comhttps://newrelic.com/pricing dynatrace.comhttps://www.dynatrace.com/pricing/

This page will be disappearing soon.

Download the whole page as a PDF to keep — just $1.

⌬ Apply this in PULSE

Pillar · Founder-Led Sales GovernanceThe governance stack that scales Gross Profit CalculatorModel margin per deal, per rep, per territory How-To · SaaS ChurnSilent revenue killer playbook

Is Datadog pricing model broken at the bottom in 2027?

The outcome you should expect

What drives that outcome

Benchmarks and realistic ranges

Risks, edge cases, and failure modes

A practical rollout plan

Related questions

Does Datadog offer any flat-rate pricing plans for small teams?

What is the typical monthly cost for a small team using Datadog?

How does Datadog churn compare between SMB and enterprise customers?

What alternatives offer better pricing for small teams?

Can customers negotiate Datadog pricing?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ