Drafts from your templates, traceable to the paragraph
A working prototype of a drafting engine for a multi-practice firm. An NDA, an engagement letter, a quarterly investor letter, a capital call notice and an offer letter are generated from the firm's templates, its playbook and the facts already on record, and each paragraph says where it came from. A lawyer or partner reviews every draft; the engine never advises and never sends.
Runs in your browser on sample data. Nothing you do in it is stored. Built for law firms, fund administrators, accounting and advisory practices.
Meridian, October 6, 2026: a mutual NDA for Halvorsen Robotics generated from the template, the matter file and the playbook, with one fact flagged as not on record.
Six things the demo does end to end
A library the firm already owns
Sixteen templates in four groups. Each card lists the facts it needs, the playbook positions it draws on and the drafts made from it, which become the precedents the engine cites.
An intake that fills itself
Pick a matter, fund or employee and the fields fill from the CRM, the fund administrator, the HRIS or the matter file. A pill beside each value names the system it came from; a fact that is not on record is marked.
Playbook choices with the firm default
Governing law, confidentiality term, fee structure, call basis and the rest start at the firm's position. Choose something else and the checklist notes the departure for the reviewer.
Generation you can read
The draft is typed paragraph by paragraph. Hover any paragraph for its chip: the template clause, the intake field, the playbook position or the named precedent. Click to read each one.
Edits, versions and the redline
Click a paragraph to edit it. The generated v1 is kept, v2 holds the edits, Compare shows the redline, and a what-changed summary is drafted from the diff for the reviewer.
A checklist before anyone signs
Missing facts, departures from the playbook, numbers that do not tie, defined terms used before they are defined, and house style. Each item is a pass, a flag with a fix, or a note for the reviewer.
Three steps, five minutes
Take the tour
Fifteen stops, about five minutes: the library, the prefilled intake, a playbook choice, generation, a paragraph's source, an edit, the redline, the checklist, the fix, and the same engine on an investor letter.
Generate the NDA yourself
New draft, Mutual NDA, Halvorsen Robotics. Change governing law to New York, press Generate and watch the paragraphs arrive with their sources. Then fix the missing signatory title from the checklist.
Open the investor letter and the playbook
Larkspur II, Q3 2026: the figures tie to the fund administrator's ledger, and a partner's comment gets a suggested reply. Then change a default in the playbook and start a new draft to see it used.
We build it custom for your firm
The demo runs on sample data. A real build connects to your own tools and is fitted to how you already work.
Your templates and your playbook
The templates your practice groups already use, with the positions your partners hold on each clause written down once and applied to every draft.
Your systems as the source of facts
Connected to the CRM, matter management, fund administration and HR systems you run, whether Clio, NetDocuments, Investran, Allvue, Workday or a spreadsheet, so the intake fills itself and every value names its source.
Your precedents, cited
Approved drafts become the precedents the engine checks against, with the reviewer's settled wording carried forward and named on the paragraph it shaped.
A person signs every draft
The engine drafts, flags and keeps versions. A lawyer, partner or director reviews, edits and approves. Nothing is sent by the system, and nothing it writes is advice.
Want this built for your firm?
Thirty minutes with Ishaan: what it would connect to, what it needs from your side, and whether it makes sense to build it together.
Book a free callor write to us at [email protected]