# Shipping Infrastructure Not Features Multiplies Who Can Build ## Claim When a platform ships standardized infrastructure instead of a finished feature, it shifts capability to the whole ecosystem of builders rather than concentrating it inside the platform itself. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the infrastructure is genuinely provider-agnostic and documented well enough that third parties can build on it without reverse-engineering it. - Breaks when the "standard" is thin, unstable, or undocumented — vendors then fork bespoke integrations anyway, and the platform gets the appearance of an ecosystem without the substance. - The payoff is ecosystem-wide, not platform-wide: the platform vendor doesn't capture all the resulting value, third-party builders do — which is the actual mechanism of "multiplying who can build." ## Evidence WordPress 7.0 added a standardized way for a site to connect to an AI provider rather than shipping finished AI features (design generation, image generation) itself. Ollie, a theme/plugin vendor, built editor-native content-rewrite and design-generation tools directly on that standard rather than building its own bespoke AI integration from scratch — the infrastructure-first choice is what let a third party ship a competitive AI feature quickly. > [!quote] > "instead of adding AI features like design features or AI image generation, what they're effectively doing is providing the infrastructure that all users of WordPress can tie into" ## Links - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — because contrasts: one is about a platform providing capability (infrastructure) that others build on, the other is about a program failing to provide a next step after building capability in people — both are about whether an enabling investment actually gets used downstream. - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in: infrastructure-first platform strategy is a recurring theme across this run's AI-and-work sources. ## Tests / falsifiers - Compare the number and variety of third-party AI integrations built on a genuinely open, documented platform standard vs. a closed or thinly-documented one — if the open standard produces more independent builders shipping competitive features, the claim holds. - Find a case where a platform shipped "infrastructure" that no third party successfully built on (due to poor docs or an unstable API) — that would show shipping infrastructure alone doesn't guarantee the multiplier effect. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/AI-Powered Content and Design, Right Inside the WordPress Editor]] — Ollie's editor-native AI features built on WordPress 7.0's AI infrastructure.