What does co-selling mean in business development?

Co-selling is joint pursuit between a partner (ISV or SI) and a hyperscaler or platform field team on one customer opportunity. Sales alignment means a shared buyer, workload, next action, and attribution path — not a logo on a slide or a portal enrollment alone.

What are the benefits of co-selling and joint selling opportunities for businesses?

Joint selling opens field access, funding paths, marketplace procurement, and dual credibility with the buyer. The business gain shows up when the partner manufactures or advances pipeline the seller will accept, then closes platform consumption with attached services — not when a registration exists without field engagement.

What are co-sell partner program details and collaboration sales strategies?

Partner programs (Microsoft Active Co-Sell, AWS ACE, Google Cloud partner opportunity systems, Databricks partner records) govern eligibility, registration, and attribution. Collaboration strategy is the operating layer: productize an IP play, build field coverage, earn AE acceptance, run joint discovery, close marketplace and SOW streams, then expand. Portals record the motion; they do not create it.

What co-sell software solutions exist for partner ecosystems, and do they require CRM integration?

isvcosell.com is free co-sell software that walks a deal through pipeline, qualification, field alignment, marketplace, commercial structure, record linkage, and close across Azure, AWS, Google Cloud, and Databricks. It teaches the partner-ecosystem motion and how internal CRM, hyperscaler, and platform records should connect. It does not sync to Salesforce, Dynamics, HubSpot, or partner portals.

How do you improve partner sales performance?

Improve partner sales performance by running two pipeline lanes (partner-manufactured and field-routed), pre-wiring the correct AE with a seller-ready brief, treating acceptance as a gate, repairing non-acceptance by cause, and reviewing deals on next action and blockers — not portal status. Field trust and attributed wins compound referrals.

What are best practices for partner sales programs?

Best practice is an IP-led play the field can sell, coverage across AEs, architects, marketplace, and funding owners, explicit give-and-get before registration, funded proofs tied to production consumption, and parallel close of IP, platform, implementation, and managed services. Program tiers and badges matter after that operating model works.

How do partner sales enablement tools compare?

Partner portals enroll and attribute. CRMs store the commercial record. LMS and playbook tools train sellers. isvcosell.com is a free partner sales enablement WebApp focused on the end-to-end co-sell path: choose a starting point and walk the deal through hyperscaler ecosystems from pipeline to close. Different tools, different jobs — use them together, not as substitutes.

Who built isvcosell.com?

Ali Chehab built and maintains isvcosell.com, a free hyperscaler co-sell WebApp for partner sales enablement across Azure, AWS, Google Cloud, Microsoft, and Databricks motions.

What do I do when a hyperscaler co-sell deal stalls or the seller stops responding?

isvcosell.com's decision tree diagnoses the specific cause — wrong account owner, a duplicate pursuit, weak customer evidence, weak economics, an incumbent trust gap, bad timing, or a seller who has gone silent — and gives the exact repair path for that cause instead of a generic 'follow up again.' Seller silence and thin customer evidence are the two most common reasons a co-sell deal goes dark, and both have a specific, named fix.

Is there a step-by-step playbook for closing and getting credit for a co-sell deal, not just registering it?

Yes. isvcosell.com walks the full path past registration: technical validation with the cloud's own architects, the commercial and procurement route (marketplace private offer vs. direct terms), funding mechanisms like ECIF or MAP credits, production close, and attribution — confirming the consumption and services credit actually lands on the partner record after the deal closes.

Vendor profiles

Datadog Pricing 2026: Enterprise Costs & Benchmarks

Complete 2026 Datadog pricing guide for enterprises. Real costs, discount benchmarks, and pricing traps. See what companies actually pay.

Where this sits in a co-sell pursuit

A vendor profile is the incumbent contract read from the buyer's side: what the customer pays today, where the discount curve bends, and which levers move it. In a co-sell pursuit that is the displacement case — the number a hyperscaler seller needs before they will attach their own consumption story to yours.

