Skip to content
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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
  1. Home
  2. Models
  3. Qwen: Qwen3 30B A3B Instruct 2507
  4. Adversarial Contract Review

See how Qwen: Qwen3 30B A3B Instruct 2507 compares on this challenge:

  • Qwen: Qwen3 30B A3B Instruct 2507 vs Claude Sonnet 4.6
  • Qwen: Qwen3 30B A3B Instruct 2507 vs Gemini 3.1 Pro Preview
  • Qwen: Qwen3 30B A3B Instruct 2507 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
Sign Up
Sign Up
Back to Qwen: Qwen3 30B A3B Instruct 2507

Adversarial Contract Review

Qwen3 30B A3B Instruct 2507's response to the 'Adversarial Contract Review' challenge.

Qwen: Qwen3 30B A3B Instruct 2507
February 3, 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 30B A3B Instruct 2507
Response

qwen3-30b-a3b-instruct-2507 logo
Qwen: Qwen3 30B A3B Instruct 2507Adversarial Contract Review
qwen3-30b-a3b-instruct-2507 logo
Qwen: Qwen3 30B A3B Instruct 2507

The provided Software Consulting Agreement contains several clauses that are heavily one-sided in favor of the Client and could significantly disadvantage the Contractor, potentially rendering the agreement unenforceable or exploitative under contract law, fairness principles, and standard industry practices. Below is a detailed breakdown of problematic clauses, how they could be exploited, recommended modifications, and the legal and practical reasoning behind each.


🔴 1. Clause 1: SCOPE – "Client reserves the right to modify the scope at any time without additional compensation"

❌ Problem:

This clause grants the Client unilateral and unlimited power to expand the scope of work without any additional pay. It exposes the Contractor to unlimited work hours and costs with no recourse.

  • Exploitation Risk: Client could continuously add new features, redesigns, or rework without compensating the Contractor.
  • This violates the principle of consideration in contract law: both parties must exchange value. If one party gains significant benefits without paying, the contract may be seen as unconscionable.

✅ Suggested Modification:

"Client may modify the scope of work, but such changes must be communicated in writing. Any material change (e.g., scope increase exceeding 10% of original effort or adding new deliverables) shall result in a mutually agreed-upon adjustment to the fee and timeline. Contractor shall not be obligated to perform additional work without prior written agreement on revised compensation."

📌 Legal Reasoning:

  • Prevents implied contract or unilateral modification.
  • Aligns with UCC § 2-207 (in U.S. jurisdictions) and common law principles of contract fairness.
  • Courts often invalidate clauses that allow one party to unilaterally expand obligations without compensation.

🔴 2. Clause 2: PAYMENT – "Client may withhold payment if deliverables are deemed 'unsatisfactory' at Client's sole discretion"

❌ Problem:

"Unsatisfactory" is undefined and subjective. "Client’s sole discretion" removes all accountability and allows arbitrary withholding of payment.

  • Exploitation Risk: Client can refuse payment for minor or subjective reasons (e.g., UI color choice), even if deliverables meet specifications.
  • This undermines the Contractor’s right to payment for work rendered.

✅ Suggested Modification:

"Client may withhold payment only if deliverables fail to meet the mutually agreed-upon specifications, acceptance criteria, or documented requirements. Any dispute over quality shall be resolved through a formal review process involving both parties within 10 business days. If unresolved, the matter may be escalated to independent technical assessment at Client’s cost."

📌 Legal Reasoning:

  • Prevents unfair delegation of discretion.
  • Aligns with contract law principles of good faith and fair dealing.
  • Under UCC § 1-203 (U.S.), parties must act in good faith in performing contracts.
  • Without defined standards, the clause may be deemed unconscionable or void for vagueness.

🔴 3. Clause 3: INTELLECTUAL PROPERTY – "All work product... shall be the exclusive property of Client in perpetuity, including any work created using Contractor’s pre-existing IP"

❌ Problem:

This automatically assigns ownership of pre-existing IP (e.g., tools, libraries, frameworks the Contractor built) to Client, even if they were developed independently.

  • Exploitation Risk: Contractor loses all rights to their own tools, code, and intellectual capital — even if used only minimally in the project.
  • This could stifle future work and undermine the Contractor’s business.

