How Startup Founders in SaaS Can Use Claude to Fix Vendor Contracts Full of One-Sided Clauses Before Signing

You are an expert startup legal advisor with 14 years of experience reviewing technology vendor agreements, SaaS subscription contracts, and API licensing terms for early-stage and growth-stage companies. Help me write a legal memo so I can reduce legal bottlenecks on commercial deals and stop signing contracts that create disproportionate liability for my company. My situation: - Company stage and team size: [e.g., "Series A SaaS company, 28 employees, no in-house legal counsel"] - Type of vendor contract under review: [e.g., "cloud infrastructure agreement with a major hyperscaler, 3-year term, auto-renews annually"] - Most concerning clause or section I have already spotted: [e.g., "unlimited liability on our side for data breaches, but vendor liability capped at one month of fees"] - Governing law and jurisdiction: [e.g., "Delaware law, US federal courts only"] - My leverage position in this negotiation: [e.g., "small customer — vendor is unlikely to redline heavily but may accept standard fallback positions"] - Timeline pressure: [e.g., "board wants this signed before the end of the quarter — 3 weeks to close"] - Prior legal review available: [e.g., "one outside counsel review two years ago on a different vendor — no current retainer"] Deliver: 1. A legal memo structured in four sections — executive summary of risk level, clause-by-clause risk flags with severity ratings, recommended redlines with plain-English rationale for each, and a negotiation priority ranking from must-fix to nice-to-have 2. A liability asymmetry analysis comparing the indemnification, limitation of liability, and warranty disclaimers on both sides — identifies where the current draft places disproportionate risk on the signing company 3. A list of eight standard fallback positions that enterprise vendors commonly accept from smaller customers, with the exact contract language for each fallback position 4. A negotiation email template that frames the three highest-priority redlines as standard market practice rather than adversarial demands — reduces vendor resistance without revealing the full extent of legal concern 5. A data liability exposure calculation — estimates the maximum financial exposure under the current contract terms in a realistic breach scenario versus the proposed redlined terms 6. A clause-specific risk explainer for three non-lawyers on the founding team — translates the three riskiest clauses into plain English with a one-sentence business impact statement per clause 7. A contract signing approval checklist with seven criteria the company must verify before executing — covers liability cap, auto-renewal notice window, data deletion obligations, and audit rights 8. A post-signature obligation tracker template — lists every ongoing compliance obligation the company accepts under this contract with the trigger, deadline, and internal owner for each **Write the memo assuming the reader is a technically sophisticated founder who understands business risk but has never negotiated a vendor contract — every legal concept must be grounded in a specific business consequence, not abstract legal doctrine.**