Peter Pedersen v. Salesforcecom Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Peter Pedersen (Denmark)
  • Defendant: Salesforce.com Inc. (Delaware)
  • Plaintiff's Counsel: Ramey LLP
• Case Identification: 6:22-cv-00409, W.D. Tex., 04/22/2022
• Venue Allegations: Venue is asserted based on Defendant having a regular and established place of business within the Western District of Texas, specifically an office in Austin.
• Core Dispute: Plaintiff alleges that Defendant's Salesforce Essentials platform infringes a patent related to a system for managing the distribution of electronic messages based on profiles created by both message senders and recipients.
• Technical Context: The technology addresses rule-based electronic message distribution, a foundational element of modern Customer Relationship Management (CRM) and marketing automation services that aim to deliver targeted content based on user preferences.
• Key Procedural History: The complaint does not mention any prior litigation, inter partes review (IPR) proceedings, or licensing history related to the patent-in-suit.

Case Timeline

Date	Event
2000-07-12	U.S. Patent No. 6,965,920 Priority Date
2005-11-15	U.S. Patent No. 6,965,920 Issued
2022-04-22	Complaint Filed

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

• Patent Identification: U.S. Patent No. 6965920 ("the '920 Patent"), titled "Profile Responsive Electronic Message Management System," issued on November 15, 2005.

The Invention Explained

• Problem Addressed: The patent's background section describes the growing complexity and inefficiency of distributing information to customers and clients in the early 2000s '920 Patent, col. 1:21-34 It notes that mass-messaging methods, such as "spam e-mail" and "junk mail," are often irrelevant and annoying to recipients, while managing individual communication preferences across multiple information providers is a difficult task for both the providers and the end-users '920 Patent, col. 1:52-2:4
• The Patented Solution: The invention proposes a centralized electronic message management system where both "messengers" (content senders) and "recipients" can create and manage profiles '920 Patent, abstract Recipients can specify rules for what messages they wish to receive, from which messengers, and via which delivery channels (e.g., email, fax) '920 Patent, col. 2:26-32 Concurrently, messengers can define their own profiles, including the types of message services they offer '920 Patent, col. 2:32-39 An "individual message generator" then matches the available messages with recipient preferences to distribute customized, targeted communications '920 Patent, col. 2:61-3:1 The overall system architecture is depicted in Figure 4 '920 Patent, Fig. 4
• Technical Importance: The patented system describes a dual-sided preference model intended to improve the relevance of electronic communications by giving both senders and receivers granular control, a concept that underpins modern permission-based digital marketing and CRM platforms '920 Patent, col. 2:26-32

Key Claims at a Glance

• The complaint asserts infringement of at least independent claim 1 Compl. ¶17
• The essential elements of independent claim 1 are:
  • An electronic message management system comprising an electronic computer system and an electronic message management database.
  • A "recipient profile application" for receiving and storing profile data from recipients, including delivery parameters (where, when, how) for messages.
  • A "messenger profile application" for receiving and storing profile data from messengers, including identifying data.
  • A "message input application" for receiving and storing message files from a messenger.
  • An "individual message generator" that accesses the database to generate and send an individual message to a recipient according to specified delivery parameters.
  • A "message management server operating system".
  • A "message management database" that includes separate recipient profile, messenger profile, and message data file databases.
• The complaint reserves the right to assert additional claims Compl. ¶22

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is "Salesforce's Essentials platform" Compl. ¶15

Functionality and Market Context

• The complaint describes the Salesforce Essentials platform as a "cloud-based email marketing service that allows messengers to send emails to recipients" Compl. Ex. B, p. 1 Its allegedly infringing functionality includes a "Web-to-Lead" application, which allows messengers to create forms to capture recipient information and preferences Compl. Ex. B, p. 2 This data is stored in a database of "Leads" Compl. Ex. B, p. 5 The platform also allegedly allows messengers to store their identifying information and provides a "Send List Email" feature for creating and sending messages to recipients based on filtering criteria Compl. Ex. B, p. 9 Compl. Ex. B, p. 10 A screenshot from the complaint's claim chart shows a "Leads Overview List" which functions as a database of recipient data Compl. Ex. B, p. 5, Fig. 6

IV. Analysis of Infringement Allegations

