Legal Document Software
A will, a living trust or a power of attorney is a document with rules behind it: who may sign, who must witness, which clauses apply in which state or country, and what must never be left blank. Most firms hold those rules in a lawyer's head and a folder of templates. We turn them into software that asks the right questions, assembles the right clauses, and refuses to produce a document that breaks the rules.
We build this for law firms, estate planners and legal-technology products. The lawyers own the clauses and the rules; we build the machine that applies them. One of the four systems shown on our projects page, Legalgen, is a document and matter platform for legal teams.
The parts of a legal document system
Each part can be built alone. Most firms start with the interview and the assembly, and add the rest as the practice grows into it.
Guided interview
Questions in plain language, in the order a lawyer would ask them, with branches: a married client with minor children sees different questions from a widow with adult children.
Clause library
Every clause lives once, with the conditions under which it applies and the jurisdictions it is valid in. Lawyers edit the library; the software applies it.
Assembly and checks
The document is built from the answers and the library. Required fields, conflicting choices and missing witnesses stop the document before it is printed.
Review and sign-off
Nothing is final until a named lawyer reviews it. The system records who reviewed what, when, and which version they approved.
Signature and witnessing
Electronic signature where your jurisdiction allows it, a printed execution pack where it does not, and a record of witnesses and dates either way.
Matter file and client portal
Each client's documents, versions, answers and correspondence in one matter file, with a portal where the client answers questions and collects signed copies.
What the software never does
A document system can cause harm quietly. These rules are built in, not bolted on.
- It does not give legal advice. It applies rules your lawyers wrote.
- It does not finalise a document without a named lawyer's review.
- It does not guess a jurisdiction. The clauses for a state or country are entered and approved by your lawyers before they can be used.
- It does not hold client data outside the environment and region you choose.
- It does not delete a signed document. Superseded versions are archived with their history.
- It does not hide its reasoning. Every assembled document shows which answers selected which clauses.
How a legal document system is built
Discovery with the people who draft today comes first. You can stop after it and keep everything produced.
Map the document set
We sit with your lawyers and take one document family at a time, usually the simple will first. Every question, every clause, every rule that decides between them is written down.
Build the library
Clauses and rules go into the library with their jurisdictions and conditions. Your lawyers approve each one in the system, not in an email.
Assemble and test
We run real scenarios through the interview and compare the output with documents your lawyers drafted by hand. Differences are fixed in the rules, never in the output.
Sign and store
Signature, witnessing and storage are wired in with the retention your regulator requires. The first clients are handled with a lawyer watching every document.
Widen the set
Trusts, powers of attorney and estate plans follow one at a time, each with its own discovery, library and tests.
What we build it with
Boring, well-supported technology on purpose. Another team can maintain it.
- Application
- PHP / LaravelPython / Django.NET
- Documents
- Template enginesPDF generationDOCX output
- Signature
- E-signature providers via APIPrinted execution packs
- Data
- PostgreSQLEncrypted storage in your regionAudit logs
- Front end
- ReactVue.jsAccessible forms
What legal document software costs
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Build it, or buy a product?
Building makes sense when
- Your clauses and your way of interviewing clients are part of why clients choose you.
- You work across jurisdictions and the products you have tried get one of them wrong.
- You want the matter file, the portal and the document engine to be one system.
- A lawyer on your side can give a few hours a week to approve rules.
Buy a product instead when
- You draft a handful of standard documents in one jurisdiction and a product already does it well.
- Nobody in the practice has time to own the clause library.
- You need it live next month.
- The budget covers the build but not the years of rule changes after it.
Asked by law firms
Who is responsible for the legal content?
Your lawyers. Every clause and rule in the library is written or approved by a named lawyer at your firm, and the system records that approval. We build and test the machine that applies them.
Can it handle more than one jurisdiction?
Yes. Each clause carries the jurisdictions it is valid in, and the interview asks where the client lives and where assets are. A document for a jurisdiction with no approved clauses cannot be produced.
Is electronic signature valid for a will?
It depends on the jurisdiction, and the answer changes. The system supports both electronic signature and a printed execution pack, and your lawyers set which applies where.
Where is client data stored?
In your own cloud account or server, in the region you choose. Nothing of yours is hosted under an account we control.
Can you take over a legal-tech product someone else built?
Yes. We start by reading the code and the clause data and writing down how it works, then agree what to fix first. See software modernisation.
What does it cost?
Billing is by the hour at the published rate of each role involved. Discovery gives a cost range for the first document family so you decide with numbers in front of you.
Tell us which documents, and where
The document families you draft, the jurisdictions you work in, and what goes wrong today. No client details, no templates yet; we sign an NDA before those change hands. We reply within one business day.