# Free Local Tools Funnel Toward Paid Hosting Tiers ## Claim A free, open source developer tool acquires users at low friction while reserving its highest-leverage workflows for a paid hosting tier, turning the tool itself into a funnel into the vendor's ecosystem. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when a tool's standout features (here: Sync, live previews) depend on vendor-hosted infrastructure that only activates on a paid plan. - Breaks when the tool is fully self-hostable and its best features don't route through any vendor account. - Does not claim the funnel is dishonest or that the free tier is bad-faith — only that the incentive structure exists and shapes adoption. ## Evidence WordPress Studio (WordPress.com) is free and open source; local site creation, PHP/WP version pinning, and custom domains work with no account. But Studio Sync — pushing or pulling a live site — is explicitly gated: "Studio Sync only works with WordPress.com sites on a business or commerce plan." Lower tiers see an upgrade prompt instead of the feature. Live previews and the AI assistant require at minimum a free WordPress.com account, so even the "free" upper tier of functionality routes through the vendor's login system. ## Links - [[AI & the Future of Knowledge Work MOC]] — the business model shaping which AI capabilities stay local and which require a vendor - [[Personal Knowledge Management MOC]] — the business model shaping which parts of a personal toolchain stay local - [[3. Resources/Permanent Notes/A Sync Tool Earns Trust for Destructive Operations by Auto-Backing Up First]] — because contrasts; that note is about the same tool's Sync mechanism building trust through safety, this one is about the same mechanism's business-model function. - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — because applies-in; free-tool-as-acquisition-funnel is a recurring product-strategy pattern worth tracking across vendors, not just WordPress.com. - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — because applies-in; plan-gating that steers users toward specific hosting tiers is a hosting-stack decision with lock-in consequences. ## Tests / falsifiers - Find a case where Studio's Sync/preview features work fully without any WordPress.com account or plan tier — would falsify the "reserved for paid tier" claim. - Track whether free-account Studio users convert to paid WordPress.com/Pressable plans at a meaningfully higher rate than users of a fully self-hostable competitor (Local, wp-env) — would support the funnel-effect claim with real numbers instead of structural inference. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/An introduction to WordPress Studio]] — vendor walkthrough stating the plan-gating rule directly.