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 Flash — Adversarial Contract Review

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

See how Qwen: Qwen3.5 Flash compares on this challenge:

  • Qwen: Qwen3.5 Flash vs Claude Sonnet 4.6
  • Qwen: Qwen3.5 Flash vs Gemini 3.1 Pro Preview
  • Qwen: Qwen3.5 Flash 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 Flash

Adversarial Contract Review

Qwen3.5 Flash 02 23's response to the 'Adversarial Contract Review' challenge.

Qwen: Qwen3.5 Flash
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 Flash
Response

qwen3.5-flash-02-23 logo
Qwen: Qwen3.5 FlashAdversarial Contract Review
qwen3.5-flash-02-23 logo
Qwen: Qwen3.5 Flash

Disclaimer: I am an AI, not an attorney. This analysis is for informational purposes only and does not constitute legal advice. Contract laws vary significantly by jurisdiction (e.g., California vs. New York vs. UK). You should consult with a qualified attorney specializing in contract law before signing or negotiating this agreement.

This contract is heavily skewed in favor of the Client (TechCorp Solutions Inc.). It contains several "poison pills" that could result in significant financial loss, legal liability, or career stagnation for the Contractor.

Below is a breakdown of the high-risk clauses, suggested modifications, and the legal reasoning behind them.


1. CLAUSE 1: SCOPE

Original: "Client reserves the right to modify the scope at any time without additional compensation."

  • The Risk: This allows for unlimited scope creep. The Client can ask for infinite features or changes without paying a cent more. It violates the fundamental contract principle of consideration (exchange of value).
  • Suggested Modification:

    "Any modifications to the Scope must be agreed upon in writing via a Change Order. Change Orders will detail the additional cost and timeline impact, which must be approved by both parties prior to work commencing."

  • Legal Reasoning: In contract law, a unilateral change to the scope without additional consideration can be deemed a breach of contract by the Client if the Contractor refuses to comply, or it creates ambiguity regarding what constitutes "performance." A Change Order process ensures mutual assent to new terms and protects your revenue stream.

2. CLAUSE 2: PAYMENT

Original: "Payment is due within 90 days... Client may withhold payment if deliverables are deemed 'unsatisfactory' at Client's sole discretion."

  • The Risk:
    1. Cash Flow: 90-day terms are predatory for freelancers; it effectively forces you to lend the client money for three months. Industry standard is Net-30.
    2. Payment Withholding: "Sole discretion" removes objective standards. The Client can withhold payment indefinitely by claiming dissatisfaction.
  • Suggested Modification:

    "Payment is due within 30 days of invoice receipt. Deliverables will be deemed accepted if the Client does not provide written notice of specific defects within 10 days of delivery. 'Unsatisfactory' will be defined by objective failure to meet the requirements in Section 1."

  • Legal Reasoning: Under the UCC and common law, payments are expected within a "reasonable time." 90 days is almost universally considered unreasonable for software consulting. Removing "sole discretion" prevents the Client from using payment as leverage to force unpaid work or free consulting.

3. CLAUSE 3: INTELLECTUAL PROPERTY

Original: "...including any work created using Contractor's pre-existing IP."

  • The Risk: This attempts to seize Background IP. If you wrote a library or framework before this contract, the Client now owns it. This prevents you from using your own tools in future contracts with other clients.
  • Suggested Modification:

    "Client shall own all 'Work Product' created specifically for this engagement. Contractor retains ownership of all pre-existing IP (Background IP). Contractor grants Client a perpetual, royalty-free license to use said Background IP within the Work Product."

  • Legal Reasoning: IP law distinguishes between foreground IP (created for the project) and background IP (existing tools). Transferring background IP ownership is an overreach that can be challenged as unconscionable. A license ensures the Client can use the software, but you retain the right to use the underlying code elsewhere.

4. CLAUSE 4: NON-COMPETE

Original: "Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months..."

  • The Risk:
    1. Enforceability: Non-competes are increasingly being struck down (e.g., by the FTC in the US, or under local employment laws like in California).
    2. Career Impact: "Same industry" is too vague. If TechCorp is "FinTech," you cannot work for any other company in FinTech for 2 years.
  • Suggested Modification:

    "Remove this clause entirely. If Client insists, limit it to: 'Contractor shall not solicit Client's specific customers for 12 months.'"

  • Legal Reasoning: Restraints of trade are scrutinized heavily by courts. They must be reasonable in time, geography, and scope to be enforceable. A 24-month, industry-wide ban is rarely enforceable and acts primarily as a deterrent that should be removed during negotiation.

