You want a chat widget on your website that captures leads and hands them to your sales team without friction. The obvious choices—Intercom and Zendesk—are everywhere. But their unit economics are brutal if you're running volume. We'll walk through what each actually costs, what you get for it, and whether a native or open-source widget makes more sense for your business. The per-conversation trap: why Intercom and Zendesk get expensive fast Intercom charges based on "conversations" (a thread between visitor and your team). Zendesk charges per "agent" but their chat widget sits behind a paywall unless you pay for customer support seats. For a business running even moderate chat volume, this inverts the math. Here's the reality: Intercom Standard: ~$74/month gets you up to 1,000 contacts, but conversations are metered separately. A 50-conversation/month business pays the base fee. A 500-conversation/month business bumps into overage territory fast. Zendesk Suite (with chat): starts at ~$55/month per agent, and you need at least one agent seat. At 2–3 agents, you're at $110–165/month. But the real cost is agent utilization—chat ties up people who could be closing deals. Visitor volume doesn't map to revenue: A SaaS company with 5,000 monthly site visitors might get 200 chat starts, of which 20 become qualified leads. You're paying per conversation, not per conversion. Both Intercom and Zendesk assume you want a full customer support operation. If you're actually running sales acquisition, you're paying for the wrong tool. Native widgets: Orin's approach vs the math If your primary goal is to capture leads and hand them to sales, a native CRM widget embedded on your site saves money and removes a data handoff step. Orin's embedded AI chat widget lives inside your CRM, meaning: Every chat creates a contact record immediately (no lead import, no API sync). Your sales team sees visitor intent in real time within your existing pipeline. AI can handle tier-1 questions (product basics, pricing) without a human; complex queries route to your team. No per-conversation fee. You pay one platform fee; the widget is included. The setup is straightforward: drop a snippet of code on your website. No Zapier, no CSV imports, no lost context. A visitor asks "Do you work with restaurants?" and that conversation—with their company name, email, and intent—sits in your CRM waiting for a reply. The trade-off: you're building a sales tool, not a support operation. If you need routing logic for 15 different support queues or multi-language support, a native widget is lean. If you need sales intent + qualification automation, it's overkill-proof. Chatwoot: open-source and flexible, but with real costs Chatwoot is genuinely free and open-source. You can self-host or use their cloud offering. It's a viable alternative if you want to own the widget and avoid vendor lock-in. What you get: Full source code; run it on your own server or Chatwoot's cloud. No per-conversation fees. CRM integrations via webhook (can push chats to your CRM , Pipedrive, Salesforce, etc.). Basic AI routing (via third-party APIs like OpenAI, which you pay for separately). What it costs (hidden or otherwise): Setup time: If self-hosting, you're managing infrastructure, SSL, backups, and updates. Budget 8–16 hours of developer time. Cloud hosting: Chatwoot's cloud starts at free (with limits) up to ~$50/month for a team. That's cheaper than Intercom, but doesn't include AI or advanced routing. Integration maintenance: Sending chats to your CRM via webhook works, but if your CRM API changes or rate-limits you, your team has to debug it. Intercom and Zendesk handle that as part of their service. No native AI: Adding AI replies requires OpenAI API keys and custom prompt tuning. A few mistakes and your token bill spikes. Chatwoot makes sense if you have engineering capacity and want flexibility. For a five-person sales team, the setup friction often outweighs the savings. Integration depth and visitor-to-lead flow This is where the tools separate: Intercom: Has native integrations with HubSpot, Pipedrive, Salesforce, and most major CRMs. A chat from your website automatically creates a contact in your connected system. The integration is solid, but Intercom owns the data first—your CRM gets a mirror. If Intercom goes down, your inbox empties. Zendesk: Similar integration ecosystem, but geared toward support workflows. If you're using Zendesk CRM (Zendesk Sell), it's native. Otherwise, expect third-party apps and occasional sync delays. Native CRM widget (Orin): The contact is created in your CRM on first message. No sync, no mirror—that's your system of record. Your sales team sees the visitor's message, company name, and behavior in real time within the CRM inbox. Unified messaging means chat lives alongside email and WhatsApp replies. Chatwoot: Integrations exist via Webhook, but they're one-directional and require custom setup. You build the handoff logic yourself. T