I built a legal ops dashboard in Cowork. Here it is.
What you'll get:
The slide deck from my L Suite presentation on AI-native legal workflows
The Legal Command Center -- free, public, ready to install
Where to go if you want the full walkthrough
L Suite Claude Series
Last week I presented to the L Suite community for Part Two of their Watch Claude for Legal: In-House Edition.
I presented two AI-native legal workflows I built and use. I don't usually give everything away at once. This time I am.
Build 01: The Legal Command Center
A live legal-ops dashboard built in Cowork. Pulls live from Slack, Notion, and Google Calendar. Six companion skills handle triage, weekly reports, monthly channel analysis, deadline tracking, and matter logging. Built for me. Now you can use the same skills and architecture to customize the Legal Command Center for your team.
Build 02: The Product Capabilities Playbook
Two pipelines. One corpus. No lawyer fielding the same question twice.
The ingestion pipeline runs in the background. AI scans Slack channels, help pages, and the website -- identifying product features, categorizing them, and drafting entries for the corpus. I review and approve the wording before anything goes live. The corpus doesn't update without me. That's the point.
The answer pipeline is what everyone sees. A question lands in Slack. n8n queries the approved Notion corpus, bundles the right answer, Wordsmith composes the response, and it replies -- directly in thread. No lawyer required.
The corpus is the product. The bot is just the interface. Legal reviewed the record once. The bot answers forever.
Same goal. Different architectures. The recording explains why.
Here's everything from the session
Watch the recording: https://www.lsuite.co/resources/claude-for-legal-part-2
Download: My presentation slide deck
Grab the Legal Command Center on GitHub -- free, MIT licensed, plain-English setup, no engineering required: https://github.com/JeffordsGreenberg/ljg-legal-command-center
Want the full walkthrough of how to use GitHub?
The GitHub repo gets you the tools. The Field Guide post gets you everything behind them (coming later this week).
