WordPress vs custom code: how we choose (and stay fast)

We still build on WordPress when the job calls for it: content teams that live in the editor, WooCommerce, or integrations where the ecosystem saves months. What burned us in the past was not the core software — it was unmaintained installs: dozens of plugins, outdated themes, page builders spitting heavy markup, and nobody scheduled to patch or prune.

Small businesses often sign off at launch and then skip updates. Plugin updates break layouts. Security fixes wait. The contact form dies quietly. That pattern exists on other platforms too, but WordPress's plugin culture makes it easy to stack weight without noticing.

So our playbook is pragmatic: lean WordPress or WooCommerce from real design when the CMS wins; custom code (React, Vite, static) when the goal is a fast marketing site with minimal moving parts. We rarely use theme builders — they are usually the drag on Core Web Vitals. When clients need editable content on a static stack, we pair a headless CMS.

Build budgets are similar either way for many sites. The difference is what you pay in performance and care over the years — and we align the stack so that bill matches how your team actually operates.

For the buyer-side framework we use with Michigan teams, see custom website vs template.