✅ Suggested Modification:

"Client shall own all work product created specifically for this engagement. Contractor retains ownership of pre-existing intellectual property (including tools, libraries, and frameworks) unless expressly incorporated into deliverables. Contractor grants Client a perpetual, royalty-free license to use such pre-existing IP solely in connection with the delivered work."

📌 Legal Reasoning:

  • Pre-existing IP is protected under copyright law (U.S. Copyright Act § 101). A contract cannot strip ownership unless clearly negotiated and compensated.
  • Courts enforce clear delineation between pre-existing and new IP (e.g., Twin Peaks Productions v. Publications International, 996 F.2d 1366).
  • Full assignment of pre-existing IP without compensation may be unfair and unenforceable.

🔴 4. Clause 4: NON-COMPETE – "Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination"

❌ Problem:

  • Overly broad geographic and time scope (24 months is long; "same industry" is undefined).
  • No geographic limitation — could ban Contractor from working globally.
  • No consideration provided for the restriction (i.e., no compensation or benefit to Contractor).

✅ Suggested Modification:

"Contractor agrees not to solicit or provide software consulting services to any direct competitor of Client within [e.g., 50-mile radius of Client’s headquarters] for a period of 6 months after termination. This restriction is limited to clients or projects directly competitive with Client’s core business and is supported by a mutual agreement on compensation or benefit."

📌 Legal Reasoning:

  • Non-compete clauses are generally unenforceable unless reasonable in scope, duration, and geography.
  • Courts in most U.S. states (e.g., California, New York) strictly limit such clauses and may strike down overbroad ones.
  • No consideration (e.g., payment, training, confidentiality benefit) makes the clause unenforceable under contract law (e.g., Caterpillar, Inc. v. Darr, 120 Ill. App. 3d 826).
  • In California, non-competes are illegal per se (Cal. Bus. & Prof. Code § 16600).

🔴 5. Clause 5: TERMINATION – "Client may terminate at any time without notice. Contractor must provide 60 days notice..."

❌ Problem:

  • Client has unilateral, no-notice termination — Contractor bears all risk.
  • Contractor must still deliver all work in progress without additional compensation — a significant loss of time and effort.

✅ Suggested Modification:

"Either party may terminate this Agreement with 30 days’ written notice. In the event of termination by Client, Client shall pay Contractor for all work completed and approved up to the termination date, plus a termination fee equal to 10% of the remaining contract value, or a pro-rata portion of uncompleted work based on effort already expended."

📌 Legal Reasoning:

  • Unilateral, no-notice termination by one party without compensation is unfair and potentially void under equitable principles.
  • Courts recognize that abandonment of work should not result in total loss for the Contractor.
  • The "implied covenant of good faith" requires that termination not be used to avoid paying for completed work.
  • Paying for work done is a fundamental principle of contract law (e.g., Restatement (Second) of Contracts § 152).

🔴 6. Clause 6: LIABILITY – "Contractor assumes all liability... including consequential damages, with no cap on liability"

❌ Problem:

  • Unlimited liability for bugs, breaches, system failures — even for events beyond Contractor’s control.

  • No cap, no exclusions, and consequential damages (e.g., lost profits, business interruption) are included.

  • Exploitation Risk: Contractor could face catastrophic financial loss from a minor bug, even if due to Client’s own inputs or third-party systems.

✅ Suggested Modification:

"Contractor shall be liable only for direct damages arising from gross negligence or willful misconduct, capped at the total fees paid under this Agreement. Contractor shall not be liable for indirect, incidental, consequential, or punitive damages."

📌 Legal Reasoning:

  • Unlimited liability clauses are unenforceable or unreasonably harsh under contract law and public policy.
  • Most jurisdictions (e.g., U.S. states, EU) prohibit or limit liability caps for services like software development.
  • Consequential damages are typically excluded in service contracts unless explicitly warranted.
  • Uncapped liability violates principles of risk allocation and commercial reasonableness.

🔴 7. Clause 7: INDEMNIFICATION – "Contractor shall indemnify Client against all claims... regardless of fault"

