Turn NDAs around same-day

Head of sales/ops processing several NDAs/week · Setup ~20 min (install skills + configure playbook); first NDA batch processed in <30 min once installed.

LegalEdit flowon X◆ new (unverified) 87

step 1connector

Load playbook and inbound NDA files

⚡ bring your own tool

step 2ready

Initial read and triage summary per NDA

contract-review4 alts

step 3ready

Deviation analysis vs. playbook

contract-review4 alts

step 4ready

Generate redlines for deviating clauses

redline-sentry4 alts

step 5ready

Prioritize redlines and plan pushback strategy

plan-contract-pushback4 alts

step 6partial

Escalation routing and reply email draft

legal6 alts

step 7partial

Log the sign/redline/escalate decision

decision-logger

Did this recipe work for you?

What you get

▸Triage table across the NDA batch with per-NDA verdict (sign / redline / escalate) and severity summary
▸Redlined NDA documents with changes scoped to deviating clauses only
▸Ready-to-send reply email drafts per NDA (clean sign-off, marked-up return, or escalation note)
▸Decision log citing the specific playbook rule behind each verdict — usable as an audit trail

tools: No paid external tools required; email/drive access uses existing accounts

tokens: ~$1-3 per NDA depending on document length and number of deviating clauses

≈ $5-20/mo at 10-30 NDAs/week

What stays yours

· Attorney or qualified legal counsel must review any NDA flagged for escalation (poison clauses, novel indemnification, IP assignment, or unlimited liability) before a response is sent — AI output is a draft aid, not legal advice.
· The user must configure the negotiation playbook and escalation thresholds once; the recipe does not self-calibrate to deal context, deal size, or counterparty leverage without human input.
· Final send decision and actual transmission of the reply email remain with the user — no step sends automatically.

The problem

When I receive inbound NDAs that need a same-day response, I want one workflow that reads each NDA, flags deviations from our playbook, generates targeted redlines, and outputs a clear sign/redline/escalate decision with a ready-to-send reply — so I clear the queue in under an hour without waiting on legal for routine NDAs.

Cybernetic layers

Memorybyo

No harvested memory artifact covers NDA-specific state (counterparty history, prior redline positions, accepted fallbacks). Use a local markdown log or Google Sheet as a running negotiation ledger per counterparty.

Background-schedulingnot-applicable

NDA review is event-driven (triggered by an inbound NDA), not scheduled. A Claude Code cron could watch an inbox folder and trigger the recipe on new arrivals, but that automation is not assembled from library artifacts today.

Harnessready

Claude Code is the runtime. Install each skill into ~/.claude/skills/ and invoke in sequence. Cowork is also supported.

Click any step to see what fills it — and the ranked alternatives you can swap in.