Redlines that argue your position.
Contracts compares counterparty markup against your playbook, flags deviation, proposes language, and signs in the same workspace. Legal stops repeating themselves. Counsel gets a real exception queue, not a 40-page wall of changes.
Five capabilities legal teams ask for.
Most contract tools handle send and sign. Contracts owns the middle. The redline pass, the approval gates, the playbook adherence, and the post-signature obligations.
Compare counterparty markup against your playbook clause-by-clause. Deviations flagged with risk score, fallback language, and a "why this matters" explainer.
For low-risk deviations the system can propose an accepted change. The rationale is recorded so counsel can re-review the policy later.
Sequential or parallel signing, witness blocks, SMS verification, identity match, full audit. Same workspace, no DocuSign bill.
Once signed, every obligation becomes a task with the right owner and date. SLAs, audit rights, MFN clauses, renewal triggers.
90, 60, and 30 days out, we surface the renewal with the cleanest version of the contract, the usage report from Analytics, and the deal owner's draft talking points.
Three loops, seven stages.
Contracts has a long shape. Drafting, negotiation, approval, signing, activation, obligations, renewal. Each loop is automated, none is locked.
Draft from playbook
The first draft is composed from your playbook clauses, with deal-specific variables filled in from CRM. Risk checks run pre-send (OFAC, jurisdiction, sanctions, blacklists).
Compare against playbook
Counterparty markup arrives, the diff runs in 6 to 12 seconds, every change is mapped to a clause and scored. HIGH-risk lands in counsel's queue with a one-paragraph "why this matters".
Sign and obligate
E-signature with witness, identity, and audit. On execution, obligations flow into Tasks with owners and dates. Every signature is recorded in the audit trail.
Nine more, all built-in.
Each is on by default for every workspace. Most replace a $30 to $200 per-seat per-month tool.
Clause library
Versioned clauses with usage analytics. Know which clauses got renegotiated and how often.
e-signature
21 CFR Part 11 compliant. Audit trail, identity verification, SMS challenge. PAdES-compliant exports.
OFAC, PEP, sanctions
Counterparty screened on every send. Source data refreshes daily. Per-region lists.
Cross-language
Source + translated copies stay synced. Negotiate in EN while the counterparty negotiates in JP, both see the same diff.
Workflow templates
NDA fast-lane (under 30 min), MSA full review, DPA + SCC bundle, vendor onboarding. Customize per pattern.
Counsel exceptions queue
Only HIGH-risk deviations land in counsel's queue. Everything else routes to the deal owner with the fallback.
External party portal
Branded portal for counterparties. They see the diff, they sign, they get an audit-trail PDF. No account required.
Renewal automation
90, 60, 30 day alarms with the cleanest version of the contract, usage data, and proposed terms.
Cross-contract search
"Find every MSA with a 3x liability cap." Returns ranked results with clause-level previews.
Contracts writes back.
A signed contract is not the end of the workflow. It is the start. Five surfaces pick up the obligations and the renewal triggers.
Five surfaces share the contract
A signed MSA updates the CRM deal. Obligations land in Tasks. The fully executed PDF lands in Documents and Search. The legal contact thread closes in Inbox. Usage rolls up to Analytics, which feeds the renewal narrative.
Programmatic contracts.
Spawn a contract from a CRM deal, attach the playbook, and stream the redline events.
// Spawn an MSA from a CRM deal, stream redline events to legal Slack. import { Wrx } from "@wrxstack/sdk"; const wrx = new Wrx({ token: process.env.WRX_TOKEN }); const contract = await wrx.contracts.spawn({ deal: "acmerobotics-eval", template: "MSA_v3", playbook: "standard_b2b_saas", reviewers: ["counsel@acme.com"], send_to: { email: "legal@acmerobotics.com", language: "en" } }); for await (const ev of wrx.contracts.stream(contract.id)) { if (ev.kind === "deviation" && ev.risk === "HIGH") { await wrx.slack.post({ channel: "#legal-review", text: `HIGH deviation in ${contract.title} · ${ev.clause}\n${ev.summary}`, thread: contract.id }); } if (ev.kind === "signed") { console.log("signed by all parties", ev.signers); // obligations flow into Tasks automatically. } }
Contracts vs. Ironclad.
Ironclad is a CLM platform with workflows. wrxstack Contracts is a CLM that lives inside the work graph.
wrxstack Contracts vs. Ironclad
| Capability | Ironclad | wrxstack Contracts |
|---|---|---|
| Playbook redline | AI Assist add-on | Native, with rationale |
| e-signature | DocuSign integration | Native, 21 CFR Part 11 |
| Obligation tracking | Repository only | Auto-task with owner + date |
| CRM linkage | Connector | Same workspace, same record |
| Cross-language | Document-level | Clause-synced |
| External party portal | Yes, branded | Yes, with audit PDF on close |
| Cost | $50k+ per year | Included, free to start |
Common questions.
Six things legal leaders ask in their first hour.
How does the AI know our playbook?
You upload your playbook as a versioned clause library, with risk tier, fallback language, and rationale per clause. The system fits a small per-tenant model on top to learn how your counsel writes. Drafts and redline suggestions reference the clause id and the fallback explicitly.
Is the e-signature legally enforceable in our jurisdiction?
Yes for ESIGN (US), UETA, eIDAS (EU), Electronic Communications Act (UK), and the major APAC jurisdictions. We support PAdES, CAdES, and XAdES output. For 21 CFR Part 11 workflows, the identity verification and audit settings are pre-configured.
Can we keep our existing DocuSign or PandaDoc?
Yes. Contracts can drive the redline and approvals while handing off to your existing signature vendor. You can consolidate to the native signature whenever you are ready, because the audit trail is unified with the rest of the work graph.
How are obligations actually tracked after signing?
Each obligation extracted from the contract becomes a Task with the right owner, deadline, and recurring schedule. SLAs are scored against actual performance. Renewal triggers fire 90, 60, and 30 days before the auto-renew date with usage data from Analytics attached.
What about negotiating with a counterparty who uses Word redlines?
That is the common case. We accept their Word file, run the diff against our last-known good version, and present the result in our redline pane. When we send back, we can ship either a native diff or a Word file with tracked changes accepted to a baseline of their choice.
Can we white-label the external party portal?
Yes. Domain, logo, color, language, and email templates. The portal supports SMS verification and IP-restricted access if you need it.
Pairs well with.
Contracts shines once CRM, Documents, and Tasks are live in the same workspace.
Who this is not for.
Contracts drafts, redlines, and routes agreements on the same record as the deal. If you need notarization, qualified electronic signatures under eIDAS, or a court-admissible signing certificate for a specific jurisdiction, use a specialist e-signature vendor. Contracts handles the negotiation and the workflow, not regulated signing formalities.
Cut your MSA cycle from 22 days to 4.
Free to start, no credit card. Upload your playbook. The first counterparty redline lands in counsel's queue, scored, the same day.