# The Enterprise WordPress Playbook > [!question] Lingering Questions > - Does an independent, non-vendor TCO comparison of enterprise WordPress vs. AEM/Sitecore/Contentful support Chapter 5's core cost-shift claim? > - Does WordPress 7.0's "AI Client" actually have the scope this document ascribes to it — needs checking against core changelogs, not this vendor's characterization. > [!tip] Article Ideas > - "The N-path framework that already decided" — a short piece on reading vendor whitepapers that offer a build/buy/evolve (or similarly-named) decision framework where one path is defined in terms synonymous with the vendor's own product. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Vendor Usage Anecdotes Need Verification Before Adoption Decisions]] — same genre of caution, applied to case-study claims rather than framework claims > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] > [!quote] Vocabulary > - **"Evolve" path** — Human Made's third option in its Build/Buy/Evolve framework: incremental improvement on an open, composable foundation instead of a full-platform replacement cycle — defined in terms that happen to match Human Made's own Altis product. ## Metadata - Source: [[3. Resources/Readwise/Full Document Contents/Articles/The Enterprise WordPress Playbook]] - Author: Human Made (WordPress enterprise agency; maker of Altis and Accelerate) ## Author's thesis (Adler Q1+Q2) Human Made argues WordPress should be evaluated by enterprise buying committees as a strategic, business-critical platform rather than a tactical CMS choice, framing the decision as Build vs. Buy vs. Evolve and resolving every comparison toward an open, WordPress-based "Evolve" platform — implicitly, toward Human Made/Altis as the implementation partner. It's a structured sales argument: well organized and directionally reasonable on TCO/flexibility trends, but not a neutral comparison. ## Key arguments (≤3) 1. **The "Evolve" path avoids full-platform replatforming cycles** by building on a flexible open foundation and improving it continuously, instead of periodic rip-and-replace. 2. **Open platforms shift cost from licensing into engineering** — WordPress's TCO argument, stated without supporting figures. 3. **WordPress 7.0's AI Client standardizes AI-provider connections**, the most independently verifiable technical claim in the document. ## Claim atoms ### Evolve strategy avoids full-platform replatforming cycles > [!quote] ID:rw_1 > "Instead of replacing everything at once, organisations build on a flexible foundation and improve it continuously." Where/why: Chapter 7.1, "The Three Paths" — defines the Evolve path against Build and Buy; central to the document's core thesis, worth testing against real migration case data. ### Open platforms shift cost from licensing into engineering > [!quote] ID:rw_2 > "Open platforms like WordPress shift more of that investment into engineering." Where/why: Chapter 5.1, "Breaking down true platform costs" — the document's central TCO claim, stated without supporting figures. ### AI Client standardizes WordPress-to-AI-provider connections > [!quote] ID:rw_3 > "Now, with emerging core support for AI through the AI Client, it becomes much simpler to connect to different AI providers in a consistent way." Where/why: Chapter 4.1, "Embedding AI into publishing workflows" — describes WordPress 7.0's AI Client; the most independently verifiable technical claim in the source. ## Permanent candidates - **Vendor comparison frameworks predetermine their outcome** — a three-path framework that defines its preferred path in terms synonymous with the vendor's own product has already decided the comparison before it starts. See [[3. Resources/Permanent Notes/A Vendor-Defined Decision Framework Predetermines Its Own Winner]]. ## Processing checklist - [ ] Find an independent enterprise-WordPress-vs-proprietary TCO study before citing Ch. 5's cost claim elsewhere. - [ ] Verify WordPress 7.0 AI Client scope directly against core changelogs. - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Product & Startup Instincts MOC]] ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — reading vendor positioning and buying-committee framing critically is a recurring product-instincts skill - [[3. Resources/MOCs/Open Source Governance MOC]] — the open-vs-proprietary platform argument is a governance/ecosystem question as much as a technical one - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11, hosting backlog).