Ironclad suits teams where contract intake starts in Salesforce, legal-ops (not IT) owns the workflow build, and the team wants a governed contract pipeline in weeks rather than months. It is built for in-house teams with meaningful contract volume, branching approval workflows, and a legal-ops function to own the platform.
Deployments go best when the buyer confirms up front that legal-ops has the Salesforce admin time to own the integration.
Is Ironclad a fit? It is built for a Salesforce-centric mid-market or enterprise in-house team running 500+ contracts a year. Reviewers rate it 4.5/5 on G2 and 4.4/5 on Capterra (June 2026), and it sits among the leaders on Gartner Peer Insights. Fit and budget are the questions to answer.
Picture a GC at a Series D software company with three direct reports and sales closing forty deals a quarter. Every custom NDA and order form sits in someone's email, Salesforce is already the source of truth, and finance wants a renewal obligation tracker. Four tests separate right-shape from wrong-shape: workflow shape, volume and complexity, integration surface, and segment fit. Ironclad is built around workflow and integration depth for teams with that profile.
TL;DR
- Ironclad is a CLM platform based in San Francisco, founded in 2014 by Jason Boehmig (ex-Fenwick & West) and Cai GoGwilt (ex-Palantir). Its customer book includes L'Oreal, Salesforce, OpenAI, Mastercard, Cisco, and Shell. Reviewers rate it 4.5/5 on G2 and 4.4/5 on Capterra, and it ranks among the leaders on Gartner Peer Insights (all June 2026).
- Funding: roughly $333M raised cumulatively, with the January 2022 Series E adding $150M at a $3.2B valuation (Franklin Templeton's venture arm leading, with Accel, Sequoia, and Bain Capital Ventures participating).
- What it is built for: the Workflow Designer is a no-code contract builder, the Salesforce integration is a core strength, and Jurist (launched November 2024) runs AI clause work inside an editable .docx workspace.
- What it is not built for: Ironclad is a contract operating system, so primary-law research, outside-counsel coordination, and self-serve API access sit outside the product.
- Pricing is quote-based and set per customer. Ask for the AI tier, implementation, and renewal terms as separate lines.
Per this review, which kind of team is Ironclad built for?
For more on legal AI vendor comparisons, see /topics/vendor-comparisons.
At a glance
| Ironclad | |
|---|---|
| Price | Quote-based, set per customer |
| Access | Sales-negotiated contract with a guided implementation |
| User ratings | 4.5/5 G2, 4.4/5 Capterra, leader on Gartner Peer Insights (June 2026) |
| Best for | Mid-market and enterprise in-house contract teams on Salesforce |
| Free trial | No self-serve trial; access arranged through a rep |
| Word-native drafting | Editable .docx Editor; Jurist AI runs on that surface |
| AI tier | Jurist, quoted as its own line |
| Trains on your data | No retention or training by the underlying model providers, per Ironclad (SOC 2 Type II, GDPR, HIPAA) |
| Public API | Enterprise accounts, no self-serve tier |
Read that table as a description of one product rather than a scorecard. Ironclad is a full CLM: post-signature obligation tracking, renewal automation, and a Salesforce-driven approval pipeline. Lighter contract workbenches are built for different jobs, so the comparison only makes sense once you know whether you need a governed contract pipeline at all.
What Ironclad actually is

Boehmig and GoGwilt founded Ironclad in 2014; Boehmig had quit Fenwick & West the same day GoGwilt walked out of Palantir. The product carried the original "self-serve CLM" thesis: contracts as data, workflows as configurable graphs, in-house counsel (not a vendor consultant) assembling the pipes.
The bet is still visible in the product. A lawyer who can describe a contract intake on a whiteboard can build it in the software.
Capital backed the thesis: Y Combinator in 2015, then Accel, Sequoia, and Bain Capital Ventures across Series A through D, and a January 2022 Series E adding $150M at a $3.2B valuation. Roughly $333M raised cumulatively.
What each product surface does on the third Tuesday of the month
Five surfaces carry the weight, and the right way to evaluate them is to ask what each one would do for the third Tuesday of a real in-house lawyer's month, not what the demo shows.
Workflow Designer. Drag-and-drop, no-code builder for contract intake, approval, and execution. The lawyer maps "sales rep submits a custom NDA" through "deal desk reviews," "legal approves anything with mutual indemnification," "DocuSign sends for signature," "Salesforce updates the opportunity."
Each node is configurable, from a five-step NDA flow to a twenty-something-step diligence intake.
Editor. Collaborative drafting in an editable .docx workspace: track changes, comments, versioning, redline reconciliation. Close enough to Word that lawyers can use it without retraining. The Editor is what Jurist runs on; the AI works on the same surface the lawyer is editing.
Jurist (the AI assistant, launched November 14, 2024). Conversational AI for drafting, editing, reviewing, summarizing, translating, and answering contracting questions. Built on Ironclad's open-source Rivet platform.
Agent actions and reasoning are surfaced inline with citations, and Jurist iterates on company precedent inside the .docx environment. It is sold with CLM, not as a standalone seat. SOC 2 Type II, GDPR, HIPAA compliant; no retention or training on customer data by the underlying model providers.
Repository. Post-execution storage, metadata extraction, search, renewals, obligation management.
Integrations. Salesforce has been the depth integration since 2018: bidirectional, opportunity-aware. Slack, a Word add-in, Google Drive, Workday for vendor and employee flows, DocuSign and Adobe Sign.
A live trial surfaces things the demo does not. Try a real intake flow, run Jurist on your own contract types, and open a Word file with heavy tracked changes in the Editor. When you scope the SOW, ask explicitly which workflows are in scope before signing, including Salesforce configuration.
Ironclad pricing

Ironclad does not publish pricing. Enterprise pricing is quoted per customer, and seat count, contract volume, and the AI tier all affect the total. Treat any third-party figure as context for a sales conversation, not as a quote.
Three line items to raise with Ironclad: the AI tier (Ironclad positions Jurist as part of CLM rather than a standalone seat, so ask whether AI is bundled or quoted separately), overage terms for contract volume above plan, and renewal terms, covered below.
Multi-year commitments and a competitive evaluation are the usual levers in an enterprise software negotiation. Implementation is scoped per customer and takes longer where Salesforce orchestration is custom.
Ask which workflows ship in implementation, whether Jurist is bundled or quoted separately, and which integrations are scoped versus billable. Our Ironclad pricing breakdown walks the line items in more detail.
Where Ironclad is built to work well
Workflow flexibility. The Designer is a no-code builder often cited by legal-ops practitioners. A multi-step intake with conditional branching, parallel approvals, and Salesforce round-trip can usually be built without consultancy hours.
Salesforce integration depth. Bidirectional and opportunity-aware. If your contract intake starts in Salesforce ("Sales rep closes an opportunity, the MSA needs to be generated and routed"), Ironclad is designed for that path.
Customer proof. Customer list includes L'Oreal, Salesforce, OpenAI, Mastercard, Cisco, Shell. Salesforce itself selected Ironclad for its own CLM in 2024.
Support. Ironclad rates 9.2/10 for customer support on G2 (June 2026).
Jurist inside the document. Jurist runs inside the .docx workspace where lawyers are already editing, with reasoning and citations inline (launch reporting).
Lawyers can read the agent's reasoning trace, see which prior contract the suggestion was anchored to, and approve or reject without leaving the document.
Time to production. Ironclad reports a working contract flow in weeks for a standard deployment.
What Ironclad is not built for
Primary-law research is not the product. Ironclad is a contract operating system, not a research tool. If your bottleneck is "we need the indemnification carve-out standard in Delaware versus California versus New York before drafting," that is a research task, and Ironclad assumes the lawyer brings the legal standard. For an in-house team where much of the week is regulatory research, pair Ironclad with a research workbench.
Outside-counsel coordination. Ironclad is designed around in-house teams owning the intake, drafting, and execution loop. Outside-counsel workflows (matter assignment, billing rate negotiation, work-product return, conflict checks) are handled in other tools such as e-billing or matter management.
API access. Ironclad has an API, available on enterprise contracts through an account rep. For a developer building a custom tool on top of contract metadata, or a legal-ops team plugging into Zapier, Make, or n8n, confirm API terms early. (See why MCP is the 2026 integration plane.)
Segment. Ironclad's pricing and implementation model are designed for mid-market and enterprise in-house teams. Solos and small firms looking for contract automation will usually look at lighter tools.
AI model stack. Ironclad builds Jurist on its Rivet abstraction layer. As with any AI vendor, ask in the demo which models are used and how multi-model fallback works. (The same question applies to AI-native review tools; see our Spellbook review.)
What users say. Ratings are high (4.5/5 on G2, 4.4/5 on Capterra, June 2026) and the workflow builder draws praise. Reviewers also mention that search findability depends on consistent contract metadata and that the platform benefits from a named admin. Budget for metadata hygiene and a named owner.
What to scope in the SOW
Three areas are worth scoping explicitly in any Ironclad statement of work.
The first is split ownership. Legal-ops owns the workflow build; RevOps or IT owns the integration. Make sure the Salesforce custom object mapping for the order form is in scope, and put the Salesforce admin in the room before signing.
The second is sales-team change management. If reps are used to emailing custom NDAs to legal, the new front door works best when enablement is budgeted explicitly and run before go-live.
The third is contract migration. Loading a backlog of historical PDFs into a searchable Repository is a separate workstream that is usually scoped apart from the standard implementation. (For adjacent vendor stack considerations, see the small-firm legal tech stack.)
Who Ironclad suits
The profile Ironclad is built for: an in-house contract team at a mid-market or enterprise company with Salesforce as the system of record, 500+ contracts a year across NDAs, DPAs, MSAs, and vendor agreements, a real no-code workflow appetite, and a budget for an enterprise platform.
Public-company in-house teams with mid-volume contract review fit that profile. Late-stage startup GCs with a legal-ops counterpart do too.
Where a different tool category fits
Litigation-first firms. Ironclad is not built for matter intake, discovery, or pleadings; a litigation practice management tool is the right shape.
Primary-law researchers. In-house teams dominated by multi-jurisdictional regulatory analysis will want a dedicated research workbench alongside any CLM.
Developer shops needing an API. For programmatic workflows, see the developer-friendly stack.
Solo and small firms. Ironclad is designed for in-house budgets and a legal-ops function.
Deal counsel doing M&A. Ironclad handles recurring commercial contracts at scale. Bespoke transaction documents in M&A diligence are a different kind of work from a repeating NDA pipeline.
Regulated industries facing novel rules. Healthcare, financial services, and defense buyers with many bespoke clause variants will find Jurist works best on contract types the company has signed before. For genuinely novel regulatory clauses, the team still does the analysis.
What to do, by segment
For a Salesforce-centric mid-market or enterprise in-house team with contract volume that justifies workflow automation, Ironclad is built for your situation.
Areas to pair with adjacent tools: primary-law research, outside-counsel coordination, and API access.
Three demo questions before anything else: (1) "Show me a Workflow Designer build of our actual intake flow, end to end, with our Salesforce custom objects, in this session." (2) "Run Jurist on a contract outside the four standard types and show me the reasoning trace." (3) "What is the API access tier, rate limits, and contract for a legal-ops team plugging into Zapier or Make this quarter?"
What to do next:
- Mid-market or enterprise in-house team, Salesforce-centric, contract-heavy. Open the trial, pick the single most painful current intake flow, and build it in Workflow Designer end-to-end.
- In-house team where research is the bottleneck, not contracts. Start with a research workbench; revisit Ironclad when contract volume justifies it.
- Solo or small firm. Look at workbenches priced for small-firm economics (the small-firm stack).
- Developer or legal-ops engineer needing an API. Confirm API access terms before signing.
FAQ
How much does Ironclad cost? Ironclad does not publish pricing. Enterprise pricing is quoted per customer based on contract volume and modules. Ask for the AI (Jurist) tier, overage terms, and implementation as separate lines in the quote.
Are Ironclad's AI features included in the base price? Ironclad markets Jurist as part of the CLM experience rather than a standalone seat. Get it in writing whether your quote bundles the AI tier or lists it separately.
Does Ironclad raise prices at renewal? Renewal terms are set in the contract. Negotiate a renewal escalator cap into the initial contract; it is easier to secure before signing than at renewal.
How long does Ironclad take to implement? Ironclad reports weeks for a standard deployment, longer when Salesforce orchestration is custom. Historical contract migration (loading a backlog of PDFs into a searchable Repository) is a separate workstream.
Is Ironclad worth it? For a Salesforce-centric mid-market or enterprise in-house team with 500+ contracts a year and a real no-code workflow appetite, it is built for your situation. Teams with lighter needs may prefer a lighter tool.
How does Ironclad's Jurist AI work? Jurist runs inside the editable .docx workspace with reasoning and citations surfaced inline (Law.com launch coverage, Nov 14 2024). It works best on standard contract types the company has signed before. Ask about the underlying model stack and multi-model fallback in the demo.
Ironclad vs Icertis: which should I buy? The two are built for different shapes of deployment. Ironclad is built for teams where legal-ops owns the workflow build and intake starts in Salesforce. Icertis is built for enterprise-scale governance across large, complex contract estates. Match the tool to your intake, ownership, and scale.
Does Ironclad have a free trial? Not a self-serve one. Ironclad's own pricing page routes everyone to "Get a Custom Quote" through a demo, and hands-on access is arranged with a rep. Once you have it, pick your single most painful intake flow and try to build it end-to-end in Workflow Designer.
What do reviewers say about Ironclad? Public reviews praise the workflow builder and the Salesforce integration. Reviewers mention that search works best with consistent contract metadata and that the platform benefits from a named admin. Teams with a resourced legal-ops function are the natural fit.
Ironclad vs DocuSign CLM: which is better? They are built for different starting points. Ironclad is built around workflow flexibility and Salesforce depth, so legal-ops can build and change intake flows without consultants. DocuSign CLM fits teams already standardized on DocuSign for signature and document generation who want CLM in the same stack. Our full CLM comparison walks the tradeoffs.
Does Ironclad fit solos, small firms, or in-house teams? Ironclad is designed for in-house and enterprise teams with a legal-ops function to run it. Smaller teams usually look at the lighter contract-workbench tier.
Does Ironclad replace legal research? No. Primary-law research is not the product; Jurist assumes the lawyer brings the legal standard. Teams where a meaningful share of the week is regulatory research should pair Ironclad with a dedicated research workbench.
For more on legal AI vendor comparisons, see /topics/vendor-comparisons.
New legal AI guides, weekly.
Further Reading
- Luminance Review 2026: What It Is Built For and Who It Fits
- Ironclad Pricing 2026: How the Quote Works and the AI Add-On
- Legora Review: Who It's For, How It's Sold, and How It Fits In-House Teams
- CoCounsel Review 2026: What It Is Built For and Who It Fits
- Westlaw Precision AI Review 2026: What It Is Built For and Who It Fits
- Lexis+ AI Review 2026: What It Is Built For and Who It Fits

Co-Founder & CEO · Attorney
Arshita leads product and strategy at Vaquill AI, the US primary law data API. As an attorney, she decides which law we carry, how each section is sourced and cited, and what legal AI and compliance teams need from the data.
