J.J.
JDOT
Open the workspace

Contract review that runs
on your playbook, not someone else's.

Upload a contract. Get it marked up against your own standard positions, with a suggested redline and a reason for every flag. Route it for approval without building a workflow first.

Open the workspaceNo setup call. No migration. Nothing to configure first.

11.1 This clause 11 shall survive termination of this Agreement howsoever arising…

11.2 Neither party shall be liable for any indirect or consequential loss. Supplier's total aggregate liability shall not exceed the fees paid in the three (3) months preceding the claim, and this limit shall apply to all claims howsoever arising.

11.3 Each party shall maintain insurance appropriate to its obligations under this Agreement, with a reputable insurer of good standing, and shall produce evidence of such cover on reasonable request…

11.4 Nothing in this Agreement operates to limit either party's liability for death or personal injury caused by negligence…

One finding, as it appears in the workspace: the clause, the position it breaches, and the wording to send back.

Your playbook, in plain English

Write your positions the way you'd explain them to a colleague — “cap should be at least 12 months' fees, with carve-outs for gross negligence.” No rule builder, no decision tree, no syntax.

Redlines you can argue with

Every flag comes with the clause it refers to, what's wrong with it, the language to propose instead, and which of your positions it breaches. If you disagree, you can see exactly why it decided that.

Routing without a workflow builder

Four approval templates that most teams can use as-is. Pick one, set the names, done. It'll suggest escalated review when the contract is genuinely high-risk.

Ask the contract questions

A chat panel grounded in the contract text and your playbook. “What's our actual exposure under this cap?” gets a number, not a summary.

How it goes

  1. 1
    Drop in a PDF or Word file
    The text is pulled out server-side. The file itself is never stored.
  2. 2
    Run the analysis
    Roughly half a minute. Deviations from your playbook come back marked up on the document, sorted by risk.
  3. 3
    Send it for approval
    Pick a routing template, assign the stages, track status. It all persists.

Have a look

There's a sample vendor MSA loaded already, with a playbook that flags six of its clauses. Nothing to sign up for.

Open the workspace