Contract review
Every contract checked against your playbook.
Pull terms, dates and obligations from your contract library, compare them with your standard positions and keep renewals and notice periods in view.
Discuss your use caseEach party's aggregate liability shall not exceed the fees paid in the three (3) months preceding the claim.
This Agreement renews automatically for successive one-year terms unless either party gives ninety (90) days written notice.
- Liability cap
- 3 months of fees § 11.2
- Renewal
- Auto, 1 year § 14.1
- Notice period
- 90 days § 14.1
What it handles
Every contract read against your playbook.
Terms, dates and obligations are pulled from your contract library, compared with your standard positions, and kept in view as renewals come around.
Each agreement read for the clauses that matter, compared with your playbook, with every deviation quoted from the page.
Contract ReviewAtlas Freight MSA2 deviationsExtracted4 fields- Liability cap
- 3 months of fees § 11.2
- Renewal
- Auto, 1 year § 14.1
- Notice period
- 90 days § 14.1
- Governing law
- Delaware § 18.4
Checks- Liability cap at least 12 months of feesPlaybook position, 9 months short
- Notice period at most 60 days90 days, needs legal sign-off
- Governing law on the approved list
Send to legalOpen playbookEvery contract's term, renewal and notice dates in one register, so nothing renews before someone has decided.
Ask a question across every agreement and get an answer with each contract and clause cited.
How it fits
Reads the library you already keep.
Strive reads contracts where they live, checks them against your playbook and keeps legal and the business ahead of every date.
Comes in from
- Contract librarySigned agreements and amendments
- Shared drivesDrafts and counterparty paper
- Contract requestsNew agreements as they come in
- 01ReadEvery page, scanned or signed
- 02ExtractTerms, dates and obligations, each cited
- 03CompareAgainst your playbook positions
- 04ReviewDeviations go to legal
Goes out to
- A contract registerTerms, renewals and obligations
- Reminders in SlackNotice dates, before they pass
- Into your systemsTerms returned as data over the API
What you can do.
Check against your playbook
Liability, renewal, notice and governing law compared with your standard positions.
Never miss a notice date
Renewals and notice periods in one register, with reminders before they pass.
Ask across the library
Questions answered across every agreement, with each contract and clause cited.
Send deviations to legal
Only the contracts that break your positions wait for a lawyer.
Apps for this work
Security
Security your IT team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.
Security
SOC 2 Type II
Independently audited security controls, tested over time.
Europe
GDPR
Personal data handled under the EU's data protection rules.
California
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
Questions
What people ask about contract review.
Where is our contract data kept?
In Strive Cloud on Google Cloud, with each organization's data kept apart at the database level. On Enterprise, the whole platform can run inside your own cloud account instead.
We're lawyers, not software people. Do we have to build anything?
No. We can set up the review around your playbook and hand your team an app that's ready to use. Anyone who wants to adjust a clause check later can do it themselves, or ask us to.
Our contracts are in a contract management system. Can it read them?
Yes, if that system has a REST API or an MCP server. Strive reads the library where you already keep it.
Can it read scanned and older contracts?
Yes. Scans and poor copies go through OCR, with the layout and reading order kept. Handwritten notes and signatures are read by a vision model.
Can we choose which terms it checks?
Yes. You choose the terms it pulls out, and it compares them with the positions in your own playbook.
Can it compare a new draft with the version we sent?
Yes. It finds what changed between the two versions, clause by clause or line by line.
Which document-heavy job would you hand over first?
Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.
Contact SalesAn hour of your time and a process you know well. That's all it takes.