Your Clauses, Your Positions. Every Finding Cites Its Page.
Drafts are built from wording you have approved. Counterparty paper is checked against your playbook and comes back as a Word redline. Every signed agreement keeps an evidence pack with a pre-filled certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023.
- E-signed contracts recognised under the IT Act, 2000
- No model call without admin consent
- India-only AI processing available
MSA — Northwind Systems
against “MSA — when we are the supplier”4. Payment Terms
The Customer shall pay each undisputed invoice within ninety (90) days from receipt of invoice. No interest shall accrue on amounts paid within this period.
Payment terms
DeviatesHigh risk p. 1Ninety days is twice the playbook position and beyond the 45-day limit that section 15 of the MSMED Act sets for micro and small suppliers.
Playbook position: invoices are paid within 45 days.
Proposed change
within ninety (90) dayswithin forty-five (45) days
Added to the Word redline
AI-generated · not legal advice. A person accepts or dismisses every finding.
01On legal’s desk
Four Requests, and What Answers Each
A legal team hears the same four requests from the rest of the business, week after week. Here is each one as it is handled today, and as it is handled with FlowVerify.
- 01
Sales needs an NDA by tomorrow.
Today
Find the last one, change the names and hope it was the current version.
With FlowVerify
A first draft built from your clause library. Approved clauses go in word for word, and facts nobody gave are left as blanks.
Drafting and clause library - 02
The counterparty’s paper has come back.
Today
Read every clause against positions that live in your head or in an old memo.
With FlowVerify
A playbook review: each rule compared with the draft, each finding with its page and a suggested change, exported as Word tracked changes.
Playbook review - 03
Finance asks what was agreed, and when it renews.
Today
Open the PDF and search for “renew”.
With FlowVerify
The repository has already read it: parties, amounts and dates, each with its page. The assistant answers with the document and the page.
Agreement repository - 04
A dispute needs the signed copy, and proof of who signed.
Today
An email thread, a scanned signature page and somebody’s memory.
With FlowVerify
The evidence pack: signed PDF, certificate of completion, audit trail and a pre-filled certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023.
Evidence and verification
02How it works
From Approved Clause to Evidence Pack
Five steps in the order an agreement moves through legal. Each one is a screen in FlowVerify, and each link goes to the page that covers it.
- Clauses
- First draft
- Redline
- Pre-send check
- Evidence pack
- 01
Keep Approved Wording in One Place
A clause library of the wording you have signed off, with a version on every change. It starts with clauses for NDAs, service, employment and vendor agreements that reflect common positions under Indian law, and it becomes yours as you edit it.
Clause libraryClause library
48 clauses · approved wording
Confidentiality — mutual, 3 years
v2ConfidentialityNDAApprovedLimitation of liability — capped at fees
v2LiabilityMSAApprovedPayment terms — 45 days
v3PaymentVendorApproved
- 02
Get a First Draft That Does Not Invent Facts
Describe the deal, the parties and the key terms. The draft opens in an editor. A section that calls for a library clause gets your approved wording word for word, and a fact you did not give becomes a blank, never a guess.
AI draftingConsulting Agreement — Lakshmi Advisory
First draft · AI-generated, not legal advice
3 blanksConsulting Agreement
This Consulting Agreement is made at Bengaluru on Date of agreement between Kiran Exports Private Limited and Lakshmi Advisory LLP, having its office at Address of Lakshmi Advisory.
Clause libraryFees and payment — monthly retainer · v2
3. Fees and Payment. The Company shall pay the Consultant a retainer of ₹1,50,000 per month, exclusive of GST.
- 03
Review Your Paper or Theirs Against the Playbook
Write your standard position, fallback and severity for each clause once. Any draft is then checked rule by rule. Deviations and missing clauses come back by risk, each with its page, and the accepted changes export as a Word redline.
Playbook reviewMSA — Northwind Systems (their draft v4)
Playbook: MSA — when we are the supplier
Redline (.docx)Playbook rule · Payment terms
Severity: high- Position
- Invoices are paid within 45 days.
- Fallback
- Up to 60 days where the supplier is not a micro or small enterprise.
Payment terms
High riskDeviatesp. 1Limitation of liability
High riskMissingp. 2Notice period
Medium riskDeviatesp. 2Governing law
Matchesp. 2
- 04
Stop the Wrong Document Before It Is Sent
The pre-send check runs fixed rules with fixed statute citations. No model is involved. It flags a document the IT Act does not apply to, a lease long enough to need registration and payment terms beyond 45 days for a micro or small enterprise, and an admin decides which of them block sending.
Send for signaturePre-send check
Runs at Review, and again on every send
4 of 14 rules- Blocks
A document the IT Act does not apply to
Information Technology Act, 2000 · First Schedule
- Warns
Lease term over 11 months (registration needed beyond one year)
Registration Act, 1908 · s.17(1)(d)
- Blocks
Payment beyond 45 days to a micro or small enterprise
MSMED Act, 2006 · s.15
- Always blocks
A signer with no field to sign
Structure of the envelope
A check, not legal advice. An admin chooses which rules block sending.
- 05
Keep Evidence Ready to Produce
When the last signer signs, the document and its certificate of completion are hashed and recorded. One download gives you the evidence pack: the signed PDF, the certificate, the audit trail and a certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023, pre-filled with what the platform knows.
Evidence and verificationCertificate of Completion
Office Lease Renewal — Indiranagar
FV-2611-104 · Completed
- S. VenkateshAadhaar eSign6 Nov 2026, 16:02 IST
- Shalini BoseEmail OTP7 Nov 2026, 10:14 IST
Signed document hash sha256 · 9f2c41…7be0a3
Scan the QR code to verify
03The paperwork
The Paper Legal Owns, and What Is Checked on Each
Four starter playbooks carry common positions under Indian law. They are copied into your workspace once and are yours to rewrite. The statute citations in the pre-send check come from a fixed registry, never from a model.
NDA, Mutual or One-Way
Term, survival, exclusions and permitted disclosure, against your positions.
Starter playbook: NDA
Master Services Agreement
Limitation of liability, indemnity, termination and payment terms.
Starter playbook: MSA
Vendor Agreement
Payment within 45 days where the supplier is a micro or small enterprise, notice period and data protection.
Starter playbook: Vendor · MSMED Act, 2006, s.15
Employment Agreement
Non-compete, notice period and confidentiality.
Starter playbook: Employment · Indian Contract Act, 1872, s.27
Lease Deed
A term long enough to need registration (more than one year; the check warns from 11 months), and the stamp duty estimate for the state.
Registration Act, 1908, s.17(1)(d)
Anything Else You Sign Often
Your own playbook, written rule by rule: position, fallback and severity.
Your playbook
Documents the IT Act Excludes
The First Schedule of the Information Technology Act, 2000, as amended in 2022, lists documents the Act does not apply to, so sign them on paper. The pre-send check reads the title and the text, flags one of these, and can block it from being sent. A sale deed is no longer on the list, but like a lease for more than a year it still has to be stamped and registered.
- Wills
- Trust deeds
- Most powers of attorney
- Negotiable instruments other than cheques
04Playbook review
Review Their Paper Against Your Positions
Upload the counterparty’s draft and pick a playbook. FlowVerify splits the document into clauses and compares each rule with what the draft says. Every finding quotes the clause, cites the page and proposes wording that would meet your position.
- One finding for each rule: matches, deviates or missing
- A finding is kept only when its quote is found in the document
- Risk follows the severity you set for the rule
- Accept a change and download the redline as Word tracked changes

