Jurisphere raises $2.2 Million from InfoEdge Ventures, Flourish Ventures, Antler and 8i Ventures

Redline contracts against your playbook, without leaving Word

AI contract redlining inside Word. Jurisphere checks the counterparty's draft clause by clause against your firm's positions and turns each deviation into a tracked change you accept, reject or rewrite.

  • Works inside Microsoft Word
  • Your playbook, not a generic standard
  • ISO 27001 and SOC 2 Type 2
Book a 30-minute session

The playbook is in someone's head

  • The firm's positions live with a partner. The associate reviewing the draft at nine at night has the clause in front of her and a guess at what the partner would say.

  • Every incoming draft is compared with the standard the way it was last year: by reading it, clause by clause, against memory.

  • A junior's redline gets checked against the standard twice. Once by the junior writing it, once by whoever signs it off.

  • A tool outside Word means copying each clause out, reading the suggestion, and pasting the edit back in. Nobody does that twice.

Used by teams who negotiate for a living

More than 500 legal teams use Jurisphere, including CMS IndusLaw, ICICI Bank and Tata Capital.

See how firms use Jurisphere
“Jurisphere is a very useful product and thoughtfully designed for legal professionals.”
Adity Chaudhury, Partner, Argus Partners

What the Word add-in does

  1. Redline and review inside Word, as tracked changes.

  2. Drafting grounded in your own precedents, not a generic corpus.

  3. Your playbook applied on every review, the same way every time.

You make the call. Jurisphere makes the edits.

Every suggestion is one of four kinds: an insertion, a deletion, a rewrite or a replacement. Every one arrives with the same four controls. Show in Document takes you to the clause. Apply puts the edit into the document as a tracked change. Apply with Comment does the same and leaves a note explaining the edit for the next reader. Dismiss drops it.

To work on one clause, highlight it and set the scope to Selection Only. The add-in then looks at that text alone, not the whole document.

Nothing is accepted on your behalf. Nothing is rewritten silently. The add-in proposes; the lawyer decides, one edit at a time.

Your firm's playbook, applied every time

A Review Playbook is the firm's negotiating position, written down once. Build it under Workflows > Review Playbooks, rule by rule, or import the playbook you already have as a PDF or Word file (up to 50MB) and refine it.

Each rule carries a Starting Position, as many ranked Fallback Positions as the firm will tolerate, and a Dealbreaker Position it will not cross. Each rule has a priority: Mandatory, Recommended or Nice to Have. An optional Applicability Condition limits a rule to the contracts it belongs in.

Take the survival clause in an NDA. Starting position, five years. Three is acceptable if the counterparty pushes. Below one year is a dealbreaker. Written as a rule, that position applies to every NDA that lands, whoever opens it.

Run the playbook from the add-in's Review Playbooks tab and every rule resolves against the draft to Acceptable, Fallback or Not Acceptable, with the clause and the rule side by side.

Spot the deviation. Push back with the position.

A flag is only useful if it tells you what to say. When a clause lands on Fallback or Not Acceptable, the rule's Starting Position sits beside the counterparty's language, so the gap is visible without re-reading the playbook.

Generate Edit turns the flag into a suggested edit. Apply it with a comment and the position travels with the redline. What goes back across the table is a redline you can defend, because it came from a rule the firm wrote, not from a model's idea of a reasonable clause.

Native Word track changes, not a parallel layer

Apply makes the change directly in your document, in track mode. No side document to reconcile, no export step at the end. The file that leaves the firm carries one revision history, opens the same way on the other side, and is the file the next round starts from.

The revision history is the audit trail. A tool that writes outside it leaves you reconstructing what moved, and when, from email. Read why in Round seven of the markup.

Grounded in your own precedents

Generic AI drafts from a generic corpus. Draft & Edit in the add-in works from the documents your firm gives it: the executed SHA from the last deal, the standard services agreement, the clause you fought for in March and want to use again.

For select enterprise clients, Knowledge sync mirrors a folder in Google Drive, OneDrive, SharePoint or Dropbox into Jurisphere, so the precedent bank is the one the firm already maintains. Custom Skills turn a firm template into a drafting step anyone in the team can run.

On the web platform, the Drafting Pane gives you a live, editable draft with version control and precedent referencing, and more than 350 workflows drafted by practising lawyers cover the agreements and reviews Indian practices run most.

The result reads like the firm's paper because it came from the firm's paper. More in Your AI is only as good as what it can see.

Built for the way Indian contracts are actually executed

