Law firm CRM adoption has historically been a compliance problem masquerading as a technology problem. The real barrier isn’t that attorneys don’t value client relationship data, it’s that entering and accessing it has required leaving the applications where legal work actually happens. Foundation 365 is Litera’s answer to that structural friction.
According to LawNext coverage by Robert Ambrogi, Foundation 365 is now available inside Microsoft 365, specifically within Outlook, Teams, and Microsoft 365 Copilot. That means attorneys can surface client relationship context, matter history, and engagement data without switching application contexts. The platform is built on Microsoft Dynamics 365, which provides the underlying CRM data infrastructure and a more durable integration path than custom-built connectors. Litera acquired the product when it was called Peppermint Client Engagement; the Foundation 365 name reflects the rebranding and broader platform ambitions.
The platform includes an AI agent called Lito. According to Litera’s announcement, Lito is designed to predict connection strengths and surface relationship opportunities within the firm’s network. The specific mechanism behind connection strength prediction, what data inputs, what model, what confidence thresholds, isn’t visible in the available source material. That claim carries qualified language here: the capability description comes from the product announcement filtered through LawNext’s coverage, but the underlying technical detail wasn’t confirmed in the source content available for this pipeline run.
Don’t expect this to solve law firm data quality problems. CRM platforms integrated with Microsoft 365 still depend on attorneys generating relationship data in the first place, logging calls, tracking contacts, noting introductions. The integration reduces the friction of access; it doesn’t solve the incentive problem of data entry. Law firms that have struggled with CRM adoption because attorneys won’t maintain contact records will find that Foundation 365’s Microsoft 365 presence improves data accessibility for existing records but doesn’t automatically populate new ones.
The MCP angle: legal technology analysts have observed growing adoption of Model Context Protocol as a framework for connecting AI models to document management systems and workflow tools. Whether Foundation 365’s Microsoft 365 integration uses MCP architecture specifically is an inference from industry analysis rather than a confirmed technical disclosure from Litera. Legal IT teams evaluating Foundation 365 should ask directly whether the integration is built on MCP or a proprietary connector architecture, the answer affects long-term interoperability with other AI tools in the firm’s ecosystem.
Unanswered Questions
- Is the Microsoft 365 integration built on MCP or a proprietary connector architecture?
- What data inputs and model methodology underlie Lito's connection strength predictions?
- How does Foundation 365 handle data entry incentives, does it include any automated data capture from email or calendar activity?
Foundation 365 occupies a specific position in the legal AI stack: it’s relationship intelligence infrastructure, not document drafting or contract review AI. For law firms building out AI tooling, it addresses a different layer than tools like Harvey or CoCounsel. The Microsoft 365 integration makes it more likely to see day-to-day use, which is the prerequisite for any CRM delivering actual value.
The TJS read: Foundation 365’s Microsoft 365 availability is the right architectural move for enterprise legal software, embedding AI capability into existing workflow context rather than requiring parallel application adoption. Whether the Lito agent’s connection strength predictions are genuinely useful or a feature-checklist addition depends on implementation quality that isn’t visible from the announcement. Legal technology buyers should request a demonstration of the Lito capability with their own data before committing, not based on the announced description.