Built for fractional general counsels
by a technologist who saw the pattern.
Sapphire Legal wasn't built by a law firm, and it wasn't built by a legal tech company chasing a niche. It was built by a fractional CTO who kept seeing the same broken workflow across multiple legal engagements — and decided to fix it.
- Quick answer
- Who built Sapphire Legal?
- Sapphire Legal was built by Brett Wilson, a fractional CTO and Chief AI Officer who has consulted with multiple legal teams and fractional general counsels. Across those engagements he kept seeing the same broken workflow — tools designed for single firms billing hours, generic AI with no per-client memory, and spreadsheets serving as the only institutional knowledge. Sapphire Legal is the platform those clients kept describing and nobody in the market was building.
The short version: I'm a fractional CTO and Chief AI Officer. I work alongside executive teams who need senior engineering and AI leadership without hiring it full-time. Several of those engagements have been with legal teams — in-house departments, boutique practices, and fractional general counsels serving multiple client companies.
Across those engagements, I kept seeing the same story. The fractional general counsels I worked with were brilliant lawyers doing the job of a full-time in-house team for 3–6 companies at once. And every one of them was using a stack of tools that didn't fit their model. Clio was built for a single firm billing hours, not a fGC managing a portfolio. Google Docs had no structure. Generic AI tools had no memory of which client they were drafting for. Everyone ended up with a spreadsheet of client preferences and a nagging feeling that something important was always being forgotten.
The breaking point was always the same: a fGC would draft the same NDA for the fourth time in a week — each time for a different client, each time adjusting the governing law, the liability cap, and the carve-outs from memory. And sooner or later they'd forget that Client A prefers Delaware, and the draft would go out with California, and Client A would catch it in review. Embarrassing. Avoidable. Not the kind of mistake these lawyers actually make when they have the right tools.
I kept asking “why doesn't a product exist for this?” The answer was that the existing legal tech companies don't see the fGC as a distinct market. Clio sees a solo practitioner. NetDocuments sees a small firm. Neither sees someone running 5 companies' worth of legal work out of a single brain.
So I built it. Sapphire Legal started as a Client Playbook system — encode a client's posture once, have the AI enforce it forever. Then the Portfolio Command Center, because my clients were losing track of which matter they touched last. Then Clarity — not a call recorder, but a post-call analysis engine where attorneys upload an existing recording and get structured legal intelligence back. Then the Kanban board, the Smart Collections, the deadlines, the conflict checks. Every feature maps back to a specific pain a real fGC described to me across a kitchen table or a Zoom call.
I'm not a lawyer. I'm the technologist who listened to enough of them to know exactly what was missing — and who had the engineering team to build it properly instead of shipping another wrapper around ChatGPT.
“Every fGC I worked with described the same broken workflow. Nobody in the legal tech market was building for it. So we did.”
— Brett Wilson, founder · fractional CTO & Chief AI Officer
Four principles we don't bend on.
Own the entire stack
No OpenAI dependency. No vendor integrations where a failure on their end takes us down. The AI is ours. The database layer is ours. The e-signature, the document engine, the call intelligence — ours. That's why features that would take competitors 2 years to ship take us a weekend.
Ship what our design partners need
Every feature maps to a pain an actual fGC described to us that week. If the feature doesn't solve a problem a real design partner is having, it doesn't ship. No speculative features. No copy-a-competitor features. Only things that move the needle in someone's actual practice.
Privacy isn't a feature, it's the architecture
Per-tenant databases. Local AI model. No OpenAI routing. Not because security is a sales objection to overcome — because I'm holding confidential information for competitors and the data cannot mingle. Period.
fractional general counsels first — everyone else later
We could broaden the ICP and chase every law firm. We won't. The moment we start designing for BigLaw or solo practitioners, the product stops being perfect for fractional general counsels. Focus is the whole edge.
Talk to the founder.
Demos go straight to the team that built the product — not a sales rep. 30 minutes, your clients, your scenarios. Bring the specific workflow that's breaking in your current stack and we'll show you how Sapphire handles it.