Skip to content
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster

Qwen: Qwen3.5 27B — Adversarial Contract Review

  1. Home
  2. Models
  3. Qwen: Qwen3.5 27B
  4. Adversarial Contract Review

See how Qwen: Qwen3.5 27B compares on this challenge:

  • Qwen: Qwen3.5 27B vs Claude Sonnet 4.6
  • Qwen: Qwen3.5 27B vs Gemini 3.1 Pro Preview
  • Qwen: Qwen3.5 27B vs Z.ai: GLM 5

4 models have responded to the "Adversarial Contract Review" challenge. Compare their approaches side-by-side on Rival. This response is part of Rival's open dataset of 5,600+ AI model responses.

Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up
Back to Qwen: Qwen3.5 27B

Adversarial Contract Review

Qwen3.5 27B's response to the 'Adversarial Contract Review' challenge.

Qwen: Qwen3.5 27B
February 26, 2026
Text

?
Prompt

Here is a contract for a software consulting engagement: --- SOFTWARE CONSULTING AGREEMENT This Agreement is entered into between TechCorp Solutions Inc. ("Client") and [Contractor Name] ("Contractor"). 1. SCOPE: Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation. 2. PAYMENT: Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion. 3. INTELLECTUAL PROPERTY: All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP. 4. NON-COMPETE: Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination. 5. TERMINATION: Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation. 6. LIABILITY: Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability. 7. INDEMNIFICATION: Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault. 8. CONFIDENTIALITY: Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination. 9. DISPUTE RESOLUTION: Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party. --- Find all clauses that could be exploited against the contractor, suggest specific modifications, and explain the legal reasoning.

Qwen: Qwen3.5 27B
Response

qwen3.5-27b logo
Qwen: Qwen3.5 27BAdversarial Contract Review
qwen3.5-27b logo
Qwen: Qwen3.5 27B

Disclaimer: I am an AI assistant and not an attorney. The following analysis is for informational purposes only and does not constitute legal advice. Contracts are governed by specific local laws (e.g., state or country-specific employment and commercial codes). You should consult with a qualified attorney before signing or negotiating this agreement.


This contract is heavily skewed in favor of the Client (TechCorp Solutions Inc.) and contains several clauses that are legally aggressive, potentially unenforceable, and financially dangerous for the Contractor. Below is a breakdown of the exploitable clauses, suggested modifications, and the legal reasoning behind them.

1. Clause 1: SCOPE

The Issue: The clause allows the Client to change the work scope at any time without paying for the extra work. This creates "unlimited scope creep," effectively allowing the Client to demand free labor indefinitely. Suggested Modification:

"Contractor shall provide software development services as directed by Client. Any material change to the Scope of Work must be documented in a written Change Order signed by both parties. Such Change Orders may include adjustments to the fee, timeline, or deliverables." Legal Reasoning:

  • Consideration: A contract requires an exchange of value. If the Client changes the scope without paying, they are demanding additional consideration without providing it.
  • Mutuality: Terms must be binding on both parties. Allowing the Client to unilaterally alter the agreement violates the principle of mutuality of obligation.

2. Clause 2: PAYMENT

The Issue:

  • 90-Day Term: A 90-day payment term is predatory for a contractor and creates significant cash flow risk.
  • Sole Discretion: "Unsatisfactory" at "sole discretion" allows the Client to withhold payment arbitrarily without objective criteria. Suggested Modification:

"Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 30 days of invoice receipt. Client may withhold payment only if deliverables fail to meet the objective specifications defined in the Statement of Work (SOW), and Client must provide a written notice of deficiency within 15 days of receipt." Legal Reasoning:

  • Commercial Standards: Net-30 is the industry standard for B2B services. Net-90 is often viewed as using the contractor as an unsecured line of credit.
  • Vagueness: Courts often strike down clauses that rely on "sole discretion" or subjective terms like "satisfactory" because they lack objective standards for enforcement.

3. Clause 3: INTELLECTUAL PROPERTY

The Issue: This is an "Assignment of Background IP" clause. It claims ownership of the Contractor's pre-existing tools, libraries, and methodologies. This could prevent the Contractor from working for other clients or using their own portfolio of code. Suggested Modification:

"All work product developed specifically for Client under this Agreement shall be the exclusive property of Client. However, Contractor retains all ownership rights to pre-existing Intellectual Property ('Background IP') used in the performance of services. Contractor grants Client a perpetual, non-exclusive, royalty-free license to use such Background IP solely in connection with the Work Product." Legal Reasoning:

  • Property Rights: A contractor should not be forced to transfer ownership of their general trade tools or proprietary libraries. This is often deemed an unconscionable transfer of property.
  • License vs. Assignment: A license allows the Client to use the Contractor's tools without the Contractor losing the right to sell or use them elsewhere.

4. Clause 4: NON-COMPETE

The Issue: A 24-month ban on working for any company in the same industry is likely overbroad and unenforceable in many jurisdictions (e.g., California, Minnesota, and increasingly under the FTC rules in the US). Even where enforceable, it effectively prevents the Contractor from earning a living. Suggested Modification:

"Contractor agrees not to solicit Client's specific employees or customers for 12 months following termination. Contractor shall not be restricted from providing similar services to other entities." (Alternative if Client insists): "Contractor agrees not to provide services to Client's Direct Competitors (specifically named: X, Y, Z) for 6 months following termination." Legal Reasoning:

  • Restraint of Trade: Courts generally disfavor non-competes that are too broad in geography or duration. A blanket industry ban is rarely seen as reasonably necessary to protect legitimate business interests.
  • Reasonableness: The restriction must be no broader than necessary to protect trade secrets or customer relationships.

5. Clause 5: TERMINATION

The Issue:

  • Asymmetry: Client can fire you instantly; you need 60 days' notice.
  • No Payment for Work: If Client terminates immediately, you lose money for hours already worked on the current project. Suggested Modification:

"Either party may terminate this agreement with 30 days written notice. Upon termination, Contractor shall be compensated for all hours worked up to the date of termination and any non-refundable expenses incurred. Contractor shall deliver work in progress within 14 days." Legal Reasoning:

  • Equity: Contracts should generally have reciprocal termination rights.
  • Quantum Meruit: Even without a contract, a contractor is entitled to be paid for the reasonable value of work actually performed. This clause attempts to waive that right explicitly.

6. Clause 6: LIABILITY

The Issue: "No cap on liability" and "consequential damages" puts the Contractor at infinite financial risk. A single bug could theoretically cost the Contractor millions in lost profits for the Client. Suggested Modification:

"Contractor's total liability under this Agreement shall not exceed the total fees paid by Client to Contractor in the 6 months preceding the claim. Neither party shall be liable for indirect, incidental, or consequential damages." Legal Reasoning:

  • Risk Allocation: Liability should be proportional to the fee earned. Unlimited liability creates an imbalance of risk that makes the contract commercially unviable.
  • Foreseeability: Consequential damages (e.g., lost revenue due to a bug) are often unforeseeable and should be excluded in standard B2B consulting.

7. Clause 7: INDEMNIFICATION

The Issue: Indemnifying the Client "regardless of fault" means the Contractor pays for the Client's mistakes, third-party errors, or acts of God. Suggested Modification:

"Contractor shall indemnify Client against claims arising solely from Contractor's negligence, willful misconduct, or breach of confidentiality. Contractor shall not be liable for claims arising from Client's use of the software or third-party actions." Legal Reasoning:

  • Causation: Indemnification should be tied to the indemnifying party's fault. Assuming liability for third-party claims unrelated to the Contractor's actions is unreasonable.

8. Clause 8: CONFIDENTIALITY

The Issue: Preventing the disclosure of "terms of this agreement" (including rates) for 5 years prevents the Contractor from benchmarking their market rates or discussing their business history. Suggested Modification:

"Contractor shall not disclose Client's trade secrets, customer data, or proprietary code. This restriction does not apply to the terms of this Agreement, including compensation rates. Confidentiality obligations shall expire 2 years after termination." Legal Reasoning:

  • Public Interest: Rates and contract terms are generally not considered "trade secrets."
  • Duration: 5 years is excessive for most general consulting data; 1–2 years is standard.

9. Clause 9: DISPUTE RESOLUTION

The Issue:

  • Forum Shopping: Requiring arbitration in "Client's home jurisdiction" forces the Contractor to travel and pay for foreign counsel if a dispute arises.
  • Fee Shifting: "Costs borne by losing party" discourages valid claims because the Contractor fears losing and paying the Client's massive legal fees. Suggested Modification:

"Disputes shall be resolved through binding arbitration in the Contractor's home jurisdiction or a mutually agreed neutral location. Each party shall bear its own legal fees and costs." Legal Reasoning:

  • Procedural Fairness: A venue clause should be neutral or convenient to both parties.
  • Access to Justice: "Loser pays" clauses can act as a barrier to legal recourse, especially when the Contractor has significantly less financial resources than the Client.

Summary of Negotiation Strategy

  1. Deal Breakers: Clauses 3 (IP), 5 (Termination), and 6 (Liability) are the most critical. If the Client refuses to cap liability or release your Background IP, you should walk away.
  2. Leverage: Remind the Client that these terms are non-standard for independent contractors and will deter top-tier talent from signing.
  3. The "Sole Discretion" Trap: Focus heavily on removing subjective language ("unsatisfactory," "sole discretion"). Replace it with objective metrics (SOW compliance, code acceptance testing).
  4. Jurisdiction: If the Client is in a different state/country, do not agree to their jurisdiction for disputes unless they agree to cover your travel costs for arbitration.

Recommendation: Do not sign this agreement in its current form. It is structured to transfer maximum risk to the Contractor with minimal obligation from the Client.

Adversarial Contract Review

Turn this model response into notes, narration, or a short video

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output lives in our open dataset — 5K+ responses across 200 models. Take it. It’s free.

About Qwen: Qwen3.5 27B

Capabilities

ConversationReasoningCode GenerationAnalysisTool UseAgentic Tool UseTranslation

Categories

TextCodeVisionMultimodal

Specifications

Provider
Qwen
Released
2026-02-25
Size
MEDIUM
Parameters
27B
Context
262,144 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Qwen: Qwen3.5 27B vs Gemini 3.1 Pro Preview

Both outputs, side by side

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster