Claude Projects vs Harvey AI Litigation Copilot

“The primitive here is a named, persistent system-prompt-plus-document-store scoped to a workspace — which is genuinely the thing developers have been duct-taping together with system prompt files committed to git and copy-pasted on every new chat. The DX bet is 'make the right thing the default thing': instead of building a wrapper that injects context programmatically, Anthropic just made the UI do it natively. The gap is API parity — if Projects context doesn't flow through the API with the same scoping, developers will still be hand-rolling this, and that's the specific thing I'd want confirmed before calling this a full ship.”

“The direct competitor is ChatGPT's Custom Instructions plus Memory, which has had persistent context for over a year — so Anthropic is catching up, not leading. The scenario where this breaks is team use at scale: shared document libraries with no versioning, no access controls beyond plan-level sharing, and no audit trail mean the first time a team's shared prompt gets silently edited and causes a bad output, trust collapses. What kills this in 12 months isn't a competitor — it's Anthropic itself shipping a proper API-native version that makes the UI feature redundant for the power users who care most about it.”

“Harvey is competing against Relativity, Lexis+ AI, and Thomson Reuters CoCounsel — not some scrappy newcomers, but entrenched enterprise vendors with decades of legal workflow lock-in. The meaningful differentiator here is that Harvey is building agents that span the full discovery-to-brief pipeline rather than bolting AI onto a document review tool that predates the iPhone. The scenario where this breaks: any litigation team where outside counsel has a mandated e-discovery platform — which is most BigLaw matters — because Litigation Copilot has to fit inside an existing toolchain it didn't design. What kills this in 12 months isn't a competitor, it's Thomson Reuters acquiring or cloning this at scale for their existing Westlaw user base. Harvey wins if they get embedded in firm workflows before the incumbents catch up; the clock is ticking but they have a real head start.”

“The job-to-be-done is sharp and singular: stop re-explaining yourself to Claude every time you start a new conversation. Onboarding is as fast as it gets — create a project, paste your instructions, upload a doc, done, under two minutes to value. The product opinion baked in here is correct: most users don't need a memory graph or semantic search over past conversations, they need a stable persona and a document library, and Claude Projects makes exactly that bet without over-engineering it. The gap between shipped and needed is team permission controls — right now it's blunt-instrument sharing, and that will matter the moment any organization with more than five people tries to use this seriously.”

“The job-to-be-done here is actually three separate jobs — document review, depo prep, and brief drafting — and bundling them into a single 'Copilot' suggests Harvey is building a feature cluster, not a complete product for any one of those jobs. A litigator who needs to do deposition prep today can't necessarily replace their existing workflow with this because it requires being an existing Harvey enterprise customer, which means this isn't a standalone product decision anyone gets to make — it's an upsell decision made at the firm level. The onboarding story for the actual end user is completely opaque from the public-facing blog post: there's no demo, no workflow walkthrough, and no description of what happens in the first session when a litigator uploads case materials. I'd ship this when Harvey can show that a litigator can complete one of these three workflows end-to-end without switching back to their legacy tool — right now, the blog announcement is a feature announcement dressed up as a product launch.”

“The thesis this bets on: within two years, AI assistants aren't used as one-off query tools but as persistent collaborators with institutional memory, and whoever owns the persistent context layer owns the workflow. The dependency that has to hold is that Claude remains the preferred model for knowledge-work tasks — if GPT-5 or Gemini Ultra pulls far enough ahead on capability, users don't move their Projects, they just stop opening the tab. The second-order effect nobody is talking about: shared Projects make Claude's system prompt a team artifact, which means prompt engineering starts being treated like documentation — owned, versioned, and argued about in PRs. That's a genuine shift in how organizations relate to AI, and Anthropic is positioning itself as the place where that institutional knowledge lives.”

“The thesis Harvey is betting on: within three years, first-chair litigators will delegate the full discovery-to-outline pipeline to AI agents and spend their billable hours on strategy and courtroom execution — and firms that resist this will be cost-uncompetitive on hourly matters. That's a falsifiable claim and it's already directionally supported by the Am Law Tech Survey data on associate leverage compression. The second-order effect that nobody is talking about: if Litigation Copilot automates 60% of first-year associate discovery work, law firm leverage models collapse — fewer junior associates, compressed pyramids, and clients who finally have a credible counter to the $500/hour doc review line item. Harvey isn't riding a trend so much as it's betting on a specific labor substitution event in a profession that has historically been immune to it. The dependency that has to hold: courts don't impose AI disclosure requirements that create enough liability friction to slow adoption at the firm level. Harvey is early on this specific litigation automation bet — not first, but well-positioned.”

“The buyer here is unambiguous — it's the AmLaw 200 litigation partner or the VP of Legal Ops at a Fortune 500, writing a check from a technology budget that already exists and is already allocated to tools like Relativity and Westlaw. Harvey's wedge is that they're already inside these firms via their base enterprise contract, so Litigation Copilot is expansion revenue, not new logo acquisition — that's a structurally sound go-to-market. The moat is workflow integration: once a firm's matter data, privilege logs, and brief templates are running through Harvey's pipeline, switching cost is real and compounding. The risk I'd stress-test is the unit economics on agentic tasks — if running a full discovery review burns $800 in inference costs that Harvey has priced at $600, the margin story inverts fast as usage scales. The business survives a 10x model price drop because the value is in the workflow orchestration and the legal-domain fine-tuning, not the raw inference.”