# Reconsidering the WordPress business model — Casey Burridge > [!question] Lingering Questions > - Can a SaaS backend stay a moat if AI reconstructs its logic from observed API behavior over time? > [!tip] Article Ideas > - "Should my plugin ship an MCP?" — a decision note for the WordPress plugin-developer audience, using this article's 12-month prediction as the framing question. #articleseed > [!link] Cross Reference > - [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]] — same author (Casey Burridge), same core thesis, from a companion podcast interview; this article is independent, later evidence for that existing claim. #xref > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — a live case of a business model repricing what its core product line item actually sells. #xref > [!quote] Vocabulary > - **GEO** (generative engine optimization) — measuring and optimizing for AI-assistant recommendations as an acquisition channel, the AI-era analog to SEO. ## Bib capsule Casey Burridge, "Reconsidering the WordPress business model: what are plugin licenses actually paying for?," caseyrb.com, 2026. https://caseyrb.com/blog/what-are-wordpress-plugin-licenses-paying-for/ ## Author's thesis (Adler Q1+Q2) The two historic pillars of a WordPress plugin license — docs-based support and routine feature updates — are both under pressure from AI. Support volume is dropping because users paste an error into Claude or ChatGPT before filing a ticket, and the AI is usually right; feature/update work is increasingly something AI can also do. What AI cannot replicate is accountability for code running on a live site, deep structured integration (via MCPs), managed infrastructure, expert services for hard edge cases, and being the plugin an AI agent actually recommends. Burridge (a plugin business owner) predicts every serious plugin ships an MCP within 12 months and that value migrates from the license itself toward a SaaS-connector model where core logic sits behind an API AI can't inspect or replicate. ## Key arguments - AI commoditizes docs-based plugin support — the easy tickets disappear first, edge-case troubleshooting stays human. - The durable value is accountability: "AI can extend a plugin, but it can't take responsibility for it." - MCPs make a plugin legible to AI agents (structured tool access vs. guessing from documentation), and the plugin increasingly becomes the connector rather than the product. ## Claim atoms ### AI commoditises docs-based plugin support > [!quote] ID:rw_pending > "their first instinct isn't to file a ticket anymore. It's to paste the error into ChatGPT or Claude, along with the plugin's documentation URL, and ask for help. And the AI is usually right." **Where/why**: The support pillar of the license is already eroding; 700+ pages of documentation become AI fodder. Edge-case troubleshooting stays human; the docs-based tier shrinks fast. **Tags**: #xref #addendum ### AI can extend a plugin but cannot own it > [!quote] ID:rw_pending > "AI can extend a plugin, but it can't take responsibility for it." **Where/why**: Names the irreducible human value — accountability for code running on a live site — and reframes the renewal pitch away from "new features" toward responsibility. Distinct from the existing companion note's "hard integration work" framing; promoted to a new Permanent note. **Tags**: #xref #aphorisms #share ### MCPs make plugins legible to AI agents > [!quote] ID:rw_pending > "Instead of the AI guessing how your plugin works based on documentation, an MCP gives it direct, structured access to create forms, submit entries, configure feeds, and manage data programmatically." **Where/why**: Structured tool access versus REST-API/HTML guessing — an hour's manual setup collapses to minutes. Author predicts every serious plugin ships an MCP within 12 months. Already substantially covered by the existing companion Permanent note's Gravity Forms MCP / block MCP examples. **Tags**: #xref #articleseed ### Value shifts from the plugin to a SaaS connector > [!quote] ID:rw_pending > "The plugin becomes the connector, not the product." **Where/why**: Core logic moves behind an API AI "can't inspect or replicate," hedging open source's exposure of replicable code in an AI-first world. This is the existing companion note's central thesis, restated. **Tags**: #xref #articleseed ## Permanent candidates - **Plugin value moves to what AI cannot replicate (SaaS/services monetization shift)** — already exists as [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]], created from a companion interview with the same author. Not duplicated here; this article is treated as corroborating evidence. - **AI can extend a plugin but cannot own its accountability** — distinct claim about accountability as the specific irreducible value, not fully covered by the existing note. Promoted to a new Permanent note: [[3. Resources/Permanent Notes/AI Can Extend a Plugin But Not Own Its Accountability]]. ## Processing checklist - [x] All claim atoms have header + verbatim quote + where/why - [x] Triage callouts populated for every tagged highlight - [x] Checked existing Permanents first — found a companion-source note covering the primary thesis, linked rather than duplicated; promoted one genuinely distinct secondary claim - [x] Connected into MOC — [[3. Resources/MOCs/Product & Startup Instincts MOC]] ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — a live repricing of a business model's core line item under AI pressure - [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]] — because evidence-for; companion-source statement of the same thesis - [[3. Resources/Permanent Notes/AI Can Extend a Plugin But Not Own Its Accountability]] — because evidence-for; new Permanent note from this article's secondary claim - [[3. Resources/Readwise/Articles/Reconsidering the WordPress Business Model What Are Plugin Licenses Actually Paying For]] — source document