05Evidence
What the Evidence Pack Holds
One ZIP for each completed agreement, for a court, an auditor or the other side’s counsel. Every file in it is fingerprinted, and the manifest lists each SHA-256.
- Anyone holding the signed PDF can check it on a public verification page
- An agreement sent by an AI agent names the agent, its mandate and the person who issued it
- One-time codes, signing links and API keys never enter a pack
- Every export is written to the audit trail
- signed.pdf
- The signed agreement, exactly as certified.
- certificate.pdf
- Certificate of completion: signers, signing methods, timestamps and a QR code that opens the public verification page.
- audit.json
- Every recorded action on the agreement, with who did it, when, and from which IP address and device.
- events.json
- Signer events: one-time code checks, consent, Aadhaar eSign and approvals. The codes themselves are never stored.
- recipients.json
- Who received it, in which role, and what each of them did.
- bsa-s63-certificate.pdf
- A certificate under section 63(4) of the Bharatiya Sakshya Adhiniyam, 2023, pre-filled with what the platform knows. The parts personal to the people certifying are left blank for them to complete.
- manifest.json
- The SHA-256 and size of every file in the pack.
- README.txt
- How to read the pack.
06After signature
Every Signed Agreement, Read and Searchable
Completed agreements, and older ones you import, sit in one repository. FlowVerify reads each of them: a summary, the parties, the amounts and the key dates, each cited to its page. Search by the words in the document or by what it means.
- The assistant answers from your agreements and names the document and page
- Legal hold keeps an agreement out of the retention sweep
- Import agreements signed elsewhere; duplicates are caught by file hash
- Audit export as CSV for the people who hold that permission

