An estate practice where reading the file was the slow part, not the advice
Built a private document assistant that reads an estate file, pulls the clauses and statutory dates that matter, and drafts a one-page client summary, all on a closed model that keeps every file confidential and never trains a public system.
Each advisor in the practice carries their own book of clients, and most of the work that fills a day is reading. A new file arrives as a stack of documents: account statements, policy terms, prior agreements, correspondence. Before any advice can be given, someone has to read all of it, cross-reference the clauses, find the dates that carry a legal consequence, and write up a short summary so the rest is quick. The reading and the write-up, not the judgment, was the part that ate the hours.
The knowledge to do it well lived in the senior advisors' heads. Twenty years of knowing which clause matters and which date you cannot miss had never been written down, so it could not be handed off, and a busy advisor reviewing files at the end of the day could quietly miss something. The practice is regulated, so client documents could not be dropped into any general online tool: confidentiality was a hard line, not a preference.
We built a document assistant that runs on a closed model inside the practice. An advisor uploads an estate file, and it reads the whole stack, surfaces the relevant clauses, flags the key dates with the deadline attached to each, and drafts a one-page summary in the format the advisors already use. Every line points back to the source document so the advisor can verify it in one click rather than re-reading the file.
The data architecture was the point as much as the speed. Files stay inside the practice, nothing is shared to the open internet, and nothing is used to train any public model. The assistant gets better at the practice's own document types with use without ever exposing a single client file, which is what let the firm put it in front of a regulated team with confidence.
The review-and-summarize step that used to take most of a morning per file now takes about thirty minutes of an advisor confirming and adjusting a draft, roughly six hours saved on every file the practice opens. The advisors spend the recovered time on the client conversation instead of the reading pile.
The judgment that used to live in two senior heads is now applied to every file consistently, the dates that carry a consequence are flagged the same way each time, and a newer advisor can carry a file end to end without waiting on a partner. The summary is faster, the misses dropped, and no client document ever left the practice.
“The advice was never the bottleneck. It was reading the whole file and writing it up before I could even start, and that knowledge only lived in a couple of heads. Now it is on the page in minutes, and the file never leaves the practice.”
Have a mess like this?
Tell us where time and money are leaking. We’ll map the fastest high-ROI win, usually a Pilot that pays for itself.
