About

A special education teacher running everything on paper — I transferred his grading book into Excel so the charts built themselves, and when I saw him cutting and taping worksheets together by hand despite having a computer on his desk, I digitized those too. Neither fix was my job. I just couldn't not see it.

That was twelve years ago. The tools have changed considerably. The instinct hasn't moved at all.

I start with the file cabinet.

Every broken Legal Operations process has a physical tell. A file cabinet organized by first name when it should be organized by response date. An inbox that became the intake system. A spreadsheet that predates the portal by six years and has a higher adoption rate than the portal. A process where nine people submit preferences manually and one person spends three days synthesizing the results before anyone can have the actual conversation.

The system exists. The work is happening. It's just happening in the wrong place, in the wrong format, by the wrong person too often.

Legal Operations is, at its core, how a legal function quantifies and manages risk — and that only works when the processes underneath it are efficient enough to be legible. You can't measure what you can't see. You can't control what lives in someone's inbox.

Before I touch a single platform, I find where the work actually lives. Not what the process document says. Not what the org chart implies. What is physically, observably happening right now. Then I build the system that moves it where it belongs and makes it structurally impossible to go back to the way it was.

If you want something truly done — not documented, not recommended, not scoped for a follow-on engagement — that is what I build.

The Bureaucracy Lab works with small in-house legal teams. One or two person Legal Ops departments where the same person who reviews the invoices also designs the intake workflow, tracks the compliance calendar, manages outside counsel relationships, and gets asked for a PowerPoint of the dashboard they built last quarter.

Those teams know exactly what's broken. They've documented it. They've escalated it. They've built the business case, received the nod, and watched it get routed to Finance in March where it has been waiting for the Q3 budget cycle ever since.

They don't need another assessment. They don't need a maturity model. They don't need a 64-slide deliverable with recommendations deferred to Phase III. They need something built. Something that runs. Something that doesn't require the one person who understands it to manually hold it together every week.

Eight years of Legal Operations work inside corporate and public sector in-house legal departments — Fortune 500 and enterprise SaaS environments, both sides of the in-house table.

I work as a one-person practice with AI as the operational layer — which means the thinking is mine, the builds are mine, and the cost structure reflects neither.

The first thing I did walking into a Fortune 500 legal department was go through an overflowing subpoena file cabinet and reorganize it by response date because you cannot build the portal until you understand what the portal needs to hold. A treasury deadline automation followed that sent payment notifications at exactly 11:01am the day before a hard wire deadline, because that is what eliminating the risk actually required. Not approximating it. Eliminating it. Five simultaneous automated workflows built and deployed at the same time across compliance tracking, corporate governance routing, document management, regulatory brief tracking, and signature delegation. An AI intake strategy and governance framework built from scratch at an enterprise SaaS legal department. A nomination rating system that converted three days of manual synthesis into a single view a director could walk into a meeting and present.

The through line across all of it: start with what is actually happening, not what the process document says is happening. The file cabinet. The inbox. The spreadsheet nobody will admit is the real system of record. That is where the build starts. Every time.

The Bureaucracy Lab exists because the same patterns show up in every legal department regardless of size, budget, or how many transformation initiatives have been announced since the last one was quietly shelved. The intake nobody uses. The dashboard nobody opens. The exception that became the policy. The charter on version seven with ownership still listed as TBD.

These problems are well-documented. They are frequently discussed. They are rarely fixed — not because the solutions are complicated, but because fixing them requires someone who understands both what the legal requirement actually is and how to build the system that meets it. Most people have one or the other. This practice was built on having both.

The products in this store document the patterns. If you have pulled an adoption report that came back at 41%, there is a mug for that. If you have sent the invoice review request four times and it is now day 74, there is a mug for that too. If you have built the dashboard, sent the link, and spent the next six months making PowerPoint decks of the dashboard — there is absolutely a mug for that.

Buy it for yourself. Buy it for the one other person on your team who will recognize it without explanation. Buy it for your GC as a form of communication that does not require scheduling a meeting.