Should ServiceNow acquire a Loom-equivalent in 2027?

A Costly Ticket That Never Needed a Meeting

Picture a Tier-2 support engineer at a mid-market ServiceNow customer, staring at an incident ticket that says "checkout flow broken, can't reproduce." The customer's screenshot shows a static error state; nothing in the ticket explains the sequence of clicks that triggered it. The engineer schedules a 30-minute screen-share for the next business day, because that's the only reliable way to see the bug in motion. The customer loses a day of productivity, the SRE queue backs up, and the mean-time-to-resolution metric that RevOps leadership tracks every quarter takes another hit.

Now picture the same ticket with a 90-second embedded video: the customer's cursor moves through three screens, the error appears, the recording auto-attaches to the ITSM ticket, and Now Assist's transcription layer surfaces a one-line summary and a suggested KB article before the SRE even opens the case. That is the actual use case ServiceNow is evaluating when the question of an "acquire a Loom-equivalent" comes up — not a general-purpose video-messaging app, but a narrow, workflow-bound recording capability that lives inside incident management, HR onboarding in HRSD, and customer service case resolution in CSM.

The scenario matters because it reframes the decision. The market question isn't "does ServiceNow need video," it's "does ServiceNow need to own a standalone video company to get this 90-second clip attached to a ticket." Atlassian answered that question with a $975M check in 2023, buying Loom outright rather than building a lighter integration. Two years later, the flagship "Loom-powered Jira" transformation that would have justified that price tag hasn't materialized as a headline product shift. That is the cautionary tale RevOps and corporate-development teams inside ServiceNow are weighing as they model a 2027 build-vs-buy-vs-partner decision, and it's the frame every other section below builds on.

How Async-Video Would Plug Into the Now Platform

If ServiceNow adds async-video capability — whether by acquiring a Loom-equivalent, partnering with one, or building natively — the mechanism has to route through three existing systems, not bolt on as a fourth silo.

First, the capture layer: a lightweight browser extension or embedded recorder that captures screen and webcam, similar to what Loom, Vidyard, and Tella already ship. This layer is the most commoditized part of the stack — nearly identical recording SDKs exist across a dozen vendors, which is exactly why paying nine figures for one is hard to justify on capability alone.

Second, the AI processing layer, which ServiceNow already owns via Now Assist. Once a clip is recorded, Now Assist's existing transcription and summarization models — the same ones already used for case summarization and knowledge-article generation — would ingest the audio/video metadata, produce a text transcript, and generate a short natural-language summary. This is the layer that turns a video from "a file someone has to watch" into "a searchable, actionable data object," and it's also the layer an acquired standalone company would not bring with it, because Loom, Vidyard, and Tella all built their own separate (and non-ServiceNow-native) transcription stacks.

Third, and most important, the binding layer: Workflow Data Fabric. This is ServiceNow's system for tying any piece of content — a case, an incident, an employee record, a change request — to its originating workflow context, permissions, and audit trail. A video recorded inside a CSM case needs to inherit that case's ACLs, retention policy, and audit log automatically; a video recorded during HR onboarding needs to respect HRSD's data-residency rules. This is the layer that makes ServiceNow's potential async-video offering different from a generic Loom clip sitting in a shared drive, and it's the layer that no acquisition target — Vidyard, Tella, Bonjoro, or a Vimeo carve-out — arrives with pre-built, because none of those products were designed against ServiceNow's ACL and instance-isolation model.

The mechanism above is why the acquisition math skews toward partner-then-build: two of the three layers already exist inside ServiceNow, and the one layer that doesn't (capture) is the cheapest and least differentiated of the three to either build or license.

What the Numbers Say: Loom, Vidyard, Tella, and the Build Cost

The benchmark everyone in this conversation returns to is Atlassian's acquisition of Loom for $975 million in cash and stock, announced in October 2023. That price bought Atlassian a category-leading async-video brand at the peak of post-pandemic hype around asynchronous work. Two years later, there is no flagship "Loom-native Jira" relaunch, no headline case study of Loom driving a step-change in Atlassian's revenue mix, and Loom as a standalone product has not meaningfully compressed Vidyard's position in the enterprise sales/marketing video segment. That is the single most important data point for anyone at ServiceNow modeling this decision: a nearly billion-dollar acquisition, evaluated two years out, reads as a feature buy, not a strategic transformation.