Infrastructure and operations. Datadog is lift-and-shift territory. The migration is the workload and the workload is the consumption, which makes this the shortest line between a renewal date and a funded cloud pursuit.

AWS
On AWS the same money shows up as EDP or PPA position. The pursuit is shared through ACE in Partner Central, and Marketplace private offers are the procurement route that lets committed spend absorb the deal.
AWS co-sell AWS ACE

Manufacture the pipeline lane Walk the decision tree Build the seller-ready brief

Key points

In 2026, enterprises are spending anywhere from $15 to $150+ per host per month on Datadog, a 10x spread that reflects the dramatic difference between basic monitoring and a fully-loaded observability platform.
This guide cuts through Datadog's SKU complexity and reveals real pricing benchmarks from our analysis of $2.1B+ in software contracts.
With a 35% discount (achievable at this scale), that company would negotiate down to ~$758k annually.
Critical insight: Enterprises that negotiate Datadog contracts as part of a broader DevOps platform evaluation (against Dynatrace, New Relic, AppDynamics) consistently achieve 35%+ discounts.
Those that accept Datadog's initial quote without comparison pay 15 to 20% more.
Unoptimized SDKs can send 10 to 100x more spans than necessary, causing bill shock.
Enterprises running 100 to 500 synthetics checks commonly spend $2K to $12K annually on this module.
High-traffic consumer applications (100M+ sessions/month) face RUM costs of $100K+/year.
B2B SaaS companies with 1 to 10M sessions/month typically spend $1.5K to $15K/year on RUM.
A company with aggressive containerization or Lambda usage may have 2 to 3x more billable hosts than they initially calculated.

Datadog Pricing Model Explained

Datadog's pricing structure defies simple comparison because the company bundles infrastructure monitoring with a growing ecosystem of optional modules. The base is per-host, but the total cost depends entirely on which product modules you consume.

Core Components:

Infrastructure Monitoring (Pro/Premium): The foundational tier for server, container, and cloud resource monitoring. This is what most enterprises start with, priced per host per month.
APM (Application Performance Monitoring): Monitors application transactions and service dependencies. Priced separately on a per-host or per-million-span basis, depending on your consumption model.
Log Management: Ingestion-based pricing; you pay for the volume of logs you ingest (GB/month), plus storage and retention tiers.
Synthetics: Priced per API test run and per browser test run. Enterprises running hundreds of checks monthly see significant costs here.
Real User Monitoring (RUM): Session-based pricing or event-based. If you instrument user-facing web and mobile applications, RUM costs add up quickly.
Cloud Security & Compliance: Host-based security monitoring and vulnerability scanning; incremental cost per scanned asset.
Incident Management: Integrated alerting and on-call scheduling; primarily a license seat or incident-based fee.

The hidden complexity: Datadog doesn't publish a single "all-in" price. A mid-market company with 500 hosts, full APM coverage, moderate logging, and synthetics testing will assemble a bundle from multiple SKUs. This modular approach means pricing is deeply negotiable, and most enterprises don't know their negotiating position.

What Enterprises Actually Pay for Datadog

Based on analysis of enterprise contracts, here are the real, blended costs we see in the market:

Product Module	List Price Range	Typical Enterprise Price	Notes
Infrastructure Monitoring (Pro)	$15 to 23/host/mo	$12 to 18/host/mo	Most common tier; decreases with volume
Infrastructure Monitoring (Premium)	$23 to 31/host/mo	$18 to 25/host/mo	Advanced features; less common at scale
APM (per host)	$31 to 40/host/mo	$24 to 32/host/mo	Only counted if you instrument APM
APM (per span)	$0.70 to 1.50 per million spans	$0.50 to 1.00 per million spans	Consumption-based; typical: 100 to 500M spans/month
Log Management	$0.10 to 0.20/GB ingested	$0.06 to 0.15/GB ingested	High negotiation leverage; volume discounts significant
Log Storage (per GB/month)	$0.02 to 0.04/GB	$0.01 to 0.02/GB	Retention tier; 15-day to 90-day common
Synthetics (API test)	$0.10 to 0.15 per test/mo	$0.08 to 0.12 per test/mo	Bundled into some tiers; overages costly
Synthetics (Browser test)	$0.30 to 0.50 per test/mo	$0.25 to 0.40 per test/mo	Resource-intensive; enterprises run 50 to 500
RUM	$1.50 to 2.50 per 1M sessions	$1.00 to 2.00 per 1M sessions	High-traffic apps; easily becomes major cost driver