5. CLAUSE 5: TERMINATION

Original: "Client may terminate this agreement at any time without notice. Contractor must... deliver all work in progress without additional compensation."

  • The Risk: Asymmetric Termination. The Client can fire you on Tuesday with no pay for the work done. "Work in progress" is often worth more than completed milestones.
  • Suggested Modification:

    "Either party may terminate with 30 days written notice. Upon termination, Client shall pay for all work completed and expenses incurred up to the date of termination."

  • Legal Reasoning: This creates a "termination for convenience" clause, but it must be reciprocal. If a Client terminates, the Contractor is entitled to quantum meruit (the value of work performed). Forcing you to deliver uncompleted work without pay is a breach of contract regarding the hours you have already committed.

6. CLAUSE 6: LIABILITY

Original: "Contractor assumes all liability... including consequential damages, with no cap on liability."

  • The Risk: Uncapped Liability. If your code causes a server crash that costs the Client $1M in lost revenue, you are personally on the hook for that $1M, even if it was a simple typo. This could bankrupt you.
  • Suggested Modification:

    "Contractor's total liability shall not exceed the total amount paid to Contractor under this Agreement in the 12 months prior to the claim. Contractor shall not be liable for indirect, special, or consequential damages."

  • Legal Reasoning: Liability should be commensurate with the risk and reward (your $150/hr fee). Uncapped liability for consequential damages (lost profits, business interruption) is standard industry practice to avoid. Most professional liability insurance policies also require a cap on coverage.

7. CLAUSE 7: INDEMNIFICATION

Original: "...indemnify Client against all claims... regardless of fault."

  • The Risk: Strict Liability Indemnity. You must pay for legal bills even if the Client made a mistake.
  • Suggested Modification:

    "Contractor shall indemnify Client only for claims arising from the Contractor's gross negligence, willful misconduct, or breach of confidentiality."

  • Legal Reasoning: Indemnification clauses are meant to protect against claims caused by your actions, not the Client's actions. "Regardless of fault" forces you to insure against risks you cannot control (e.g., the Client misusing your software or third-party attacks on their infrastructure).

8. CLAUSE 8: CONFIDENTIALITY

Original: "...including the terms of this agreement, for 5 years..."

  • The Risk: You cannot tell anyone (including other potential clients) that you signed this contract. This can hinder your marketing and reputation building.
  • Suggested Modification:

    "Contractor shall not disclose Client's proprietary information. The existence of this agreement and the terms (fees) shall not be considered confidential, but Contractor agrees not to publicly disclose the Client's identity without written permission."

  • Legal Reasoning: It is standard practice to allow contractors to disclose the existence of a contract for portfolio/reference purposes (with permission). Keeping the terms strictly confidential prevents you from benchmarking your rates in the market.

9. CLAUSE 9: DISPUTE RESOLUTION

Original: "Binding arbitration in Client's home jurisdiction, with costs borne by the losing party."

  • The Risk: Venue Shopping. If you live in New York and the Client is in California, you must fly to California to arbitrate. The costs (travel, legal fees) will likely exceed the value of your dispute.
  • Suggested Modification:

    "Disputes shall be resolved via mediation, and failing that, arbitration in the Contractor's home jurisdiction. Each party shall bear its own legal costs."

  • Legal Reasoning: Arbitration clauses that impose excessive travel burdens on one party can sometimes be found procedurally unconscionable. Furthermore, "loser pays" provisions can deter you from pursuing valid claims because the risk of cost is too high.

Summary of Negotiation Strategy

This contract is not fair market value; it is designed to transfer all risk to the Contractor.

  1. Non-Negotiables: You must negotiate Clause 6 (Liability Cap) and Clause 2 (Payment Terms). Unlimited liability and 90-day terms are deal-breakers for any professional business.
  2. High Priority: Clause 5 (Termination) and Clause 3 (IP). You need to ensure you get paid for work done and keep ownership of your tools.
  3. Negotiable: Clause 4 (Non-Compete) and Clause 9 (Arbitration). These are often points of leverage. If the Client refuses to budge on these, you may be overpaying for the risk.

Recommendation: Do not sign this agreement in its current form. It exposes you to risks that far outweigh the $150/hour revenue.

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 Flash

Capabilities

ConversationReasoningCode GenerationAnalysisTool UseAgentic Tool UseTranslation

Categories

TextCodeVisionMultimodal

Specifications

Provider
Qwen
Released
2026-02-25
Size
MEDIUM
Context
1,000,000 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Qwen: Qwen3.5 Flash 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