Company rollout

Launch checklist

Confirm the workspace is production-ready before expanding beyond the pilot group

Use this checklist before you widen access beyond the original pilot team.

Workspace readiness#

  • A workspace admin, legal lead, and support contact are named and reachable.
  • Matter naming standard is documented and all existing matters follow it.
  • Library folder structure is clean and follows the agreed pattern.
  • At least one completed matter exists as a reference example for new users.
  • Playbooks are configured for the practice areas your team uses most.

Process readiness#

  • Review and approval path is documented for each output type (research note, draft, external advice, court filing).
  • Users know which outputs require human review before they leave the workspace.
  • Upload policy is defined — which document types are allowed, and any that require extra handling.
  • Onboarding guide is written and covers: how to create a matter, how to run research, how to use the Document editor, and who to ask when something is unclear.

Pilot validation#

  • The pilot group has completed at least one full workflow from intake to saved output.
  • At least one research answer has been used as the basis for a real work product.
  • The pilot group has identified the top three friction points and addressed or accepted them.
  • The workspace has been used for at least one week without the founding team needing to intervene.

Signals you are ready to scale#

Teachable workflow

New users can get productive with a short written guide and one walkthrough — no repeated live rescue required.

Clean workspace

Matters, documents, and outputs remain organised and understandable after several weeks of active use.

Visible value

The team can point to specific time saved, research quality improved, or document turnaround accelerated — from real work, not demos.

After launch#

  • Add new FAQs within the same week they appear during onboarding.
  • Update naming and storage guidance whenever the team improves its habits.
  • Review governance rules whenever the rollout expands to a new team or use case.
  • Treat documentation as an operating manual — update it whenever real usage diverges from the written guidance.