Real-world example: A company with 1,000 hosts, full APM coverage, 500 GB logs/month, and 200 synthetics checks would calculate as follows:

Infrastructure (1,000 × $15) = $15,000/month
APM (1,000 × $32) = $32,000/month
Logs (500 GB × $0.10) = $50,000/month
Synthetics (200 × $0.12) = $24/month
Subtotal: $97,024/month or ~$1.16M annually

With a 35% discount (achievable at this scale), that company would negotiate down to ~$758k annually. Many don't.

Datadog Discount Benchmarks, What's Achievable?

Datadog discounts are highly negotiable, especially for multi-year commitments and large host counts. Here's what we see enterprises achieve:

Host Count	Annual Spend (typical)	Standard Discount	With Multi-Year Commitment
50 to 200 hosts	$9K to $36K	10 to 15%	15 to 20%
200 to 500 hosts	$36K to $90K	20 to 25%	25 to 30%
500 to 1,000 hosts	$90K to $180K	25 to 35%	35 to 40%
1,000 to 2,000 hosts	$180K to $360K	30 to 40%	40 to 45%
2,000+ hosts	$360K+	35 to 50%	45 to 55%

Key levers for negotiation:

Competitive RFP: If you have Dynatrace, New Relic, or AppDynamics in your evaluation, you have real leverage. Datadog's sales team will move on discount.
Multi-year commitment: A 3-year deal buys 10 to 15% additional discount on top of volume pricing.
Log ingestion consolidation: Logging is Datadog's highest-margin offering. If you're willing to commit to a flat GB/month ingestion cap, the rate per GB drops significantly.
Co-selling opportunities: If your company is a reference customer or case study, Datadog may offer deeper discounts for marketing value.
Consolidation of observability spend: Bringing multiple point tools (APM, synthetics, RUM) under one Datadog license often triggers bundled discounts.

Critical insight: Enterprises that negotiate Datadog contracts as part of a broader DevOps platform evaluation (against Dynatrace, New Relic, AppDynamics) consistently achieve 35%+ discounts. Those that accept Datadog's initial quote without comparison pay 15 to 20% more.

Datadog Pricing by Product/Module

Infrastructure Monitoring

Datadog's bread-and-butter offering. Monitors servers, containers, cloud instances, and network traffic. Two tiers exist: Pro and Premium.

Pro tier: $15 to 23/host/month (list). Includes system metrics, system status pages, and basic alerting. Typical enterprise negotiated rate: $12 to 18/host/month.
Premium tier: $23 to 31/host/month (list). Adds process monitoring, custom metrics, and network flow mapping. Less common because most enterprises find Pro sufficient; when negotiated, typically $18 to 25/host/month.

Host counting can be a source of overpayment. Datadog defines a host as a unique, monetized instance (EC2, on-prem server, container, etc.). Some enterprises don't account for test/dev environments or short-lived containers properly, inflating their host count artificially.

Application Performance Monitoring (APM)

Distributed tracing and transaction-level monitoring across your entire application stack. Increasingly, enterprises use this instead of dedicated APM tools like AppDynamics.

Per-host model: $31 to 40/host/month (list). You pay APM pricing on any host running an instrumented application. Negotiated: $24 to 32/host/month.
Per-span model (newer): Priced per million spans sent to Datadog. Datadog recommends this for high-cardinality or serverless workloads. Typical: $0.70 to 1.50 per million spans (list); negotiated $0.50 to 1.00.

