You can use Slack, Asana, and Figma directly inside Claude now - here's how

Anthropic expanded Claude to interact directly inside workplace apps — including Amplitude, Asana, Box, Canva, Clay, Figma, Hex, monday.com and Slack — enabling the assistant to pull account data, preview in-app deliverables and execute tasks from within a chat; Salesforce integration is planned. Built on the open-sourced Model Context Protocol and available to Pro, Max, Team and Enterprise subscribers (with the Claude Cowork preview now on web/desktop for Team and Enterprise), the feature aims to position Claude as a primary enterprise interface and escalates competition with OpenAI and Perplexity; no revenue or financial metrics were disclosed.

Analysis

Market structure: Direct winners are integrated SaaS vendors (ASAN, FIG, BOX, MNDY, AMPL, and eventually CRM) as integrations increase stickiness, enabling 2–5% incremental ARR uplift per major connector within 6–12 months and higher gross margins from low incremental cost upsells. Losers include niche point-tool vendors and any vendor that resists integration; pricing power shifts toward platforms that own user workflows and can levy API/enterprise premiums. Supply/demand: demand for hosted LLM compute and API calls will rise materially (expect +10–30% YoY consumption among adopters), tightening cloud capacity and boosting cloud infra vendors. Cross-asset: tighter SaaS cashflows should modestly compress credit spreads in IG tech names; equity options implied vols may rise near earnings; FX/commodities impact negligible.

Risk assessment: Tail risks include regulatory data-protection fines (GDPR/CCPA exposures >$50M for midcaps), antitrust scrutiny if an AI-agent becomes a dominant portal, and operational hallucinations leading to client losses. Immediate (days–weeks): stock moves on partnership news/earnings; short-term (3–9 months): proof-of-concept adoption and ARR inflection; long-term (1–3 years): platform consolidation or vendor lock-in. Hidden dependencies: reliance on Anthropic’s uptime, contract terms (rev-share), and cloud providers; second-order effects include higher support/SaaS R&D spend. Catalysts: Salesforce integration, customer case studies, and quarterly ARR beats (>+3% vs guidance).

Trade implications: Direct plays — consider establishing a 2–3% long position in ASAN and a 1–2% long in FIG to capture early monetization (target 12–24% upside over 6–12 months). Pair trade — long ASAN vs short MNDY (equal notional 1–2%) expecting Asana to monetize integrations faster; trim/exit if spread narrows <5% or either stock moves >15% intraday. Options — Buy 3–6 month call spreads on ASAN (buy 15–25% OTM, sell 35–45% OTM) sized to 0.5–1% portfolio to lever upside while capping premium; use 4–8% stop-loss on outright positions. Rotate 5–10% portfolio weight toward SaaS/cloud infra and reduce exposure to legacy software by 3–5% within 30 days.

Contrarian angles: Consensus overlooks margin leakage from API fees and revenue shares to Anthropic and cloud providers — net benefit to vendors may be <50% of gross integration revenue in year one. Historical parallel: platform-enabled feature aggregation (e.g., early app-store consolidations) led to initial hype followed by price competition and regulatory pushback within 18–36 months. Unintended consequences include increased vendor concentration risk (single-agent failure) and customer pushback on data sharing that could slow renewals; size positions accordingly and set clear stop-loss/catalyst-based exits.

Key Decisions for Investors

• Establish a 2–3% long position in ASAN within the next 1–4 weeks to capture expected 6–12 month ARR uplift from Claude integrations; risk target: 12–24% upside, stop-loss 8%.
• Initiate a 1–2% long position in FIG to play interactive design stickiness; target 15% upside over 6–12 months, sell into any >20% pop or if integration case studies fail to appear within 3 quarters.