Consumer vs Internet-native support

The split in customer mix shows two different wedges into the same market. Sierra is winning where support is tied to messy consumer operations, physical goods, phone calls, billing systems, and large legacy stacks, while Decagon is winning where support lives inside modern SaaS workflows and product onboarding. That helps explain why Sierra ramped faster early, because bigger consumer brands have larger support budgets and more expensive pain to replace.

• Sierra’s early logos skew toward consumer brands like WeightWatchers, SiriusXM, Sonos, and ADT, and the broader positioning is closer to replacing a BPO for high volume support across chat and voice. That fits companies handling subscriptions, devices, returns, scheduling, and other workflows that still create lots of phone and back office work.
  1 sacra 4 sacra
• Decagon’s traction with Notion, Duolingo, Webflow, Rippling, and similar companies reflects a more internet native environment, where support is tightly connected to product onboarding, account changes, and software workflows. In those settings, deep integrations into the app stack matter more than handling the long tail of offline service operations.
  2 sacra 4 sacra
• Under the hood, both products use the same playbook, forward deployed engineers, custom integrations, and per resolution pricing around $1.50. The difference is less model quality than where each company found fastest proof of ROI, with Sierra selling into larger consumer enterprises and Decagon into fast moving software companies.
  1 sacra 2 sacra 3 sacra

Going forward, this segmentation is likely to narrow as both move upmarket and broaden use cases beyond reactive support into onboarding, retention, sales, and voice. The near term advantage goes to the company that can turn its initial customer base into a repeatable deployment motion before the market converges around a few full stack AI service platforms.