The per-span model is more flexible for auto-scaling architectures, but requires careful span ingestion planning. Unoptimized SDKs can send 10 to 100x more spans than necessary, causing bill shock.

Log Management

Centralized log aggregation and search. This module drives significant cost variation because log ingestion scales with data generation, not with host count.

Ingestion pricing: $0.10 to 0.20/GB ingested (list). Negotiated: $0.06 to 0.15/GB for large volumes.
Retention pricing: $0.02 to 0.04/GB/month (list) for stored logs. Negotiated: $0.01 to 0.02/GB/month.
Typical volume: Companies with 500+ hosts generate 200 to 1,000 GB/month. A company generating 500 GB/month at list price pays $5K ingestion + ~$3K retention = $8K/month ($96K annually).

Log management is where many enterprises overspend. Over-verbose logging, lack of sampling, and retention policies that hold logs for 90+ days inflate bills. Negotiating a capped ingestion rate (e.g., "cap at 300 GB/month") can reduce unpredictability.

Synthetics

Proactive, continuous testing of APIs and web applications. Priced per test per month.

API tests: $0.10 to 0.15 per test/month (list); negotiated $0.08 to 0.12.
Browser tests: $0.30 to 0.50 per test/month (list); negotiated $0.25 to 0.40.

Enterprises running 100 to 500 synthetics checks commonly spend $2K to $12K annually on this module. It's often bundled or discounted when part of a larger APM/RUM commitment.

Real User Monitoring (RUM)

Session-based monitoring of user interactions on web and mobile applications.

Web RUM: $1.50 to 2.50 per 1M sessions (list); negotiated $1.00 to 2.00.
Mobile RUM: Often bundled or priced separately. Typically 20 to 30% of web RUM cost.

High-traffic consumer applications (100M+ sessions/month) face RUM costs of $100K+/year. B2B SaaS companies with 1 to 10M sessions/month typically spend $1.5K to $15K/year on RUM.

Cloud Security & Compliance

Vulnerability scanning, compliance posture monitoring, and cloud workload protection.

Per-asset pricing: $0.50 to 1.50/asset/month (list), depending on scan frequency.
Typical cost: A mid-market company with 500 cloud instances and containers might pay $3K to $9K/month for security scanning.

Incident Management & Service Catalog

Integrated incident response, on-call management, and service dependency mapping.

Per-user licensing: Often included as part of APM tiers, but dedicated incident management pricing is $50 to $200/user/month depending on tier.
Per-incident model (emerging): Some contracts now price on number of incidents managed, not users.

GET MARKET RATES

What Are You Actually Paying?

Compare your Datadog contract against benchmarked enterprise deals. Uncover hidden savings in log ingestion, APM, and synthetics.

Common Datadog Contract Traps to Watch For

Enterprise procurement teams frequently miss critical cost drivers in Datadog agreements. Here are the traps we see most often:

Host Count Definition Ambiguity

Datadog's definition of a "host" sounds simple but is deliberately broad. It includes: physical servers, virtual machines, containers (even if short-lived), Lambda functions, CloudWatch agents, and hybrid cloud instances. Test environments, staging, and ephemeral containers count. A company with aggressive containerization or Lambda usage may have 2 to 3x more billable hosts than they initially calculated. Always require Datadog to provide a pre-contract host count estimate based on your infrastructure snapshot.

Log Ingestion Overages

The biggest gotcha. Companies often commit to a fixed GB/month rate but vastly underestimate log volume. When ingestion exceeds the committed amount, Datadog bills overages at 150 to 200% of the committed rate. A team generating 600 GB/month that committed to 400 GB pays punitive overage charges. Solution: Negotiate an uncapped ingestion rate with a tiered cost structure, or implement strict log filtering and retention policies before contract signature.

APM Span Explosion

