Kaufman v. Zoho Tech Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Michael Philip Kaufman (New York)
  • Defendant: Zoho Technologies Corporation (California)
  • Plaintiff's Counsel: Jackson Walker LLP; Liston Abramson LLP
• Case Identification: 1:25-cv-01082, W.D. Tex., 02/26/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendant Zoho Technologies Corporation maintains its U.S. headquarters and a regular and established place of business within the district, and has allegedly committed acts of infringement there.
• Core Dispute: Plaintiff alleges that Defendant's Zoho CRM online services infringe three U.S. patents related to the technology for automatically generating a user interface to work with data in a relational database.
• Technical Context: The technology at issue addresses the automated generation of user interfaces for complex relational databases, a foundational process for creating modern data-driven software applications such as customer relationship management (CRM) systems.
• Key Procedural History: The complaint alleges that Plaintiff licensed U.S. Patent No. 10,977,220 to Salesforce.com Inc. on July 7, 2021. The alleged period of infringement for all asserted patents is from July 2019 to February 2022.

Case Timeline

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,885,981 - "System and Method for Generating Automatic User Interface for Arbitrarily Complex or Large Databases"

The Invention Explained

• Problem Addressed: The patent addresses the "recurring practical problem" that user interface (UI) routines for relational databases historically had to be written and adjusted by hand on a per-table basis, a process that was inefficient and difficult to maintain, especially when the underlying database structure changed Compl. ¶13
• The Patented Solution: The invention provides for a software system that automatically generates a fully functional user interface based on an "automated interrogation" of the database schema (structure) '981 Patent, abstract This automated process constructs a working application that supports standard database interactions (e.g., create, retrieve, update, delete or "CRUD" operations) and enforces the database's relational rules, all without requiring manual, per-table programming Compl. ¶14 '981 Patent, col. 8:5-10
• Technical Importance: This automated approach aimed to significantly reduce the development time and maintenance burden for complex, data-driven applications by decoupling the UI generation from manual coding.

Key Claims at a Glance

• The complaint asserts independent claim 5 Compl. ¶20
• Claim 5 of the '981 Patent recites the essential elements of:
  • A computer-readable storage medium with instructions for a general-purpose computer.
  • The instructions are for automatically generating a user interface for working with data in a relational database of arbitrary size or complexity.
  • The instructions comprise:
    • (a) a routine for providing a user interface paradigm with modes for interaction (create, retrieve, update, delete) and corresponding display formats.
    • (b) a routine for scanning the database to determine its structure (tables, constraints, relationships) and storing representations of that structure.
    • (c) a routine for using these representations to construct a corresponding client application that connects to the database and provides displays and mechanisms for interacting with the data.

U.S. Patent No. 10,025,801 - "Systems and Methods for Automatically Generating User Interface Elements for Complex Databases"

The Invention Explained

• Problem Addressed: The complaint describes a major drawback in automatic UI generation where relationships between database tables are represented by cryptic "foreign key" values (e.g., a numerical ID), which have no meaning to the end-user Compl. ¶¶50-51 A user would see an ID number instead of a human-readable value like "English" or a customer's name.
• The Patented Solution: The invention provides a technique to solve this problem by automatically creating an "enhanced representation" of the data '801 Patent, abstract The system identifies the foreign key, locates the corresponding record in the related "foreign" table, and selects a descriptive value (like a name or description) from that record to display in place of the cryptic key ID Compl. ¶51 '801 Patent, abstract
• Technical Importance: This technique makes automatically generated UIs more intuitive and user-friendly by presenting meaningful data rather than internal database identifiers.

Key Claims at a Glance

• The complaint asserts independent claim 5 Compl. ¶49
• Claim 5 of the '801 Patent recites the essential elements of:
  • A non-transitory machine-readable medium with routines for displaying an "enhanced representation of data" from a database containing a primary and a foreign table.
  • The routines automatically construct this representation by:
    • Identifying a foreign key (FK) value in a primary table row that references the foreign table.
    • Locating the row in the foreign table whose primary key (PK) matches the FK value.
    • Selecting a value from that foreign table row "other than the PK value."
    • Using the selected value to derive a description that supplants the original FK value in the final representation.
    • Displaying the constructed representation.

U.S. Patent No. 10,977,220 - "Systems and Methods for Automatically Generating User Interface Elements for Complex Databases"

The Invention Explained

The '220 Patent claims a system for automatically generating a database UI. It describes a set of instructions that include a routine for scanning the database to determine its data model, a routine for creating machine representations of that model, and a routine for using those representations to construct a client application that provides CRUD functionality and manages data relationships, all without requiring "any incremental human intervention on a per table basis" Compl. ¶¶60-69 The complaint alleges that the Zoho UI's ability to dynamically adapt when a user alters the database structure (e.g., adds a column) is evidence that it performs the claimed process of re-scanning the database, creating new representations, and re-rendering the UI accordingly Compl. ¶64

Key Claims at a Glance

The complaint asserts independent claim 14 Compl. ¶59

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are Zoho's customer relationship management (CRM) software and related online services ("the Services") Compl. ¶16

Functionality and Market Context

