Yeah ok, I feel a little bit dirty inside. Go ahead, you can close the tab. I’ll wait.
Still here? Good. Because if you’ve spent any as a web developer, building custom applications, you already know the reaction this take tends to produce. WordPress? That WordPress? The one your aunt uses for her recipe blog? The one with the fifteen-year-old theme marketplace and the plugin called “Ultimate Membership Pro Turbo Plus”?
Yes. That one. And I’m going to make the case that for getting new products off the ground and proving out concepts, WordPress is not just acceptable. It’s genuinely excellent. Heresy, I know. Light the torches gently, please.
The Old Playbook
The answer to “I have a product idea, what shall I build it with?” was almost always Ruby on Rails or Laravel. Or if you are a Javascript dev, the brand new, very latest shiny framework that just had 30 YouTube videos and ZERO applications in product. And for good reason: beautifully designed frameworks that require real world experience, give you everything you need to ship a web application: routing, authentication, an ORM, migrations, a templating layer, a rich ecosystem of packages. They’re genuinely great.
But here’s the thing: WordPress gives you all of that too and more. And it’s been quietly doing so for over twenty years, growing to power 43% of the internet while developers confidently dismissed it as “just a blogging platform.”
Everything You Actually Need
A few years ago I read Building Web Apps with WordPress by Brian Messenlehner and Jason Coleman, and it reframed how I thought about the platform entirely. The book treats WordPress not as a CMS you reluctantly extend, but as a full application framework, which, when you look at what’s actually under the hood, is exactly what it is.
Consider the checklist for a new product:
Authentication & Authorisation WordPress ships with a complete user system, role and capability management, nonce-based request verification, and cookie/session handling. You don’t write any of this. It’s there on day one.
Routing The rewrite API and query vars give you full control over URL structure. Pair it with a REST API endpoint registration or a headless setup and you have clean, expressive routing with very little ceremony.
Data Modelling Custom Post Types and Custom Taxonomies let you model almost any domain concept quickly. Combined with Custom Fields (or update_post_meta directly), you can represent surprisingly complex data structures. It’s not a full ORM in the Rails sense, but it gets the job done at proof-of-concept speed.
Database Migrations The dbDelta() function and plugin activation hooks handle schema creation and upgrades. It’s not as elegant as ActiveRecord migrations or Laravel’s schema builder, but it’s pragmatic and it works.
UI Framework This is the one people don’t expect: the @wordpress/components library is a full, well-maintained React component library built on Gutenberg. Buttons, modals, form controls, data tables, notices: it’s all there, accessible, consistent, and documented. Combined with the block editor or an admin panel, you can build real product interfaces without touching a CSS framework.
The Hidden Advantage: Backward Compatibility
Here’s something Rails and Laravel developers will appreciate more than they’d like to admit: WordPress is obsessive about backward compatibility.
The WordPress core team famously prioritises not breaking existing sites. Updates ship regularly, but they almost never require you to rewrite your application code to keep up. Compare this to the upgrade treadmill of some frameworks, with major version bumps that require hours of migration work, and the appeal becomes obvious. When you’re trying to validate a product idea, time spent on framework upgrades is pure waste.
Objections, Handled
“But it won’t scale.”
Many of the largest publishers on the internet, organisations serving hundreds of millions of page views, run WordPress. With proper caching (WP Super Cache, Redis object cache), a CDN, and sensible infrastructure, WordPress scales further than most products will ever need to. The “WordPress doesn’t scale” argument usually reflects how it’s deployed, not a fundamental limitation.
“But the code will be a mess.”
Only if you let it be. The key is encapsulation. Build your custom functionality as a well-structured, object-oriented WordPress plugin: proper namespacing, PSR-4 autoloading via Composer, clean separation of concerns, hooks used as an internal event bus. Done right, your business logic lives in a plugin that knows very little about WordPress itself. When (or if) the scaling refactor ever comes, extracting that logic into standalone services or libraries is a tractable engineering problem, not a rewrite.
The plugin architecture is actually a strength here: it forces a natural boundary between your product logic and the platform layer.
The Abilities API: Your Plugin Becomes an AI-Ready Service
This one is brand new and worth paying attention to. WordPress 6.9 shipped the Abilities API, a standardised framework for registering your plugin’s functionality as typed, discoverable, permission-aware units called abilities. Think of an ability as a formally declared action your application can perform, complete with defined inputs and outputs validated by JSON Schema, a clear permission callback, and automatic documentation that both developers and machines can read.
If you’ve built your plugin with solid object-oriented design (as argued above), mapping your existing business logic onto abilities is a natural fit. Each method that encapsulates a meaningful operation becomes an ability: register_ability( 'myapp/create-order', ... ), register_ability( 'myapp/get-customer-report', ... ), and so on. The same capability checks you’ve already defined in your plugin govern who can execute each ability, so security is not an afterthought bolted on later.
Here’s where it gets interesting. The official WordPress MCP Adapter bridges the Abilities API to the Model Context Protocol, the open standard for connecting AI agents to external systems. Once your abilities are registered, exposing them as an MCP server is a matter of calling register_mcp_server() and listing which abilities to surface. From that point, any MCP-compatible AI client, including Claude, Cursor, or a custom agent built with LangChain, can discover and execute your application’s functionality in a structured, authenticated, context-aware way.
In practical terms this means an AI agent can ask your WordPress-backed product questions, trigger workflows, and retrieve data, without you having to build a bespoke API layer or write any glue code. The structure you built for good software design reasons doubles as the interface for AI automation.
This also reframes the “extract it later” argument. An OO plugin designed around the Abilities API is not just easier to refactor into microservices: its interface is already formally declared, documented, and accessible to agents. The work you do during the proof-of-concept phase compounds rather than being discarded.
When This Doesn’t Apply
Of course this argument has limits, they all do. If you know a product is validated and will immediately attract tens of thousands of users from launch day, the infrastructure conversation changes. Premature optimisation isn’t premature anymore.
WordPress for product development is an argument for the messy, uncertain, is-this-even-a-good-idea phase: the part where shipping fast and learning fast is the only metric that matters. Get something in front of users. Charge for it. See if they care. WordPress is very good at that phase.
The Punchline
The developers most likely to dismiss WordPress out of hand are often the same ones who’ve spent weeks configuring a bespoke React frontend talking to a custom API backed by a framework chosen because it was interesting, for an audience of twelve users.
WordPress is boring technology in the best possible sense. It’s stable, it’s understood, it has an enormous ecosystem, and it does the commodity parts of building a web application so you can focus on the parts that are actually specific to your product.
Sometimes the heresy is just the thing that works.