Observability
Outbound Pipeline Generation for Observability & APM Platforms
Done-for-you outbound for observability and APM companies. We help platforms like Datadog, New Relic, and Grafana reach VPs of Engineering, SREs, and Platform Engineering leaders at mid-market and enterprise software companies.
Observability is one of the largest categories in B2B software — Gartner pegs the application performance monitoring and observability market at well over $10B annually, and Datadog alone reached a market cap above $40B before broader cloud-sector volatility. The category compounded as cloud workloads scaled: every microservice, Kubernetes cluster, and serverless function generates telemetry that engineering teams need to consolidate, correlate, and alert on. The buyer set is unusually technical, and the bar for credible outbound is correspondingly high.
VPs of Engineering, Platform Engineering Directors, and SREs are not impressed by feature lists. They live inside the problem — incident review, on-call rotation, latency budgets, cardinality explosions — and outbound that doesn't demonstrate that fluency dies on first read. At the same time, observability is a high-ACV category with deep stickiness, so the outbound investment is justified: a single signed enterprise customer often clears the cost of a full year of pipeline generation.
We build outbound programmes for observability platforms by combining technical specificity with the right buyer signals. Lists filter on cloud spend, Kubernetes adoption, and recent platform-engineering hires. Messaging assumes the buyer is already deciding between Datadog, New Relic, Dynatrace, and the open-source stack — and the angle is the specific operational pain (alert fatigue, MTTR, cost explosion at scale) that justifies opening a conversation right now.
Datadog
www.datadoghq.comCloud-scale unified observability platform spanning infrastructure monitoring, APM, log management, real-user monitoring, and security — the category-defining commercial alternative to the open-source observability stack.
Founded
2010
HQ
New York, NY
Employees
7,500+
Funding
Public (NASDAQ: DDOG), market cap ~$40B
Customers
28,000+ customers, 3,610 with ARR ≥ $100K, 396 with ARR ≥ $1M (Q4 2024)
ARR / revenue
$2.68B (Q4 2024 annualised)
Market position
The most successful observability vendor of the cloud era. Datadog assembled what was previously a fragmented category (infrastructure + APM + logs + security) into a single platform with consumption-based pricing — and built one of the most technically-credible outbound + content marketing engines in B2B software to drive adoption.
Why they win
- Unified platform spanning infrastructure, APM, log management, RUM, and security creates compounding switching costs as more modules deploy.
- Consumption-based pricing scales naturally with the buyer's cloud growth, so customer expansion is automatic rather than negotiated.
- Industry-leading integration count (700+ pre-built integrations) means almost any cloud or container stack can plug in within hours.
- Datadog State of the Cloud reports and engineering blog function as required reading inside platform engineering teams — the brand sits inside the buyer's mental "must evaluate" list.
- Public market validation and analyst coverage (Gartner, Forrester, IDC) provide the third-party signals enterprise procurement requires.
Citations (3)
- Datadog reported $738M in Q4 2024 revenue, $2.68B annualised. Datadog Q4 2024 Earnings Release
- Datadog has 3,610 customers with $100K+ ARR and 396 customers with $1M+ ARR as of Q4 2024. Datadog Q4 2024 Earnings Release
- Datadog supports 700+ pre-built integrations across cloud providers, container orchestrators, databases, and SaaS tools. Datadog integrations directory
Spotlight information sourced from public records. BookedCalls.ai has no affiliation with Datadog.
Tech Sales Challenges We Solve
The specific outbound problems we run into when selling into observability buyers — and what we build to clear them.
Buyers Are Technical And Pattern-Match Generic Outreach Instantly
Platform engineers and SREs spend their day filtering noise. Generic "improve your monitoring" outreach is treated like an alert that should be ignored. The opening line has to demonstrate the sender understands the prospect's actual stack (Kubernetes, Prometheus, OpenTelemetry, AWS services in use) or the email is closed and the sender mentally blocklisted.
Open-Source Alternatives Anchor Buyer Expectations
Prometheus, Grafana, OpenTelemetry, and Jaeger are free and good enough for many teams. Outbound has to articulate why the commercial platform is worth the line item, and the answer is rarely the feature — it is the cost of running the open-source stack at scale, the engineering hours, the alert quality, the integration count.
Multi-Team Buying With Engineering, Platform, And Finance Stakeholders
Observability platforms get adopted by individual engineering teams (often via PLG signup) and then face a consolidation question when central platform engineering takes inventory. The buying committee involves VP Eng, Platform Lead, SRE, Security (for log access), and increasingly Finance (because observability costs have become a top-3 cloud line item).
Cardinality And Cost Anxiety
Observability buyers have all seen a bill jump 5x when a high-cardinality label or a logs surge hit. Outbound that pitches "more visibility" without addressing the cost-control narrative is dismissed; outbound that names the cost control as the wedge gets through.
Long Procurement Cycles With Security Review
Observability platforms ingest logs and traces that contain PII, secrets, and infrastructure topology. Security and compliance review (SOC 2, ISO 27001, FedRAMP for some buyers) adds 60-120 days even after the technical evaluation is done. Outbound has to clear the security narrative early.
Tool-Sprawl Backlash And Vendor Consolidation Pressure
Most engineering teams already run 8-15 monitoring, alerting, and logging tools — some by team choice, some by acquisition inheritance. Finance is asking them to consolidate. The buyer is not looking for "yet another tool" but the platform that lets them retire two or three line items. Outbound that opens with the consolidation thesis lands; outbound that pitches a new tool joins the sprawl problem.
The Buyer Dossier
Who Datadog sells to
The shape of Datadog's buyer — who they are, what they care about, and what triggers a purchase decision.
Buyer summary
Datadog sells across SMB to global enterprise, but observability ACV scales with cloud spend — the deepest pockets are mid-market and enterprise engineering teams running meaningful workloads on AWS, GCP, or Azure. The economic buyer is the VP of Engineering or CTO; the technical champion is Platform Engineering or SRE; and the procurement gate is increasingly FinOps as observability costs hit the cloud-spend top-3 list.
Primary buyer titles
Company profile
- Size
- Mid-market to enterprise — 200 to 50,000+ employees; observability ACV scales with cloud spend not headcount
- Geographies
- North America (primary) · EMEA (UK, Ireland, Germany, France) · APAC (Japan, Australia, Singapore) · LATAM (Brazil)
- Tech-stack signals
- AWS, GCP, or Azure as primary cloud (minimum signal — open-source observability cost makes Datadog economic above ~$30K/month cloud spend)
- Kubernetes or container orchestration in production
- Existing point solutions (New Relic, Splunk, PagerDuty, Sumo Logic) — consolidation opportunity
- Recent hiring of Platform Engineer, SRE, or Director of DevOps roles
What they care about
- MTTR (mean time to recovery) — measured in minutes and tracked at the incident review.
- Alert quality — reducing the false-positive rate that drives on-call burnout.
- Observability cost as a percentage of cloud spend (target <5%, often hits 10-15% before optimisation).
- Engineering hours spent maintaining observability infrastructure vs building product.
- Security and compliance — SOC 2, ISO 27001, FedRAMP, HIPAA depending on the buyer's industry.
Buying triggers
- Production incident with significant blast radius (often public — status page, post-mortem post)
- Kubernetes adoption announcement or migration project
- New VP Engineering or CTO hire (driving stack consolidation)
- Cloud-cost optimisation initiative (FinOps-led)
- Compliance milestone (SOC 2 Type 2, ISO 27001) driving audit-trail requirements
Common objections
- "We're fine with Prometheus + Grafana — adding a commercial vendor is just more cost."
- "Datadog pricing scales with cardinality, and we're worried about a bill explosion."
- "Migration cost from our current stack (New Relic / Splunk / Dynatrace) is significant."
- "Security review of cloud-hosted log ingest will take 6 months minimum."
- "We tried Datadog two years ago and the bill scared us off."
How We Help
Our services tailored for the observability sector.
- Cloud-spend and Kubernetes-adoption-aware ICP definition — we segment by AWS / GCP / Azure footprint, container orchestration maturity, and observable engineering-team size, because the buyer fit is bimodal (early-stage teams with sub-£50K observability spend are not the fit)
- Multi-team sequencing: VP Engineering and Platform Engineering Lead as primary; SRE Leads, Site Reliability Managers, and Director of DevOps as secondary; CISO and Head of FinOps as stage-progression triggers
- Trigger-driven list refresh: post-incident press, Kubernetes migration announcements, hiring spikes in Platform / SRE / DevOps roles, public cost-optimisation initiatives
- Technical copy review — every email reviewed by someone who has run production systems, because tone-deaf technical copy kills a campaign faster than no campaign at all
- Dedicated sending infrastructure with strict deliverability monitoring — engineering teams use server-side spam filters and quarantine more aggressively than marketing teams
- Reporting in the buyer's vocabulary — MTTR, MTBF, alert-to-incident ratio, p95 / p99 latency, cardinality counts. We don't pretend to be engineers, but the campaign communicates that we have engineers in the loop
The Outbound Angle
How we'd run outbound here
For an observability platform, the angle is never "better visibility" — it is the specific operational pain the buyer's current stack is causing today. The successful outbound message names the cost, the engineering hours, the alert fatigue, or the incident response gap with technical specificity, and the platform becomes the answer rather than the pitch.
Channel mix
- EmailPrimary
Engineering leaders read email for substantive technical content. A well-targeted, technically-specific email earns reply rates in the 4-8% range in this category.
- LinkedinSecondary
VPs of Engineering and Platform Engineering Leaders are increasingly visible on LinkedIn. Engagement with their published content (conference talks, post-mortem reflections) materially lifts cold-email reply rates.
- PhoneSupport
Engineering leaders are phone-resistant when cold-called but more willing on signal — post-incident response, post-funding cycles, or following an internal team-level adoption signal.
Who & when
Target titles
Signal types
Sequencing shape
Multi-touch (5-7 touches over 28 days), multi-threaded into VP Eng, Platform Lead, and SRE Lead in parallel. Every sequence pegs to a public technical signal (incident, migration, hiring spike) and the messaging assumes the buyer is already comparing the commercial options against the open-source stack.
What we won't do
- No marketing-vendor copy ("AI-powered observability!") — engineering buyers screen this out instantly.
- No outreach into companies without observable cloud / container maturity — the value proposition fails below ~$30K/month cloud spend.
- No FUD against open-source alternatives. We position the cost / engineering-hours trade-off, not the technical inferiority.
The shape, not the script.
Want the actual sequences, queries, and angles? That's the discovery call.
Example Campaigns
How outbound works in practice for observability companies.
PLG-To-Enterprise Migration
An observability platform with bottom-up adoption inside engineering teams needs to broker the enterprise-wide conversation. Outbound targets the VP Eng or Platform Director at companies where the platform already has team-level usage, leading with internal-reference proof.
Open-Source-To-Commercial Conversion
Targeting companies running Prometheus + Grafana + Jaeger at scale who have hit the operational cost ceiling. The outbound message is specifically about the engineering hours spent maintaining the open-source stack vs the line-item cost of a commercial platform.
Vendor Consolidation Plays
Targeting companies running three or four point solutions (e.g. New Relic for APM + Splunk for logs + PagerDuty for alerts) where a consolidated platform pitch lands as a cost-reduction story rather than a new line item. The outbound angle is the consolidation, not the new tool.
Real-World Success Stories
See how companies in observability have grown their pipeline with outbound.
Datadog
Infra & Cloud / ObservabilityChallenge
Datadog pioneered the unified observability category by combining infrastructure monitoring, APM, log management, and security in one platform. The challenge was reaching enterprise engineering leaders who were already using point solutions and educating them on the value of consolidation — without being dismissed as a generic monitoring vendor.
Approach
Datadog built one of the most technically-credible outbound motions in B2B software. Reps were trained to speak about Kubernetes, distributed tracing, and cardinality with engineering depth. Outbound was paired with technical content marketing (the Datadog State of the Cloud reports became required reading inside engineering teams) so reps had something to point at when opening conversations.
Results
- Reached $40B+ peak market capitalisation as a public company (NASDAQ: DDOG)
- Built one of the largest enterprise customer rosters in observability — over 28,000 customers including over 3,000 with ARR above $100K (as of recent filings)
- Outbound + content marketing combination became the operational case study for technically-credible B2B SaaS go-to-market
Source: Based on Datadog 10-K and investor materials
New Relic
Infra & Cloud / APMChallenge
New Relic was an early APM leader that had to defend its position as Datadog expanded into application performance monitoring. The outbound challenge was reaching engineering leaders who were evaluating the competitive set and articulating a specific differentiation against the unified-platform pitch.
Approach
New Relic ran outbound focused on consumption-based pricing transparency (vs Datadog's per-host cost) and on specific technical depth in front-end / browser monitoring. The motion targeted FinOps leaders alongside engineering as observability costs became a board-level cloud-cost line item.
Results
- Reached over $700M ARR before being taken private by Francisco Partners and TPG in 2023 at $6.5B valuation
- Established consumption-based pricing as a meaningful market segmentation against per-host competitors
- Continued to defend a significant share of mid-market and enterprise APM through targeted outbound + technical content
Source: Based on Francisco Partners / TPG 2023 acquisition announcement
Honeycomb
Infra & Cloud / ObservabilityChallenge
Honeycomb positioned itself as the observability platform for high-cardinality, event-based debugging — a specific technical wedge against legacy APM tools. The challenge was reaching engineers sophisticated enough to value the high-cardinality story (debug your service the way the SRE-book describes) over the broader category narrative.
Approach
Honeycomb ran outbound exclusively into engineering teams already using OpenTelemetry, distributed tracing, or event-based architectures. The opening hypothesis was always technically specific: "your service handles N concurrent traces with M dimensions — here is what high-cardinality debugging would surface that aggregate dashboards miss."
Results
- Built a multi-hundred-customer roster of high-engineering-maturity buyers (Slack, Vanguard, Spotify alumni) against incumbent APM platforms
- Established high-cardinality observability as a recognised category subset with significant analyst coverage
- Demonstrated the power of technical-narrative-led outbound in a saturated infrastructure category
Source: Based on publicly reported case studies and analyst coverage
We help companies like Datadog, New Relic, and Honeycomb build predictable outbound pipelines. Yours could be next.
Your Pipeline, Built From Scratch
We build your outbound pipeline from scratch — targeting the right prospects, booking qualified meetings, and filling your calendar so you can focus on closing. Or let us handle the full sales cycle and close deals on your behalf.
Observability Pipeline Calculator
Leads
500
Intent
75
Booked
17
Deals
3
Monthly Revenue
£255,000
3 deals × £85,000
Annual Revenue
£3,060,000
12-Month Revenue Forecast
Forecast Assumptions
- Month 1: 30% of target (setup & warming)
- Month 2: 60% (campaigns ramping)
- Month 3: 85% (optimising)
- Month 4+: 100% (full run rate)
Revenue = meetings × close rate × deal size
12-Month Current Revenue
£510,000
12-Month With BookedCalls
£2,796,075
Additional Revenue
+£2,286,075
More in Infra & Cloud
Related Tech Sales Verticals we have built outbound playbooks for.
Ready to grow your observability pipeline?
Book a discovery call and we will show you how outbound can work for your business.