Solutions / Contract review and obligations
Legal, procurement and sales operations
Contracts reviewed against your playbook, then remembered
Every incoming contract compared to your positions, redlined in Word with tracked changes, and every obligation turned into a reminder before it can be missed.
Representative blueprint. The targets below are design targets we scope and measure against in a Loop Audit. They are not results from a named client.
Contracts are read once and forgotten
- Lawyers spend hours finding the same ten clauses in every agreement.
- Fallback positions live in a document few people open.
- Renewal notices, SLA credits and insurance certificates are missed because nobody tracks them.
- Sales waits for legal and legal waits for context.
- After signature, the contract goes into a folder and is never read again.
How the loop runs.
7 stages, from the moment work arrives to the moment it is proven done. Each one is observable, testable and can be paused.
Receive
Accepts contracts by email, shared folder or e-signature platform and identifies the document type and parties.
Extract clauses
Finds and classifies clauses such as liability, indemnity, termination, data protection and governing law, with exact text and location.
Compare to playbook
Scores each clause against your preferred and fallback positions and explains the gap.
Draft the redline
Produces proposed edits as Word tracked changes using your approved fallback language.
Brief the reviewer
Summarises the risk in plain language, ordered by what matters most, and links every point to the clause.
Extract obligations
Turns dates, notice periods, deliverables, credits and certificates into structured obligations with owners.
Remind and report
Creates calendar events and tasks, and reports upcoming renewals and exposure across the portfolio.
The hard parts, and how we handle them.
Playbooks need structure to be machine-usable
We turn your playbook into explicit rules with preferred, acceptable and unacceptable positions, and keep them editable by your legal team without engineers.
Clause boundaries are messy
Real contracts have cross-references, defined terms and exhibits. We resolve definitions and references before judging a clause.
Redlines must be exactly what you would send
Edits come only from approved fallback language and are inserted as real tracked changes in the original file, never retyped copies.
Not legal advice, and built that way
The tool prepares and flags. A lawyer decides. Privilege and confidentiality are handled by design, with no cross-client learning.
What a person always decides
- Lawyers approve every redline and every position taken
- Each client or matter is isolated, with no shared learning
- Original files never modified: changes produced as new versions
- Complete log of what was reviewed and by whom
- Unusual clauses always escalate rather than guess
Connects to
- DocuSign
- Ironclad
- SharePoint
- Google Drive
- Salesforce
- HubSpot
- Jira
- Microsoft Outlook and Google Calendar
Built with
- Document parsing for Word and PDF
- Clause library and playbook rules
- Tracked changes writer
- Obligation registry
- Calendar and ticket integrations
A realistic timeline.
Shadow mode first. Nothing acts on its own until its accuracy has been measured against your team’s own work.
- Weeks 1 to 2Collect your playbook and a sample of past agreements. Define clause categories and risk rules.
- Weeks 3 to 5Extraction and comparison validated against your lawyers’ own reviews.
- Weeks 6 to 8Redline generation and reviewer briefs live on new inbound contracts.
- Week 9 onwardObligation tracking across the existing portfolio.
What we design for.
Modeled targets, confirmed or corrected with your own data in a Loop Audit.
- Matter-level isolation and access control
- Retention aligned to your records policy