Our Take
Embedding CRM into existing workflows is sound product strategy, but the real measure is whether lawyers actually update client records now—the core problem Foundation was built to solve.
Why it matters
Law firms struggle with CRM adoption because data entry interrupts billable work. If Litera's integration into Microsoft 365 genuinely closes that friction gap, it moves CRM from a compliance chore to a byproduct of daily work.
Do this week
CRM managers: audit your current firm adoption rate (logins per user per month) before switching platforms, so you know whether the problem is the tool or the workflow.
Litera launches Foundation 365 across Microsoft 365
Litera announced on June 3rd that Foundation 365, its AI-powered CRM platform for law firms, is now available natively across Microsoft 365, embedding client and relationship intelligence into Outlook, Teams, and Microsoft Copilot. The product combines Litera's 2021 acquisition of Foundation with Peppermint Technology (acquired in February 2025), now rebranded as a single platform built on Microsoft Dynamics 365.
The integration follows Litera's existing partnerships with Microsoft, including a Sharepoint integration in December 2024 and a Copilot integration since 2024. Karan Nigam, head of product marketing for agentic customer experience at Microsoft, framed the collaboration as delivering "critical business data directly in the flow of work, without the friction of switching between applications."
Litera reports that Foundation 365 serves over 4,000 law firms globally, including five of the world's ten largest (company-reported). The platform operates across 99% of Am Law 100 firms and supports 2.3 million daily active users (company-reported).
Deployment evidence
Lewis Davies, CRM manager at Womble Bond Dickinson, stated in the release that the tool enables teams to "track relationships and opportunities in a way that suits them." Frost Brown Todd, a Foundation user, has built a client intelligence tool called Co360 on top of Foundation and the firm's data lake, generating company research reports in minutes and powering a proactive litigation-matching algorithm that alerts clients to newly filed cases and government contract reviews.
The real problem: CRM adoption, not feature count
Law firms universally struggle with CRM adoption because lawyers view data entry as friction, not value. Embedding client context into the tools lawyers already open hourly (Outlook, Teams) removes the switching cost that kills adoption. If Foundation 365 actually captures relationship updates as a side effect of normal work rather than as a separate task, that is a structural improvement over traditional CRM deployment.
The proof will not be in user counts; Litera already reports high reach. The proof will be in update frequency and data freshness. Does Foundation 365 see lawyers creating and updating client records at the point of communication (sending an email, scheduling a meeting), or does it sit idle like most firm CRM systems?
Microsoft's integration plays to this. By surfacing relationship data inside Copilot, Litera gains a plausible mechanism for context-aware suggestions without requiring lawyers to leave their current task. That is credible product design.
For CRM managers and law firm operations
Foundation 365 is a narrower bet than a wholesale CRM replacement. It assumes your firm already runs Microsoft 365 (true for most US law firms) and that embedding data in communication tools solves the adoption problem. That assumption is testable before full deployment.
If your firm has previously implemented a CRM and abandoned it due to low adoption, interrogate whether Foundation 365 solves the underlying behavior problem or simply moves the same problem into a new interface. Co360 (Frost Brown Todd's use case) suggests the platform enables real analytic work, not just data collection.
The product is mature: 4,000 firms using Foundation, five of the ten largest firms as customers. This is not an experiment. The integration into Microsoft 365 is incremental positioning, not a capability breakthrough.