When WordPress is enough — and when you need a web service

“What should we build it on?” often sounds like a tech holy war. In practice it is a product question: what must work in six months, and who will maintain it.

Short and practical — how I explain the choice between WordPress and a dedicated PHP web service (Yii2, Laravel, Symfony) or an API + React setup.

WordPress fits well when you need

• A company site, blog, service landing pages.
• Leads and articles editable without a developer for every text change.
• SEO content: clean URLs, meta, internal linking — faster to start.
• A light storefront or catalog without heavy business logic.

If the goal is search leads and a clean company site, WordPress with a proper theme and few plugins is often optimal. That is how I ship it: custom theme, no “do everything” page builder stack.

When WordPress gets tight

• Roles, complex workflows, statuses, job queues.
• Client areas with permissions, reports, CRM/warehouse/payment integrations.
• Load and data where transactions, background work and strict code control matter.
• A product that grows by modules, not “one more plugin”.

Then you want a web service: Yii2/Laravel/Symfony backend, React frontend when needed. WordPress can stay beside it as the marketing site and blog — that split often works well.

How to choose without religion

1. Describe year-one scenarios: who does what in the system every day.
2. Separate the marketing site from the product. Often two contours.
3. Decide who edits content vs who owns logic.
4. Price maintenance: a cheap start with a heavy combo can cost more later.

Practical takeaway

WordPress is strong for content and lead gen. A web service fits when the product itself is a business process. Mixing them up is the main pain source: either “CRM on plugins” or “a custom CMS just for articles”.

If you are unsure on your project — describe the job in two paragraphs. I will say plainly where WordPress is enough and where a service is better from day one.