---
id: "entity-zendesk"
type: "entity"
entityType: "organization"
canonicalName: "Zendesk"
aliases: ["\\\"Zendesk", "Inc.\\\""]
source_timestamps: ["¶5"]
tags: ["acquirer", "customer-service-software", "case-study"]
related: ["entity-smooch", "concept-complementors"]
source_url: "https://hbr.org/2026/06/when-evaluating-an-ma-opportunity-consider-the-broader-digital-ecosystem"
source_title: "When Evaluating an M&A Opportunity, Consider the Broader Digital Ecosystem"
sources: ["ecosystem"]
sourceVaultSlug: "hbr-seg-ecosystem"
originDay: 11
articleStem: "hbr-cl-80-ma-digital-ecosystem"
sourceUrl: "https://hbr.org/2026/06/when-evaluating-an-ma-opportunity-consider-the-broader-digital-ecosystem"
sourceTitle: "When Evaluating an M&A Opportunity, Consider the Broader Digital Ecosystem"
---
# Zendesk

**Entity type:** organization · **Canonical name:** Zendesk, Inc.

**Role in source — complementor-access exemplar.** A customer-service software provider that acquired [[entity-smooch]] in **2019**. Zendesk used the acquisition to gain access to Smooch's network of [[concept-complementors]] (developers building chatbots and automation workflows), thereby expanding its own functionality and customer value. The example illustrates that acquisition value "wasn't just in the core code" but in the complementor community.

**Enrichment note:** Canonical reference is Zendesk, Inc. The specific claim that value "wasn't just in core code" is inferential — consistent with ecosystem logic, but the provided search results do not independently validate the exact complementor-network impact described.