Claude Design NDA Triage Internal Tool Build

Claude Design for NDA triage is the most concrete legal-ops use case I've seen since Anthropic shipped the tool on April 17, 2026. Most in-house legal teams handle 40-200 NDAs per month, a flat triage problem that's been waiting for a flat triage UI. The traditional path: a vendor contract, a six-week IT procurement cycle, or a half-broken Outlook rule. The Claude Design path: one person, one prompt, half a day. This walks through how to build a working NDA triage internal tool using Claude Design plus Claude Code, what to ask the model for, and where the output is genuinely production-ready versus where it's prototype-only. The build references Anthropic's Cowork legal plugin — open-sourced February 2026 — for the underlying triage logic.

What an NDA triage tool actually needs to do

Before prompting Claude Design, get the spec right. An NDA triage tool isn't an NDA review tool, it's a routing tool. The job is sorting incoming NDAs into three buckets:

- Standard approval, vanilla mutual NDA, counterparty pre-approved, no edits to the firm template. Auto-route to e-signature. - Counsel review, non-standard terms (assignment, IP carve-outs, non-compete adjacent language) but inside known-acceptable bands. Routes to a designated reviewer with a 48-72h SLA. - Full review, anything outside known-acceptable bands, unfamiliar counterparty, or a strategic deal. Routes to lead counsel with no SLA, scheduled directly.

The tool needs four screens: an inbox of incoming NDAs, a triage interface (categorize + add notes), a queue dashboard for each bucket, and an audit log. Each NDA record needs counterparty name, document hash, redline status, current bucket, assigned reviewer, and timestamps.

That spec is small enough to fit in a single prompt. Anthropic's Cowork legal plugin /triage-nda command already handles the analysis layer. Claude Design handles the interface layer. Claude Code wires them together. Three components, one tool.

The actual build: prompt sequence I'd use

Open Claude Design (Pro tier or higher per the Anthropic pricing page, $20/month is enough). The first prompt:

*"Build me an NDA triage dashboard. Three columns: Standard Approval, Counsel Review, Full Review. Each NDA card shows counterparty name, date received, redline status (clean / minor edits / non-standard), assigned reviewer, and a status pill. Sticky top bar with a counterparty search and a 'New NDA' upload button. Match the brand tokens I'll attach."*

Attach a screenshot of your firm's existing site or upload your brand guideline PDF. Claude Design extracts colors, typography, spacing as defaults. Iterate on the visual until it looks like your firm, usually three to five rounds, ten minutes total.

Second prompt: *"Add a triage interface. When I click an NDA card, open a side panel showing the document text, a redline diff, three large action buttons (Standard / Counsel / Full), a free-text notes field, and an assign-to-reviewer dropdown. Save action triggers a status update on the card."*

Third prompt: *"Add an audit log view. Filterable by date range, reviewer, bucket. Each entry shows NDA name, action taken, reviewer, timestamp, notes."*

When the prototype is right, hand it off to Claude Code with one instruction: *"Build this as a deployed app. Use [your firm's preferred stack, typically Next.js + Postgres or similar]. Add auth via [your firm's SSO provider]. Wire the upload to call the Cowork legal plugin /triage-nda command for initial categorization."*

Claude Code handles auth, database schema, deployment to Vercel or your firm's preferred hosting. The how to use Claude Design in Claude Code legal workflow covers the broader pattern.

Where the output is production-ready and where it isn't

Honest assessment: not every layer of this build is shippable on day one.

Production-ready out of the box: the visual interface, the routing logic between buckets, the audit log, the basic upload flow. Claude Design's React output is clean enough to deploy. Claude Code's authentication and database schema are conventional patterns it handles well.

Production-ready with review: the integration to your firm's existing systems. If your firm runs DocuSign for e-signature, iManage for document management, or NetDocuments for storage, the integration patterns are documented but require your IT team to validate the API tokens and access scopes. Claude Code can write the integration code; your IT team should review it before production traffic.

Prototype-only: the actual NDA classification. The Cowork plugin's /triage-nda command provides a starting categorization, but a triage tool that handles privileged or strategic counterparty NDAs needs human judgment in the loop. The tool routes; the lawyer decides. Don't auto-approve a Standard Approval bucket without a human spot-check sample. Per the United States v. Heppner ruling, the deployment surface and the privilege posture of inputs matters, make sure you're using Claude Team or higher (Anthropic's no-training-on-data tier per the pricing page), not consumer Claude.

The second-order read: legal-ops directors who ship this kind of tool get pulled into product-management work they didn't sign up for. Plan for ongoing maintenance, the NDA template changes, counterparty list changes, IP language patterns evolve. A tool you own is a tool you maintain. Third-order: the maintenance load is still less than the cost of vendor contract renewals plus the dev team's queue, but it's not zero. Budget two to four hours per month of legal-ops time for ongoing tool care.

What this replaces and what it doesn't

Replaces or pressures: generic NDA-management SaaS subscriptions in the $400-$2,000/month range for mid-size firms. Generic intake forms cobbled together from Google Forms or Typeform. Outlook-rule triage that breaks every quarter. The half-built SharePoint dashboard nobody updates. For each of these, an internally-shipped Claude Design + Claude Code tool wins on customization, ownership, and total cost over 18+ months.

Doesn't replace: your contract lifecycle management (CLM) platform if you have one, your e-signature provider, your document management system, or your matter-management software. Those platforms own data and workflows that an NDA triage tool needs to integrate with, not duplicate. Per the conflict-check dashboard mockup walkthrough, the same logic applies, these tools handshake with vendor systems, they don't replace them.

The deeper read: the right unit of analysis isn't "Claude Design replaced our vendor." It's "we used to file a Jira ticket and wait six weeks for a vendor evaluation. Now we ship the tool ourselves and integrate to our existing vendors where it makes sense." That's a procurement-velocity unlock, not a vendor-elimination unlock. The Claude Design for legal operations 2026 anchor frames the broader pattern.

The Bottom Line: The verdict: an NDA triage tool is the canonical first build for any in-house legal team trying Claude Design. The spec fits in three prompts, the brand integration is straightforward, and the routing logic is bounded enough that the prototype gets to working in half a day. Don't skip the human-in-the-loop step on the Standard Approval bucket — let the tool route, let counsel sample. Pair this build with Claude Team ($25/seat/month) or higher for the data-handling guarantees that match privileged work.