WordPress or a custom framework - how to actually choose

Nearly every first conversation with a new client starts with a platform opinion already formed - usually “should it be WordPress?” - before what the site actually needs to do has been discussed. That’s backwards. The platform is a consequence of the requirements, not the starting point.

What actually determines the answer

The honest deciding factor is who updates the site after launch, and how often. A business that publishes new listings, blog posts or promotions weekly needs a content system a non-developer can drive without calling in a developer every time - that usually points to WordPress on a clean, lightweight theme, built without the plugin sprawl covered elsewhere on this page. A business whose site barely changes after launch, a landing page for a development project or a small service business with a fixed set of pages, gains nothing from carrying a CMS’s weight and its ongoing security surface. A static build on something like Astro loads faster, has effectively nothing to hack, and costs less to maintain because there’s less of it to maintain.

Where a custom PHP build still earns its place

Between those two extremes sits the case that gets ignored most often: a business with specific, narrow functionality - a booking calendar, a quoting tool, an unusual layout requirement - that doesn’t map cleanly onto either a CMS theme or a fully static page. A lean custom build, written for exactly what’s needed and nothing else, tends to outperform both a bloated WordPress plugin stack pretending to solve the problem and a static site straining to fake dynamic behaviour with JavaScript bolted on afterwards.

The question worth asking first

Not “which platform is best” but “who is touching this site in six months, and how often.” Answer that honestly and the platform choice mostly makes itself.