DraftWise

What it is

DraftWise is an AI-native contract drafting and negotiation assistant for transactional lawyers, built around a firm’s own precedent library. It lives in Microsoft Word as an add-in, surfaces clause suggestions and redlines grounded in the firm’s prior deals (not generic templates), and learns each negotiation team’s preferred fallback positions. Originally built by ex-Allen & Overy lawyers; targets BigLaw transactional practices and large-firm corporate deal teams as its core customer base.

Why it shows up in Legal Ops stacks

• Precedent-grounded suggestions, not generic templates. DraftWise indexes the firm’s own document store (iManage, NetDocuments, SharePoint) and surfaces clauses from real prior deals. When a lawyer drafts a representations-and-warranties section, the suggestions are pulled from how the firm’s own deal teams have actually drafted the section in past matters — not a library of generic boilerplate.
• Negotiation-pattern recognition. Tracks counterparty patterns across the firm’s deal history. “Acme has accepted this MAC clause shape in three prior deals” is the kind of context the firm previously held in senior partners’ heads; DraftWise surfaces it for the associate drafting the next deal.
• Word-native UX, no platform migration. Same posture as Spellbook — meets lawyers in Word. No new system to learn.

Pricing reality

DraftWise is custom-quoted; no public pricing page. Based on customer-side reports, mid-market transactional firms (50-200 lawyers) land in roughly the $50K-$200K annual range depending on seat count and document-corpus size. Large firms (500+ lawyers) typically negotiate enterprise contracts in the high-six-figure to low-seven-figure range with multi-year commits. The firm’s existing iManage / NetDocuments licensing is a prerequisite expense — DraftWise indexes those systems but doesn’t replace them.

The pricing posture is BigLaw-firm-tier, not boutique-tier. Per-seat economics don’t compete with Spellbook at the small-firm end of the market.

Best for

• BigLaw transactional practices (M&A, finance, capital markets) where the firm’s own precedent is the deal team’s competitive advantage and the precedent library lives in iManage / NetDocuments.
• Large in-house corporate teams (Fortune 500 legal departments) with mature precedent libraries and a transactional volume that justifies the spend.
• Firms where the senior-partner “I remember how we did this in the Acme deal” knowledge is the bottleneck — DraftWise surfaces that institutional memory at draft time.

Versus the alternative

• vs Spellbook. Spellbook starts cheaper and works against generic clause libraries plus the firm’s own templates if connected. DraftWise’s precedent-grounded suggestions are stronger but the price point is multiples higher. Pick Spellbook for sub-20-lawyer firms or when the firm’s precedent library isn’t centralized enough to index meaningfully. Pick DraftWise when the firm’s competitive edge IS the precedent library and the spend can be amortized across enough deals to matter.
• vs Harvey. Harvey is broader (litigation + transactional + research) but generally less specialized at transactional drafting. Pick Harvey if the firm wants one platform across practice areas. Pick DraftWise if the transactional practice is the one that drives the revenue and demands specialist tools.
• vs ContractPodAi / Ironclad (full CLM). Different tier. CLMs handle the contract lifecycle (workflow, approval, repository, e-signature). DraftWise handles drafting and negotiation. Most large firms run both; the question is whether the drafting layer is DraftWise, Spellbook, or another tool.
• Status quo (no precedent-search at draft time). The default in firms without a precedent-search tool. The cost shows up in associate hours spent searching iManage manually for “the last time we did a deal like this,” and in inconsistent-with-firm-precedent drafts that surface in deal review.

Watch-outs

• Document-store integration is the binding setup cost. DraftWise’s value depends on it indexing the firm’s actual precedent corpus. Firms with messy iManage or scattered SharePoint sites will see weaker suggestions until the corpus is cleaned. Guard: scope the rollout to one well-organized practice area first; expand once the corpus tagging proves out.
• Confidentiality posture for indexed precedent. Indexing firm-internal documents into a third-party AI service raises confidentiality questions, especially for matters under engagement-letter confidentiality or with client-sensitive content. Guard: review the firm’s outside-counsel guidelines and DraftWise’s data-handling commitments per the firm’s general counsel before contracting; some firms negotiate dedicated-instance deployments.
• Annual pricing minimum makes 1-year pilots expensive. DraftWise’s contracted pricing typically requires multi-year commits or substantial annual spend. Guard: negotiate a 6-month proof-of-value period with named success metrics (suggestion-acceptance rate by associates, deal-cycle reduction) before signing the multi-year.
• Limited litigation utility. DraftWise is a transactional drafting tool. Guard: firms with primarily litigation practice should look at Harvey, Casetext, or Thomson Reuters CoCounsel instead.