Leah (formerly ContractPodAi)

What it is

Leah is the enterprise contract lifecycle management platform that sold as ContractPodAi until 5 January 2026, when the company renamed itself after its own AI agent and repositioned from a CLM vendor to an agentic platform spanning legal, procurement and finance. contractpodai.com now 301-redirects to leahai.com. Same company, same product, under a name that no longer contains the word “contract” — which matters if you are working from a 2025 shortlist and cannot find the vendor.

The line as sold today is six named products: Leah Agentic OS (the layer where agents are designed, deployed and governed), Leah Maestro (the orchestrator), Leah Agentic CLM, Leah Legal, Leah Procurement and Leah Finance. CLM is now one module of six rather than the whole company. For a buyer that cuts both ways — the contracting depth built over a decade is intact, and the roadmap attention is now shared with three adjacent functions.

The Microsoft alignment that always defined this platform got deeper. On 26 June 2025 the company moved its AI stack onto Microsoft Azure OpenAI in Foundry Models and began distributing through the Azure Marketplace, where Leah Legal is listed as a transactable offer. The platform Leah most resembles is Icertis — enterprise scale, quote-gated, partner-led rollout. What separates them is which stack you already run.

Why it shows up in Legal Ops stacks

• Microsoft-first down to the model layer. Azure backbone, Azure OpenAI Foundry models, Azure Marketplace procurement, and contract work that moves through Word, Teams and SharePoint rather than beside them. For a legal department already standardized on M365, that removes an integration project other CLM vendors hand you as a services line. It is the specific reason Leah wins head-to-heads against Ironclad, and it counts for nothing if you are a Google Workspace shop.
• One tenant for legal, procurement and finance paper. Intake, drafting, negotiation, signature, repository and obligation tracking sit in a single environment, and after the rebrand the procurement and finance modules run against the same contract data. Fewer handoffs for a legal ops team of two to babysit.
• The agents are the product, not a feature on top of it. Leah Agentic CLM is sold on multi-step execution — risk identification, drafting, extraction, redline markup — rather than a chat window over the repository. Reviewers name the generative review capability as the thing that cut lawyer review time.
• The reference base is real. G2 rates it 4.6/5 across 48 reviews and Gartner Peer Insights 4.7/5 across 170 ratings, as reported in July 2026. What reviewers name most is the support relationship, not the software.

Pricing

Leah publishes nothing. As of 30 August 2026 the old contractpodai.com/pricing URL 301s to leahai.com/pricing, which returns a 404 — there is no pricing page on the site at all, only a “Request a Demo” path. Every deal is quoted against seat count, contract volume and module mix.

Public procurement data exists but is thin enough that you should treat it as a directional signal rather than a budget. Vendr’s ContractPod listing reports an average contract value of $124,000 with a proposed price as high as $372,000, drawn from only 3 recorded purchases. Three data points is not a distribution. For scale, Vendr’s Ironclad dataset carries a median of $40,000 across 363 purchases and SpotDraft a median of $25,278 — Leah sells well above the mid-market CLM field.

Third-party trackers put license at an estimated $50,000–$200,000 per year with $25,000–$100,000+ in implementation, and per-seat estimates running $70–$100/user/month at 5–15 seats down to $40–$70/user/month above 40 seats. Every one of those figures is an estimate, and a separate August 2026 analysis of the same vendor concluded that nobody outside the company can state the real number. That is the more honest position. Plan on six figures all-in for year one and negotiate against a live Icertis or Ironclad quote, which is the only pressure a quote-gated vendor responds to.

On tier names: the vendor publishes none. Third-party sources variously report Starter/Growth, Professional and Enterprise editions, and the version of this page they replace named Essentials/Professional/Enterprise. None of that is vendor-confirmed, so treat any edition name you have not seen on a quote as unverified.

Best for

