Contracts from draft to renewal.
Contracts and eSign keeps every agreement on one record. Draft from your clause library, compare versions in a redline view, route internal and external approvals, and send for signature with sequential or parallel signers. Obligations and renewals stay tracked after signing. Contracts and eSign is on paid plans.
Five capabilities legal teams ask for.
Most contract tools handle send and sign. Contracts also covers the middle and the end: versions, redlines, approval gates, and the obligations and renewals after signature.
MSA, SOW, NDA, DPA, and custom contract types, drafted from a reusable clause library with version history on every clause.
Upload each new version and compare it in a redline view. Request changes, approve, or decline, internally and with the counterparty.
Sequential or parallel signers, reminders, decline handling, and void. Each agreement gets a signer audit trail and a completion certificate.
Record payment, deliverable, renewal, and termination-notice obligations with an owner and a due date, so nothing slips after signature.
Propose, send, and accept or reject renewals on the contract record. Expiry alerts and renewal reminders give the owner time to act before the notice window closes.
Three loops, seven stages.
Contracts has a long shape: drafting, negotiation, approval, signing, activation, obligations, renewal. Each step is a state on the same record, with an audit entry at every change.
Draft from your clauses
Start from a contract type or template, add clauses from your library, and set parties, value, dates, governing law, and renewal terms. Then submit it for internal review.
Compare versions
When the counterparty sends markup, upload it as a new version and open the redline view against the last one. Approvers approve or request changes, and each decision is recorded.
Sign and track
Send for signature with sequential or parallel signers and reminders. Once signed, the certificate and signed document sit on the record, and each obligation has an owner and a date.
Nine more, all built-in.
Each is part of Contracts and eSign, which is on paid plans.
Clause library
Versioned clauses with soft locks, so two people do not overwrite the same clause at once.
Signer audit trail
Every view, field, and signature is recorded in a hash-chained audit trail that you can verify later.
Bulk send
Send one agreement to many recipients at once, each with their own signing link and audit trail.
eSign templates
Save documents with signer roles and fields as templates, so a standard NDA is ready to send quickly.
Approvals
Internal and external approval steps on each contract. Approvers approve, decline, or request changes.
eSign analytics
Signing funnel, time to sign, and a count of stuck agreements, so you know which ones need a nudge.
No signer account
Signers open a link to view the document, fill fields, and sign or decline. They do not need an Atlas account.
Renewals
Propose a renewal, send it, and record acceptance or rejection on the contract record, next to its history.
Contract search
Contracts show up in Atlas search beside deals, accounts, and tasks, with each user's permissions applied.
Contracts writes back.
A signed contract is not the end of the workflow. Five surfaces in the same workspace pick up what comes next.
Five surfaces share the contract
A contract sits on its CRM deal. Follow-up work lands in Tasks. Signed PDFs can be worked on in Documents and found in Search. Status changes reach owners in Inbox. Analytics tracks time to sign and what is expiring.
Programmatic contracts.
Create contracts from your own systems, submit them for review, add obligations, and verify the audit trail with the REST API. TypeScript shown.
// Create an MSA, submit it for internal review, add an obligation. const API = "https://api-atlas.wrxstack.com/v1"; const headers = { Authorization: `Bearer ${process.env.ATLAS_TOKEN}`, // atlas_pat_..., contracts:write "Content-Type": "application/json" }; const res = await fetch(`${API}/contracts`, { method: "POST", headers, body: JSON.stringify({ title: "Acme MSA", kind: "msa", valueAmount: 48000, valueCurrency: "USD", renewalDate: "2027-06-30", renewalNoticeDays: 60 }) }); const contract = await res.json(); await fetch(`${API}/contracts/${contract.id}/submit-internal`, { method: "POST", headers }); await fetch(`${API}/contracts/${contract.id}/obligations`, { method: "POST", headers, body: JSON.stringify({ kind: "payment", dueDate: "2026-12-31T00:00:00Z", description: "First invoice due" }) }); // Later: check the audit trail for this contract. const audit = await fetch(`${API}/contracts/${contract.id}/audit/verify`, { headers });
Contracts vs. Ironclad.
Ironclad is a dedicated contract lifecycle platform. wrxstack Contracts is contract management in the same workspace as your deals and tasks.
wrxstack Contracts vs. Ironclad
| Capability | Ironclad | wrxstack Contracts |
|---|---|---|
| AI review against a playbook | Offered | Version redline view for reviewers |
| e-signature | Built in or via a signature vendor | Built in, with completion certificate |
| Obligations | Tracked in the repository | Owner and due date per obligation |
| CRM linkage | Integration | Same workspace, same record |
| Tasks and projects | Separate tool | Same workspace |
| Depth for large legal teams | Purpose-built CLM | Core contract lifecycle steps |
| Pricing | Quote from sales | Free to start; module on paid plans |
Common questions.
Six things legal leaders ask first.
How do we keep our standard language consistent?
Keep your standard clauses in the clause library with version history, and build contracts by type: MSA, SOW, NDA, DPA, or custom. Reviewers compare each new version in the redline view and request changes where it departs from your standard.
Is the e-signature legally enforceable in our jurisdiction?
Atlas eSign records each signer's actions in an audit trail and issues a completion certificate. Whether an electronic signature is enforceable depends on the document type and the jurisdiction, so check with your counsel for regulated documents.
Can we keep our existing DocuSign or Dropbox Sign?
You can keep them alongside Atlas, but they do not connect today. Connectors for DocuSign, Adobe Acrobat Sign, and Dropbox Sign are in development. The built-in eSign works now when you want one place.
How are obligations tracked after signing?
Each obligation has a kind (payment, deliverable, renewal, termination notice, or custom), a due date, a description, and an owner. Contracts with a renewal date and notice period get renewal reminders ahead of the deadline.
What if the counterparty sends their own markup?
That is the common case. Upload their markup as a new version of the contract. The redline view compares it with the previous version, so reviewers see exactly what changed before they approve or request changes.
Do signers need an Atlas account?
No. Signers open a link sent by email to view the document, fill fields, and sign or decline. Reminders go out on the cadence you set, and you can void an agreement before it completes.
Pairs well with.
Contracts does the most 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 AI review of counterparty markup against a legal playbook, use a specialist vendor. Contracts handles drafting, approvals, signing, and renewals on the same record as the deal, for teams of any size up to large organizations.
Keep every agreement on one record.
Atlas is free to start, no credit card. Contracts and eSign is on paid plans. Load your clause library and send your first agreement for signature.