❌ Problem:

  • Contractor must pay for all claims, even if caused by Client’s own design, data, or third-party tools.
  • "Regardless of fault" removes the Contractor’s ability to defend itself.

✅ Suggested Modification:

"Contractor shall indemnify Client for claims arising from Contractor’s breach of this Agreement, gross negligence, or willful misconduct. Client shall indemnify Contractor for claims arising from Client’s data, specifications, or third-party materials provided by Client."

📌 Legal Reasoning:

  • Indemnification must be reciprocal or balanced; one-sided indemnity is often unenforceable.
  • No fault-based allocation violates principles of fairness and risk allocation.
  • Standard practice in software contracts is shared responsibility based on fault and control.

🔴 8. Clause 8: CONFIDENTIALITY – "Contractor shall not disclose... for 5 years after termination"

❌ Problem:

  • 5-year non-disclosure is excessive for a consulting engagement, especially without clear definition of what constitutes "confidential" information.
  • Could prevent Contractor from discussing work in future jobs or portfolios.

✅ Suggested Modification:

"Contractor shall keep confidential all non-public information disclosed during the engagement for a period of 3 years after termination, except as required by law. Confidentiality obligations do not apply to information that is publicly known, independently developed, or rightfully received from a third party."

📌 Legal Reasoning:

  • 5-year confidentiality is longer than typical and may be unreasonable.
  • Courts often limit confidentiality periods to 2–3 years unless justified by trade secrets (e.g., Gartner, Inc. v. Meltzer, 900 F. Supp. 2d 766).
  • Overly broad restrictions may violate public policy regarding free speech and career mobility.

🔴 9. Clause 9: DISPUTE RESOLUTION – "Binding arbitration in Client’s home jurisdiction, with costs borne by the losing party"

❌ Problem:

  • Forces Contractor to litigate in Client’s home jurisdiction, which may be far away and costly.
  • "Losing party pays costs" can deter small contractors from pursuing disputes.

✅ Suggested Modification:

"Disputes shall be resolved through binding arbitration in [neutral city, e.g., Chicago, IL, or online via AAA/ICDR]. Both parties shall share arbitration fees equally. Each party bears its own legal fees, unless otherwise awarded by the arbitrator."

📌 Legal Reasoning:

  • Forum non conveniens — forcing a contractor to go to a distant, inconvenient jurisdiction is unfair.
  • "Losing party pays all costs" can deter legitimate claims and is unfairly punitive.
  • Courts favor neutral, cost-sharing dispute mechanisms.

✅ Summary of Key Fixes (Recommended Revised Clauses)

Original ClauseRecommended Fix
1. ScopeRequire mutual agreement for scope changes; define material change
2. Payment WithholdingTie to documented specs; require review process
3. IPRetain pre-existing IP; grant license, not assignment
4. Non-competeLimit time, geography, and scope; ensure compensation
5. TerminationMutual 30-day notice; pay for completed work + termination fee
6. LiabilityCap liability at fees paid; exclude consequential damages
7. IndemnificationMutual and fault-based
8. ConfidentialityLimit to 3 years; include exceptions
9. Dispute ResolutionNeutral venue; shared arbitration costs

📌 Final Advice for the Contractor:

  • Do not sign this agreement as-is — it is highly one-sided and legally risky.
  • Request revisions using the above suggestions.
  • If Client refuses, consider declining the engagement or seeking legal counsel.
  • For future contracts, use standard templates from professional bodies (e.g., IEEE, ABA, or legal platforms like LegalZoom or Ironclad).

🔥 Bottom Line: A fair consulting agreement must reflect mutual risk, fair compensation, and balanced rights. This contract violates those principles and could expose the Contractor to serious legal and financial risk.

Adversarial Contract Review

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

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output is part of our open dataset — 5K+ AI responses across 200 models

About Qwen: Qwen3 30B A3B Instruct 2507

Capabilities

ConversationReasoningCode GenerationAnalysis

Categories

TextCode

Specifications

Provider
Qwen
Released
2025-07-29
Size
LARGE
Context
131,072 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Qwen: Qwen3 30B A3B Instruct 2507 vs Gemini 3.1 Pro Preview

Both outputs, side by side

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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