Ironclad, reviewed

Ironclad is contract lifecycle management software. It covers a contract from first draft to the obligations that follow signature, in six stages it calls Create, Review, Sign, Store, Analyze and Fulfill.

At its centre is a searchable repository. Ironclad extracts clauses and metadata from each contract, groups related agreements into contract families, and imports legacy contracts in bulk. Around the repository sit the Workflow Designer, a no-code tool for routing, approvals and notifications; AI Playbooks; Ironclad Signature for e-signature; Ironclad Insights for reporting; and Policy-Based Access Control.

It connects to Salesforce, Word, Teams, Slack, Coupa, NetSuite and SAP, and offers a public API and MCP connectors. It is built for legal and legal operations, general counsel, procurement and sales, with IT and finance as approvers.

The useful way to read Ironclad is as a system the business routes its contracts through. Someone designs the workflows, someone maintains the integrations, and every team that touches a contract learns where it goes. That shape decides who it suits.

1. Ironclad Agent. A conversational front door that searches contracts, answers questions across the portfolio and calls the other agents. Announced on 8 October 2026, with no availability date or price given.
2. Contract Review Agent. Formerly called Ironclad Jurist. Redlines against playbook positions and fallbacks, uses precedent, and works through a Word add-in. Runs on models from Google, OpenAI and Anthropic, and is sold within Ironclad CLM.
3. Intake Agent. For the contract requests that come in from the business.
4. Renewal Agent. Writes a brief on an upcoming renewal, with key terms, auto-renewal windows and savings.
5. Archive, Analytics and Contract Family agents. For legacy contracts, reporting across the repository, and related agreements.
6. Workflow Designer Agent and Contract Knowledge Graph. Also announced on 8 October 2026: an agent for the Workflow Designer, and a graph that links clauses, obligations and past decisions.

Ironclad sells by custom quote, for the CLM, the AI assistant, e-signature or a mix. The number of users is one of the factors. Its pricing page lists paid add-ons: API and integrations, extra instances and enhanced customer success. Some integrations are included; others cost extra. No per-seat rate or minimum is stated.

The figures that rank for Ironclad's pricing come from purchase data and from competitors' blogs. Vendr puts the median at about $40,110 a year, in a range of about $15,000 to $107,025. It estimates that AI and analytics add-ons add 15–40%, and that implementation is a separate one-time fee: about $10,000–$40,000 for a standard rollout, and $75,000 or more for a complex one. Bind, another CLM vendor, reports a similar median and says rates rise at renewal. All of these are estimates.

Claren publishes its plans. Free is $0 for one member. Pro is $70 per seat per month for one to three members, with $50 of usage included per seat. Team is $250 per seat per month for three or more, with $200 of usage per seat, pooled across the team, and shared team envoys. Enterprise is priced to the team, with zero data retention and single sign-on. Setup is the envoys' work: load the contracts, describe the views, and they build the rest.

The legal AI pricing guide sets Claren's plans beside the legal AI platforms.

Ironclad gives its own ranges. One repository or one workflow: days to a few weeks. Several workflows and integrations: weeks to months. An enterprise rollout: several months. It cites its 2026 Contracting Benchmark Report: about six months to meaningful value, and 178 days on average to launch the first ten workflows. It says 88% of its customers need no extra professional services, and it has offered a Self-Start option, with no implementation cost, for lean teams.

The time goes where it goes in every CLM project: legacy contracts found, cleaned and imported; each workflow designed and approved; each integration built and tested. Someone on the team owns all of it, alongside the day job.

For an in-house team of a few lawyers, that is the real cost. Six months of setup is six months of NDAs, supplier contracts and renewals still handled by hand.

Reviewers on G2 praise Ironclad's ease of use, its Salesforce and Outlook integration, and its support. The recurring complaints are repository search, a steep learning curve, integration issues, and initial setup when a team brings a large volume of agreements.

Obligations draw a similar point. Ironclad tracks them as properties on a contract (type, trigger, status, due date and assignee), and users in its own community describe needing other tools to tie owners and dates to obligations that were negotiated.

What the reviews rarely ask is who keeps the system running. A CLM is only as good as the records in it and the workflows around it, and in Ironclad both are built and maintained by people. For a large legal operations team, that is the job. For an in-house team with more requests than lawyers, it is one more job.

Ironclad suits a business that runs its sales contracting through Salesforce, has procurement and finance in the approval chain, and has a legal operations function to design workflows and maintain integrations. It is good for teams that want one system of record for every agreement, and have the months to build it.

It is not suited to a small in-house team. The work there arrives one request at a time: an NDA from sales, a supplier's paper, a renewal nobody flagged. The team needs each request picked up, reviewed against its positions, sent back and filed, and the records kept current without anyone maintaining them.

1. Juro. An AI-native CLM for growing B2B companies and scale-up in-house teams, with AI Review that redlines against playbooks. Priced by contract volume, with unlimited users, workflows and templates on every plan; Salesforce, HubSpot and Workday integrations cost extra. Juro says implementation takes 18 days on average.
2. SpotDraft. A CLM for in-house legal teams at growth and mid-market companies, with VerifAI, a Word add-in for playbook review. Priced by users or contract volume. SpotDraft says it goes live in weeks, with implementation and migration included.
3. Docusign CLM. One product in Docusign's Intelligent Agreement Management, alongside eSignature, with its AI engine Iris. Built for enterprises. CLM pricing is not published.
4. Claren. The CLM that builds and keeps itself. AI employees take contract requests from Slack, review against the team's playbook, redline in Word, and file every contract and its terms in the team's records. Published per-seat plans. See CLM software.

Every CLM, Ironclad included, starts from the same idea: build a system, then route the work through it. Claren starts from the work. It gives the team envoys: AI employees, each with its own computer and its own memory, that take a request, do the work and hand it back finished. The CLM is what they leave behind.

Envoys take contract requests from the Claren app or straight from Slack, where the business already asks. They review each contract against the team's playbook and hand back redlines in Word with tracked changes, a comment on every change, fallback positions applied and a summary of what's off-playbook. Then they file the contract and its terms in the team's datastore. Nobody fills in a form.

On top of the datastore, envoys build apps: a contract tracker, an obligations tracker, a review screen, with the views the team asks for and nothing it doesn't. Ask for a new view, and the envoy changes the app. Datastores are read-only for people by design, so the records stay consistent.

Routines watch what's coming. An envoy pulls renewal and notice dates, payment and reporting duties, termination windows and who owns each one into a tracker, and a routine checks it on schedule and tells the team, in the app or in Slack. Envoys pass work to each other, and ask before anything leaves the team.

There is no migration project and no new system to learn. Claren can replace a CLM, or sit beside one as the tracker the team actually uses.

1. Who will run it? Ironclad needs someone to design workflows, maintain integrations and keep the records clean. With Claren, the envoys do it as they work.
2. How soon do you need it working? Ironclad puts meaningful value at about six months. Claren starts with the next contract that lands in Slack.
3. Do you need a system, or the work done? A CLM routes the work to a lawyer. Claren's envoys review the contract, redline it in Word and hand it back for sign-off.
4. Do you know what it will cost? Ironclad sells by quote, with implementation estimated separately. Claren's plans are published, per seat, with usage included.

Most in-house teams start with what they already have: a shared drive of signed contracts and a channel where the business sends new ones. Point an envoy at both. It files each contract and its terms, builds the tracker, and a routine starts watching renewals.