The complaint describes Zoho CRM as a widely used, internet-accessible application for managing business data related to procurement, inventory, and accounting Compl. ¶¶16-17 Functionally, the data in Zoho CRM is organized into "modules," which the complaint alleges are relational database tables Compl. ¶18 Compl. ¶22 The complaint provides a screenshot showing default modules like "Leads, Contacts, Accounts, Deals" and notes that users can also create custom modules Compl. ¶22 Compl. ¶23 These modules allegedly comprise tables with defined relationships, such as a "Contact" record containing a field that cross-references a corresponding "Account" record Compl. ¶24 Compl. ¶32

IV. Analysis of Infringement Allegations

U.S. Patent No. 7,885,981 Infringement Allegations

Identified Points of Contention

• Evidentiary Question: The complaint alleges that the existence of the "routine for scanning" (element b) can be "reasonabl[y] infer[red]" from the observed behavior of the Zoho UI Compl. ¶36 A primary point of contention may be whether discovery will produce direct evidence that the accused system actually performs the claimed scanning and representation-storing steps, or if the observed dynamic UI is achieved through a different technical method.
• Scope Question: The analysis may raise the question of whether Zoho's browser-based UI, which is generated and updated in response to user actions, constitutes a "client application" that is "construct[ed]" using stored "representations" as required by the claim, or if it operates on a different architectural principle.

U.S. Patent No. 10,025,801 Infringement Allegations

Identified Points of Contention

• Technical Question: Claim 5 requires that the descriptive value be selected from the foreign table "based on at least one of 'column name,' 'column position,' etc." Compl. ¶54 A key technical question will be what evidence the complaint provides that Zoho's selection mechanism relies on one of these specific, claimed heuristics, as opposed to another method, such as a user-defined setting or a hard-coded default.
• Scope Question: The dispute may raise the question of what constitutes an "enhanced representation." While the patent provides a specific method, a defendant might argue its representation is achieved differently and thus falls outside the claim scope, even if the end result appears similar to the user.

V. Key Claim Terms for Construction

U.S. Patent No. 7,885,981

• The Term: "a routine for providing a user interface paradigm" (Claim 5)
• Context and Importance: This term is central to defining the overall system architecture required by the claim. The construction will determine whether a "paradigm" simply refers to any organized UI or if it requires the specific, structured set of modes (Browse, Search, etc.) and navigational elements detailed in the patent specification.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The term itself is general. The patent repeatedly discusses generating a "fully functional UI system" as the goal, which may support an interpretation that any system achieving this is a "paradigm" '981 Patent, col. 8:1-5
  • Evidence for a Narrower Interpretation: The detailed description states that the "paradigm encompasses: 1) A set of 'modes' for interacting" including "BROWSE," "SEARCH," "EDIT," and "ADD," along with specific navigational elements like a "TITLE BAR," "TABLE-NAVIGATION HEADER," and a "CONTEXT-STACK DISPLAY" '981 Patent, col. 9:53-65 '981 Patent, col. 10:1-12 This detailed enumeration could support a narrower construction requiring these specific features.

U.S. Patent No. 10,025,801

• The Term: "select a value...based on at least one of the following attributes...: column name; column datatype; at least one column constraint; or column position" (Claim 5)
• Context and Importance: This limitation defines the specific technical mechanism for choosing the human-readable data. The infringement analysis may turn entirely on whether the accused system uses one of these four enumerated heuristics to select the descriptive field.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The use of "at least one of" suggests that employing any single one of these methods is sufficient to meet the limitation. The patent's focus is on the general problem of replacing cryptic keys, and these may be presented as exemplary, non-limiting ways to do so.
  • Evidence for a Narrower Interpretation: The patent provides a detailed default behavior for determining the "name" field, which relies on a field-naming convention (a specific type of "column name" attribute) '801 Patent, col. 12:55-64 A defendant might argue that the "based on" language requires a direct and intentional use of one of these attributes as the logical basis for selection, not merely an incidental correlation.

VI. Other Allegations

• Indirect Infringement: The complaint's formal counts are exclusively for "Direct Infringement" Compl. p. 5, header for Count I Compl. p. 20, header for Count II Compl. p. 25, header for Count III However, the complaint alleges that Zoho's infringement arises from acts that include creating copies of its software on servers "from which it may cause users to download the ZRMS to make additional copies thereof on each user's computer" Compl. ¶45 Compl. ¶55 Compl. ¶70 While these factual allegations could potentially support a theory of induced infringement, no formal count for indirect infringement is pleaded.
• Willful Infringement: The complaint does not contain an explicit allegation of willful infringement.

VII. Analyst's Conclusion: Key Questions for the Case

This dispute centers on whether Defendant's widely-used CRM platform utilizes the specific patented methods for automatically generating its user interface. The case will likely turn on the following key questions for the court:

• A core issue will be one of technical implementation and proof: Does the Zoho CRM system, in fact, perform the specific routines recited by the claims, such as "scanning" the database to create "representations" ('981 Patent) and "selecting" descriptive values based on specific heuristics like column name or position ('801 Patent)? Because the complaint infers the existence of some of these internal software routines from the UI's external behavior, a central focus of discovery will be to determine the actual underlying architecture of the accused system.
• A second key question will be one of definitional scope: Can the term "client application," which the patent describes as being "construct[ed]" from stored representations of a database, be construed to read on a dynamic, browser-based service like Zoho's? The interpretation of this term will be critical in determining whether the architecture of the accused web service aligns with the system described in the patents.