Built for the agent era
Agents do the work. You approve what matters.
Three CLIs for the contract workflow — drafting an NDA, reviewing what comes back, negotiating, converting to PDF, collecting signatures with a tamper-evident audit trail. Designed so an LLM agent can run 90% of the operational work and a human stays in the loop only for the gates that actually need a human gesture.
The workflow at a glance
Each box is a separate CLI you install and use on its own. The arrows are file types — the agreed text flows out of one tool and into the next. There is no proprietary glue, no shared database, no daemon process. Just three command-line tools that read and write standard file formats.
The tools
Draft, review, and negotiate NDAs against your own house playbook. Deterministic by default; opt-in LLM augmentation.
pipx install nda-review-cliHonest DOCX → PDF conversion with batch processing, parallel runs, font validation, and pluggable backends.
npm i -g docx2pdf-cliTry the NDA review live
Sandboxed browser demo runs draft, review, and the negotiation simulator end-to-end. No install. No sign-in.
Open the live demo →Built for an agent-driven workflow
Most legal-tech assumes a human at a desk: dashboards, threaded comments, in-app redlining. These CLIs assume the opposite — an LLM agent doing the operational work and a human approving the things that legitimately need a human. Drafting, scoring, suggesting amendments, sending, tracking: agent. Signing, escalating non-negotiable conflicts, accepting a final position: human, with a deliberate gesture.
- Drafts NDAs from your house templates
- Reviews counterparty docs against your policy
- Proposes amendments using your stance + priorities
- Sends documents for signature, tracks status
- Verifies signed PDFs and audit chains
- Signing — every signature requires a per-signer token
- Escalations on non-negotiable redlines
- Accepting the final agreed position before finalize
- Anything outside the deterministic policy guardrails
The MCP server in sign-cli exposes every command to any MCP-aware client (Claude Code, Cursor, Codex). Same per-signer guardrails — the agent never sees the approval token, the human does. Read the MCP guide for the wire-up.
Why three small tools instead of one big platform
Most contract operations products are SaaS suites. They want every step in one dashboard, every document in their database, every signature behind their identity provider. That's a fine business model for them, but it makes contract operations expensive, opaque, and — critically for an agent-driven workflow — hard for an agent to drive without scraping or RPA glue.
The three CLIs here take the opposite stance. Each does one thing well. None of them require an account, a subscription, or a network call you didn't ask for. An agent can drive them over stdio or MCP; a human can drive them from a terminal. You can swap any one of them, fork them, or audit the source end to end. Together they cover the same workflow a SaaS suite would, with the documents and audit trail on your machine — and an interface an agent can use natively.
Where to go from here
- The workflow — step-by-step walkthrough of how the three tools chain together, with copy-paste commands.
- Install — one page covering all three install paths.
- nda-review-cli — drafting, reviewing, and negotiating NDAs against your house policy.
- docx2pdf-cli — DOCX to PDF, honestly. No surprises, no hidden conversions.
- sign-cli — multi-provider e-signature with audit-grade evidence.
- Comparison — how the suite stacks up against SaaS contract platforms.
- Changelog — what's new and what's coming next.
- Principles — what these tools have in common and what they refuse to do.