Host a web form collecting: requester name, email, company, NDA type (mutual vs one-way), purpose, and any special terms; validate inputs server-side.
On submission, generate a prefilled NDA from your approved template by substituting the collected fields; use a document generation API (PandaDoc, DocuSign Template, or a server-side DOCX library).
Route based on NDA type and deal size: standard NDAs below a threshold can auto-send via e-signature API; non-standard or high-value NDAs route to legal review queue before sending.
Send the generated NDA to the counterparty for e-signature; upon completion, also obtain your authorized signatory's signature via an embedded signing ceremony.
Store the fully executed NDA in your CLM with metadata extracted from the form submission and the signed document.
Notify both parties with the executed document attached, and set renewal/expiry alerts per your alerting pipeline.
Known gotchas
Allowing requesters to freely edit NDA terms before sending defeats the purpose of a self-service workflow; lock editable fields to only approved variable fields (names, dates, purpose) and send any clause changes to legal.
Authorized signatory logic must be enforced server-side; do not rely on client-side form validation to determine whether a deal requires legal approval.
Mutual NDAs require both parties to sign as both disclosing and receiving parties; ensure your e-signature template has signature blocks for both sides or the document may be legally defective.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp