The legal industry has never moved faster, or with more hesitation. Every firm and every in-house team is testing the waters with AI — piloting GenAI for contract review, embedding copilots in workflows, surfacing insights from matter data. The pattern is consistent: pilots multiply, practice does not.
Most teams are not stuck because of the technology. They are stuck because they treat “pilot” and “practice” as a binary, when the canon names five stages between them.
The pulse — AI everywhere, ROAI missing
- 95% of legal professionals expect GenAI to be embedded in daily workflows within five years
- Only 20% are measuring return — strategy lags behind speed
- Most GenAI adoption is stuck in pilot mode — few defined metrics, little change enablement, limited business alignment
Adoption is not the finish line. It is where the real work begins.
The canonical 5-stage AI Lifecycle
Every AI capability the function deploys runs the same five stages. Each has its own discipline; skip any one and the capability either fails outright or operates as a hidden liability.
- Concept. Use case identified; problem and outcome defined; success criteria written. Most legal AI pilots skip the success criteria and call it discovery. The output of Concept is a one-page brief, not a vendor demo.
- Build. Bounded technical pilot with named users, defined input data, named owner. Time-boxed: four to eight weeks. Output: a working capability and the decision to advance, iterate, or sunset.
- Deploy. Production rollout with monitoring, training, change-management lead, and entry into the AI BoM. The most common legacy failure is shipping Build outputs as Deploy because no one defined what Deploy meant separately.
- Operate. Ongoing use with documented controls, incident response, and quarterly health review. This is where most legal AI silently degrades — model drift, data drift, vendor change, regulatory update. Operate is a discipline, not a state.
- Sunset. Planned retirement with data handover, audit log preservation, and explicit decommission. Functions without a Sunset discipline accumulate operational debt that becomes visible only when the regulator or board asks.
“Pilot” typically covers Concept and Build. “Practice” covers Deploy, Operate, and Sunset. The whole pilot-to-practice problem is the three-stage gap most functions never explicitly cross.
Stack spotlight — read benchmarks against the Lifecycle
Legal-specific GenAI copilots are rising. Harvey Assistant achieved 94.8% accuracy on Document Q&A, outperforming human lawyers on multiple tasks. CoCounsel (Thomson Reuters) scored 77.2% on document summarization. Vincent AI showed promising results in drafting and legal research. The Vals Legal AI Report (VLAIR) gives the function its first credible benchmark. But these are Concept- and Build-stage validations — they prove a capability is possible, not that it is operable. Tech-ready does not equal Lifecycle-ready.
Five moves to scale legal AI past the pilot
- Define the outcome, not just the use case. Every Concept-stage brief names a measurable outcome and the ROAI 4-Quadrant cell it serves (Value, Risk, Capability, Velocity). Skipping this step is the most common silent failure.
- Map the data — structured, relevant, secure. Build cannot start until the data has been audited, classified, and assigned an owner. This is Pillar 2 (Data & Knowledge Infrastructure) doing its job. See Module DAT-01 (Knowledge Readiness Audit).
- Train for trust — human and AI actors. Onboarding is not a one-time event; it is the connective tissue between Build and Deploy. The AI Literacy Curriculum (Module TAL-01) operationalises this.
- Create adoption loops — feedback to iteration to improvement. Operate-stage feedback (from users and from monitoring) flows back into the Build queue. Without the loop, the capability calcifies.
- Align with canonical KPIs. Tie every output to the ROAI 4-Quadrant scorecard and to the function’s position on the Maturity Stack. Generic productivity metrics do not survive a serious board review; ROAI evidence does.
The deep take — why scaling is hard, structurally
It is not hallucinations. Not integrations. Not budget. The structural diagnosis is that most legal teams are tool-rich and structure-poor. They lack a framework for what “good AI” looks like (the Defensibility Posture Statement); a model for build versus buy (Capability Portfolio + ROAI 4-Quadrant — see Issue 14); an intake process to surface repeatable, high-value use cases (the Legal Front Door — see Issue 12).
The fix is the canonical operating model. Scale is a Lifecycle problem, not a tool problem. Functions that name each of the five stages — with explicit owners, metrics, and governance per stage — ship more capabilities, ship them safer, and ship them with the Defensibility evidence the board recognises. Functions that do not, accumulate pilots that quietly become shelfware.
Share this issue