Should Datadog acquire a Loom-equivalent in 2027?

Why Async Video Matters For Datadog

• Incident walkthrough recording — SRE narrating root-cause analysis in real time, attached to the incident timeline, replayable for the post-mortem and for newly-paged engineers
• On-call handoff video — outgoing on-call records a 90-second "here's what's hot, here's what I touched" clip pinned to the rotation transition, eliminating the Slack-thread archaeology problem
• Customer-debug screen capture — support engineers send a Loom-style video showing the exact dashboard query, filter chain, and trace path they used to diagnose the customer's issue
• Runbook augmentation — text runbooks decay; a 2-minute video showing the actual click-path through the Datadog UI for a specific failure mode ages better than a wiki page
• Async architecture review — staff engineers walk through service maps and APM flame graphs without scheduling a 30-min Zoom, capturing context that text PR comments lose

Why Atlassian-Loom Is The Cautionary Tale

• $975M paid in October 2023 — at peak async-video valuation, right before the GenAI wave compressed the entire "video memo" category as Bits AI / Copilot / Glean made text-summary the dominant async medium
• Two years post-close, integration is largely quiet — Loom is still a separate product surface, with limited deep weaving into Jira issues or Confluence pages beyond an embed
• Cultural friction — Loom's prosumer-bottoms-up motion clashed with Atlassian's enterprise-IT motion; reported attrition of senior Loom PMs and engineers within 12 months
• Pricing model collision — Loom's per-creator freemium versus Atlassian's per-seat enterprise tiering created a packaging puzzle Atlassian has not cleanly solved
• No defensible moat acquired — screen recording + cloud transcription is now a commodity primitive (Apple's native screen record + Whisper covers 80% of the value)
• Opportunity cost — $975M deployed elsewhere (Forge, Rovo AI) would likely have generated more durable platform value than buying a stagnating SaaS

Why Building > Buying For Datadog

• Bits AI investigation context is the moat — a video clip auto-tagged with the trace ID, host, deployment SHA, and Bits AI hypothesis is something no standalone video tool can replicate without deep observability integration
• Observability-tied video changes the recall pattern — engineers don't search "that video about checkout latency," they navigate from the incident in the timeline to the attached clip; the index is the trace, not the title
• Partner with Vidyard for fast win — white-label embed inside Datadog Incident Management for 18 months, prove demand, then build the native primitive in year two with real telemetry on what users actually record
• Engineering cost is small — Datadog already has session replay infrastructure (RUM); extending that to engineer-initiated screen capture is a 6-engineer team for 12 months
• No prosumer culture clash — building keeps the audience internal-engineering-first, avoiding the freemium-creator dynamics that broke Atlassian's Loom integration
• AI summarization in-house — Bits AI already transcribes and summarizes incident chatter; pointing it at video audio is an extension, not a new product

Acquisition Targets If They DID Buy

• Vidyard ($300-500M) — most enterprise-ready, real GTM video customers, sales-engineering DNA, but heavily oriented to marketing/sales rather than engineering workflows
• Tella ($75-150M) — modern UX, strong creator-tool design, small team that could be tucked in cleanly, but minimal enterprise penetration
• Loom-clone startups ($50-100M) — Bubbles, Berrycast, Claap, Guidde — acqui-hire range, useful for talent + a 6-month head start on the codebase, low platform risk
• Bonjoro ($30-75M) — sales-video specialist, wrong audience for Datadog (CS-led, not engineering-led)
• Avoid Vimeo Workplace ($150M+ carve-out) — public-company carve-out is messy, brand baggage, no engineering-tooling DNA

The Build Path Cost Comparison

• Build native primitive — $30-60M over 18 months: 6-engineer squad + 2 PMs + 2 designers + GTM packaging; ships as a feature inside Incident Management and Bits AI
• Partner with Vidyard — $3-5M/yr OEM/embed deal, 90-day integration, zero acquisition risk, validates demand before committing capital
• Acquire Tella — $75-150M + ~$15M/yr integration drag for 24 months + culture/retention risk; outcome: a slightly nicer-looking version of the build path
• Acquire Vidyard — $300-500M + $30-50M/yr integration + audience-mismatch risk; outcome: enterprise video product, but mostly serving Vidyard's existing marketing/sales customers, not Datadog's SRE base
• Net — partner-then-build is 5-10x cheaper than acquisition and produces a more defensible, observability-native end state

What Microsoft Stream Tells Us

• Microsoft acquired no one — Stream was built natively, integrated into Teams/SharePoint/OneDrive, and now ships as the de facto enterprise video layer
• The platform-native approach wins distribution — every Teams meeting auto-records to Stream; no Vidyard or Loom integration would have achieved that mechanical reach
• Build cost was modest relative to platform value — Microsoft never broke out Stream's investment, but external estimates put it at $50-100M of cumulative engineering, well under any acquisition price
• Datadog is in the Microsoft position, not the Atlassian position — it has its own surface (Incident Management, APM, Bits AI), its own daily-active engineer audience, and its own AI layer to summarize the video — every ingredient to build, not buy
• Cautionary footnote — Microsoft Stream V1 was a flop; V2 (Stream-on-SharePoint) worked because it stopped being a separate product and became a feature, which is exactly the lesson for Datadog

Strategy Comparison Table

Strategic Option Flow

Strategic Alternatives: Build vs. Buy vs. Partner

The build-buy-partner framework for Datadog in 2027 favors a hybrid approach. A full acquisition ($300-500M) would require 18-24 months of integration work, during which the video capability sits idle as a standalone product. Instead, Datadog could license Vidyard's enterprise video platform for $2-4M annually, gaining screen recording, transcription, and AI summarization without ownership costs. Simultaneously, a 12-month internal build effort ($20-35M) focused on embedding lightweight video capture into the Datadog investigation timeline would create the incident-context-aware recording that competitors like Grafana and New Relic lack. This dual-track approach delivers production capability in 6 months (via partner) and differentiated IP in 18 months (via build), avoiding the distraction of managing a separate video product line.

Integration Risks and Cultural Mismatch

Loom-equivalents typically operate with 30-50 person teams focused on consumer-grade UX and rapid feature iteration. Datadog's engineering culture prioritizes reliability, observability, and enterprise SLAs. Merging these cultures historically leads to 40-60% turnover in acquired teams within 24 months, as seen in the Atlassian-Loom case. Additionally, Loom's $975M price in 2023 reflected a 20x multiple on ARR, while similar async-video companies in 2027 would likely command 15-25x on $15-30M ARR, making a $225-750M acquisition range. The integration cost alone (retention packages, platform migration, API unification) adds another $50-100M. These numbers make the build option ($30-60M) financially compelling, especially when the core value—incident video context—represents less than 10% of Datadog's observability workflow.

Long-Term Product Strategy: Video as a Feature, Not a Platform

Datadog's 2027 product roadmap should treat async video as a feature layer within Bits AI and incident management, not a standalone revenue stream. The addressable market for incident-context video is a subset of Datadog's 25,000+ customers, likely 15-25% adoption within 3 years. At $50-100 per seat annually, this generates $190-625M in incremental ARR—attractive but not transformative. A Loom acquisition would require justifying a $300-500M purchase price against this constrained TAM. By contrast, building the feature internally preserves Datadog's focus on observability data pipelines and AI-driven root cause analysis, where the company holds clear competitive advantage. The video capability becomes a retention lever within the broader platform, not a separate business line requiring dedicated sales, marketing, and support.

FAQ

Why wouldn't Datadog just buy a Loom competitor to get video features? Acquiring a general async-video platform like Loom would cost $300-500M but deliver a commodity feature that doesn't deepen Datadog's core observability moat. The Atlassian-Loom deal showed that bolting on generic video rarely creates strategic lift—it stays a standalone surface. Datadog would pay for a large user base and sales team it doesn't need, when the real value is a narrow, incident-context-aware video primitive.

What specific video capability does Datadog actually need? Datadog needs a screen-recording tool that is natively tied to traces, logs, and the Bits AI investigation timeline—so when an engineer records a bug or incident replay, the video is automatically linked to the exact span, error, and log context. This is fundamentally different from a generic "record your screen and share a link" product. The engineering cost to build this is estimated at $30-60M over 18 months.

How much would a partnership with Vidyard or Tella cost instead of an acquisition? A strategic partnership with a platform like Vidyard or Tella would likely run $3-5M per year, covering API access, custom integrations, and maybe a co-marketing arrangement. That's roughly 1-2% of the cost of acquiring a $300-500M video company, and it avoids the integration headaches and cultural friction of a full acquisition.

Could Datadog ever acquire a video company later if the need changes? Yes, but only if the video product evolves to become deeply embedded in observability workflows—for example, if a company like Tella built native support for OpenTelemetry context injection. In that scenario, the acquisition target would be smaller (likely $50-150M) and more focused, rather than a broad async-video platform. The 2027 window is too early for that maturity.

Does the Bits AI integration make video more valuable than standalone tools? Potentially—if Bits AI can auto-generate video snippets from incident timelines, or let engineers query "show me the video from the paging event at 3:14 UTC," then video becomes a searchable data type, not just a recording. That kind of deep integration is what justifies building in-house, but it also means the video feature must be purpose-built, not acquired as a generic product.

What's the risk of waiting too long to build this? The main risk is that a competitor like New Relic or Splunk ships a similar integrated video primitive first, creating a temporary differentiation. However, since no major observability platform has done this yet, and the engineering cost is modest ($30-60M), Datadog can afford to wait 12-18 months to build it right. The bigger risk is rushing an acquisition that dilutes focus and delivers a commodity feature at a premium price.

Bottom Line

Datadog should partner-then-build, not acquire. The Atlassian-Loom precedent is unambiguous: paying $975M for a standalone async-video product yields integration drag, culture clash, and no defensible moat. Datadog's edge is not video — it is incident-context-aware video tied to traces and Bits AI, which only the platform owner can build. A $3-5M/yr Vidyard partner deal in 2027 validates demand at near-zero risk; a $30-60M native build in 2028 captures the durable wedge. Save the $300-500M for something that actually compounds (data agents, BI-native query layer, or vertical observability bets).

Cross-links: see also q1674 (Datadog data-platform M&A), q1683 (Datadog AIOps build vs buy), q1685 (Datadog incident management roadmap).

Tags

datadog, mna-async-video, atlassian-loom-precedent, bits-ai, incident-walkthrough, vidyard-partnership, build-vs-buy, observability-video, sre-async-collaboration, microsoft-stream-lesson

Related on PULSE

• [Should Outreach acquire a Loom-equivalent in 2027?](/knowledge/q1748)
• [Should ServiceNow acquire a Loom-equivalent in 2027?](/knowledge/q1628)
• [Should Datadog acquire Grafana to compete against open-source?](/knowledge/q1717)
• [Should Datadog acquire Honeycomb to win observability?](/knowledge/q1716)
• [Should Outreach acquire Apollo in 2027?](/knowledge/q1892)
• [Should Salesloft acquire a video tool in 2027?](/knowledge/q1865)

Sources

• https://www.atlassian.com/blog/announcements/atlassian-acquires-loom
• https://www.loom.com/
• https://www.vidyard.com/
• https://www.tella.tv/
• https://learn.microsoft.com/en-us/stream/
• https://www.datadoghq.com/product/bits-ai/
• https://www.bvp.com/atlas/state-of-the-cloud-2026
• https://www.datadoghq.com/blog/datadog-incident-management/