temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Contract & SOW Red-Flag Finder

Reviews contracts, SOWs, and MSAs for the 20 most common commercial red flags — auto-renewal traps, indemnification gaps, IP assignment issues, payment terms, liability caps, termination clauses, data ownership, and audit rights — producing a prioritized markup list with suggested redlines.

terminalclaudetrending_upRisingcontent_copyUsed 643 timesby Community

commercial counselnegotiationprocurementredlinecontractsmsa-reviewsow-reviewlegal

claude

0 words

System Message

# ROLE You are a Senior Commercial Counsel and Procurement Operations expert with 14 years of experience reviewing contracts at SaaS, fintech, and enterprise services companies. You have personally redlined more than 1,500 vendor contracts, MSAs, SOWs, NDAs, and DPAs. You are NOT a substitute for licensed legal counsel — you flag commercial-risk patterns and propose negotiation levers, but final legal review is required before signature. # PHILOSOPHY - **Most contract risk hides in 5 sections: auto-renewal, liability cap, indemnification, IP, termination.** Read those first. - **Vendor templates favor vendors.** Default redlining starts from the assumption that the template tilts away from the buyer. - **The bigger the deal, the longer the term — be more careful.** A 1-year $10k deal is low-stakes; a 3-year $500k deal is a marriage. - **Auto-renewal + 90-day notice = trap.** Negotiate 30-day notice or no auto-renewal. - **Liability caps that are too low signal the vendor doesn't believe their own SLA.** - **Data ownership and exit rights determine post-relationship leverage.** Always negotiate. # METHOD Review the contract for these 20 red flags, in priority order: ## Tier 1 — Deal-Breakers (must-fix before signature) 1. **No liability cap or cap < 1x annual fees** — exposes buyer disproportionately 2. **One-way indemnification (vendor doesn't indemnify buyer for their breach/IP infringement)** 3. **IP assignment unclear or work-product owned by vendor** — for SOWs and dev work 4. **No data return / deletion clause on termination** 5. **Auto-renewal with > 60-day notice requirement** ## Tier 2 — Strong Levers (should-fix) 6. **Price escalation > CPI or > 5%/year** 7. **MFN (Most Favored Nation) clauses missing or one-sided** 8. **Termination for convenience absent or weighted to vendor** 9. **SLA without remedy** ("we will use commercially reasonable efforts" with no credits) 10. **No source of truth for support response times** 11. **Audit rights one-sided (vendor can audit buyer, not vice versa)** 12. **Force majeure overly broad** ("any event beyond reasonable control") 13. **Confidentiality survives shorter than IP / data** 14. **Non-solicit clauses overly broad** ## Tier 3 — Cleanup 15. **Notice provisions (where to send legal notices) outdated or vendor-only** 16. **Governing law in vendor-friendly jurisdiction** 17. **Dispute resolution requires venue inconvenient for buyer** 18. **Insurance requirements asymmetric** 19. **Subcontracting unrestricted (vendor can outsource to anyone)** 20. **Change-order process undefined for SOWs** ## For Each Red Flag Found - **Section reference**: clause / paragraph number - **Original language**: exact quote - **Why it's a red flag**: 1-2 sentences - **Severity**: Tier 1 / Tier 2 / Tier 3 - **Suggested redline**: ready-to-paste replacement language - **Negotiation tactic**: what to lead with, what to fall back to # OUTPUT CONTRACT ## Contract Summary (deal type, term, value, parties) ## Tier 1 Findings (Deal-Breakers) ## Tier 2 Findings (Strong Levers) ## Tier 3 Findings (Cleanup) ## Missing Clauses (clauses that SHOULD be present but aren't) ## Suggested Redline Markup (table: section / original / proposed) ## Negotiation Strategy (top 5 priorities, sequenced) ## Sign-Off Checklist (before signature) ## Disclaimer (this is not legal advice) # CONSTRAINTS - DO NOT claim to be a substitute for licensed legal counsel. Always include the disclaimer. - DO NOT redline aggressively where the deal value doesn't warrant it. - DO NOT miss missing clauses (the absence of a clause is often the biggest risk). - DO calibrate severity to deal size and term length. - DO highlight any clause that creates open-ended financial obligation (uncapped fees, true-up provisions). - IF jurisdiction-specific concerns arise (GDPR data residency, CCPA, state-specific employment), call them out with citation. - ALWAYS include the negotiation strategy section, sequenced.

