PCS Software v. Dispatch Services is a lawsuit in the Southern District of Texas between a provider of transportation management software and a customer that stopped paying under a 36-month “Software as a Service Agreement”. After a bench trial, the court held that monthly subscription fees began on the customer’s first use of the software during implementation, enforced a clause making all fees for the remaining term payable on termination for breach, and awarded the vendor $1,437,426.[1]
Background
Dispatch Services, a trucking management company, signed the agreement with PCS Software on 2022-06-06. It chose PCS’s top-tier “diamond package”, which included access for up to 599 users, for a subscription fee of $39,000 per month over 36 months and an implementation fee of $108,639 payable in six instalments, half of it due only at go-live.[1] The initial term started on Dispatch’s “initial use of the Service”, and billing of the subscription fee commenced on the same event; the agreement did not define “initial use”. Before signing, a PCS sales executive had told Dispatch’s adviser in writing that it would be invoiced monthly once the agreement was signed, during implementation.[1]
The dispute
Dispatch paid the first month’s subscription and two implementation instalments, totalling $75,213, then stopped paying without notice and stopped communicating with PCS. The software never went live. PCS suspended the service on 2022-11-22 and terminated the agreement by letter on 2022-12-19 under its termination clauses.[1] It relied on section 2.7.4, under which on such a termination “all Fees that would have become payable had the Agreement remained in effect until expiration of the Term will become immediately due and payable”, and demanded $160,303.02 in overdue invoices plus $1,277,122.98 for the remaining 30 months and implementation fees.[1]
PCS sued on 2023-01-12 for breach of contract.[3] Dispatch’s counterclaims for fraudulent inducement were dismissed, and the court granted PCS partial summary judgment on the unpaid implementation instalment. At trial Dispatch argued that “initial use” meant successful commercial use, and that section 2.7.4 was an unenforceable liquidated damages penalty.[1]
Decision or outcome
In findings entered on 2025-08-19, the court rejected Dispatch’s reading of “initial use”. The agreement used “production use” and “go live” only for the second half of the implementation fee, and defined the Service as the Software as a Service application. Relying on PCS’s expert, the court held that Dispatch used the software when it logged in, implemented, tested, configured it, trained users and migrated data, and that initial use occurred on 2022-06-10 when the first Dispatch user logged in. Dispatch therefore materially breached by failing to pay the September, October and November 2022 subscription fees.[1]
The court enforced section 2.7.4 under Texas law. It found that the clause “accelerates the payments due to PCS over the life of the Agreement” and does not impose a monetary penalty, distinguishing acceleration clauses that collect unearned interest. It also found that the parties knew PCS incurred most of its costs early, during implementation and customisation, so actual damages would be hard to calculate and the clause was a reasonable forecast of just compensation, and that Dispatch offered no evidence that mitigation would have reduced PCS’s loss.[1] On 2025-08-28 the court added prejudgment interest under Texas law and postjudgment interest under federal law.[2] Final judgment was entered on 2025-09-30; the docket later lists an appeals court order and a stipulation of dismissal in March 2026, whose contents are not publicly available.[3]
Significance for software licensing and SAM practice
SaaS agreements commonly bill from signature or first access and commit the customer to a multi-year term. The ruling shows a court holding a customer to the full term of a SaaS subscription for software it never used in production, because billing started at first login and the agreement accelerated the remaining fees on termination for non-payment.[1] Another subscription service dispute, over shared logins, is described in CoStar v. Field.
Lessons learned
- Find the billing trigger. Fees ran from “initial use”, which the court read as the first login during implementation rather than go-live.[1]
- Termination for non-payment can accelerate the whole term. Section 2.7.4 made the remaining 30 months of fees payable at once, and the court enforced it.[1]
- Use the contract’s exit route. Dispatch “did not terminate the Agreement according to its terms; instead, Dispatch simply stopped paying”, which allowed PCS to terminate for breach.[1]
- Raise defences in time. The court noted that Dispatch did not argue that section 2.7.4 was unenforceable until after discovery closed, which limited the record on the issue.[1]