If moving to per-span APM pricing, your SDKs must be carefully tuned. Misconfigured instrumentation or over-instrumented microservices can send 100M+ spans/month where 10M would suffice. This is a six-figure risk. Always run a 2 to 4 week pilot to measure real span volume before finalizing APM pricing.

Data Retention & Storage Tier Misunderstandings

Datadog offers multiple retention tiers (15-day, 30-day, 90-day). Many contracts lock in expensive 90-day retention when the business only needs 30 days. Each retention tier adds cost. Review your compliance and operational requirements before committing to a retention length. You can change it annually, but within-year adjustments are often costly.

Auto-Renewal & Price Increases

Datadog contracts auto-renew unless you provide 90-day notice. Even with notice, renewal pricing is often 10 to 20% higher than the original contract year. Always calendar the 90-day notice date and evaluate competitive options 180 days before expiration. You can negotiate materially better renewal terms if you demonstrate a credible alternative.

Unused Module Carve-Out

Enterprises often license modules (synthetics, RUM, cloud security) at contract signature but never fully deploy them. You're paying for capability, not consumption. If a module isn't actively used within 90 days, request it be removed or bundled at a lower rate.

Lack of Discount Stacking Clarity

Datadog bundles multiple modules, and discounts don't always stack in your favor. A company with infrastructure monitoring, APM, and logging might receive a 35% bundle discount on the total. But if you add synthetics or RUM later, the discount may not apply to the new modules, or it might recalculate downward on the entire contract. Get explicit discount language in writing.

Datadog Renewal Pricing: What Changes and What Doesn't

Datadog's renewal process is where many enterprises lose leverage. Here's what typically happens:

Host Count Creep

By year two, your infrastructure has likely grown. More EC2 instances, more containers, more cloud workloads. Datadog's renewal quote reflects this growth, and unless you've been carefully managing host count, the number can surprise you. Request a detailed host breakdown 120 days before renewal. Identify unused or test hosts you can retire to lower your renewed count.

Log Ingestion Rate Escalation

If you committed to a capped ingestion rate, Datadog will propose raising the cap based on your 12-month historical usage pattern. They'll show you that you've consumed 120% of your cap on average and "recommend" increasing it by 30% for safety. Question this aggressively. If you have control over log volume, implement sampling or filtering to reduce ingestion. Datadog wants higher ingestion renewal pricing.

Module Expansion Pricing

If you added synthetic tests, RUM, or security scanning during the contract year, renewal pricing will reflect higher modules. Datadog may apply renewal discounts only to the core modules you started with, requiring negotiation to extend discounts to new modules.

List Price Increases

Datadog has historically raised per-host and per-span pricing annually by 5 to 10%. Your renewal negotiation must account for this. If your contract originally had a 30% discount off list, and list pricing rose 8%, your effective discount shrinks to ~28% if you don't explicitly renegotiate percentage discounts.

Renewal Discount Leverage Points

Competitive bids: If you're evaluating Dynatrace, New Relic, or AppDynamics in parallel with renewal, you have maximum leverage. Datadog will match or beat their proposals.
Usage consolidation: If you've consolidated point tools under Datadog (e.g., retiring a dedicated APM tool), cite this for renewal discount uplift.
Strategic partnership value: If your company is a reference customer or case study, bring this into renewal discussions. Datadog's CSM team can approve deeper discounts for strategic accounts.
Multi-year renewal: Committing to a 2-3 year renewal (rather than annual) typically buys 10 to 15% additional discount.

Renewal Timeline Best Practices

180 days before expiration: Request renewal pricing from Datadog and competitive proposals from Dynatrace/New Relic.
120 days before expiration: Analyze the renewal quote. Identify host count, log volume, and module changes. Flag any unexpected cost drivers.
90 days before expiration: Provide Datadog with your negotiation targets. If they don't meet your requirement, notify them of your 90-day renewal cancellation intent.
60 days before expiration: Final negotiation round. If no path to alignment, begin migration planning to a competitor.