Enterprise legal departments of 1,000+ employees running on Microsoft 365, with paper spread across legal, procurement and finance. That is the shape where the module bundle and the Azure alignment both pay, and where a five-month rollout is an acceptable cost. The second strong fit is a legal ops function that owns contract policy across business units and wants obligation tracking and playbook enforcement in the same tenant as the executed paper.

Do not buy Leah if legal is a team of one to five, or if your contract volume is under a few thousand a year. The economics assume an enterprise deal, and a small team will pay six figures for capacity it cannot staff against — LinkSquares or Juro do the same job at a fraction of the number. The same holds if you are not on Microsoft: strip out the M365 story and the remaining case against Ironclad or Icertis gets thin.

Versus the alternatives

• Icertis — the head-to-head Leah loses most often on governance depth, regional partner bench and repository scale. Pick Icertis when the archive runs to millions of agreements and SAP or Oracle compliance drives the requirement. Pick Leah when M365 is the system of record and the buying center spans legal plus procurement.
• Ironclad — the better in-house legal workflow tool and the US tech default, at roughly a third of the contract value on Vendr’s data. Pick Ironclad when the bottleneck is legal review throughput and the company is not a Microsoft shop. Full head-to-head: ironclad-vs-contractpodai.
• Agiloft — pick it when the requirement is configurability without code and the contract process is unusual enough that a packaged workflow will not fit.
• Sirion — pick it when the money leaks after signature. Obligation tracking and invoice reconciliation against agreed terms is Sirion’s core; Leah treats post-signature as one module among several.
• Luminance — the fastest-growing AI-native entrant in contract analysis. Cheaper and narrower, and the right call when the job is review and negotiation rather than lifecycle management.
• Down-market, Juro and LinkSquares cover the same ground for a small legal team — see juro-vs-contractpodai and linksquares-vs-contractpodai. The full field is in best-clm-platforms.

Watch-outs

• Implementation runs five months on average, and reviewers describe the process as the weakest part of the product. Gartner data puts average deployment at five months; G2 reviewers name a steep learning curve and a rollout that needs dedicated legal ops attention throughout. Guard: get the go-live date, the named implementation lead and the services fee written into the SOW with a milestone schedule, and staff a half-FTE legal ops owner for the whole window rather than assuming the vendor’s team absorbs it.
• Extraction covers a bounded attribute set, not your clause library. Reviewers report the AI extracting a limited number of attributes and struggling with clause nuance a lawyer would catch; a March 2026 review rated it 2.5/5 on exactly that. Guard: pilot on 200–500 of your own executed contracts across your three highest-volume paper types, score extraction against a human baseline per clause type, and write the accepted accuracy threshold into the contract before signing.
• The connector list is not publicly auditable. leahai.com/integrations claims pre-built connectors plus open APIs but exposes only an alphabetical slice — Adobe Acrobat Sign, Amazon S3, Azure DevOps, ADP Workforce Now, BigQuery and seven others — behind a “See More” gate. Guard: hand the account team your actual system list (CRM, e-signature, ERP, DMS) and make them mark each one pre-built, API-buildable or unsupported in writing before the quote is signed.
• No MCP server. Leah’s agents run inside Leah’s own surfaces. Querying your contract repository from Claude or ChatGPT alongside the rest of your stack is not a path that exists today, and the vendor has announced nothing. Guard: scope the REST API work explicitly during evaluation rather than assuming an assistant-side connector arrives; the alternatives in best-mcp-tools-for-legal-ops are the current answer.
• Rebrand debris outlives the rebrand. Analyst notes, review sites, procurement records and your own vendor master still carry “ContractPodAi”, and the pricing URL your team bookmarked now 404s. Guard: update the vendor record and the renewal calendar entry to “Leah (formerly ContractPodAi)” now, and confirm at renewal that the legal entity on the paper matches the one you contracted with in 2025.
• CLM is one of six modules competing for roadmap attention. The Agentic OS reposition is nine months old and the procurement and finance lines are newer than the contracting one. Guard: ask for the CLM-specific release notes from the last three quarters, not the platform roadmap deck, and check whether contracting shipped features or absorbed platform work.