Solutions
The tools I set up, and the ones I've built.
The core of my work is implementation and training. The two custom tools further down this page were built for specific client needs.
AI implementation & training
Four steps, in order.
-
Assess & select
I start with how your firm actually works: practice areas, document flows, who does what. Then I select AI software that fits. That has meant Claude for the teams I've worked with so far.
-
Implement & configure
Installation, account structure, and configuration inside your firm's own accounts. I go through data residency, retention settings, and access controls during setup, rather than leaving vendor defaults in place.
-
Train & enable
Hands-on sessions for lawyers and staff: structured prompting, verifying AI output, and embedding AI into the daily work your team already does. The sessions are built around your firm's actual documents and workflows.
-
Build only if needed
Where off-the-shelf tools leave a gap, I build custom tooling. The two tools below both started this way.
CanLII citation verification
A stateless MCP server that lets your AI assistant check citations against the real database while it drafts.
Large language models can produce citations that look right but aren't. This tool gives your AI assistant a way to verify. It's a Model Context Protocol (MCP) server that acts as a translation layer between your assistant of choice and the CanLII API, checking case citations, case IDs, and metadata against the actual database during drafting and review.
Only public citation queries travel this path. No client documents, no confidential material.
How the engagement works. Your firm connects with CanLII and obtains its own API key, so you own the API relationship. I deploy the stateless MCP server on Cloudflare using that key, and connect it to your AI assistant as a verification tool it can call while working.
The server is stateless and handles only public citation lookups. Your documents and client information don't route through it, and your firm keeps control of its own CanLII access throughout.
Voice transcription
Meeting notes, transcribed, with the data staying in Canada.
A transcription tool for legal teams that turns meetings and dictations into usable notes. It's built on Google Cloud's Canadian region, with data residency handled in the code, so transcripts are processed and stay on Canadian servers, in your firm's own cloud environment.
How I approach security & privacy
Everything I set up works the same way: your firm owns every account and API key, custom tooling is stateless wherever possible, and systems are built with Canadian data residency and privacy obligations in mind.
Everything I set up can be inspected and controlled by your own IT team. If you'd like to walk through the details, get in touch.