When WordPress Is the Wrong Tool (And What to Use Instead)
A practical cut: content sites stay on WordPress. Multi-role products usually should not. Here is how we decide on real briefs.WordPress is the right default for a content site, a brochure with a blog, and a lot of marketing sites that editors must own. It is the wrong default the moment the product has roles, unique rules, queues, or a workflow that is the business — not a page around the business.
We still ship a lot of WordPress development. This article exists because we also decline WordPress on briefs that look like a CMS request and behave like an application. The cut is practical, not ideological.
The three questions that decide
First: who publishes, and how often? If the answer is “marketing, weekly, in a visual editor,” WordPress (or a headless WordPress with a real front) is still in the running. If the answer is “operators in three roles, with approvals and audit logs,” you are describing an admin, not a theme.
Second: is the data a tree of pages, or a set of records with relationships? Pages, posts, and a few custom types are WordPress. Orders plus inventory plus a second product that is not a SKU is already stretching Woo. Multi-tenant accounts, usage billing, and background jobs are Laravel territory.
Third: what happens when it is wrong? A slow blog is annoying. A broken checkout or a wrong permission is a support queue. If the cost of a mistake is operational, do not put the rules in a pile of plugins.
What we still use WordPress for
Editorial sites, company sites with a block or Elementor pattern library, and stores where the catalog is the product. Custom themes and small plugins beat the fifth marketplace add-on. Maintenance is a checklist, not auto-updates on production Friday.
WooCommerce stays when merchandizing lives in WordPress and the catalog is not a second ERP. The moment you need a custom quoting engine, field-service scheduling, or a portal that is not “a page with a form,” we scope a custom web application.
The usual wrong turn
Agencies keep adding CPTs, ACF, and membership plugins until the site is an unpublished SaaS with no tests. Editors are afraid to click. Deploys are FTP. That is not “WordPress at scale.” That is an application hiding in a CMS, and it will cost more than starting on Laravel once you count the rework.
The other wrong turn is forcing Laravel on a five-page site because someone on the team likes React. A marketing site that must rank still needs a render story search can read. See our note on React vs Next.js before you default to a client-only SPA.
What we tell you on the call
Bring the outcome, the people who will log in, and what you will not compromise. If WordPress fits, we say so and send you to the WordPress page. If it does not, we will not stretch a theme into a product to win the job. Book a free consultation or read a case study first.