Browse docs
Company rollout
Team setup
Roles, naming conventions, and workspace standards before expanding access
The pilot becomes a real rollout when ownership is explicit and the operating model is written down. This page covers the steps to take before adding your second wave of users.
Define clear owners#
Legal lead
Owns workflow quality and review standards. Decides what counts as acceptable AI output for different task types.
Workspace admin
Keeps naming, folder structure, and playbook standards clean. Manages user access and onboarding.
Executive sponsor
Clears blockers and ties the rollout to a specific business outcome — not general AI curiosity.
Pilot users
First wave of real users. Their patterns, friction points, and shortcuts inform every decision before broader rollout.
Workspace naming standards#
Agree on a matter naming pattern before the first live project enters the system. A consistent format makes matters readable to anyone on the team and keeps the overview page useful.
Recommended pattern: Client or BU / Issue or Project / Year
Examples:
Acme Corp / Supply Agreement Review / 2026HR / Employment Policy Update / Q2Litigation / Sharma v. Singh / 2026
30-day rollout plan#
Week 1: prove one workflow
Run a small number of matters end to end with the pilot group. Note where the team hesitates, leaves the product, or falls back to email.
Week 2: fix the operating model
Revise naming, folder, and review standards based on real pilot behaviour — not theory. Write down what changed and why.
Week 3: train the next group
Onboard the next wave with a short written guide, one or two example matters, and a walkthrough of the most common workflow. Don't teach by demo alone.
Week 4: decide on expansion
Look for repeatable value, not novelty. Expand only when the team can explain how the product should be used without needing live support.
Before adding more users#
- The matter naming standard is written down and the existing matters follow it.
- The folder structure in the Library is clean and predictable.
- Review expectations for external-facing outputs are explicit and communicated.
- At least one completed matter exists as a reference for new users.
- The workspace admin has a process for onboarding new users consistently.
On this page