Against that benchmark, the alternative price points look very different. A revenue-share partnership with Vidyard or Tella — embedding their SDK via existing plugin or API integrations rather than acquiring the company — runs in the range of $5-10 million per year, ships inside a single quarter, and preserves ServiceNow's option to walk away, renegotiate, or acquire later once usage data justifies it. A native build of a recording-and-playback primitive inside Now Platform, wired into the Now Assist transcription pipeline and Workflow Data Fabric binding described above, is estimated at roughly $50-100 million in R&D spread over 18 months — a fraction of the Atlassian-Loom price, and critically, it produces IP and integration depth ServiceNow fully owns rather than integration debt it inherits from an acquired codebase.

If ServiceNow did pursue acquisition anyway, the realistic target list and rough valuation bands look like this: Vidyard, the most enterprise-ready of the group with strong traction in sales and marketing video, in the $300-500 million range, though its footprint overlaps more with Salesforce and HubSpot's territory than ServiceNow's ITSM/HRSD core; Tella, a smaller, modern, pre-Series B product in the $75-150 million range with the lightest integration lift; Bonjoro, a narrower sales-ops/CRM-video play at $50-100 million; and a Vimeo Workplace carve-out, which would require Vimeo to spin its B2B unit out entirely and carries the highest regulatory and IP complexity, estimated at $200-400 million. None of these price points comes close to the native-build cost, and all of them import integration work comparable to or exceeding the Atlassian-Loom timeline.

Finally, there's a later acquihire option: if the partner-plus-build path surfaces a specific team or technology gap by 2028, a small-team acquihire — roughly 15-25 engineers — in the $30-50 million range is a plausible fallback, an order of magnitude cheaper than acquiring a full standalone company today.

Buy vs. Partner vs. Build: Trade-offs and Alternatives

Every path here trades cost against speed against strategic fit, and the honest comparison has to hold all three variables at once rather than optimizing for just one.

Buying Vidyard outright would deliver the most enterprise-ready product on day one, but at $300-500 million it also imports the highest integration risk — Vidyard's product was architected for sales and marketing teams inside Salesforce and HubSpot workflows, not ITSM incident management, so ServiceNow would be paying full price for a product it would need to substantially re-platform. Buying Tella is cheaper and the UX is stronger, but it's a small, early-stage team; the retention risk that hit Loom's founders after the Atlassian deal (several early leaders moved on within 18 months of close) would likely repeat, and ServiceNow would still owe 9-12 months of integration work. The Vimeo Workplace carve-out is the worst risk-adjusted option: it requires Vimeo to spin out a business unit, invites regulatory review, and offers the least clear alignment with ServiceNow's ITSM/HRSD/CSM core.

The partnership route inverts all of these trade-offs. At $5-10 million a year, a Vidyard or Tella integration ships in roughly a quarter, carries low financial risk, and — critically — lets ServiceNow observe real usage data (which teams actually record video, how often, on what workflow types) before committing capital to either a full acquisition or a native build. The tradeoff is that ServiceNow doesn't own the capture layer, so pricing, roadmap, and product decisions stay partially outside its control, and a competitor could poach the same partner.

The native-build path is the highest strategic fit because it's the only option that fully owns the Workflow Data Fabric binding and Now Assist integration described in the mechanism section above — but it carries execution risk (18 months is optimistic if scope creeps) and doesn't solve the near-term competitive gap while it's being built, which is why the partner-now, build-by-H2-2027 sequencing is the pragmatic answer rather than picking one path exclusively.

Common Pitfalls in an Acquire-vs-Build Decision Like This

The first pitfall is treating the recording widget as the product. Loom, Vidyard, and Tella all built genuinely good capture experiences, but capture is the least defensible layer in this stack — nearly every video-messaging startup ships a comparable recorder. A RevOps or corporate-development team that anchors an acquisition case on "our recorder is better than theirs" is buying a commodity at a strategic price, which is exactly what happened in the Atlassian-Loom deal.

The second pitfall is underestimating integration cost. ServiceNow's platform is built around instance-level data isolation, role-based access control, and enterprise SSO — none of which map cleanly onto a consumer-grade video product's architecture. Any acquired company would need its storage layer rebuilt for ServiceNow's data-residency requirements and its sharing model rebuilt for ServiceNow's ACL system before it could sit natively inside ITSM, HRSD, or CSM workflows. Skipping or underscoping that work is how an acquisition becomes "quiet" two years later, which is the exact outcome the Atlassian-Loom case illustrates.

The third pitfall is bad timing. Microsoft already bundles Clipchamp into Teams and Viva at no incremental cost for E5 customers, Google has built video messaging into Workspace, and Zoom ships Clips inside Zoom Workplace. All three reach hundreds of millions of daily active users through their existing collaboration-suite distribution — a scale advantage ServiceNow cannot match by acquiring a standalone video company. Waiting until 2027 to acquire, rather than partnering now and building natively on a faster timeline, risks entering the category after enterprise buyers already expect async-video as a built-in feature of whichever suite they're on, not a separately procured tool.

