SaaS & Tech Payment Disputes Are Different
After representing dozens of SaaS companies and tech startups over the past 15 years, I've learned that technology payment disputes have unique characteristics that require specialized legal strategies:
- Higher contract values: Average B2B SaaS contracts range from $25,000 to $500,000 annually — well above small claims limits
- Complex contracts: MSAs, SOWs, SLAs, data processing agreements, and security addenda create multiple breach points
- IP complications: Who owns custom integrations? What happens to client data upon termination? These questions affect leverage
- Federal statutes: Computer Fraud and Abuse Act, Defend Trade Secrets Act, and DMCA provide powerful remedies unavailable in other industries
- Regulatory overlay: GDPR, CCPA, SOC 2, and HIPAA requirements create both obligations and leverage points
A generic demand letter won't work. You need to cite the specific contract provisions they violated, reference applicable federal statutes, and demonstrate you understand the technical and legal complexity of your position.
Common SaaS & Tech Payment Scenarios
1. Customer Refusing to Pay SaaS Subscription Invoices
The customer has been using your platform for months, but stopped paying 60-90 days ago. They're still actively using the service (you can see login activity), but ignoring your billing emails.
Legal theories:
- Breach of contract: Your Terms of Service and/or MSA create enforceable payment obligations
- Unjust enrichment: They're receiving the benefit of your service without paying for it
- Account stated: Their previous payments establish a course of dealing acknowledging the debt
Strategic considerations: Should you suspend their account before sending the demand letter? This depends on your contract's termination provisions and whether you want to preserve the customer relationship. I generally recommend suspending access concurrent with sending the demand letter — continued free access undermines your urgency.
2. Enterprise Client Breaching Annual Contract
You signed a 3-year, $150,000/year enterprise agreement. Six months in, they announce they're "sunsetting the relationship" and stopping payment. They claim your platform doesn't meet their needs or that you breached the SLA.
This is the most valuable SaaS demand letter scenario because the damages are substantial and the contract terms are usually crystal clear.
Your demand letter should address:
- Term and termination provisions: Quote the exact contract language on early termination. Most enterprise SaaS contracts require 60-90 days notice and don't allow termination for convenience
- SLA compliance: If they claim you breached the SLA, produce your uptime logs and response time metrics. Most SLA disputes evaporate when you show 99.9% uptime
- Liquidated damages or early termination fees: Many enterprise contracts include these provisions — cite them explicitly
- Acceleration clause: Some contracts make all future payments immediately due upon material breach. If yours includes this, the entire 3-year contract value becomes collectible now
3. Data Breach Notification Demands
This scenario is reversed — you're the one sending a demand letter TO a vendor or service provider that exposed your customer data due to their security failure.
Key statutes:
- CCPA (Cal. Civ. Code §1798.150): Private right of action for data breaches involving nonencrypted personal information, $100-$750 per consumer per incident
- GDPR Article 82: Right to compensation for material or non-material damage resulting from GDPR violations
- Contractual indemnification: Most SaaS vendor agreements include security breach indemnification provisions — quote them
Your demand letter should quantify:
- Cost of breach notification to affected customers (typically $5-$15 per notification)
- Credit monitoring services you're required to provide (typically $150-$300 per affected individual for 1-2 years)
- Internal investigation and remediation costs
- Regulatory fines and penalties you face
- Reputational harm and customer churn
Even a "small" breach affecting 1,000 customers can generate $200,000+ in quantifiable damages. The vendor's insurance will typically cover this, which is why these demands often settle quickly.
4. IP/Trade Secret Theft by Former Employee or Contractor
A developer left your company and took proprietary code, customer lists, API documentation, or product roadmaps. You discovered they're now working for a competitor or started their own competing service using your IP.
This is my favorite tech demand letter scenario because the legal remedies are so powerful.
Applicable federal statutes:
Civil remedies under §1030(g): Compensatory damages, injunctive relief, and costs (including attorney's fees).
Remedies under §1836(b): Injunctive relief, damages for actual loss and unjust enrichment, exemplary damages up to 2x if willful, and attorney's fees if willful and malicious.
Remedies: Injunctive relief, damages, and attorney's fees if willful and malicious (§3426.4).
Your demand letter should:
- Identify the specific trade secrets taken (source code, customer lists, algorithms, etc.)
- Establish that these qualify as trade secrets (not generally known, economically valuable, subject to reasonable secrecy measures)
- Prove they took it (forensic evidence, timeline of downloads, analysis of their new product)
- Cite their confidentiality agreement or IP assignment agreement
- Demand immediate return/destruction of all materials and cessation of competitive use
- Preserve your right to seek injunctive relief and damages
Important: Send this letter from an attorney (me). Trade secret and CFAA claims are criminal in nature, and a lawyer's demand letter signals serious intent. These cases often settle within 2-3 weeks because the defendant faces catastrophic exposure.
5. Vendor SLA Violation Demands
You're a SaaS company that relies on a third-party infrastructure provider (hosting, email delivery, payment processing, etc.). They experienced extended downtime or performance degradation that violated the SLA, causing you to miss your own SLAs with your customers.
Damages you can claim:
- Service credits you had to issue to your customers due to your vendor's downtime
- Lost revenue from customers who churned due to the outage
- Engineering time spent troubleshooting and implementing workarounds
- Reputational harm (harder to quantify but can be argued)
Common vendor defense: The SLA includes a limitation of liability capping damages at fees paid in the prior 12 months or some de minimis amount like $1,000.
Your counterargument: California Civil Code §1668 voids contracts that exempt liability for fraud, willful injury, or violation of law. If the vendor's failure was due to gross negligence (not just ordinary negligence), limitation of liability provisions may not apply. Additionally, many limitation of liability clauses exclude consequential damages but still allow direct damages — frame your claim as direct damages from the breach.
6. Chargebacks and Payment Processor Disputes
A customer disputed the charge with their credit card company or PayPal. The payment processor froze funds or reversed payment, even though the customer actively used your service.
This is frustrating because you're dealing with two parties: the customer (who initiated the chargeback) and the payment processor (who is holding your money).
Your demand letter should go to the customer (not the processor) and should:
- Establish that they received and used your service (include usage logs)
- Quote the contract provisions establishing their payment obligation
- Note that chargeback fraud is prosecutable under California Penal Code §484g (theft by false pretenses)
- Demand they contact the processor to withdraw the chargeback within 10 days
- Warn that you'll pursue breach of contract litigation if they don't
Separately, challenge the chargeback through the processor's dispute resolution process. Most processors will reverse the chargeback if you provide evidence of service delivery and contract acceptance.
What to Include in Your SaaS/Tech Demand Letter
1. Contract Identification and Key Provisions
SaaS companies often have multiple layers of agreements: Master Service Agreement, Statement of Work, Terms of Service, SLA, DPA. Your demand letter must identify which agreement was breached and quote the specific provisions.
Example: "Pursuant to Section 4.2 of the Master Service Agreement executed on January 15, 2024 (attached as Exhibit A), Client agreed to pay $50,000 annually in monthly installments of $4,166.67, due on the first of each month."
2. Breach Timeline with Evidence
Document exactly when the breach occurred and what you did in response:
- Invoice dates and amounts
- Payment due dates
- Your collection attempts (emails sent, calls made)
- Any partial payments or promises to pay
- Service usage during non-payment period (if applicable)
3. Damages Calculation
Be precise. SaaS contracts often involve recurring revenue, so damages can accumulate quickly:
- Past due amounts (specific invoices with dates)
- Future amounts if the contract includes acceleration clause
- Late fees (if your contract allows them)
- Interest under California Civil Code §3289(b) — 10% annually on unpaid contract amounts
- Attorney's fees and costs (if your contract includes prevailing party provision per Civil Code §1717)
4. Applicable Statutes
For SaaS and tech disputes, I typically cite:
- 18 U.S.C. §1030: Computer Fraud and Abuse Act (for unauthorized access or exceeding authorization)
- 18 U.S.C. §1836: Defend Trade Secrets Act (for IP theft)
- California Civil Code §3426: Uniform Trade Secrets Act
- California Civil Code §1671(b): Liquidated damages provisions
- California Civil Code §1717: Prevailing party attorney's fees
- 17 U.S.C. §1201: DMCA anti-circumvention provisions (if they hacked or bypassed your security)
5. Next Steps and Consequences
Give them 14 days to cure. Specify what happens if they don't:
- Immediate account termination and data deletion (cite your data retention policy)
- Filing a lawsuit in California Superior Court (or federal court if federal claims)
- Seeking preliminary injunction (for IP theft or trade secret cases)
- Reporting to credit bureaus (if you're a creditor)
- Pursuing attorney's fees and costs under Civil Code §1717
SaaS Contract Dispute? Get Attorney Help.
I'll draft a custom demand letter for your SaaS payment dispute, IP theft, or vendor breach — with federal and state statutes tailored to your situation.
- Written by me personally (CA Bar #279869), not a template
- CFAA, DTSA, and trade secret analysis for IP theft cases
- Review of your MSA, SLA, and Terms of Service for breach points
- Typically increases recovery rates to 70-80% for tech disputes
- 48-hour turnaround in most cases
- Includes strategy call on injunctive relief if they don't comply
Sample SaaS Demand Letter Language
Here's how I structure a demand letter for an enterprise SaaS non-payment case:
[Client General Counsel]
[Company Address]
Re: Breach of Master Service Agreement — Demand for Payment of $87,500
I represent [Your SaaS Company] in connection with [Client Company]'s material breach of the Master Service Agreement executed on January 15, 2024 (the "MSA").
Background
Pursuant to Section 4.2 of the MSA, Client agreed to pay $150,000 annually for access to [Your Platform], payable in monthly installments of $12,500 due on the first of each month. Client has failed to pay invoices #1047 through #1053, covering the period of June 1, 2024 through December 1, 2024, totaling $87,500.
Despite Client's non-payment, Client has continued to actively use the Platform. Our logs indicate Client users logged in 1,247 times during the non-payment period and processed 15,384 transactions through our API. Client cannot claim non-use or dissatisfaction while simultaneously deriving substantial business value from our service.
Legal Basis for Demand
Client's failure to pay constitutes material breach of the MSA. Under Section 8.3 of the MSA, material breach entitles us to (a) immediate termination, (b) acceleration of all remaining payments under the 3-year term, and (c) recovery of attorney's fees and costs as the prevailing party per California Civil Code §1717.
We have elected not to pursue the full acceleration remedy at this time. However, we demand immediate payment of the $87,500 past due amount, plus:
- Late fees: $4,375 (5% per MSA Section 4.4)
- Interest: $1,458 (10% APR per Cal. Civ. Code §3289(b), calculated from each invoice due date)
- Total amount due: $93,333
Required Action
Payment must be received within 14 days of this letter. If we do not receive payment by [date], we will (1) immediately terminate Client's access to the Platform and delete all Client data per our retention policy, (2) file a lawsuit in Santa Clara County Superior Court seeking the full accelerated contract value of $412,500 plus attorney's fees, and (3) seek a preliminary injunction prohibiting Client from using any proprietary information or data obtained through the Platform.
This template combines breach of contract basics with SaaS-specific leverage points: usage logs, acceleration clauses, and data deletion threats.
Frequently Asked Questions
It depends on your Terms of Service and MSA. Most SaaS contracts allow suspension for non-payment after 30-60 days. I generally recommend suspending access concurrent with (or immediately after) sending the demand letter. Continued free access undermines your leverage and suggests the amount isn't truly urgent. However, read your contract carefully — some agreements require written notice and a cure period before suspension. If you suspend prematurely, the customer might claim you breached first.
This is the most common defense in SaaS payment disputes. Review your SLA carefully. Most SaaS SLAs provide service credits (e.g., 10% credit for 99.5-99.0% uptime) but don't excuse payment entirely unless uptime falls below a catastrophic threshold like 95%. Pull your uptime logs and response time metrics. If you met the SLA thresholds, their defense fails. If you did breach the SLA, calculate the credits owed and offset them against the amount due — they still owe the balance. In your demand letter, include a section titled "SLA Compliance" with your actual performance metrics to preempt this defense.
Generally no. The Computer Fraud and Abuse Act (18 U.S.C. §1030) requires "unauthorized access" or "exceeding authorized access." A paying customer who becomes a non-paying customer still had authorized access — their payment default doesn't retroactively make their access unauthorized. However, if they continue using your service after you've terminated their account or suspended access, that's a different story — at that point they're accessing without authorization. CFAA is most useful against former employees who steal IP, competitors who scrape your platform, or customers who bypass your security measures.
Yes, if your Terms of Service or MSA include a data retention policy that allows deletion upon termination for non-payment. Most SaaS companies retain customer data for 30-90 days post-termination, then permanently delete it. This is powerful leverage — the customer's data is often more valuable than the amount they owe you. In your demand letter, cite the specific contract provision and data retention timeline: "Pursuant to Section 12.3 of our MSA, we will permanently delete all Client data 30 days after termination. Your account will be terminated on [date] if payment is not received, with data deletion occurring on [30 days later]." But don't bluff — if you say you'll delete data, you must actually do it if they don't pay.
The Defend Trade Secrets Act (18 U.S.C. §1836) is a federal statute enacted in 2016. California's Uniform Trade Secrets Act (Civil Code §3426) is the state-level equivalent. They cover similar conduct (misappropriation of trade secrets) and provide similar remedies (injunctive relief, damages, attorney's fees if willful). The key difference is jurisdiction: DTSA allows you to file in federal court regardless of the amount in controversy or state citizenship. Federal court can be advantageous for tech companies because federal judges often have more experience with complex IP issues. I typically cite both statutes in demand letters for IP theft cases to preserve all options.
You can demand reimbursement for the attorney's fees you've already incurred (including my $575 fee to draft the demand letter), but you can't recover them unless your contract includes a prevailing party attorney's fee provision under California Civil Code §1717. In the demand letter, I typically include language like: "Under Section 15.4 of the MSA and California Civil Code §1717, we are entitled to recover attorney's fees and costs as the prevailing party in any litigation arising from this breach. To date, we have incurred $2,450 in attorney's fees addressing your non-payment." This puts them on notice that the amount will keep growing if they force you to file a lawsuit.
For demand letters I personally draft in SaaS disputes, I see full payment or settlement in about 70-80% of cases within 30 days. SaaS companies tend to have better documentation than other industries (detailed contracts, usage logs, clear payment terms), which increases success rates. The key variables are contract quality (well-drafted MSA with clear payment terms vs. clickwrap ToS), amount owed (larger amounts get more attention but also more resistance), and whether you have leverage beyond just the money (data deletion, service termination, IP claims). Enterprise SaaS disputes (contracts over $50K annually) settle at higher rates than SMB disputes because enterprise customers care more about legal risk and vendor relationships.