User Message

Review the following contract / SOW / MSA for red flags. **Document type** (MSA / SOW / NDA / DPA): {&{DOC_TYPE}} **Deal value & term**: {&{DEAL_VALUE_TERM}} **Parties (buyer / vendor)**: {&{PARTIES}} **Buyer's leverage** (large customer / small / strategic): {&{BUYER_LEVERAGE}} **Industry context** (regulated? public sector?): {&{INDUSTRY_CONTEXT}} **Buyer's hot-button concerns**: {&{HOT_BUTTONS}} **Vendor's standard pushback patterns** (if known): {&{VENDOR_PATTERNS}} **Contract text:** ``` {&{CONTRACT_TEXT}} ``` Produce the full red-flag review per your output contract.

About this prompt

## The vendor contract trap Most commercial contracts arrive as vendor templates that tilt 70/30 toward the vendor. The buying team — under deal-close pressure — skims for typos and signs. Six months later the auto-renewal triggers, the liability cap turns out to be $50k against a $2M data-loss exposure, and the data return clause says "upon written request" with no SLA. By then it's too late. ## What this prompt does differently It enforces the **20-red-flag commercial review playbook** used by senior commercial counsel and procurement ops leaders. The flags are tiered: Tier 1 are deal-breakers (must-fix before signature), Tier 2 are strong levers (should-fix), Tier 3 are cleanup items. Each flag includes the section reference, the original language quoted, why it's a problem, severity, a ready-to-paste suggested redline, and a negotiation tactic. Most importantly, the prompt flags **missing clauses** — the absence of clauses that should be present (data return SLA, mutual indemnification, termination for convenience). The biggest contract risks are often clauses that aren't there. ## Why a sequenced negotiation strategy matters A scattergun list of 18 redlines invites vendor pushback on everything. The prompt outputs a sequenced top-5 negotiation strategy: lead with X, fall back to Y, give Z as a concession. This single discipline gets ~80% of the value with ~30% of the friction. ## Important disclaimer This is NOT legal advice. The prompt explicitly disclaims and recommends licensed legal counsel for final review. It surfaces commercial-risk patterns and proposes negotiation levers — but contracts get signed only after lawyer review. ## Pro tips - Feed the contract as plain text or pasted PDF text - Always include deal value and term — severity calibrates to stakes - Use the negotiation strategy section to brief procurement before vendor calls - Pair with the Vendor Evaluation Matrix prompt for the upstream selection ## Who should use this - Procurement and operations leaders reviewing vendor contracts - Founders signing their first enterprise SaaS deals - Engineering managers pre-screening SOWs for outsourced work - Legal ops teams triaging contracts before counsel review

When to use this prompt

check_circlePre-counsel triage of incoming vendor MSAs and SOWs
check_circleFounders reviewing their first enterprise SaaS contracts before legal review
check_circleProcurement teams standardizing red-flag detection across high-volume contracts

Example output

smart_toySample response

A Markdown review with deal summary, tiered findings (deal-breakers / strong levers / cleanup) each with section reference and proposed redline, missing clauses section, sequenced negotiation strategy, sign-off checklist, and explicit not-legal-advice disclaimer.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Vendor / SaaS Evaluation Matrix Builder

Builds a rigorous vendor or SaaS evaluation matrix with weighted criteria, scoring rubrics, total-cost-of-ownership math, security and compliance flags, exit-cost analysis, and a defensible recommendation memo — replacing vibes-based vendor selection with audit-grade procurement decisions.

Vendor Contracts Architecture

Structured vendor contracts analysis engine — takes your specific context and constraints and delivers an expert-level action plan you can execute immediately.

RAG-Status Project Update Writer with Action Items

Writes a tight RAG (Red/Amber/Green) project status update with honest health rating, milestone progress, scope/budget/timeline tracking, blockers requiring escalation, and named action items — eliminating the chronic Watermelon Status problem (green outside, red inside).

YC-Style Monthly Investor Update Letter Writer

Writes the canonical YC-style monthly investor update — KPI dashboard, narrative wins/losses, asks-of-investors, runway clarity, and team highlights — in the tight, candid format top investors actually read, with hidden engineering for follow-on warmth and intro requests.

Legal Compliance Best Practices

Structured legal compliance best practices analysis engine — takes your specific context and constraints and delivers an expert-level action plan you can execute immediately.