The fourth pitfall is ignoring talent retention. Async-video founders and early engineers generally want to keep building a standalone product, not become a feature team inside a much larger platform roadmap. Structuring any deal — partnership or eventual acquihire — with realistic retention expectations, rather than assuming a founding team will happily fold into ServiceNow's release cycle, avoids repeating the leadership churn Loom saw after its Atlassian acquisition.

The fifth pitfall is skipping the partnership step entirely and jumping straight to "build vs. buy." A revenue-share deal with Vidyard or Tella costs a rounding error next to either alternative, ships in a quarter, and generates real usage data that should inform whether ServiceNow ever needs to acquire or build at all — treating partnership as a placeholder rather than a legitimate long-term option is the single most avoidable mistake in this decision.

Related questions

Should Outreach acquire a Loom-equivalent in 2027?

Outreach's core workflow is sales engagement, not ITSM/HRSD case management, so the video-context binding argument is weaker there than for ServiceNow — a lighter partnership fits Outreach's sales-motion use case better than a full acquisition.

Should ServiceNow acquire Atlassian in 2027?

This is a fundamentally different scale of deal — Atlassian is a multi-billion-dollar public company with its own workflow platform, not a point acquisition; the strategic logic and price tag are not comparable to a Loom-equivalent purchase.

Should ServiceNow acquire Workato in 2027?

An iPaaS acquisition targets integration/orchestration depth, a much closer strategic fit to ServiceNow's Workflow Data Fabric than a video-recording company, making the buy-vs-build calculus genuinely different from the async-video case.

What did Atlassian pay for Loom, and did the deal work out?

Atlassian paid $975 million in cash and stock in October 2023; two years later there is no flagship product relaunch built around Loom, making it the reference case for "overpaying for a feature" in acquisition strategy.

FAQ

Why would ServiceNow even consider a Loom-equivalent in 2027? Async-video is becoming a standard way to attach visual context — a screen recording — to incidents, HR onboarding, and customer cases. ServiceNow's interest isn't in video as a standalone product; it's in feeding that visual context into Now Assist and Workflow Data Fabric so it becomes structured, searchable workflow data.

What's the biggest risk of ServiceNow buying a Loom-equivalent outright? The Atlassian-Loom precedent: paying nearly $1 billion for a standalone async-video company and getting a quiet, feature-level integration two years later rather than a strategic transformation. The recording capability itself is commoditized, so the acquisition price rarely buys a defensible moat.

Could a partnership with Vidyard or Tella work instead of an acquisition? Yes — a revenue-share partnership in the $5-10 million per year range would give ServiceNow async-video capability without acquisition risk, ship inside a quarter, and let video metadata feed into Workflow Data Fabric for automation while preserving the option to build native or acquihire later.

What would it cost ServiceNow to build async-video natively? Roughly $50-100 million in R&D spread over about 18 months for a recording primitive wired into the existing Now Assist transcription pipeline and Workflow Data Fabric binding — a fraction of any acquisition price and fully owned IP rather than inherited integration debt.

How does this fit ServiceNow's existing AI stack? Now Assist already handles transcription, summarization, and semantic search. Adding a video layer would let a recorded screen walkthrough automatically generate a transcript, a knowledge-base article, or a follow-up task — the video becomes another input to automation ServiceNow already owns, not a new standalone product line.

What's the bottom line for a RevOps team modeling this decision? Skip the large acquisition. Partner with Vidyard or Tella now for roughly $5-10 million a year, build a native async-video primitive into Now Platform by H2 2027 for roughly $50-100 million, and hold acquihire optionality in reserve for 2028 — the moat is Workflow Data Fabric and Now Assist, not the record button.

Sources

• https://www.atlassian.com/company/news/press-releases/atlassian-completes-acquisition-of-loom
• https://www.servicenow.com/products/now-assist.html
• https://www.servicenow.com/investor-relations.html
• https://www.vidyard.com
• https://www.tella.tv
• https://www.gartner.com
• https://www.forrester.com
• https://www.techcrunch.com
• https://www.microsoft.com/en-us/microsoft-teams/clipchamp

Related on PULSE

• [Should Outreach acquire a Loom-equivalent in 2027?](/knowledge/q1748)
• [Should Datadog acquire a Loom-equivalent in 2027?](/knowledge/q1688)
• [Should ServiceNow acquire Atlassian in 2027?](/knowledge/q1887)
• [Should ServiceNow acquire Workato in 2027?](/knowledge/q1912)
• [Should ServiceNow acquire Workato to compete in iPaaS?](/knowledge/q1657)
• [Should ServiceNow acquire UiPath to win agent automation?](/knowledge/q1656)