在结构上需要优先考虑并简化 CRM 集成，以实现向企业客户的转变。

AXDRAFT 即将失去其最大的客户之一，因为他们迫切需要 Slack 集成来续订。其他客户也表达了对整合的兴趣。

Tactic 是一家提供无代码工具的公司，用于从非结构化数据中提取可操作的见解，该公司面临着将其产品与客户的 CRM 数据集成的挑战。这种集成对于他们的企业收入团队和满足客户的需求至关重要。内部构建集成既耗时又昂贵，导致路线图延迟。

高接触 SaaS 销售周期中最重要的组成部分之一是安全审查，这在许多公司中并不是一个完善的流程。 Trustpage 通过为 B2B SaaS 公司提供动态信任中心，涵盖软件生命周期的每个阶段（从产品发现和销售到安全审查），将安全性转变为竞争优势。除了现有客户之外，销售渠道中的多个潜在客户还需要确保他们的所有团队都可以通过他们已经使用的工具有效地利用 Trustpage，这进一步推动了快速扭转这些集成的紧迫性。

MainStem 是大麻行业的 B2B SaaS 供应和采购平台，面临着重大挑战。该公司的首席技术官 Garrett 同时处理三个关键的集成请求（Teams、Slack 和 Quickbooks）。然而，他的团队无法确定这些集成的优先级，因为他们专注于为其企业产品 Purchasing Pro 开发核心产品功能。现有客户因消息应用程序中缺少 MainStem 通知而感到沮丧，而潜在的企业客户则需要 QuickBooks 集成来进行决策。此前，MainStem 在内部构建了许多集成，但这些集成需要大量的工程工作来构建和维护。该团队将花费数周时间来了解每个第三方应用程序的 API 文档、处理用户身份验证和令牌管理，以及由于供应商 API 的变化而维护集成。这种方法有几个缺点，包括将工程资源从核心产品中转移出来，影响销售和客户成功团队对其集成路线图的信心，以及增加维护要求。

Harbour faced challenges in providing seamless and user-friendly integrations for their contract management platform. Initially, they released a public API and webhooks, allowing technical customers to build their own integrations. However, this approach was not suitable for non-technical users. Integrating with Zapier was a temporary solution, but it required customers to leave Harbour and pay separately, detracting from the user experience. Harbour needed a more sustainable and scalable integration strategy that minimized engineering effort and provided a frictionless experience for all customers.

The business value for building out integrations was clear for tl;dv, but they faced a consistent problem. Initially, they attempted to build a Slack integration in-house but lacked the engineering resources to justify dedicating significant efforts on integrations without slowing down the development of their core product offering. Prior to becoming aware of Paragon, tl;dv had built Zoom and Google Meet integrations in-house, as these integrations were essentially the backbone of their product, and they needed to understand their APIs inside and out. However, while integrations with platforms like Slack, Salesforce, or HubSpot are still extremely important product features for them to build, they knew it wouldn’t make sense to have their developers spend weeks learning each platform’s API documentation. Additionally, maintaining each integration would cost them approximately a week per year, which would quickly add up as they scale to dozens, if not hundreds, of integrations in the future. As a result, tl;dv knew that the logical decision was to buy, not build.