WordPress or Custom Code: How to Actually Decide

I get asked this in almost every first call: "Should we just use WordPress, or build something custom?" People expect a technical answer. It's mostly a business answer.

Here's the framework I actually use, after building both for years.

Start with how the site will change over time

The real question isn't "what can this platform do on day one." It's "who touches this site in month six, and how often."

If a marketing person, a founder, or a non-technical team member needs to publish pages, swap images, run a sale, or add a blog post without opening a pull request, WordPress (or a similar CMS) wins almost every time. That's what it's built for. Fighting that by hand-rolling a custom CMS just to avoid "WordPress" as a word is usually wasted budget.

If the site is really an application, logic-heavy, with custom workflows, non-standard data models, or tight performance requirements, a custom build (Next.js or similar) usually wins. You're not fighting a CMS's assumptions about what a "page" or "post" is.

Plugin dependency is the real cost of WordPress

WordPress's strength, its plugin ecosystem, is also its biggest long-term liability. A typical WooCommerce store I've inherited has 15 to 30 active plugins. Each one is a dependency you didn't write, maintained by someone else, on their schedule.

When I audit an existing WordPress site, I'm not looking at the theme first. I'm looking at:

• How many plugins overlap in function (two SEO plugins, two caching plugins)
• Which plugins haven't been updated in over a year
• Which "critical" features live inside a single plugin with no backup plan if it's abandoned

That's not a knock on WordPress. It's a maintenance reality you should budget for, the same way you'd budget for server costs.

Custom code has its own hidden cost: you own everything

The flip side people underestimate: when you go custom, there's no ecosystem to lean on. Need a booking calendar, a review widget, a subscription flow? Someone has to build it, and someone has to maintain it forever, because there's no "just update the plugin" button.

That's fine when the thing you're building is your actual product and the custom logic is the point. It's a bad trade when you're rebuilding a content marketing site from scratch just because custom code "sounds more modern."

The questions I actually ask a client

1. Who edits content after launch, and how technical are they?
2. Is the core value of this site standard (blog, catalog, marketing pages) or genuinely unusual (custom logic, non-standard workflows)?
3. What's the realistic maintenance budget for year two, not just launch?
4. Do you need e-commerce, and if so, how deep? A 40-product store and a 4,000-SKU marketplace are different problems even though both say "WooCommerce" or "Shopify."
5. How much does page speed and Core Web Vitals actually matter to your traffic, versus how much editorial flexibility matters?

The honest answer for most small and mid-size business sites is still WordPress or WooCommerce, built properly, with a lean plugin list and a developer who actually reads the plugin code before installing it. The honest answer for a product, a marketplace with custom logic, or a site where speed is a competitive edge, is usually custom.

Pick based on who's going to run the thing in a year, not based on what's trending in developer Twitter this month. That one decision saves more rebuild money than almost anything else you'll decide about your site.