InQuisient v. ServiceNow: Three Data-Platform Patents Settled After 897 Days
InQuisient, Inc. asserted three patents covering computerised data-set manipulation against ServiceNow’s enterprise platform in the District of Delaware. After nearly two and a half years of litigation, the parties reached a confidential settlement, dismissing all claims with prejudice — each side bearing its own legal costs.
Data-platform patent clash ends in confidential deal after 897 days
InQuisient, Inc. filed suit against ServiceNow, Inc. on 5 July 2022 in the District of Delaware before Judge Christopher J. Burke, asserting infringement of three US patents — US7979468B2, US8219585B2, and US8224855B2 — all directed at computerised systems for manipulating data sets. The accused product is ServiceNow’s enterprise platform, which consolidates capabilities into a single shared data model with an extensible table schema and reusable components, eliminating departmental data silos.
The case closed on 18 December 2024 via a stipulated dismissal with prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(ii), the mechanism used when both parties jointly agree to end litigation following a settlement. The underlying settlement agreement is confidential, so the financial terms — including any licence, royalty, or lump-sum payment — are not part of the public record. The with-prejudice designation means InQuisient cannot re-file the same claims against ServiceNow, and the cost-neutrality clause signals a negotiated balance rather than a clear victor.
An 897-day duration is consistent with cases involving multiple software patents that require claim construction, significant prior-art searches, and potentially inter partes review proceedings before settlement pressure peaks. The equal-costs provision suggests neither party had secured a decisive litigation advantage by the time negotiations concluded. What drove the precise settlement terms — licensing value, invalidity risk to the patents, or commercial relationship considerations — remains unknown from the public record.
Filing to Case Settled in 897 days
897 days — nearly 2.5 years, above median for multi-patent Delaware district court cases
Confidential settlement: what dismissal with prejudice means for both parties
FRCP 41(a)(1)(A)(ii): joint stipulated dismissal explained
A Rule 41(a)(1)(A)(ii) dismissal is signed by both parties and filed without requiring court approval. It is the standard procedural vehicle for ending litigation after a private settlement. ‘With prejudice’ means the action is permanently closed — InQuisient cannot reassert the same three patents against ServiceNow on the same facts in any future proceeding.
Permanent bar on re-filingInQuisient secures an exit — but confidential terms limit public signal
The with-prejudice dismissal confirms the dispute is resolved, consistent with InQuisient receiving some form of consideration — though the public record is silent on amount or structure. The cost-neutrality clause suggests InQuisient did not achieve a fee-shifting award. The three patents remain valid and enforceable against other defendants unless separately challenged.
Patents remain live vs. third partiesServiceNow buys litigation peace — scope of licence unclear
ServiceNow avoided a merits adjudication and any public finding of infringement or validity. The confidential settlement likely provides some form of freedom to operate under the asserted patents, but the geographic and temporal scope of any licence granted is unknown. The equal-costs term suggests ServiceNow negotiated from a position of reasonable strength.
No public infringement findingShared data-model patents remain a credible enforcement tool
The settlement — without an invalidity ruling — leaves US7979468B2, US8219585B2, and US8224855B2 intact as enforcement assets. Other enterprise SaaS platforms with unified data-model architectures should assess their exposure to this patent family. The 897-day timeline also signals that InQuisient is prepared to litigate for extended periods, raising the cost calculus for any future defendant.
Risk for SaaS data-platform vendorsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | InQuisient, Inc. | Company | Enterprise data-management IP licensor — holder of US7979468B2, US8219585B2, US8224855B2Search in Eureka ↗ |
| Defendant | ServiceNow | Individual | ServiceNow — cloud-based enterprise workflow and data-platform providerSearch in Eureka ↗ |
| Plaintiff counsel | Adam J. Kessel | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Chet D. Campbell | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Jason W. Wolff | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Meghana Thadani | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Susan E. Morrison | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Taylor Reeves | Attorney | Counsel for InQuisient, Inc.Search in Eureka ↗ |
| Plaintiff law firm | Fish & Richardsin PC | Law Firm | Representing InQuisient, Inc.Search in Eureka ↗ |
| Defendant counsel | Darice Xue | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Diane M. Doolittle | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Gavin Frisch | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Iman Lordgooei | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Jack B. Blumenfeld | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Jennifer Ying | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Jodie Cheng | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | John T. Mckee | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Kevin P.B. Johnson | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Quincy Lu | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Ray R. Zado | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Sandy Shen | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Sean S. Pak | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant counsel | Travis J. Murray | Attorney | Counsel for ServiceNowSearch in Eureka ↗ |
| Defendant law firm | Morris, Nichols, Arsht & Tunnell LLP | Law Firm | Representing ServiceNowSearch in Eureka ↗ |
| Presiding judge | Judge Christopher J. Burke | Judge | Delaware District CourtSearch in Eureka ↗ |
Official order — verbatim text
The stipulated dismissal is formulaic in language but commercially significant in effect. The phrase ‘pursuant to a confidential settlement agreement’ confirms value exchanged, though amount and structure are sealed. ‘With prejudice’ forecloses any future InQuisient action on these patents against ServiceNow on these facts. The equal-costs provision — departing from the American Rule default only when a court orders otherwise — was negotiated, not imposed, suggesting both parties viewed it as equitable. No merits finding was made on infringement or validity.
US7979468B2, US8219585B2 & US8224855B2 — Computerised Data-Set Manipulation
The three asserted patents — US7979468B2, US8219585B2, and US8224855B2 — are directed at computerised systems and methods for manipulating data sets, with particular relevance to enterprise platforms that consolidate information within a single shared data model. The patents cover architectures where reusable components and an extensible table schema eliminate departmental data silos, a design pattern central to modern enterprise workflow and SaaS platforms.
These patents are strategically significant because the accused functionality — a unified data model serving the entire enterprise rather than individual departments — is a core architectural differentiator for platforms like ServiceNow. Any SaaS vendor positioning its platform on data centralisation, schema extensibility, or cross-functional reuse may find its architecture within the claims’ scope. The survival of all three patents without an invalidity ruling raises their value as enforcement instruments against the broader enterprise SaaS sector.
Should your platform be assessed against US7979468B2 and related patents?
Product and engineering teams building enterprise SaaS platforms with a unified data model, extensible table schemas, or shared reusable components should treat this patent family as a live risk. The settlement without invalidity finding means the claims have not been narrowed or invalidated through litigation — their full scope remains intact. Workflow automation, ITSM, CRM, and ERP vendors with single-data-model architectures are the most directly exposed.
PatSnap Eureka’s FTO Search Agent can map your product’s data architecture against the claim language of US7979468B2, US8219585B2, and US8224855B2, identifying design-around options and prior art that may support invalidity arguments. Eureka’s patent family analysis also surfaces continuation or divisional applications that may extend InQuisient’s enforcement reach beyond the three asserted patents.
Run a freedom-to-operate analysis on US7979468B2 to assess your product’s exposure
Run FTO in Eureka →Similar enterprise data-platform patent cases in the District of Delaware
Explore related software and data-platform patent infringement cases litigated in the District of Delaware involving enterprise SaaS and unified data-model architectures.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable A computerized system for manipulating data sets,Platform delivers a common set of core capabilities and reusable components to the entire enterprise rather than individual departments or functions. This eliminates data silos by sharing information within a single data model. The data model is extendible with a flexible table schema and reusable components.-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedInQuisient, Inc.’s broader IP enforcement history
InQuisient, Inc.’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the enterprise SaaS IP landscape
Three surviving data-platform patents, a 2.5-year fight, and a confidential exit — the pattern carries lessons for any SaaS vendor operating a unified data-model architecture.
Multi-patent assertion on a single platform raises claim construction stakes
Asserting three related patents covering data-set manipulation systems — as InQuisient did — concentrates infringement risk on a single accused product. For ServiceNow and peers, this means claim construction rulings on one patent can influence the others. Engineering teams building extensible data models should audit each patent independently for design-around opportunities.
Equal-cost clause signals neither party held a decisive advantage
When settlements include mutual cost-bearing rather than fee-shifting, it typically signals the parties were comparably positioned at the time of resolution — neither having won a dispositive motion outright. For IP strategists, this outcome neither validates nor defeats InQuisient’s infringement theory, leaving the patents’ strength ambiguous for benchmarking purposes.
Patent family exposure extends beyond ServiceNow to competing SaaS platforms
All three patents survived without an invalidity finding. Vendors offering unified-schema, enterprise-wide data platforms — including competitors and adjacent workflow automation providers — remain exposed. A freedom-to-operate analysis against this family is warranted for any product sharing a single extensible data model across enterprise functions.
897-day litigation posture reveals InQuisient’s enforcement patience
InQuisient sustained litigation against a well-resourced defendant for nearly 2.5 years with a six-attorney team. This enforcement stamina, combined with a confidential — rather than public — resolution, is consistent with a licensing programme targeting multiple defendants. Monitoring InQuisient’s filing history for follow-on actions is advisable for SaaS platform operators.
InQuisient v ServiceNow — key questions answered
InQuisient asserted three patents: US7979468B2, US8219585B2, and US8224855B2. All three are directed at computerised systems for manipulating data sets, specifically targeting ServiceNow’s enterprise platform architecture, which uses a shared data model, extensible table schema, and reusable components across the enterprise.
The case was resolved via a confidential settlement and dismissed with prejudice under FRCP 41(a)(1)(A)(ii) on 18 December 2024. Dismissal with prejudice means InQuisient is permanently barred from re-filing the same patent claims against ServiceNow on the same facts. The financial terms of the settlement are not publicly disclosed.
Yes. The dismissal with prejudice resolves only the dispute between InQuisient and ServiceNow. No court made a finding of invalidity or unenforceability as to US7979468B2, US8219585B2, or US8224855B2. These patents remain valid and enforceable against third parties unless separately challenged through IPR, ex parte reexamination, or another litigation.
The stipulation explicitly states each party bears its own costs, expenses, and attorneys’ fees. This mutual cost-bearing is a negotiated term rather than a court-ordered outcome. It typically signals that neither party secured a sufficiently decisive litigation position — such as a winning summary judgment motion — to justify demanding fee-shifting from the other side.
The case lasted 897 days from filing on 5 July 2022 to closure on 18 December 2024 — approximately 2.5 years. This duration is consistent with multi-patent software litigation involving claim construction proceedings and extensive discovery. It suggests InQuisient was prepared to litigate aggressively and that settlement was reached relatively late in the proceedings rather than at an early stage.
Protect your enterprise platform from data-model patent risk
The InQuisient patents survive without an invalidity finding. Run an FTO analysis on US7979468B2 and related patents now, and set alerts for new enforcement filings targeting SaaS platforms with shared data architectures.
PatSnap Eureka searches patents and litigation data to answer instantly.