ContractPodAi (rebranded to Leah) is an enterprise AI-native contract lifecycle management platform serving corporate legal departments and large law firms. Core capabilities: AI contract drafting and review (Leah Legal Copilot / Leah AgenticOS), clause library and playbook enforcement, obligation management, contract analytics, self-service contract templates, and integrations with Salesforce/SAP/Microsoft. Founded 2012 (UK), $179-202M total funding (SoftBank Vision Fund 2 led Series C at $695M valuation, Sep 2021; additional $50M extension Q2 2025), ~$47.1M revenue (GetLatka), 144 employees, 29,714 LinkedIn followers. Gartner Peer Insights 4.7/5 (170 reviews), G2 4.6/5 (47+ reviews). Enterprise pricing (~$50K-$150K/year custom, 2-4 month implementation). Named customers include EY, Bosch Siemens, Total Petroleum, Pennon Group. Partners with Epiq and Morae for implementations. Competes with Ironclad, Agiloft, Icertis, LinkSquares, Docusign CLM. Reddit sentiment mixed: ‘decided on ContractPodAi’ (positive), ‘UI seemed clunky’ (negative), ‘many issues with updates affecting templates’ (negative).
Company Info
- Founded: 2012
- Funding: $170M
- HQ: United Kingdom
- Sector: LEGAL_SERVICES
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Contract Pod AI is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Contract Pod AI addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
Sales sends contract requests via Slack, email, and hallway conversations — legal has no queue, no triage, and no idea how many requests are pending
Contract redlining is a nightmare — 7 rounds of Track Changes in Word, counterparty turns off tracking, and nobody knows what changed between v5 and v7
NDAs and routine contracts take 3-7 days because every single one routes through legal — no self-service for standard terms
Signed contracts vanish into email threads and shared drives — when a dispute arises, nobody can find the executed version
Contract auto-renewed at 15% higher because nobody tracked the 60-day opt-out window buried on page 37
Enterprise CLM implementation is itself a nightmare — 6-18 month projects, $150K+ budgets, dedicated admin required, and the tool that was supposed to reduce complexity just added another layer of it
Legal ops team selects a CLM but the UI is so complex that adoption craters — non-technical business users in sales and procurement refuse to use the self-service portal, and legal ends up doing everything manually anyway
Where it fits in your workflow
Before Contract Pod AI
Business unit submits contract request (via Salesforce/SAP integration) → Leah routes to legal or auto-approves standard contracts via self-service templates
After Contract Pod AI
AI drafts/reviews contract using playbook rules → clause library enforcement → negotiation tracked → approval workflow → e-signature → executed contract in repository → obligation management → analytics dashboards for CLO
Integrations & hand-offs
Salesforce/SAP → Leah (contract request trigger). Leah Legal Copilot/AgenticOS → attorney (AI-powered drafting and review). Leah → e-signature (execution). Leah → obligation management (deadline tracking). Leah → Epiq/Morae (implementation partners).
Community Data
Loading practitioner-sourced data…