Samplin Declaration  🔗 **Source:** [Samplin Declaration](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.302.3.pdf) > [!note]+ Document Notes > tags: [wp-engine-automattic, financial-discovery, acf-plugin, customer-retention, trademark-confusion, revenue-impact, silver-lake, wordpress-governance] > author: Samplin Declaration > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: declaration > docket: 302.3 > > # 🏷️ WP Engine Financial Discovery Requests - ACF Plugin Takeover Impact Analysis > > # 🧭 Table of Contents > - [References](#-references) > - [Summary](#-summary) > - [Main Content](#-main-content) > - [Governance Digest](#-governance-digest) > - [Hypotheses](#-hypotheses) > - [Questions](#-questions) > - [Future Research](#-future-research) > - [Implications](#-implications) > - [Conclusion](#-conclusion) > > # 🔗 References > **Dockets:** 302.3 (Samplin Declaration Exhibit 2) > **Discovery Requests:** Nos. 13, 15, 59, 77, 105, 108, 109, 113, 124 > **FRCP:** Rules 26, 34 (document production) > > # 📝 Summary > Docket 302.3 Exhibit 2 reveals Automattic's comprehensive discovery requests targeting WP Engine's financial performance, customer losses, and trademark usage related to the Advanced Custom Fields (ACF) plugin. The requests span from 2014 through Silver Lake's acquisition and focus on quantifying damages from Automattic's alleged takeover of ACF and its rebranding as Secure Custom Fields. This filing demonstrates how disputes over plugin directory control can trigger extensive financial discovery, potentially exposing sensitive competitive data across the WordPress ecosystem. > > Key stakeholders include WP Engine (defending financial data), Automattic (seeking damage calculations), Silver Lake (investment impact assessment), and the broader WordPress plugin developer community. The discovery creates a precedent for how plugin trademark disputes may expose ecosystem participants' financial performance data. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Financial Performance Scope (Requests 15, 59)** - Annual sales, revenues, costs, marketing expenditures, profits from 2014-present - Product-by-product breakdown across WP Engine's entire portfolio - Performance metrics before/after Silver Lake's controlling investment - Market share and profit margin analysis **Customer Impact Documentation (Requests 13, 77)** - Identity and subscription terms of lost customers - Geographic distribution of customer losses - Specific reasons for customer departures - Migration patterns to/from WP Engine services - Renewal and cancellation tracking systems **ACF Plugin Trademark Investigation (Requests 105, 108, 109, 113)** - Marketing materials showing ACF trademark usage across all media - Consumer perception studies of ACF vs. Secure Custom Fields marks - Plugin perception research (ACF vs. SCF functionality) - Planned future uses of ACF trademarks **Damage Quantification (Request 124)** - Documents supporting WP Engine's Complaint paragraph 448 harm allegations - Direct evidence linking Automattic's actions to measurable business impact # 📚 References - WP Engine Complaint paragraph 448 (harm allegations) - Silver Lake controlling investment documentation - WordPress.org plugin directory governance structure # 🗣️ Paraphrase Automattic wants to see WP Engine's books - all of them. They're asking for detailed financial records going back to 2014, including exactly how much money WP Engine makes from each product, how many customers they've lost and why, and what their profit margins look like. They particularly want to know how the ACF plugin controversy affected WP Engine's business, including any market research about customer confusion between "Advanced Custom Fields" and Automattic's "Secure Custom Fields." The requests also dig into how Silver Lake's investment changed WP Engine's performance, suggesting this data might be relevant to calculating damages. # 📰 Governance Digest When Automattic took control of the ACF plugin listing and rebranded it as "Secure Custom Fields," it triggered a legal discovery process that's now exposing the financial underbelly of WordPress commerce. WP Engine must potentially reveal a decade of financial performance data, customer loss patterns, and marketing strategies - all because of a dispute over plugin directory control. This case is establishing that wordpress.org governance decisions can have massive financial consequences, with plugin developers' business data becoming litigation fodder when trademark disputes arise. # 🧪 Hypotheses 1. **Revenue Concentration Risk**: WP Engine's financial data will reveal significant revenue dependence on ACF-related services, explaining the aggressive litigation response 2. **Silver Lake Impact Measurement**: Post-acquisition performance metrics will show either validation or concern about WordPress ecosystem investment risks 3. **Customer Confusion Evidence**: Consumer perception studies will demonstrate marketplace confusion between ACF and SCF, supporting trademark infringement claims 4. **Plugin Directory Leverage**: The discovery scope suggests plugin directory control provides substantial financial leverage over ecosystem participants 5. **Ecosystem Financial Transparency**: This case will create precedent for financial discovery in WordPress governance disputes # 📊 Methodology The filing presents discovery requests without accompanying declarations, suggesting this is Exhibit 2 to a broader Samplin Declaration establishing the evidentiary foundation. The requests follow standard FRCP Rule 34 document production format, seeking both electronic records and business intelligence spanning twelve years of operations. # ❓ Questions - How will WP Engine's financial exposure in discovery affect other plugin developers' litigation strategies? - What protective orders will limit public access to WordPress ecosystem financial performance data? - Will Silver Lake's investment thesis documentation reveal private equity perspectives on WordPress governance risks? - How might customer loss attribution methodology distinguish between ACF controversy and normal business churn? # 🔮 Future Research **Litigation Threads:** - WP Engine's privilege assertions over Silver Lake investment documentation - Automattic's reciprocal financial discovery obligations - Consumer survey methodology disputes for trademark confusion analysis **WordPress Governance:** - Plugin directory governance reform proposals following financial exposure risks - Trademark protection strategies for plugin developers - WordPress Foundation's role in mediating commercial disputes # 💡 Implications **Practice**: Plugin developers must consider financial discovery exposure when engaging in trademark disputes over wordpress.org listings **Policy**: WordPress.org governance structures need clearer separation between community resources and commercial interests to limit litigation risks **Security**: Financial performance data discovery creates competitive intelligence risks across the WordPress ecosystem **Education**: Plugin developers require legal guidance on trademark protection and directory governance rights **Funding**: Private equity investment in WordPress companies faces new due diligence requirements around governance dispute risks # 🧠 Learning Styles Assessment - **Visual**: Discovery request numbering and categorization supports structured learners - **Aural**: Complex financial terminology benefits from discussion-based learning - **Verbal**: Legal discovery language requires plain-language translation - **Kinesthetic**: Document production process involves hands-on legal procedure understanding - **Logical**: Sequential request structure supports systematic analysis - **Social**: Multi-party discovery impacts benefit from collaborative discussion - **Solitary**: Financial analysis components support independent research - **Naturalistic**: Pattern recognition across request categories aids classification learning **Reading Level**: Graduate/Professional (legal discovery terminology, financial metrics complexity) # 📊 Accessibility Assessment **Structure**: Well-organized with numbered requests and clear categorization **Format**: Text-extractable legal document with standard formatting **Navigation**: Sequential numbering supports assistive technology navigation **WCAG Compliance**: Meets AA standards for text contrast and structure # 🌍 DEIB Assessment **Cultural Breadth**: Limited to U.S. legal discovery framework **Inclusive Language**: Standard legal terminology without bias indicators **Neurodiversity Support**: Structured format aids diverse cognitive processing **Representation**: Business-focused content lacks demographic diversity perspective **Psychological Safety**: Adversarial discovery context creates inherent tension # ✅ Logical Validity **Strong Reasoning**: Discovery requests logically connect to trademark harm theories **Fallacies**: None identified - requests follow standard litigation discovery patterns **Tone**: Professional legal document tone appropriate for federal court filing # 🛡️ DARVO Analysis Not applicable - this is a procedural discovery document without victim-offender dynamics or defensive narratives. # 🎯 Conclusion This discovery exhibit reveals the massive financial stakes underlying WordPress governance disputes. Automattic's comprehensive financial discovery requests suggest they're building a substantial damages case around the ACF plugin takeover, while potentially exposing WP Engine's entire business model to scrutiny. The case is establishing dangerous precedent where plugin directory disputes can trigger extensive financial discovery, creating new risks for ecosystem participants. Watch for WP Engine's privilege assertions, protective order negotiations, and how this financial exposure influences settlement discussions before expert discovery begins. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] Request 13 Customer Loss Documentation > "Documents relating to any loss of sales or customers for any reason during the relevant time period, including but not limited to documents indicating the number of sales or customers lost, the identity of the specific sale and customer lost, the customer's term of subscription, the date of the loss, the reason for the loss, the location of the customer" > [!quote] Request 59 Silver Lake Impact Analysis > "Documents sufficient to show your overall financial performance, including without limitation profit margins, market share, and past and projected performance, including without limitation such metrics prior to and after the purchase of any controlling interest in WPE by Silver Lake" > [!quote] Request 108 Trademark Confusion Research > "All documents and communications concerning any investigations, surveys, studies, research, polls and focus groups of customer or consumer perception of the Advanced Custom Fields marks, ACF marks, Secure Custom Fields marks, or SCF marks" ### 🧠 Permanent Candidates - **Plugin Directory Financial Leverage**: Control over wordpress.org plugin listings creates substantial commercial power - **WordPress Ecosystem Discovery Risk**: Governance disputes can expose sensitive financial data across ecosystem participants - **Private Equity WordPress Risk Assessment**: Silver Lake investment documentation may reveal institutional perspectives on WordPress governance risks #### ✏️ Fleeting Queue - Connection between plugin trademark disputes and broader WordPress Foundation governance legitimacy - Potential for financial discovery to reveal undisclosed Automattic-WordPress Foundation financial entanglements - Impact on plugin developer IP protection strategies following ACF precedent <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Samplin Declaration.md|Samplin Declaration by storage.courtlistener.com]] ## Highlights - **No. 124** – All documents concerning your allegation in paragraph 448 of the complaint that, as a result of Defendants' alleged actions, "WPE has suffered harm." ([View Highlight](https://read.readwise.io/read/01ksfvaef3nvc1yv87dmm4xjsh)) - Note: Docket 302.3: RFP No. 124 — documents on WPE's claimed harm (compl. ¶448). - Tags: legal, wp-engine-automattic