A playbook written for a Delaware company does not know what an Indian counterparty expects on the execution page, or which clauses an Indian court will not enforce. These are the positions Indian firms write in as rules. The reasoning and the case law behind each one are in our guide to AI contract redlining tools in India.

  1. Post-term non-competes. Nothing that runs past the term; hold the line at in-term exclusivity, confidentiality and non-solicitation.

  2. Liquidated damages. A genuine pre-estimate with a recital of why loss is hard to quantify, never a sum payable on demand.

  3. Claims periods. No clause barring claims not brought within twelve months; use notice-of-claim conditions and liability caps instead.

  4. Stamping. Duty paid before signing and recited in the document, with stamping treated as a closing deliverable.

  5. The execution block. Authorised signatories with the board resolution or power of attorney recited, witnesses where attestation is required, and wet ink for the instruments that cannot be signed electronically.

  6. Seat of arbitration. A named seat, not a venue or a place, paired with exclusive jurisdiction for the courts of the seat.

  7. MSME payment terms. No more than 45 days from acceptance for a micro or small supplier registered on Udyam, with an MSME status representation.

See a review from open to save

A contract opened in Word. A playbook applied. Deviations flagged with the position beside each one. Edits generated, accepted, rejected. The document saved, revision history intact.

Contract redlining for different desks

  • Corporate.

    SHAs, SPAs and services agreements reviewed against the firm's positions, deal after deal. The playbook becomes the firm's negotiating memory, not one partner's.

  • In-house.

    Every vendor and customer paper reviewed to one standard, whoever picks it up. The fallbacks are written down, so only the dealbreakers reach the GC.

  • Disputes.

    Settlement agreements and consent terms redlined against positions the client has already approved. When a negotiation turns into a dispute, Redline Analysis tables every change in the file by author, date and consequence.

See use cases by practice

Why not a general AI assistant in Word

A general assistant can rewrite a clause fluently. What it cannot do is the work.

It has no playbook, so every review starts from the model's idea of reasonable, not the firm's. It has no precedent bank, so the draft reads like everyone's paper. It has no tracked-change discipline of its own: unless track changes is already on, what it rewrites lands as plain text with no record of what moved. And it keeps no record of why a change was made, so the comment that explains the position is yours to write afterwards.

Jurisphere starts from the rule, edits in track changes, and leaves the reason on the page.

Security and retention

Jurisphere is ISO 27001 certified and SOC 2 Type 2 compliant. Customer content is not used to train, fine-tune or improve any AI model. Content is held in memory only for as long as it takes to generate a response, and is encrypted in transit and at rest.

A contract opened in the add-in is processed for the review you ask for and is not retained inside an AI system afterwards. Firms can also choose where their data is hosted, including deployment within their own cloud environment where required.

The detail is on the security page and in the trust centre. Clients are asking harder questions about this; we wrote down the answers.

  • ISO 27001 certification badge

    ISO 27001 certified

    Certified information security management.

  • SOC 2 Type 2 compliance badge

    SOC 2 Type 2 compliant

    Controls audited against industry standards.

  • Not used for training

    No customer content trains, fine-tunes or improves any model.

  • Encrypted throughout

    In transit and at rest, and held in memory only while answering.

Before you book

Which versions of Word does the add-in work in?

Word for Windows and Word for Mac on Microsoft 365, and Word on the web. It is not yet supported on iPad or mobile, and older non-subscription versions such as Word 2016 have limited support. Install it from Home > Add-ins by searching "Jurisphere", or from the Microsoft Marketplace, and try it on your own contracts with a free trial.

What happens to our playbook file?

Playbooks are built and kept on the Jurisphere web platform under Workflows > Review Playbooks, where the rules can be edited at any time. Importing a PDF or Word playbook builds the rules from it.

Does it work offline?

No. The add-in sends your instruction and the relevant text to Jurisphere, which generates the review or the edit and sends it back, so Word needs an internet connection while you use it. The contract itself stays an ordinary Word file: you can open, edit and save it offline, and every tracked change already applied stays in place.

What about a contract that is not in English?

Translate it first with Jurisphere's Translation tool, which reads 22 Indian languages, then run the review on the English text.

Who signs off the redline?

Your lawyers. The add-in proposes edits against the rules you wrote; a lawyer accepts, rejects or rewrites each one, and the document goes out under the firm's name.

Can it read the counterparty's markup?

Yes. Redline Analysis on the web platform reads a document that already carries tracked changes and tables every change by author, date, category and consequence, so you can see what moved in each round and who moved it.

Does it work with our CLM and document systems?

Yes. Every edit stays in the Word file, so the document goes back into your CLM or DMS as normal. For select enterprise clients, Knowledge sync connects Google Drive, OneDrive, SharePoint, Dropbox and DocuSign, so executed agreements sit beside the precedents your team drafts from.

Related reading

Send us the contract that took seven rounds

Bring the draft and the playbook, or just the draft. We run the review on your document in a 30-minute session, and you keep the redline.

Book a 30-minute session