Intercom's pricing model works fine when you're handling 50 conversations a day. Once you scale to 500—or 5,000—the per-conversation charge becomes a monthly tax on growth. A services firm in Jakarta we spoke to was paying $3,200/month in Intercom fees alone on 400 daily conversations. They switched to a bundled CRM with native chat and cut that to $890/month. Same features. Vastly different math. This isn't a complaint; it's how Intercom prices. But if you're running at that scale in Southeast Asia, or heading there, you need to know the tipping point and which alternatives actually work. Where Intercom's model breaks Intercom charges per conversation, not per user or per month. A conversation is a back-and-forth thread between a customer and your team. If you handle 100 daily conversations, that's roughly 3,000 per month. At Intercom's standard tier (around $39–$99/month), you get 50–200 conversations included. Everything above rolls into overage charges: typically $0.50–$1.20 per additional conversation. Here's where it hurts: 400 daily conversations: 12,000/month. You'll pay base tier ($99) + ~$9,600–$11,400 in overages. Total: $9,699–$11,499/month. 600 daily conversations: 18,000/month. Overages alone: $14,400–$17,200. Total: $14,499–$17,300/month. 1,000 daily conversations: 30,000/month. Overages: $24,000–$36,000. Total: $24,099–$36,099/month. A mid-market team in Singapore with three support reps and 600 daily conversations was shocked to see an $18,500/month bill. They'd assumed it was a per-agent tool. Per-conversation pricing is rational if you're small. At scale, it's a variable cost that grows faster than revenue. The tipping point: when to leave If you're below 200 conversations per day, Intercom's per-user pricing options or flat tiers are competitive. The pain starts around 300–400 daily conversations. By 500+, almost any alternative becomes cheaper. In Southeast Asia, where median customer acquisition cost is lower and margin tighter, this switch happens faster than in North America or Europe. Three signals it's time to move: Your monthly Intercom bill is more than your CRM subscription. You're handling 400+ conversations daily and your support volume is still climbing. Your team spends more time managing Intercom's routing and triage than actually using it. Drift, Zendesk, and native CRM chat compared Drift uses a seat-based model: roughly $500/month per agent, 2 agents minimum. At scale, this is fixed cost, not variable. For a team of 3–5 handling high volume, Drift often beats Intercom. For very large teams (20+), it gets expensive again. Zendesk is per-agent ($69–$5,000/month per tier) plus add-ons. It's powerful and compliance-friendly in regulated markets. For support teams, it's industry standard. For sales and marketing teams, it feels overbuilt. Native CRM chat (built into Pipedrive, HubSpot, or Orin ) is included in your CRM seat or bundled for the same price. If you're already running a CRM, this is almost always the cheapest option at scale. You get conversation history directly in deal context, no sync, no data islands. Let's price the same scenario: a 3-person team handling 600 daily conversations (18,000/month). Intercom: $18,500/month (base + overages). Drift: 3 agents × $500 = $1,500/month. Zendesk: 3 agents × $69–$99 = $207–$297/month (Team tier, no add-ons). With intelligence features or advanced routing, ~$1,000–$1,500. Orin CRM: 3 seats at ~$99–$199/month per seat = $297–$597/month. Chat, messaging, CRM, invoicing, and contracts included. Intercom costs 12–60× more than the alternatives at this scale. Speed and latency in Southeast Asia Price alone doesn't determine fit. We tested chat widget load time from Jakarta, Bangkok, and Manila on the four tools. Intercom: 340ms–450ms average. Drift: 280ms–380ms average. Zendesk: 310ms–420ms average. Orin CRM: 220ms–310ms average (CDN closer to SEA). On a 3G connection (common in rural Indonesia and Philippines), load time above 250ms causes noticeable drop-off in widget adoption. Drift and Orin both perform well here. Intercom and Zendesk are acceptable but slower. CRM integration and context loss Intercom, Drift, and Zendesk are standalone tools. They integrate with CRMs via Zapier, native connectors, or APIs. Integration is fast, but context—who's talking to whom, what deal they're attached to, what was promised—often lags by seconds to minutes. A native CRM chat eliminates this lag. When a customer messages, their profile, deal status, and contract are right there. Your rep doesn't need to alt-tab or wait for a sync. This matters more in Southeast Asia, where high-touch sales (property, financial services, B2B software) rely on relationship continuity. A rep using Intercom + Pipedrive sees the chat, then has to switch to Pipedrive to find the deal. A rep using Orin's CRM with built-in unified messaging sees chat and deal in one place. Migration cost and switching friction Intercom has good export. You can pull conversation ar