Embedded chat widget cost: DIY vs Orin vs Intercom

Q: Does the cost of an embedded chat widget scale with my website traffic?

It depends on the tool. Intercom scales with contacts (anyone who's chatted or appeared in your CRM). Zendesk scales with support agents. Orin doesn't have per-visitor or per-contact limits—pricing is per user. DIY costs scale with server usage, which is directly tied to traffic.

Q: What's the biggest hidden cost of building a chat widget myself?

Maintenance and scaling. Initial build is 80–120 hours. But after month two, you hit browser incompatibility bugs, your database starts locking under traffic, and someone needs to monitor uptime at 2 a.m. That ongoing cost typically exceeds the initial build within six months at moderate traffic.

Q: Can I integrate a bought chat tool with my CRM?

Yes, but it requires API work. Intercom and Zendesk can push chats into most CRMs via webhooks or Zapier, but you'll spend 10–20 hours setting it up. If your CRM is Orin, chat is already integrated—conversations become contacts automatically.

Q: Which tool should I pick for an e-commerce site with 2,000 monthly visitors?

For 2,000 visitors, buy. Zendesk Chat (~$110/month) or Orin ($50–100/month for 1–2 users) are both solid and cost-effective. DIY would cost you $800–1,500/month in dev time and hosting. Buy, get out of the way, and focus on conversion—not infrastructure.

You want live chat on your website. The first instinct is to build it yourself—grab a WebSocket library, spin up a server, and ship it. The cost looks trivial next to the $600–1,200/month Intercom quotes. But at month seven, when your servers are melting under traffic, your support queue is stuck because the chat database locked itself, and your only developer is on parental leave, the math changes. This post walks through the real numbers at 100, 500, and 5,000 monthly site visitors, so you can stop guessing. The DIY trap: what you'll actually spend Building your own embedded chat widget means owning the full stack: the JavaScript widget, the backend API, the database, monitoring, authentication, rate limiting, mobile rendering, browser compatibility testing, and feature work. Let's price it honestly. At 100 visitors/month (a new site) Initial build: 80–120 developer hours (one dev, 2–3 weeks part-time). At $50–100/hour consultant rates, that's $4,000–12,000. In-house, it's your salary cost, same impact on cashflow. Hosting: A modest Node.js or Python server on AWS, DigitalOcean, or Fly.io: $10–30/month. Database (PostgreSQL or MongoDB managed): $15–50/month. You're looking at $25–80/month. Maintenance: Browser updates break things. SSL certificates need rotation. Dependencies need patching. Plan 2–4 hours/month of a developer's time: roughly $200–400/month in cost of payroll or hiring. Total monthly cost (steady state): $225–480/month. Upfront build absorbed over 12–24 months. At 500 visitors/month (growing site) Hosting scales: Your modest server now stutters under traffic. You need auto-scaling, a CDN for the widget JavaScript, and database optimization. AWS costs jump to $80–200/month; database to $50–150/month. Total: $130–350/month in infrastructure. Feature creep arrives: Your support team wants canned responses, conversation history export, and API endpoints to push chats into your CRM. That's another 40–60 hours of dev work: $2,000–6,000. Spread over 12 months, add $170–500/month to the burn. Maintenance doubles: More traffic means more bugs, more edge cases (yes, some users have 6-year-old browsers), and more customer support requests about broken chats. 5–8 hours/month: $300–600/month. Total monthly cost (steady state): $600–1,450/month. Now your 'cheap' DIY solution costs more than Intercom's base tier. At 5,000 visitors/month (serious e-commerce site) Infrastructure is now a job: You need database replication, load balancers, monitoring alerts, and incident response. AWS bill: $400–1,200/month. You're probably paying a DevOps engineer part-time: add $1,500–3,000/month. Scaling the API costs money: Every visitor who opens chat hits your server. Rate limiting, caching, and connection pooling become non-negotiable. This isn't a weekend fix; it's deliberate architecture work: 60–100 hours = $3,000–10,000 upfront, then $500–1,500/month to maintain. Support and monitoring: You need uptime alerts, error tracking (Sentry or New Relic: $500–1,500/month), and on-call rotation because your chat going down means customers can't reach you. Add another engineer part-time or a dedicated ops hire: $2,000–5,000/month. Security and compliance: GDPR (data retention policies), PCI (if handling payments), and bot mitigation. Roughly 20–40 hours/quarter = $1,000–4,000/quarter. Call it $400–1,300/month. Total monthly cost (steady state): $4,800–12,500/month. You've now built a small team around a chat widget. At 5,000 monthly visitors, your DIY chat costs as much as a dedicated team member. By 10,000 visitors, it costs more than two. The bought solution math: Intercom, Zendesk, and Orin Third-party chat platforms bundle the infrastructure, updates, and support into one bill. The pricing model is different, but the cost is transparent—and the hidden costs are fewer. Intercom Intercom charges based on contacts , not visitors. Their lowest tier, the Starter plan at $39–99/month, covers up to 1,000 contacts. But contacts are anyone who has ever chatted, emailed, or appeared in your CRM. At 500 monthly visitors, expect 150–300 new contacts/month; at 5,000 visitors, 1,500–3,000 new contacts/month. You'll outgrow Starter fast. 100 visitors/month: Starter plan, $39–99/month. No extra cost. 500 visitors/month: You hit 2,000–3,000 contacts within a few months. Upgrade to Growth ($99–499/month). Assume $250/month. 5,000 visitors/month: You're at 10,000–15,000 contacts. You need Pro ($499+/month, per contact overage is $0.05–0.10/contact). Budget $1,000–2,500/month depending on your growth rate. Hidden costs: Intercom's widget is good but vanilla. Customization beyond their settings requires their API and your dev time. Custom colors, themes, and workflows: plan 20–40 hours setup. Their mobile SDK also requires integration work if you want in-app chat on an app you own. Zendesk Zendesk's chat product (formerly Zopim) is part of their unified suite. Pricing is agent-based (cost per support person), not visitor-based. Their Chat