When Not to Build the Site on WordPress

WordPress is a reasonable CMS when someone on your side will publish every week without an engineer. It is a poor default because “everyone in BiH uses it.” A ThemeForest file with your logo and five plugins that break on the first core update is not website development. It is a stall.

CodeLoop Studio in Sarajevo does not ship that stall. We are not in a holy war against CMS software. We pick the stack after the brief. Public sites we often ship on Next.js. This article is when WordPress is the wrong product — and when we will still leave a working WP install alone.

When WP is the wrong default

Booking, checkout, and login are not cheaper because the admin is green. A plugin postpones the real flow. Those jobs are a shop, a web app, or a form you actually answer — not membership bolted onto a blog theme.

If nobody owns updates — core, theme, plugins — “cheap WP” becomes a site that does not open. Maintenance is a separate conversation: hosting is not a retainer.

When a CMS still makes sense

• Daily publishing without us. News, programmes, listings. Fear of code is not a reason. A named editor is.

• An existing WP that already ranks and is maintained. We will not burn it for a portfolio screenshot. Rebuild is a decision, not a reflex.

• A brochure with a form. That can be WP, Next.js, or something quieter. The map comes first — website development notes.

• Proof is operators, not a CMS logo. SD Nail Studio is a site people use to book. The stack is the delivery, not the headline.

What we do instead

Brief, then stack. If the job is findability, we build a site. If the job is roles, we do not hide it in WooCommerce. Ten decisions before colour: ten things before a site.

How to start

Send the current CMS (or none), who publishes, and whether you need booking, pay, or login. We reply within 24 hours — online estimate or contact. If the brief is “pick a theme and swap the logo,” we will say that is not our job.