Legal document automation that drafts from your templates and files to the right matter
We build a workflow that drafts engagement letters, client care letters and routine correspondence from your approved templates and the data already in the matter, sends them for lawyer review and e-signature, and files incoming email, scanned post and e-filing notices to the right matter with consistent names. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.
The problem
Why copied templates and scattered documents create risk
Engagement letters are often built by copying the last one. That is fast, but a stale fee estimate, the wrong responsible attorney or a scope paragraph from a different matter can follow the template into a new letter. In the US, ABA Model Rule 1.5 expects the scope and basis of fees to be communicated, preferably in writing, and contingent fee agreements to be in writing and signed by the client.
Meanwhile documents arrive everywhere: attachments in personal inboxes, scanned post, court e-filing notices and portal downloads. Filing them to the right matter and naming them consistently is tedious, and anything mis-filed tends to surface at the worst moment.
What we build
What our legal document automation includes
Engagement letters from data
The right template by practice area and fee basis, filled from the matter: client, scope, responsible lawyer and rates.
Routine drafts
Acknowledgement letters, document requests and standard updates drafted for review, never sent unreviewed.
E-signature and filing
Approved letters sent through DocuSign and the signed copy filed to the matter automatically.
Inbound filing
Emails, scans and e-filing notices suggested to the right matter with a consistent name; uncertain items go to a person.
Clause library control
Templates and clauses kept in one approved place with an owner and review date.
Bundle indexes
Draft indexes and chronologies built from filed documents for the paralegal to check.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Matter event
A cleared matter or a new document triggers the workflow.
-
02
Automated
Draft or file
The right template is filled, or the document is matched to a matter and named.
-
03
Automated
Queued for review
Drafts and uncertain filings go to the right person's queue.
-
04
Staff review
Paralegal checks
The paralegal checks drafts, filing suggestions and indexes.
-
05
Attorney or solicitor decides
Lawyer approves
Every letter to a client, the other side or a court is approved by the responsible lawyer.
How it behaves
How document automation and filing behave
What the client sees
- An accurate engagement letter to sign quickly
- Consistent, professional correspondence
What staff see
- Drafts waiting for review with matter data filled
- Inbound documents already suggested to a matter
- Draft bundle indexes to check
What the automation does
- Fills approved templates and names files consistently
- Routes uncertain items to a person
- Never sends anything without lawyer approval
Edge cases and fallbacks
- Document matches two matters
- Sent to the paralegal to choose; not filed automatically.
- Template missing a required field
- Draft blocked and the gap flagged.
- Signed letter returned with changes
- Flagged to the responsible lawyer.
- DMS or e-signature outage
- Items queue and retry, and staff can file manually as before.
Architecture
Document automation and matter filing at a glance.
- Input
- Logic and services
- Output
- AI step
- People
- Data
How it flows
- 1 Matter data and inbound documents feed the workflow.
- 2 Letters are drafted from approved templates and inbound documents are matched to matters.
- 3 The paralegal checks drafts and filing suggestions; the lawyer approves anything that leaves the firm.
- 4 Signed and filed documents land in the matter in the DMS or practice system.
Project planner
How the project runs, phase by phase.
Legal document automation & matter filing project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Templates, fee bases, naming conventions, DMS or practice system and where documents arrive.
-
02
Design
About 1 week
Template fields, approval routes, filing rules, naming scheme and confidence thresholds.
-
03
Build
1 to 2 weeks
Template filling, e-signature, inbound matching, queues and indexes.
-
04
Shadow run
About 1 week
Drafts and filing suggestions produced alongside the current process for checking.
-
05
Launch
1 to 2 days
Switch on for agreed practice areas.
-
06
Support
Ongoing
Template changes and filing rule tuning.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Templates, filing rules and naming scheme.
$200 – $400
-
Build
Template filling, matching, queues and indexes.
$550 – $1,300
-
Integrations
Practice system, DMS, e-signature and Microsoft 365.
$150 – $450
-
Testing and shadow run
Parallel drafts and filing checks.
$75 – $250
-
Launch and training
Switch-on and paralegal walkthrough.
$25 – $100
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Drafting and inbound filing can be one workflow or two depending on volume. DMS, e-signature and AI usage are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- DMS and e-signature: Each vendor's own plan.
- AI model usage: Billed by the provider per use; usually a small monthly amount at firm volumes.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: fee communication
ABA Model Rule 1.5 expects the scope and basis of fees to be communicated, preferably in writing, and contingent fee agreements in writing signed by the client. Templates are kept current and approved by the firm.
Source: www.americanbar.orgUS: generative AI and client information
ABA Formal Opinion 512 (July 2024) addresses competence, confidentiality and client consent when lawyers use generative AI tools; outputs are always checked by a lawyer.
Source: www.americanbar.orgEngland and Wales: costs information
Paragraph 8.7 of the SRA Code requires clients to receive the best possible information about how their matter will be priced, which client care templates must reflect.
Source: www.sra.org.ukUS: electronic signatures
Under the E-SIGN Act a contract cannot be denied effect solely because it is electronic; consumer disclosures delivered electronically need prior consent.
Source: www.law.cornell.eduFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Legal document automation & matter filing questions, answered.
Software that fills approved templates with matter data to produce first drafts. Ours also routes drafts for review and e-signature and files inbound documents to matters.
It fills templates your lawyers approved and can draft routine correspondence. It does not create legal advice, pleadings or contracts unsupervised, and every outgoing document is approved by a lawyer.
Clio, MyCase, Smokeball and Actionstep have APIs for documents. NetDocuments and iManage gate API access through their own programmes, so the route is confirmed per project with your administrator.
It looks at matter numbers, party names and senders and suggests a matter. Anything below the confidence threshold goes to a person rather than being guessed.
It drafts indexes and chronologies from filed documents for the paralegal to check. The final bundle is always assembled and checked by the team.
Time to issue an engagement letter, share of letters needing correction, documents filed without manual sorting and mis-filed items found.
Free 20-minute call
Want this for your law firm?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for law firms
All servicesLegal CRM & enquiry follow-up automation
Every enquiry from your website, directories, referrals and phones in one legal CRM pipeline, with fast acknowledgements, consultation booking and follow-ups until the prospect retains you or declines.
From $1,000 · About 4 weeks Details
Client intake & conflict check preparation
Structured intake by practice area that collects every party, company and related name a conflict search needs, runs the search in your practice system and puts the results in front of a lawyer.
From $1,000 · About 4 to 5 weeks Details
Client matter updates & status communication
Proactive updates at the milestones you choose, in plain language the lawyer approved, so clients know where their matter stands and stop calling to ask.
From $1,000 · About 3 to 4 weeks Details