07Agents
Agents May Propose. People Decide.
If your business lets an AI agent draft or send agreements, legal sets the limits. The agent works under a mandate, and nothing it proposes counts until a person approves it.
Agent-to-Agent Negotiation, Approved by a Person on Each Side
Your agent and the counterparty’s can exchange wording on the clauses you allow. Each turn waits for a person on that side to release it, and the terms are agreed only when a person on each side approves the same wording. They bind once the agreement is signed. The transcript goes into the evidence pack.
Negotiation · Clause 4, Payment terms
MSA — Northwind Systems · draft, not sent
Kiran Exports · agent “Claude”
Released by Shalini Bose
Northwind Systems
A Mandate Keeps an Agent Inside Limits You Set
An admin chooses the templates, the actions, the recipient domains, a daily cap and an expiry date. Anything outside the mandate is refused, and everything inside it is recorded in the run log, in the audit trail and on the certificate.
Mandate · Legal drafts
Agent “ChatGPT” · issued by Shalini Bose
- May
- Create and prepare drafts, negotiate
- May not
- Send, remind, void or download
- Negotiable clauses
- Payment terms, notice period
- Turns per negotiation
- 3
- Expires
- 15 Jan 2027
Revoking the mandate stops the agent at once.
08Before you roll it out
What the Board and IT Will Ask
Short answers to the questions a general counsel is asked before a new system holds the company’s agreements.
Access
Built-in roles such as Owner, Admin, Sender, Approver and Auditor, custom roles on a permission matrix, and departments that limit who sees which agreements. Single sign-on and two-factor.
Evidence
Every signed agreement carries a tamper-evident certificate of completion and an audit trail. The evidence pack is one download, and the audit log exports as CSV.
ComplianceAI controls
Nothing reaches a model until a workspace admin accepts the AI terms. Each AI feature has its own switch, India-only processing is available, and your data is not used to train AI by default.
Deployment
Shared cloud, or a dedicated single-tenant deployment for one organisation. AES-256 at rest and TLS in transit.
Security
Other teams
The Same Workspace, Used Differently
- HROffer Letters and Joining FormsJoiner listBulk sendSigned
- SalesQuotes and Order FormsTemplateReminders chaseCRM updated
- Finance & ProcurementVendor AgreementsTerms checkedSignedReminder
- Founders & Small BusinessesOne Tool Instead of ThreeDraftSignTrack dates
- Developers & AI TeamsAPI, SDKs and an MCP ServerAPI or MCPMandateWebhook on signed
Contracts signed electronically are recognised under the Information Technology Act, 2000, and Aadhaar eSign is an electronic signature under section 3A. The First Schedule of the Act, as amended in 2022, leaves out wills, trusts, powers of attorney (except those that empower an entity regulated by the RBI, NHB, SEBI, IRDAI or PFRDA) and negotiable instruments other than cheques (with a matching exception for demand promissory notes and bills of exchange). The pre-send check flags a document that reads as one of these and can block it from being sent. Whether a particular agreement is enforceable still depends on its own facts.
No. It is AI-generated and every screen says so. The review compares a draft with positions you wrote, quotes the clause, cites the page and suggests wording. A person accepts or dismisses each finding, and nothing in the document changes until they do.
Only after a workspace admin accepts the AI terms, and only for the AI features you leave switched on. Consent can be withdrawn at any time, an India-only mode keeps processing in India, and your data is not used to train AI by default. The pre-send check, the evidence pack and public verification do not use a model at all.
A Word document with tracked changes, so the other side can open it and respond in the tool they already use. The changes sit at the clauses the findings refer to.
No. In a negotiation an agent can only propose or counter, inside the clauses and the number of turns its mandate allows. Every agent turn waits until a person on that side releases it, and terms are agreed only when a person on each side approves the same wording. They bind once the agreement is signed. An agent or an API call never signs for anyone.
Yes. Put it on legal hold and the retention sweep leaves it alone. Retention only ever removes stored files: certificates, audit records, document hashes and the extracted key terms are kept. A dry-run report shows what a retention rule would remove before you switch it on.
Book a demo
See It on a Draft
You Are Reviewing
Bring a counterparty MSA or NDA and the positions you hold on it. We set up the playbook with you, run the review and open the Word redline.
What you get
- Your positions written into a playbook
- A review of a real draft, with the redline
- Answers from the people who build it