The setting
is an AI platform for legal work, used by law firms and the legal teams of companies. is its software that uses AI agents to draft, negotiate, review, and manage contracts.
Completed training and recorded activity tell different stories about readiness for a live review.
Early intervention protects go-live dates, while planned pauses and unrecorded progress make unnecessary outreach costly.
Who you’d be doing this for
“Our training box was green, then the general counsel asked who'd actually reviewed a supplier contract. I had to ask every group separately.”
Jun Lin · Legal Operations Director · a character in this brief
Sponsors an enterprise legal department's onboarding and reports readiness to the general counsel.
What is at stake
Enterprise legal customers reach go-live discussions with training complete and their first live review still uncertain. You decide when conflicting Salesforce and Snowflake evidence warrants an AI flag, and when a CSM must first establish what happened.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- standard milestones vs account-specific success plans
- early flags vs unnecessary sponsor outreach
- recorded activity vs readiness for legal work
- broad stall coverage vs predictable event checks
Why Harvey
Onboarding includes tailored legal workflows and agents built on real matters, so attendance alone does not establish readiness for daily use.
Written with these in mind
Not your kind of problem? 56 more at Harvey, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Harvey. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Legal Engineer (Law Firm, Corporate) (opens in a new tab)
- Legal Engineer, Mexico (opens in a new tab)
- Legal Engineer (Law Firm, Litigation/Regulatory) (opens in a new tab)
- Legal Engineer Manager, Germany (opens in a new tab)
- Lead product demonstrations tailored to the context of various law firm practice groups and in-house legal teams, asking questions to validate how Harvey can add value and then showcasing Harvey’s features and benefits relevant to each prospective client’s potential use cases.
- Act as the “Voice of the Customer,” using your legal perspective to help the broader sales team to develop and implement more effective strategies and synthesize customer feedback for the product team through a legal lens.
- Customer Success Manager, Enterprise, EMEA (opens in a new tab)
- Training & Enablement: Evangelize the power of Harvey as you meet with end users and collaborate with Legal Product Specialists to enable end users to adopt Harvey on a daily-basis as it becomes a “must have” product.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about people starting something and never quite finishing it.
CSMs discover missed UAT steps at account reviews despite scientists using the application.
You decide whether the watcher can classify a missed step as a stall or must ask the CSM to interpret conflicting notes first.
New enterprise customers remain active while their onboarding steps stall.
You decide whether AI can assign a stalled milestone from conflicting notes and activity, or must ask the CSM to establish the step first.
Strategic developers reach weekly calls with onboarding work still stalled after cases close.
You must decide whether the AI only flags missing evidence or also names the stalled milestone for CSM review.
The same setting, from another role
Each is set around Harvey’s Contracts, written for a different role. They’re separate briefs, not the same scenario.
Fewer lawyers keep coming back to contract review in Word each week, even as more of them try it for the first time.
You decide whether the AI may rank a release as the leading explanation when release exposure and user tenure point in different directions.
Business owners needed another explanation for 11 of 18 contract decisions in discovery.
You must choose what a new decision experience preserves, what it simplifies, and whether customers will return to it.
Lawyers could lose usable histories for 1,200 active contract reviews in 48 hours.
You must weigh continuity in live negotiations against carrying uncertain verification claims past an irreversible cutover.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a person's earliest brush with a product into a habit they keep coming back to.
Sixty-two percent of newly activated workspaces do not return for a second production session within 21 days.
You must weigh a scalable configuration-and-enablement path against a simpler setup change that uses the same capacity.
New enterprise accounts are starting tables but not returning to run a second workflow.
You have to weigh a fast activation path against a promise that still feels safe for RevOps.
New desktop users are skipping iOS setup and staying in a single-device inbox habit.
You need to decide how prominently mobile setup belongs before users reach their first inbox.
