You received a contract. It is 40 pages. You have 30 minutes before the call to sign or push back. You could skim it for the obvious stuff — payment terms, termination clause, non-compete — and hope you did not miss anything material. Or you could run 4 prompts and get a 1-page brief that tells you exactly what you are agreeing to and what to push back on.
Today I am going to show you how I process any long document — vendor contracts, employment agreements, partnership terms, loan documents — in under 10 minutes using a sequence of prompts I have refined over dozens of real contracts.
Fair warning: this is not legal advice. The prompts extract and organize information. They do not replace a lawyer for anything material. But most contracts you will sign in your career are not high-stakes enough to warrant $500/hour legal review. This is for everything below that threshold.
The Problem with Reading Contracts
The instinct when you receive a contract is to read it front to back. This is the wrong approach.
Long documents are designed to be exhaustive, not readable. Standard terms, definitions sections, and boilerplate language exist for legal completeness, not to communicate risk to you. If you read front to back, you finish knowing what the document says but not what it means for your specific situation.
The useful information in any contract is concentrated in four places: the obligation schedule, the limitation of liability section, the termination conditions, and the one or two unusual clauses that are not standard. Everything else is either boilerplate or consequences of those four things.
The Plain-Language Summary (2 minutes)
Paste the full contract text. Then use this prompt:
I need to understand this contract before a call in 30 minutes. Give me a plain-language summary with ONLY: 1. What am I agreeing to do (my obligations, timeline, and deliverables) 2. What am I getting in return (payment, access, rights, or services) 3. How long does this last and how do I get out of it 4. What happens if either party fails to deliver Keep each answer to 2-3 sentences. Skip definitions, recitals, and boilerplate.
Why this works: This takes 2 minutes and gives you the core structure. You will already be ahead of 80% of people who sign contracts by having these four answers clearly stated.
The difference: The payment terms are on page 3. The auto-renewal clause that locks you in for another 12 months is on page 34.
The Risk Extraction (2 minutes)
This is where passive reading falls apart. The AI specifically scans for asymmetry and ambiguity rather than just summarizing.
Now read this same contract looking for risk. Flag anything that is: 1. Non-standard (unusual compared to typical agreements of this type) 2. One-sided in favor of the other party 3. Vague enough that it could be interpreted against me later 4. A potential trap (auto-renewal, evergreen clauses, broad IP assignment, indemnification without limits) For each item, give me: the clause name, the risk in plain language, and whether it is a dealbreaker, negotiable, or acceptable.
The test: I have used this on vendor contracts and had it surface an IP assignment clause that would have transferred ownership of any work I created — not just the deliverable — to the vendor. The clause was buried in the definitions section on page 7.
The Obligation Timeline (1 minute)
This is for execution, not negotiation. Once you sign, this table is your compliance checklist.
From this contract, extract every obligation with a deadline or trigger. Format as a table: | Party | Obligation | Deadline/Trigger | Consequence if missed | Only include specific obligations, not general best-efforts language.
Why it matters: Payment due 30 days after delivery. Notice required 60 days before termination. Quarterly reporting due the 15th. Miss any of these and you are technically in breach, even if the other party never mentions it.
The Negotiation Prep (2 minutes)
This is where the brief pays off on the call. Instead of saying “I had some concerns,” you walk in with three specific requests and the language to back them up.
Based on this contract, what are the 3 things I should try to change before signing? For each: 1. The exact clause or section (quote it) 2. Why it is unfavorable to me 3. What I should ask for instead (specific alternative language) 4. How likely they are to agree (high / medium / low) and why
The power move: The specificity signals that you read it carefully, which changes the dynamic of the negotiation entirely.
A Real Example
I received a 38-page SaaS vendor contract last year. Running all four prompts took 9 minutes. The brief surfaced:
None of these were dealbreakers. All three were negotiated in a 20-minute call. The vendor’s response to the first request was “most people don’t catch that.” That is the point.
When to Use This
Use your judgment about stakes. A $50/month SaaS renewal does not need a 4-prompt review. A $50,000 annual contract does.
The Compound Effect
The more contracts you process this way, the faster you get at spotting the patterns yourself. After a few dozen reviews, you will start recognizing auto-renewal language on sight. You will scan to page 8 for the IP clause before reading anything else. You will know which clauses are boilerplate and which are negotiated.
The prompts accelerate the pattern recognition you would eventually develop anyway. You are not outsourcing judgment — you are training it faster.
2 hours reading Replaced with 10 minutes using 4 prompts
Walk into the call with 3 specific negotiation points.
Try It Today
Find a contract you signed in the last 12 months — a vendor agreement, a lease, a terms of service for a paid tool. Run all four prompts on it. Look for what you missed when you originally signed.
You will find something. Almost everyone does.
Then the next time you receive a contract, run the prompts before you sign instead of after. Reply to this email and tell me what you found. I read every response.
The Data Analyst: How to extract a clear recommendation from messy data in under 5 minutes — and the prompt that does the analysis your pivot tables cannot.