Are Declining Plugin Sales the Canary in WordPress’ Coalmine

Are Declining Plugin Sales the Canary in WordPress’ Coalmine? ![rw-book-cover](https://www.therepository.email/wp-content/uploads/2026/07/canary-coalmine-wp.jpg) 🔗 **Source:** [Are Declining Plugin Sales the Canary in WordPress’ Coalmine?](https://www.therepository.email/are-declining-plugin-sales-the-canary-in-wordpress-coalmine) > [!note]+ Document Notes > tags: [wordpress-ecosystem, plugin-business, ai-commoditization, seo-decline, product-strategy, subscription-pricing] > author: [MISSING] > source: The Repository > reference: https://www.therepository.email/are-declining-plugin-sales-the-canary-in-wordpress-coalmine > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Are Declining Plugin Sales the Canary in WordPress' Coalmine? >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [WordPress faces an event horizon, not a sunset — The Repository](https://www.therepository.email/wordpress-faces-an-event-horizon-not-a-sunset) - [A letter to the WooCommerce community — Jessica Risch, Woosa](https://www.woosa.com/blog/a-letter-to-the-woocommerce-community/) - Katie Keith survey on WP Product Talk (33 plugin companies) - Freemius CodeCanyon analysis; WP Rankings install-velocity data; Patchstack 2024 report; WP Engine economy study; Red Stag WooCommerce GMV analysis ## 📝 Summary - **What happened.** A wave of public founder venting, shop closures, and conflicting "WordPress is fine / WordPress is dying" takes prompted this data-driven piece asking whether declining plugin sales signal ecosystem collapse or just a rules change. The author (a founder advisor) argues it's the latter. - **Why it matters.** Plugin shops are a load-bearing layer of the WordPress economy. If new-license sales are structurally drying up because of AI and search shifts, the indie product tier that feeds the ecosystem is at risk even while macro numbers stay huge. - **Key stakeholders.** Indie and mid-size plugin founders (Woosa, WP Umbrella, Studio Wombat, SNIP, DLX, Business Bloomer, EssentialPlugin), platform players (Automattic/Woo, Awesome Motive, StellarWP/Liquid Web), and analysts/data sources (Katie Keith, Freemius, Patchstack, WP Rankings). - **Risks and tradeoffs.** Renewals mask top-of-funnel decay; utility/replaceable plugins face the worst declines; lifetime and race-to-the-bottom pricing become unsustainable when maintenance never stops; SEO-dependent discovery is collapsing under AI Overviews and directory flooding. - **Bottom line.** Closures are "the tide going out," exposing shops built on old-school SEO, leaky renewals, and lifetime pricing — not proof WordPress is doomed. Survival means owning more of the customer, investing in marketing/discoverability, de-commoditizing via services and support, and fixing pricing. ## 📖 Main Content - The core move is to **disaggregate "plugin sales"** into distinct data layers that people conflate: (1) *new license sales* (top-of-funnel health), (2) *total plugin revenue* (new + renewals, which can look flat while the floor crumbles), (3) *org install velocity* (distribution momentum on WordPress.org), (4) *macro TAM/GMV* (the "WordPress is massive" numbers), and (5) *marketplace earnings* (CodeCanyon-tier, mostly subsistence). The argument: enterprise WordPress can look healthy while indie Woo extension shops die. - **New-sales pressure is documented, not vibes.** Katie Keith's survey of 33 plugin companies found ~80% reporting flat or lower new sales in 2025 vs 2024. Founder exit posts (Minesh/EssentialPlugin −35–45%, Flo/SNIP shutdown, Ronald Huereca/DLX closing) corroborate. But growth cases exist (+15–29%) for heavier-marketing, partnership-driven, or platform-critical products (WP Umbrella hit $110k MRR; Studio Wombat still grew despite traffic −28%). - **Shared failure patterns.** Discovery (AI-shifted search erodes organic acquisition, the top channel and the one most tied to declines), replaceability (the sharper question: "if your plugin didn't exist, how hard to get the same outcome?" — easily replaceable utilities fare worst), crowding (WordPress.org submissions ~700+/week, ~5x the 2024 pace, driven by AI-assisted dev and "ghost" plugins), renewals (AI weakens updates/feature-gating/add-ons; support still defensible), platform anxiety (WP Engine dispute, Woo-into-core, ACF controversy), and pricing (lifetime/one-time and $19–29 race-to-the-bottom are brutal when maintenance is perpetual). - **Contested / uncertain claims.** The Freemius CodeCanyon figures ($3,838 avg/year, 97.6% under $1,001/mo) are 9 years old — the author concedes this and speculates it's "even worse now." Paolo Tajani's claim that WPBeginner traffic loss drives Awesome Motive install bleed is flagged as a hypothesis. The central "not a canary" verdict is a judgment call, not proof. - **Prescription.** Own more of the customer / get closer to their revenue (the Woosa payments-and-services pivot), invest in off-site discoverability and branded search, double down on non-commodity assets (support, expertise, services), and fix pricing (higher prices, agency tiers, legacy renewal increases). ### 🗒️ Notes - **Five data layers, defined:** new license sales = first-time purchases (are you finding new customers?); total revenue = new + renewals (can stay flat while new sales fall); install velocity = .org distribution speed (WP Rankings: Rank Math ~+60k installs/week vs AIOSEO ~−34k); macro TAM/GMV = WP Engine "hundreds of billions" economy, Red Stag $30–35B Woo GMV; marketplace earnings = CodeCanyon subsistence tier. - **Woosa case (Jessica Risch):** record €70,000 month in 2023 → €15,000 MRR by 2026. Response: made dropshipping/marketplace plugins free forever, pivoted to Woosa Payments, WooCommerce Support, and the Woosa Collective agency network. Thesis: proximity to customer revenue > license keys. - **Replaceability tiers:** easily replaceable (competitors/core/themes/AI code) → worst, many −30%+; utility/nice-to-have → many −15–29%; platform-critical → mixed, some +15–29%; irreplaceable/only-option → most stable, declines tied to pricing/marketing not vanished demand. - **Renewal erosion:** Justin Ferriman — AI weakens updates, feature gating, add-ons; support still matters. Ben Ryan's "one-time-pricing trap": rising support cost + falling new revenue, 59% of plugins not updated in 2+ years. - **Rodolfo Melogli / Business Bloomer reversal:** ~15 years lifetime-only Woo mini-plugins; changed his mind because AI generates simple code in seconds, educational content goes stale faster, and upkeep isn't funded by one-time sales. Moved the Club to subscriptions first. - **Security signal (Patchstack 2024):** 7,966 new vulnerabilities (+34% YoY), 827 abandoned plugins, >half of notified devs failed to patch before disclosure. - **Platform anxiety events:** Jason Coleman pulled Paid Memberships Pro off .org (Oct 2024, post-ACF); Liquid Web dissolved StellarWP; Studiocart retired to PublishPress Cart. - **Strategic responses observed:** close honestly (DLX open-source + find maintainers; SNIP; Plugins & Snippets); diversify beyond WP (Patchstack → Drupal/Joomla/Laravel; WP Deals → SaaS/hosting); double down on marketing/partnerships (WP Umbrella word-of-mouth; Studio Wombat kept shipping); reposition to platform-critical/whole-job products. ## 📚 References - [WordPress faces an event horizon, not a sunset — The Repository](https://www.therepository.email/wordpress-faces-an-event-horizon-not-a-sunset) - [A letter to the WooCommerce community — Jessica Risch / Woosa](https://www.woosa.com/blog/a-letter-to-the-woocommerce-community/) - Freemius — CodeCanyon plugin-earnings analysis (avg $3,838/yr; 97.6% under $1,001/mo) - Katie Keith / Barn2 — WP Product Talk survey of 33 plugin companies (~80% flat-or-lower new sales) - WP Rankings — install-velocity estimates (Rank Math vs AIOSEO) - Patchstack — 2024 State of WordPress Security report - WP Engine — WordPress economy study; Red Stag — WooCommerce GMV analysis ($30–35B) - WPBay — "ghost" AI plugin flooding and race-to-$19–29 lifetime pricing; WebTNG 2025 predictions ## 🗣️ Paraphrase - The noise about dying plugin sales conflates several different metrics; separate them and the picture is "new-customer acquisition is under real, documented pressure," not "the whole platform is collapsing." - Struggling shops share overlapping causes — broken SEO discovery, high replaceability, directory crowding, weak renewals, platform anxiety, and unsustainable lifetime/cheap pricing — and the survivors respond by getting closer to customer revenue, marketing harder, de-commoditizing through services, and repricing. ## 📰 Newsletter - WordPress product founders: if your sales chart is sagging, read this before you panic. The Repository breaks "plugin sales" into five metrics people keep confusing — and shows why renewals can look fine while your new-customer funnel quietly dries up. - Highlights: Katie Keith's survey (~80% of 33 shops report flat-or-lower new sales), Woosa's radical "make the plugins free, sell payments and services" pivot, and Patchstack's sobering 7,966-vulnerability year. The through-line: AI is commoditizing utility code and gutting SEO discovery, so the moat moves to support, expertise, and proximity to your customers' revenue. - Worth your click: [Woosa's letter to the WooCommerce community](https://www.woosa.com/blog/a-letter-to-the-woocommerce-community/) and the earlier [event horizon, not a sunset](https://www.therepository.email/wordpress-faces-an-event-horizon-not-a-sunset) piece. ## ✅ Action Items #### DevRel - Developer advocacy: publish a "five layers of plugin-sales data" explainer for the founder community; measure adoption by citations. - Education: run office hours on branded-search measurement and off-site discoverability for plugin teams. - Developer experience: template a transparency year-in-review (Studio Wombat / WP Umbrella style) shops can reuse. - Developer marketing: build attribution beyond organic — social, video, forums, sponsorships as second/third channels. - Community management: survey founders quarterly on new-license sales to replace anecdote with a running index. - Internal/external/cross-project: align .org directory, hosting, and product founders on discovery health metrics. #### OSPO - Policy & Governance: define contribution/maintainership handoff paths for shops open-sourcing on exit (DLX pattern). - License Compliance: guidance for teams re-licensing utility plugins to "free forever" while monetizing services. - Security Management: push Patchstack-style disclosure SLAs; target the >50% no-patch-before-disclosure gap. - Software Inventory: track abandoned-plugin counts (827 in 2024) as an ecosystem-health SBOM signal. - Developer Support: legal/pricing guardrails for shops raising legacy renewal rates. - Community Engagement: fund maintainers adopting orphaned commercial plugins. - Strategic Alignment: report "new-license velocity" as an OSPO KPI alongside GMV/TAM. #### Community - Maintainers: roadmap clinics on moving from lifetime to subscription without churning legacy buyers. - Contributors: "first issue" rotations for adopted-out plugins (DLX/Studiocart handoffs). - Sponsors: transparent budgets tied to discovery-channel experiments. - Ecosystem: coordinated response to "ghost" AI-plugin flooding eroding directory trust. #### WordPress - Core: assess how Woo-features-into-core decisions affect dependent extension shops. - Core Performance: n/a to this source directly; monitor directory-search load as submissions hit ~700+/week. - Core AI: responsible-AI guardrails for AI-generated plugin submissions and quality gating. - **Core Program Team:** coordinate directory-quality and trust initiatives across Plugins/Meta/Security teams. - Plugins: raise review throughput and provenance checks to counter untested AI "ghost" plugins. - Themes: watch for the same AI-commoditization pattern in the theme market. - Marketing: reframe "$600B economy" messaging so it doesn't paper over indie-shop distress. - Documentation: examples-first guidance on branded-search and off-site discoverability. - Accessibility: n/a to this source. - Meta: expose install-velocity data so founders can read category dynamics. - Hosting: cross-host defaults that surface trustworthy plugins amid directory flooding. - Tide: revive automated scoring to help buyers distinguish quality from AI-generated noise. #### The WPCC - Programs: maintainer stipends for adopting orphaned commercial plugins. - Projects: governance clinics for exit/handoff transparency. - Funding experiments: matched grants for shops pivoting to services/SaaS. #### FAIR - Technical independence: local metadata/provenance so discovery isn't hostage to a single search channel. - Policies and covenants: anti-capture terms as PE roll-ups (StellarWP) shake confidence. - Productized governance artifacts: operator agreements for plugin handoffs and open-sourcing. ## 🧪 Hypotheses - **H1.** Plugin shops whose products score "easily replaceable" show materially worse new-sales declines than "platform-critical/irreplaceable" shops in the same period. - **H2.** Shops dependent on organic search for acquisition suffered larger 2024→2025 declines than shops with diversified (social/video/paid/partnership) channels. - **H3.** Lifetime/one-time pricing correlates with faster revenue erosion than subscription pricing once maintenance costs and AI-code substitution rise. - **H4.** Rising WordPress.org submission volume (~700+/week) reduces per-plugin directory discovery (measured as installs-per-new-listing) even for high-quality plugins. - **H5.** Branded search volume predicts survival better than total organic traffic during the AI-Overview transition. - **H6.** Shops that "own more of the customer" (payments/services) retain revenue better than pure-license shops when new-license sales fall. ### 📊 Methodology - **H1/H2/H3/H6:** longitudinal survey of plugin shops with self-reported new-license MRR, a replaceability score, primary acquisition channel, and pricing model; regress YoY new-sales change on those covariates. Triangulate against Freemius/Woosa-style disclosed financials. - **H4:** join WordPress.org submission timestamps with per-plugin install trajectories (WP Rankings) to estimate discovery decay per additional listing. - **H5:** panel of shops with Search Console branded vs non-branded query splits against retention/churn outcomes. - **General:** guard against survivorship bias (exited shops underrepresented) by including closure announcements; note the 9-year-old Freemius data as a stale prior needing refresh. ### ❓ Questions - Which replaceability tier is the true inflection point where subscriptions stop rescuing a shop? - Is AI-driven install bleed a portfolio-wide phenomenon (Awesome Motive hypothesis) or concentrated in SEO-adjacent categories? - Does "make plugins free, sell services" scale beyond ecommerce-proximate shops like Woosa? - How much of the decline is macro AI vs WordPress-specific platform anxiety (WP Engine, ACF, StellarWP)? - What's the minimum viable second/third acquisition channel for a solo shop? ### 🔮 Future Research - A live, anonymized "new-license velocity" index for WordPress plugin shops to replace anecdote. - Refresh of the CodeCanyon/marketplace economics study (the cited data is 9 years old). - Category-level study of AI-code substitution: which plugin types are already "vibe-codeable" and how fast the moat erodes. - Trust-impact study of "ghost" AI plugins on directory conversion rates. ### 💡 Implications - **Practice.** This is a strong evidence node for the **WordPress-market-decline** thread: the "$600B economy" macro framing coexists with genuine indie-shop distress, so headline health metrics (TAM/GMV) are the wrong instrument for founder decisions — watch new-license velocity and branded search instead. - **AI-site-builder / AI-commoditization thread.** The piece is a concrete instance of the broader pattern where AI collapses the value of easily generated code: utility plugins are "vibe-codeable," educational SEO content decays, and discovery moves from Google/directory to AI Overviews and ChatGPT. The defensible layer shifts to support, expertise, services, and proximity to customer revenue — the same "sell the outcome, not the artifact" logic that AI site builders impose on agencies and template shops. - **Policy/governance.** Directory flooding and abandoned-plugin/security gaps (827 abandoned, >50% unpatched) argue for stronger provenance and quality gating; PE roll-up fragility (StellarWP) argues for anti-capture covenants. - **Education.** Founders need re-skilling in off-site discoverability, pricing experimentation, and services/SaaS transitions, not more on-site content SEO. - **Funding models.** Subscriptions and agency tiers outperform lifetime/one-time as maintenance becomes perpetual; grant/stipend programs can absorb orphaned-plugin maintenance. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch–Kincaid Grade ~10–12 (business-analytical prose, long sentences with embedded clauses, named-entity dense). Flesch Reading Ease ~45–55. #### 👀 Visual learners - Present: one hero image (mine/canary); no charts despite heavy quantitative content. - Improve: a metric-layers diagram, a replaceability-tier ladder, and before/after MRR sparklines (Woosa €70k→€15k, WP Umbrella $60k→$110k). #### 🔊 Aural learners - Present: none. - Improve: 3–5 minute audio summary; a founder-interview podcast cut. #### 🗣️ Verbal learners - Present: strong — definitions of TAM/GMV/MRR, analogies ("tide goes out," "canary in the coalmine"). - Improve: a glossary callout box for the five data layers. #### 🧩 Kinesthetic learners - Present: implicit checklist in "What I'd do if I were you." - Improve: a downloadable self-audit worksheet (score your replaceability, channels, pricing). #### 🧠 Logical learners - Present: clear taxonomy (layers, tiers) and cause lists. - Improve: a decision tree from "which metric is falling?" to recommended response. #### 🧑‍🤝‍🧑 Social learners - Present: references community discourse (X polls, WP Product Talk, founder posts). - Improve: discussion prompts; a founder cohort/peer-review rubric. #### 🧘‍♀️ Solitary learners - Present: reflective closing ("The bar has moved... Are you?"). - Improve: journaling prompts per recommendation. #### 🌿 Naturalistic learners - Present: ecosystem/tide/canary metaphors throughout. - Improve: lifecycle framing of a plugin shop from launch to exit/handoff. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: single figure with descriptive alt text ("Dark mine tunnel with a cart and a yellow bird in a cage..."); heading-lite article body. - Improve: ensure section subheads use real heading elements; add landmarks. #### Keyboard navigation - Present: standard article links. - Improve: verify visible focus and logical order on the source site (not assessable from content alone). #### Contrast and readability - Present: not determinable from extracted text. - Improve: confirm 4.5:1 body contrast and adequate line-height on therepository.email. #### Text resizing and reflow - Present: responsive srcset image markup suggests a responsive theme. - Improve: confirm no clipping at 200% zoom. #### Media and captions - Present: figcaption on the hero image. - Improve: if an audio version is added, ship a transcript. #### Forms and interactions - Present: none in content (ends with an ad slot). - Improve: n/a. #### Standards reference - Map gaps to WCAG 2.2 AA: 1.1.1 (alt text — met), 1.4.3 (contrast — unverified), 1.4.10 (reflow — likely met), 2.4.6 (headings/labels — improve). ### 🌍 DEIB Assessment #### Cultural breadth - Present: European (Woosa/Netherlands, WP Umbrella) and international founders cited. - Improve: global South and non-English-market plugin economics are absent; add. #### Inclusive language - Present: plain, jargon-defined ("TAM," "GMV," "MRR" all glossed); gender-neutral. - Improve: brief plain-language TL;DR for non-native readers. #### Neurodiversity support - Present: consistent structure, short paragraphs, bulleted tiers. - Improve: more frequent subheadings; icon+text callouts for the five layers. #### Representation - Present: names many founders across shop sizes and outcomes (growth and closure). - Improve: quotes skew to established/visible founders; include first-time and non-Western indie devs. #### Psychological safety - Present: respectful framing of closures ("sometimes walking away is the honest answer"). - Improve: content note that exit ≠ failure; link support resources for founders in distress. ### ✅ Logical Validity #### Strong reasoning - **Analogical (strong):** the canary/tide metaphor is used carefully — the author explicitly *rejects* the canary reading and reframes closures as "what you see when the tide goes out," attributing them to specific structural bets (SEO, leaky renewals, lifetime pricing) rather than platform death. Located in "What I'd do if I were you." - **Inductive (strong):** the ~80% flat-or-lower survey finding plus multiple named founder disclosures build a converging case that new-sales pressure is real; strengthened by counter-cases (WP Umbrella, Studio Wombat) that keep it from overclaiming. - **Causal (moderate):** replaceability → decline is well-argued via the tiered survey; could be sharpened with effect sizes and controls. #### Fallacies - **Stale-data / weak-analogy risk:** citing 9-year-old Freemius CodeCanyon numbers ("$3,838 per year," "97.6% earning under $1,001 per month") then asserting "the economics are most likely even worse now" — hasty generalization from outdated data. Fix: flag as directional only or refresh. - **Anecdote-as-trend:** several claims rest on individual exit posts and X hypotheses (Paolo Tajani on WPBeginner/Awesome Motive). The author labels these as hypotheses, which mitigates it. Fix: quantify portfolio-wide install bleed. - **Survivorship framing:** growth cases are named prominently; without base rates the "you can still grow inside WordPress" conclusion risks overweighting survivors. Fix: report denominators. #### Tone of voice - Candid, practitioner-advisory, mildly contrarian ("Next time someone says 'the market is shrinking,' ask them which metric they mean"). Confident but hedged with data caveats. ### 🛡️ DARVO Analysis - Not applicable to this source — reason: the article is a market analysis, not a defense against accusation. There is no accused party denying wrongdoing, no attack on accusers, and no victim/offender reversal. The closest adjacent content is neutral reporting of disputes (WP Engine, ACF/PMP, StellarWP) without the author adopting a DARVO posture. ## 🎯 Conclusion - **Bottom line.** Declining plugin sales are not the canary signaling WordPress's death; they're the receding tide exposing shops built on old-school SEO, leaky renewals, and lifetime/cheap pricing at the moment AI commoditized utility code and rerouted discovery. New-license pressure is real and documented; total collapse is not. - **Practical next steps for readers.** (1) Diagnose which metric is actually falling before reacting. (2) Own more of the customer and get closer to their revenue (Woosa playbook). (3) Shift spend from on-site SEO to off-site discoverability and branded search. (4) Invest in non-commodity value — support, expertise, services. (5) Fix pricing: higher prices, agency tiers, legacy renewal increases; run a small experiment on your hardest-to-replace product before betting the company. ## 🔄 Refactor Appendix — Are Declining Plugin Sales the Canary in WordPress' Coalmine? > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] Renewals mask a collapsing new-customer funnel > [!quote] ID:rw_01kx6gnm1gnanx1s0gt97z0a0r > 80% reported flat or lower new sales in 2025 compared to 2024 **Context & use**: - Body, "level-set on data layers" and Katie Keith survey of 33 companies. - Total-revenue headlines hide top-of-funnel decay; new-license velocity is the metric that matters. **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://open?id=01kx6gnm1gnanx1s0gt97z0a0r)  #### [H2] AI erodes the code moat for utility plugins > [!quote] ID:rw_01kx6gnm1gnanx1s0gt97z0a0r > a future where the code itself stops being the moat **Context & use**: - Body, "On replaceability" section. - Easily replaceable/vibe-codeable utilities post the worst declines (−30%+); the moat moves to support and services. **Tags**: #xref #addendum **Highlight**: [view highlight](readwise://open?id=01kx6gnm1gnanx1s0gt97z0a0r)  #### [H3] Closures expose fragile bets, not platform death > [!quote] ID:rw_01kx6gnm1gnanx1s0gt97z0a0r > Shop closures are what you see when the tide goes out. **Context & use**: - Body, "What I'd do if I were you." - Reframes the canary metaphor: closures trace to SEO, leaky renewals, lifetime pricing — not WordPress collapse. **Tags**: #xref #aphorisms **Highlight**: [view highlight](readwise://open?id=01kx6gnm1gnanx1s0gt97z0a0r)  #### [H4] Sell proximity to revenue, not license keys > [!quote] ID:rw_01kx6gnm1gnanx1s0gt97z0a0r > betting that proximity to your customers’ revenue matters more than license keys **Context & use**: - Body, Woosa case (free plugins → payments/services pivot). - The survivor playbook: own more of the customer instead of defending a replaceable license. **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://open?id=01kx6gnm1gnanx1s0gt97z0a0r)  ### 🧠 Permanent Candidates (H4) #### [P1] Commoditized artifacts push value toward the surrounding service **Claim** (one sentence, Courtney's voice): When AI makes an artifact cheap to reproduce, durable revenue moves to the support, expertise, and customer-proximity that surround it. **Evidence pointer**: [[#H2]] — and Woosa's payments/services pivot at [[#H4]] **Scope & conditions**: Holds for easily replaceable utility software; weaker for platform-critical or irreplaceable products where the artifact itself is still the moat. **Links**: - [[WordPress-market-decline]] — because evidence-for - [[AI-site-builder-commoditization]] — because extends - [[Lifetime-vs-subscription-pricing]] — because applies-in pricing strategy  ### ✏️ Fleeting Queue - [F1] Refresh the 9-year-old Freemius CodeCanyon economics before citing "$3,838/yr" as current — https://www.therepository.email/are-declining-plugin-sales-the-canary-in-wordpress-coalmine #fleeting #inbox - [F2] Track branded-search as the survival metric for courtneyr.dev / client plugin advising #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a "five layers of plugin-sales data" explainer for the WP founder audience — content #things - [ ] Build a replaceability self-audit checklist (tier + channel + pricing) — advising #things  📄 **Full text:** [[Full Document Contents/Articles/Are Declining Plugin Sales the Canary in WordPress’ Coalmine.md|Are Declining Plugin Sales the Canary in WordPress’ Coalmine? by therepository.email]] ## Highlights - reported flat or lower new sales in 2025 compared to 2024 ([View Highlight](https://read.readwise.io/read/01kx6hm26p7e24m8k7yvcaghv9)) - Note: Key quantified evidence (~80% of 33 shops) — new-sales pressure is documented, not vibes. - Tags: atom/literature/h4 - a future where the code itself stops being the moat ([View Highlight](https://read.readwise.io/read/01kx6hkqwm596spa200zgwseyc)) - Note: Core AI-commoditization claim — utility-plugin code loses defensibility. - Tags: atom/literature/h2 - 7,966 new vulnerabilities (a 34% increase year over year), 827 abandoned plugins ([View Highlight](https://read.readwise.io/read/01kx6hm7xz6cmx4qj37s2917c9)) - Note: Patchstack 2024 ecosystem-health signal — abandonment and security decay. - Tags: atom/literature/h5 - betting that proximity to your customers’ revenue matters more than license keys ([View Highlight](https://read.readwise.io/read/01kx6hkxas09dbp9pnezc7a15j)) - Note: Woosa survivor playbook — own the customer, sell services not licenses. - Tags: atom/literature/h3 - Shop closures are what you see when the tide goes out. ([View Highlight](https://read.readwise.io/read/01kx6hkft776y7mkf8s2s1z8s7)) - Note: Thesis reframe: closures expose fragile bets (SEO, leaky renewals, lifetime pricing), not WordPress death. - Tags: atom/literature/h1