You're comparing Slack, Microsoft Teams, and Lark for your Southeast Asian team. The headline pricing looks simple: Slack and Teams both sit at $8–15 per user per month, and Lark undercuts them by 30–40% in some markets. But headline price is not true cost. Integration gaps, regional payment friction, and vendor lock-in create hidden expenses that often dwarf the licence fee. We'll walk through the real numbers and show you where consolidated platforms beat best-of-breed chat tools. Headline pricing misses the integration tax Slack Pro costs $8.50 USD per user per month (or roughly RM35–40 in Malaysia, IDR125k–140k in Indonesia). Teams Essentials matches that. Lark (ByteDance's messaging platform, popular in China and Southeast Asia) enters at 50–60% of that price in regional currencies—often RM15–20 or IDR60k–70k. But here's where it breaks down: you rarely run chat in isolation. Your team also needs: CRM or sales tool to track customer context (Pipedrive, HubSpot, or Orin) Project or task management (Monday, Asana, Trello) File storage or document management (Google Drive, Box, Dropbox) Calendar and scheduling (Google Calendar, Calendly) Invoicing and contracts (FreshBooks, Zoho, or Orin) Slack and Teams both integrate reasonably well with these Western SaaS tools. Lark's integrations exist, but they lag: Zapier covers it, but native connectors to Pipedrive, HubSpot, or Orin are incomplete. Your ops team ends up copy-pasting or paying for Zapier tasks. At scale—say 50 people—that friction costs you 10–20 hours per month in manual work. One integration gap doesn't sound like much until your team is replicating deal updates by hand. Then it costs you focus, accuracy, and the ability to scale without hiring ops overhead. Microsoft Teams has a bundling advantage (if you're already on Microsoft) If your team uses Microsoft 365 (Outlook, OneDrive, Excel), Teams comes free with Microsoft 365 Business Standard (roughly USD 12.50/user/mo in SEA). You're not paying extra for chat—it's bundled. The integration to Exchange, SharePoint, and OneDrive is native and frictionless. Your files live in the same ecosystem; your calendar works without syncing; Outlook mail threads into Teams context. For a 30-person team in Kuala Lumpur or Jakarta already committed to Microsoft 365, Teams costs RM1,500–2,000 per month total. Switching to standalone Slack and keeping Microsoft means doubling your chat spend. The catch: Teams' AI features (Copilot) and some premium integrations cost extra. And if you're in a sector with tight budget control (e.g., professional services in Singapore or Malaysia), your finance team may already have standardized on Microsoft, making Teams a non-negotiable choice regardless of preference. Lark's regional price advantage evaporates under integration load Lark is genuinely cheaper on headline price. A 50-person team in Indonesia saves RM5,000–8,000 per year versus Slack, or USD 1,400–1,800. That matters to many SMBs. But Lark's ecosystem is narrower. If your CRM is Orin, Pipedrive, or HubSpot, you'll spend time and money bridging Lark to the rest of your stack. Native Slack and Teams integrations exist for these tools; Lark's do not. You're looking at: Zapier (5–15 tasks per month at USD 19–99/mo) to push deal updates or customer mentions into Lark Manual review workflows where automation would do Slower time-to-value on customer conversations (your team misses context because it's not flowing from your CRM) For a startup or small team relying on chat to stay aligned on customers, that friction compounds. One Zapier task that runs daily costs USD 20 over a month, but the human time to manage fallback workflows can run 5–10 hours per month. At a fully-loaded rate of USD 30–50 per hour, you've erased Lark's price advantage. Lock-in and switching cost reshape long-term TCO Switching away from Slack, Teams, or Lark is not free. You lose: Message history: Most platforms let you export, but you must pay to retain and search old conversations. A year of Slack history for a 20-person team is laborious to migrate. Custom integrations: Any no-code automations you built (Workflow Builder in Slack, Power Automate in Teams) must be rewritten. Tribal knowledge: Your team will resist a platform switch if workflows are embedded and familiar. In regions where Lark is dominant (parts of China, Vietnam, or Thailand with tech-heavy teams), switching away is harder because vendors and partners often assume Lark is your baseline. In Malaysia and Singapore, Slack and Teams dominate, so your future vendor integrations and new hires already expect one of those two. This means your true switching cost favours the incumbent in your region. If you start with Lark and later want to shift to Slack for better CRM integrations, you're paying Slack's setup, retraining, and integration rebuild. Factor that into year-three and year-five math, not just year one. When chat belongs inside your CRM instead Here's the insight that most team