'920 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
An electronic message management system comprising: an electronic computer system in operative communication with a global digital communications network, and an electronic message management database in operative communication with the computer system...	Salesforce Essentials is described as a cloud-based service operating on web servers that are in operative communication with the internet and store information in databases. The complaint provides a screenshot showing Salesforce's server status page (Compl. Ex. B, p. 1, Fig. 1).	Ex. B, p. 1	col. 5:1-14
a recipient profile application for receiving recipient profile data from recipients via the global network and storing the recipient data in the database, the profile data including delivery parameters specified by a recipient of where, when and how specific types of messages from specific messengers are delivered to the recipient,	The "Web-to-Lead" application allegedly allows messengers to create a recipient profile form. The "Custom Fields" feature is alleged to enable the specification of "when" and "how" parameters, such as the weekday and device for receiving messages. The complaint includes a screenshot of the "Web-to-Lead Set-up" interface (Compl. Ex. B, p. 2, Fig. 2).	Ex. B, pp. 2, 6	col. 3:11-23
a messenger profile application for receiving messenger profile data from messengers via the global network and storing the messenger data in the database, including messenger identifying data,	Salesforce Essentials allegedly provides "Email Footers," which allows a messenger to enter, store, and maintain identification information and an email signature.	Ex. B, p. 9	col. 3:24-33
a message input application for receiving message files from a messenger via the global network and storing the message files in the database, and	The "Send List Email" application allegedly allows messengers to create messages using a content editor via a web browser. A screenshot shows the content editor interface for composing an email (Compl. Ex. B, p. 11, Fig. 13).	Ex. B, p. 10	col. 3:40-47
an individual message generator in communication with the database and operative to access and utilize data and files from the database to generate an individual message to be sent to the recipient specified by the messenger via the global communications network according to the delivery parameters...	The "Send List Emails" feature allegedly generates individual messages for recipients based on delivery parameters. The complaint alleges this is accomplished through a filtering function that creates a Leads List based on parameters like email, promotions, and day of the week.	Ex. B, p. 12	col. 3:48-58
the message management database including recipient and messenger profile databases for storing recipient and messenger profile data respectively, and a message database for storing message data files.	Salesforce allegedly operates web servers that store information associated with the Salesforce Essentials application, including recipient data (in "Leads"), messenger data, and the messages created by messengers.	Ex. B, p. 14	col. 3:7-10

• Identified Points of Contention:
  • Scope Questions: The infringement theory maps components of a modern, integrated SaaS platform onto the distinct "applications" (e.g., recipient profile, messenger profile) described in the patent. A potential dispute is whether Salesforce's "Email Footers" feature, which the complaint alleges to be the "messenger profile application", performs the functions contemplated by the patent, which describes a system for messengers to define the types of message services they offer, not just their identity '920 Patent, col. 8:19-22
  • Technical Questions: The complaint alleges that the "Web-to-Lead" feature, which is typically used by a business to capture sales leads from its own website, constitutes the claimed "recipient profile application". This raises the question of whether a form created and controlled by the messenger to capture data is equivalent to the patent's system where a recipient can centrally create and manage their own profile to control messages from multiple, independent messengers '920 Patent, col. 7:46-54

V. Key Claim Terms for Construction

• The Term: "recipient profile application"

  • Context and Importance: The infringement case hinges on mapping this term to the accused "Web-to-Lead" feature. The construction of this term will be critical to determining if a messenger-created lead capture form is equivalent to the recipient-centric profile management system described in the patent.
  • Intrinsic Evidence for a Broader Interpretation: The claim requires an application "for receiving recipient profile data from recipients via the global network and storing the recipient data in the database" '920 Patent, col. 11:25-29 Plaintiff may argue that the "Web-to-Lead" feature literally meets this functional description.
  • Intrinsic Evidence for a Narrower Interpretation: The specification describes a system where "a recipient will access the message server... through recipient profile editor/web interface" to "enter his/her basic identification data" and define preferences '920 Patent, col. 7:49-59 This language, along with the problem statement of giving recipients centralized control, may support an interpretation that requires the application to be primarily a tool for the recipient, not a lead-generation tool for the messenger.

• The Term: "messenger profile application"

  • Context and Importance: The complaint's allegation that the "Email Footers" feature satisfies this limitation appears tenuous. The viability of this infringement theory depends on whether a simple identity/signature feature can be construed as the claimed "application."
  • Intrinsic Evidence for a Broader Interpretation: The claim language requires an application for receiving "messenger identifying data" '920 Patent, col. 11:35-36, which an email footer arguably contains.
  • Intrinsic Evidence for a Narrower Interpretation: The detailed description states that a messenger uses this application to specify "the types of messages and types of content the messenger is providing to recipients in general" '920 Patent, col. 8:19-22 Practitioners may focus on this language to argue that the term requires a structured system for defining a messenger's service offerings, a function potentially absent from a simple email footer setting.

VI. Other Allegations

• Indirect Infringement: The complaint makes conclusory references to indirect and induced infringement but does not plead specific facts to support the required elements of knowledge and intent, such as referencing user manuals or specific marketing materials that instruct users to perform the infringing steps Compl. ¶3 Compl. ¶11
• Willful Infringement: The complaint alleges that Defendant made "no attempt to design around the claims" and "did not have a reasonable basis for believing that the claims of the '920 Patent were invalid" Compl. ¶18 Compl. ¶19 These allegations are not supported by specific facts demonstrating pre-suit knowledge of the patent or its infringement. The filing of the lawsuit itself provides post-suit knowledge for the purpose of potential ongoing infringement.

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

• A core issue will be one of architectural mapping: can the patent's circa-2001 model of distinct, separately defined "applications" be read onto the features of a modern, integrated, multi-tenant SaaS platform like Salesforce Essentials, or is there a fundamental mismatch in the way the systems are structured and operate?

• The case may also turn on a question of functional scope: does the act of setting an email signature (the accused "messenger profile application") satisfy the claim requirement for an application where messengers define the specific types of message services they offer, or does the claim require a more robust, structured functionality that is not present in the accused product?

• A central claim construction dispute will likely be one of definitional perspective: is the "recipient profile application" a tool controlled by the recipient to manage incoming messages from many sources, as the patent specification may suggest, or can it be a form created and controlled by a single messenger to capture leads, as alleged in the complaint?