# Open Source Project Market Share Tracks Founder Trust Open source projects with concentrated leadership — a BDFL, a foundation chair, a single trademark holder — accrue market share through a chain of vendor and integrator recommendation decisions that depend on trusting the person at the center. When that trust erodes, vendors quietly stop recommending the project to clients; that change in recommendation behavior precedes and predicts measurable market-share decline by months. The relationship is not direct, but the recommendation layer is the transmission belt between specific founder actions and aggregate adoption numbers. The clearest current data point is WordPress. Roger Montti's Search Engine Journal analysis documents six consecutive months of market-share decline (43.2% → 41.9%, December 2025 to May 2026) at precisely the moment WordPress 7.0 shipped the AI integration scaffolding that should have driven the opposite trajectory (Source: [[3. Resources/Readwise/Articles/WordPress Market Share Declines For Six Months In A Row]]). The article includes a vendor's first-person account explaining the mechanism: "Honestly your position on the WP issue pushed me away from WordPress and I haven't recommended it in about 2 years because I as a vendor need to trust the people leading the software I recommend." That single quote names the causal layer the headline number measures — the recommend-rate among integrators and vendors who place clients on platforms, and who treat founder posture as a precondition for their recommendation. The trust erosion is documentable as specific events. Trent Lapinski's first-person testimony as a former Foundation volunteer ("basically just used as a shell nonprofit that never reached its potential or promise" — Source: [[3. Resources/Readwise/Tweets/I Obviously Don’t Want Any Harm to Come to WordPress]]) names a specific governance failure. Pancho Avila's critique of the WP23 post for using Eric Binnion's terminal-cancer diagnosis as "legal-PR leverage" (Source: [Matt, I’ve Followed the WordPress Saga for a While Now...](3.%20Resources/Readwise/Tweets/Matt,%20I’ve%20Followed%20the%20WordPress%20Saga%20for%20a%20While%20Now....md)) names a specific ethical failure. Each event by itself is recoverable; in aggregate they shift the trust calculus for vendors who recommend. The market-share decline is what that aggregate shift looks like after months of compounding. The contrast case sharpens the claim. Dries Buytaert's "Grow the ecosystem, not just yourself" (Source: [[3. Resources/Readwise/Articles/Grow the ecosystem, not just yourself]]) was written in response to a similar competitive attack on Acquia from Pantheon — but Drupal's market share has not collapsed in response. The founder posture is materially different: Buytaert published contribution data (2,955 Acquia credits vs Pantheon's 30) as the basis for an argument, declined to escalate, and framed the disagreement in terms of social-contract stewardship. Trust in Buytaert as project lead has not measurably eroded, and Drupal's recommendation behavior among Acquia's customers and integrators has not visibly shifted. Same competitive structure, different founder posture, different downstream outcome on the trust → recommendation → market-share chain. The mechanism is specific to founder-concentrated projects, which is most consumer-grade open source. Linux's distributed governance distributes the trust function across many maintainers — Linus's individual reputation matters but doesn't gate enterprise distribution decisions in the way Mullenweg's gates WordPress hosting recommendations. Apache and similar foundation-governed projects similarly buffer the trust impact of individual figures. The note applies most strongly where governance is concentrated, recommendation is the primary growth channel, and the founder's public conduct is legible to the recommend-makers. <!-- atomicity: 1 idea ✓ --> ## Why This Matters For **vendor evaluation of OSS platforms**, this claim implies treating founder trust as a real measurable input rather than a soft cultural variable. Specifically: track the recommendation behavior of vendors and integrators in the project's ecosystem (have any prominent ones publicly stopped recommending? what reasons did they give?), not just official adoption metrics. The recommendation-layer signals lead the headline-share signals by months. For **founder behavior in OSS projects**, the implication is that public conduct decisions in the trust-erosion direction have to be priced against not just short-term reputation cost but the months-later market-share consequences. The WP23 post's "LITERALLY DYING" framing and the WordPress.org-as-pulpit choice each looked locally tactical but each cost trust among the recommend-makers, and the cumulative effect shows up in the SEJ headline number ~6 months later. For **enterprise platform decisions**, the implication is that a project's stated technical roadmap is less predictive of where market share goes than the founder's trust trajectory among the integrator community. WordPress's actual AI integration in 7.0 is technically substantial; that's not what's driving the 6-month decline. Buying decisions are being made through the recommendation layer, which is being made through the founder-trust layer. For **open source governance design** more broadly, this note adds empirical weight to the case for distributing the founder role (see [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] and [[3. Resources/Permanent Notes/Empowerment Without Clarity Is Abdication]]). A project that can survive specific founder-trust events without losing market share is one whose recommend layer doesn't depend on any single person's trust capital. ## Counterpoints to Hold - The Search Engine Journal six-month window is short relative to the underlying WP saga (started 2024-09). Six months of decline could reverse if founder posture changes; the claim that "market share tracks founder trust" needs longer-window data than is currently available to be confidently structural rather than temporally coincident. - Other factors plausibly contribute to the WP decline that the trust narrative may overweight: AI-native site builders that didn't exist a year ago (Vercel v0, Lovable, Bolt), Shopify's commerce integration improvements, broader CMS market consolidation. Disentangling founder-trust effect from these adjacent shifts is hard without controlled comparisons. - The "vendor recommendation" mechanism is partially observable through public statements but mostly happens in private — sales calls, integrator advisories, client deck slide updates. The Hayes Smith / Schroeder / Wynne public quotes are visible-tip data; the underlying recommendation behavior is less measurable directly. - The Drupal counterfactual is suggestive but not controlled. Drupal's market position is different from WordPress's (smaller absolute share, different enterprise mix), and Buytaert's lower public profile means fewer trust-erosion events would be visible even if they occurred. The "different founder posture, different outcome" framing risks selection bias. - The claim says trust *tracks* market share, not that trust *causes* market share. There are versions of the dynamic where both are caused by an underlying factor (e.g., AI displacement of the broader CMS category) and founder trust is just a more legible barometer than the underlying cause. ## Links - [[NAR and Charismatic Authority Critique MOC]] — the same trust-erosion mechanism this MOC traces in religious authority, measured in market share - [[3. Resources/Permanent Notes/Zet · Block themes are overtaking classic themes in install share]] — applies-in: theme install share is a lagging behavior signal whose interpretation depends on separating defaults from chosen adoption - [[3. Resources/Permanent Notes/The Recommend Layer Is Where Vendor Markets Make Their Real Decisions]] — evidence-for: founder trust reaches market share through the advisors and practitioners who decide what to recommend for the next project - [[3. Resources/Permanent Notes/In-Kind Labor Hides How Dependent a Commons Is on a Single Backer]] — evidence-for: hidden sponsor dependence turns a trust shock at one backer into ecosystem-wide recommendation and share risk. - [[BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]] — extends: the same concentrated-role structure that erodes founder trust also widens the records implicated when conflict reaches discovery. - [[Active Installs Reward Existing Winners]] — contrasts: both are lagging adoption signals, but install ranking compounds product incumbency while market share reflects ecosystem trust. - [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]] — extends; founder trust affects market share because trust is part of the community asset that integrators recommend. - [[3. Resources/Permanent Notes/The Merit Trap - Self-Worth in Systems of Singular Authority]] — adjacent claim about BDFL meritocracy and circular validation; the trust-erosion mechanism described here is downstream of the structural pattern that note names - [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]] — most projects are one maintainer at the center; this note is what happens when that central figure loses trust - [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] — the structural response to concentrated-founder-trust risk - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — same pattern at a different level; both about how invisible relational work becomes visible only when it breaks - [[3. Resources/Permanent Notes/Default-On AI Activation Inflates Adoption Metrics at the Cost of Consent]] — related observation about how vendor-reported numbers can fail to represent the underlying user posture they appear to measure - [[3. Resources/Literature Notes/WordPress Foundation Institutional Independence - Tracking Note]] — applies-in; visible institutional independence can either preserve or further erode the trust carried through the platform's recommendation layer. - [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] — evidence-for: delayed market-share decline makes accumulated governance and founder-trust damage visible after the structural problem is established - [[3. Resources/Permanent Notes/Enterprise Adoption Validates a Platform Through Authority Transfer]] — contrasts: founder behavior can drain trust from a platform while a marquee institution transfers some of its own authority back into the recommendation layer. - [[3. Resources/Permanent Notes/Greenwashing]] — applies-in: public inconsistency between environmental language and institutional practice becomes one founder-trust signal that can affect platform recommendation and adoption - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — applies-in: when scarce maintenance judgment remains concentrated in a founder-led structure, operational strain becomes a trust and adoption risk - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — extends: legal permission can preserve usage while deterioration in the social contract and founder trust weakens recommendation and adoption - [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — applies-in: credible contribution records shape the trust signals through which users and organizations recommend a project - [[3. Resources/Permanent Notes/Trademarking a Commons's Descriptive Terms Converts a Steward Into a Gatekeeper]] — applies-in: charging rent on a shared descriptive name spends the founder trust that supports project recommendations. - [[3. Resources/Permanent Notes/Trust Erosion in Concentrated Systems Is Slow to Build and Fast to Manifest]] — applies-in: recommendation and market-share changes are late visible signals of trust judgments that accumulated around concentrated leadership. - [[3. Resources/Permanent Notes/WordPress Market Share Is a Lagging Indicator That Trails Momentum Loss]] — extends: founder trust affects recommendations first, while installed-base market share records that momentum change only later. - [[3. Resources/Permanent Notes/WordPress's 2026 Losses Went to No-CMS Sites Not Competitors]] — contrasts: trust erosion and AI-driven category exit are competing mechanisms behind the same visible share decline. - [[3. Resources/Permanent Notes/One Channel Cannot Carry Both Project Voice and Commercial Interest]] — a specific mechanism feeding the trust erosion this note measures: the project's official voice used for competitive positioning - [[3. Resources/Permanent Notes/Founder Concentration Flips From Asset to Liability at Scale]] — the slow structural version of the same dependency; this note is the fast one, where trust erodes before the structure does. ## Open Questions - Is there a measurable "founder trust score" or composite metric that predicts market-share decline at meaningful lead times? Candidates: prominent-vendor public-statement sentiment, GitHub-stars-vs-new-issue ratio, search-volume "[project] alternative" growth rate, conference-attendance trajectory. - Does the relationship reverse cleanly? If WordPress's founder posture shifts (negotiated settlement, foundation governance reform, leadership transition), does the recommendation-layer trust rebuild fast enough to recover share, or is the recommend-rate effect more sticky than the trust event itself? - Does this dynamic apply to commercial open-source as cleanly as to community OSS? Companies like GitLab, MongoDB, HashiCorp have CEO figures whose trust matters in a different way (capital markets vs vendor community). Worth testing the claim against those cases. - Are there documented historical OSS founder-trust collapses with sufficient post-event data to test the lag-time and recovery prediction? Candidates: Linus's burnout interregnum (2018-2019), Joyent's Node.js dispute (2014), Theo de Raadt episodes in OpenBSD history. The historical record may provide cases to calibrate against the current WP situation. ## Source - [[3. Resources/Readwise/Articles/WordPress Market Share Declines For Six Months In A Row]] — Roger Montti / SEJ (May 2026): six-month decline data (43.2% → 41.9%); competitor gains (Shopify, Wix, Squarespace); vendor first-person quote on trust-as-precondition for recommendation - [Matt, I’ve Followed the WordPress Saga for a While Now...](3.%20Resources/Readwise/Tweets/Matt,%20I’ve%20Followed%20the%20WordPress%20Saga%20for%20a%20While%20Now....md) — Pancho Avila: Eric Binnion diagnosis-as-leverage critique; specific ethical-failure event in the trust-erosion sequence - [[3. Resources/Readwise/Tweets/I Obviously Don’t Want Any Harm to Come to WordPress]] — Trent Lapinski: "shell nonprofit" first-hand testimony from former Foundation volunteer; specific governance-failure event - [[3. Resources/Readwise/Articles/Matt Mullenweg Uses WordPress’s 23rd Birthday to Appeal Directly to Silver Lake “You’ve Won. I Submit.”]] — The Repository (May 2026): community-reaction roundup (Hayes Smith, Schroeder critiques); the WP23 post as a discrete trust-erosion event - [[3. Resources/Readwise/Articles/Grow the ecosystem, not just yourself]] — Dries Buytaert: contrast case; same competitive structure as WP saga but different founder posture and different downstream outcome - See also: [[Open Source Governance MOC]] for the WordPress Saga thread context this note distills