A live contract negotiation is one of the messier document-flow problems in a founder's week. The other side sends a draft. You mark it up. They send a counter. You take a call. Counsel sends three clause variants. Somebody asks why you accepted that exact indemnity cap and you can't remember whether it was something the other side dug in on or something you traded for the renewal language two redlines ago.
A working notes setup doesn't make you a lawyer. It holds the thread of what changed when, and why — across drafts, calls, and emails — so the next decision is grounded in the actual record instead of a half-remembered Tuesday. The same matter-file shape underwrites AI notes for lawyers: case research, client meetings, and court prep and shows up at deal scale in AI notes for due diligence in acquisitions.
A vault per active deal, not a folder per draft
The shape that holds up is one top-level page per deal — Acme MSA, 2026 renewal — with sub-pages for each draft version, the call recordings, the open-issues list, and your decision rationale. Capy supports unlimited page nesting, so a deal that grows three side letters and a separate DPA can fan out without forcing you to flatten or re-name folders.
The vault is plain markdown, which matters because the agent can read across every page in a single query. Three weeks into a back-and-forth, when you ask "did the other side ever explicitly agree to the audit-rights language we proposed in v2," Capy walks the deal vault and surfaces the exact moment — in the redline, the call transcript, or the email exchange — where the answer lives.
Drop the actual contract PDFs in, not screenshots of them
The expensive habit in contract work is paraphrasing the draft into your notes. You write "they're asking for a 6-month termination" instead of capturing the exact clause. By the next round, "6-month termination" turns out to be 6 months for-cause and 12 months for-convenience and you've collapsed two terms into one in your head.
Drop the actual contract PDFs onto the deal page. Capy auto-converts them to markdown via docstrange, which means the agent reads the full text — every recital, every defined term, every cross-reference — as searchable content rather than an opaque PDF. You can ask "list every clause that references confidentiality, and tell me which ones changed between v1 and v2" and get an answer grounded in the actual document. The conversion runs once per upload; the contract stays searchable from then on.
This is what makes "chat with the contract PDF" actually useful in a negotiation rather than a parlor trick. The agent isn't running OCR on every question; it's reading text it already has, line by line. The agent acting on the document, not just describing it, is the Cursor-for-documents idea applied to redlines.
Negotiation calls with speaker labels you can quote
A negotiation call usually contains the most important commitments of the deal — and the worst record. Two lawyers, two business leads, an hour of "we'd be open to that, but only if…" and the action items get summarized in a 4-line follow-up email that loses 80% of the nuance.
Record the call in Capy. The transcript comes back with speaker diarization — labels like Speaker 1: … so you can see who from your side proposed the cap and who from theirs verbally agreed. Park the recording on the deal's calls sub-page. Then ask Capy to pull out:
- Each commitment made (with the speaker who made it)
- Each open question left on the table
- Anything counsel flagged as a hard line
- Disagreements that didn't fully resolve
The next time the other side claims you agreed to something on the call, you can search the transcript and find the exact passage. The shape of the answer changes from "I think we said…" to "here's the line."
A redline log that survives counsel rotations
Every round of redlines comes with implicit reasoning that lives in counsel's head and decays the moment they roll off the deal. Two months later you're working with a different attorney who asks "why did we accept the indemnity carve-out for IP claims?" and the answer is unrecoverable.
The cheap fix is a redlines inline database on the deal page, with rows for date, version, clause, what changed, what we traded for it, and the reasoning. The database lives inside the markdown page via the :::database::: directive, so you log changes alongside the prose context — no separate tracker, no spreadsheet that decays. After each redline round, ask Capy to read the diff between versions and propose entries; you confirm or edit before they land.
Six months later, when the other side comes back with a renewal proposal that walks back something you fought for, the answer to "why did we hold this line in the first place" is a row in the database — not a guess.
A clause library grounded in your real history
Most founders end up negotiating contracts that are 80% similar to contracts they've negotiated before. The MSA template is mostly the same. The data-processing addendum is mostly the same. The variations are in a handful of clauses where the other side has leverage or a quirk.
Build a clause library page in your vault — one entry per clause type (limitation of liability, indemnity, term and termination, IP ownership, audit rights, etc.) with the language you've held, the language you've conceded, and the deals where each variant ended up. The library compounds: every closed deal contributes to the next one's first draft.
When a new MSA shows up, ask Capy to compare the proposed clauses against your library and flag where the other side's language is meaningfully tighter or looser than the patterns you've held in the past. You walk into the call with a structured starting position grounded in your own deal history rather than an attorney's instinct or a hasty Google. (The clause-library habit echoes the past-applications corpus in our writeup of AI notes for grant writing and applications.)
Counter-party history that stops you from re-learning
If you're negotiating with the same counter-party more than once — a recurring vendor, a strategic partner, a renewing customer — the second negotiation should benefit from the first. In practice it usually doesn't, because the working notes from round one are scattered.
Park a counter-party page per relationship in the vault. Use it to capture: who their lawyer is and how they negotiate, the specific clauses they reliably push on, the specific clauses they reliably concede, the operational quirks that show up in the contract (their billing cycle, their renewal-notice rules, their indemnity carve-outs). Across the next negotiation, ask Capy to read the counter-party page and propose a one-page brief on what to expect, where to anchor, and what to avoid bringing up early.
This is the kind of memory that big legal teams build into a CLM tool. A single founder running their own deals can build it as a markdown page per relationship.
A walk-up summary for counsel
When you bring counsel into a deal mid-stream — or hand it off to a different attorney for a renewal cycle — the cost of the walk-up is real. Expensive billable time spent reconstructing what's already happened.
Ask Capy to draft a one-page deal brief: the current state of every open issue, the redline path that got us here with the rationale, the commitments made on calls, the clauses where we have flex and the clauses where we don't. Counsel reads the brief in five minutes instead of an hour of catch-up. They show up to the next call already in context.
The brief sits in the vault and updates as the deal moves. The next handoff is cheaper too.
What this isn't
Capy isn't a CLM and isn't legal advice. The contract still gets reviewed by counsel; the signing still happens in your e-signature tool; the obligations still get tracked in whatever vendor-management system you use. The vault holds the thinking part of the negotiation — the rationale, the call record, the redline reasoning, the counter-party history — which is the part that's currently invisible across PDFs, emails, and call recordings.
It's also single-user by design. The deal lead owns the vault. Outputs ship to counsel as briefs, to the team as summaries, to the other side as redlines and counter-proposals through the channels you already use.
A small first test
The cheapest way to see whether this fits your work is to take one closed deal — even an old one — and rebuild it in a Capy page. Drop the final contract, the relevant call recordings, your email exchanges with counsel, and the open-issue list you kept at the time. Ask Capy to summarize the redline path and the rationale behind the three biggest concessions you made. If the synthesis catches a tradeoff you'd already half-forgotten, you've got a sense of what the next live deal could look like with the record kept properly.
Try Docapybara free. Load one active deal's drafts and call recordings, and see what the agent does with the thread.