A San Jose law firm · Legal
Every email matched to its matter, a reply drafted in his voice, nothing sent.
An email operating system: every message read, matched to its matter, and answered in draft before the attorney opens it.
- Status
Built, handed over, and running in the business today.
- When
- Scoped 19 August 2026 · live 27 August 2026
- Works inside
- Microsoft 365 · Outlook · Dropbox · Google Calendar · Obsidian · Claude
What was happening before.
Luxin, an AI consulting firm, built, is building, or proposed this work. The status above says which.
Over 100 emails deep in the inbox, and on it all day.
Every reply written from scratch, in one of four different registers depending on who it was to.
Deadlines re-typed into the calendar by hand, across dozens of open matters.
The numbers, with what they mean.
- 100+
- emails deep in the inbox before the system was built
- The problem found
- 2 days
- from signed and paid to the system running in the firm
- What was built
- 4
- voices learned from the attorney’s own sent mail
- What was built
Every figure says where it came from. A problem found is not a result.
What was built.
- 01
Every inbound email is read and matched to the right client file (the matter) across the firm’s own folders.
- 02
Replies are drafted in four learned voices, straight into the drafts folder, never sent.
- 03
To-do items are captured out of the message and kept in one running list.
- 04
A calendar entry is created only after the attorney replies yes to an approval email.
- 05
Every action is logged, so the firm can say exactly how AI touched a matter.
The tools it works inside.
Nothing goes out without you.
A calendar entry is created only after the attorney replies to an approval email. Replies wait in the drafts folder until a person sends them.
Where it stands today.
The system is live in the firm today. Email is read and matched as it arrives, and drafted replies wait in the drafts folder for a person to send. This client has since referred two more business owners to Luxin; one is now at proposal.
More case studies.
Bender Engineering
Read what happened: Bender EngineeringThe operating system Luxin runs on
Read how it runs: The operating system Luxin runs onA sales team scaling outbound
Read what was built: A sales team scaling outbound
Tell me what’s eating the most time.
Thirty minutes, no deck. You describe how the work actually happens, and I tell you plainly whether there is something worth building.