After 50+ WordPress builds, the custom theme versus page builder question has a clearer answer than most blogs suggest. Here it is, plus the three exceptions where the answer flips.
The default answer
For most projects: use a well-built theme (Kadence, GeneratePress, or Blocksy) and the WordPress block editor. Skip page builders. Skip custom themes unless you have a specific reason.
The reason is simple: a clean theme plus the block editor produces sites that load fast, are easy to maintain, and survive theme updates without breaking. Page builders and custom themes typically do not.
What page builders cost you
Bloat
Every page builder adds CSS and JavaScript the site loads on every page, whether you used the builder on that page or not. On a 5-page site, this is 200-400KB of dead weight. On a 50-page site, it is the reason your TTFB is 800ms instead of 200ms.
Lock-in
When your content lives in a page builder’s shortcodes, switching themes becomes a multi-week migration. The builder format is not portable. This is fine if you never plan to change themes. Most clients change themes.
Update friction
Page builders update frequently, often breaking existing content. The fix is usually “save the page again” or “rebuild the section.” This is why clients with page builder sites call me three times a year asking for help with a layout that broke.
What a custom theme costs you
Cost
A real custom theme is 80-200 hours of development. For most small-business sites, that is more than the entire project budget. The math does not work.
Maintenance
You now own the theme. WordPress core updates can break things. Plugins change. The theme has to be maintained by someone who knows the codebase. That someone is rarely the client.
When to use a page builder
Exception 1: The client insists on drag-and-drop editing
Some clients want to edit layouts themselves without learning the block editor. A page builder gives them that. Accept the trade-off, document the costs, ship it.
Exception 2: The site has heavily customized layouts on every page
If every page needs a unique layout that the block editor cannot easily produce, a page builder reduces friction. But this is rarer than people think.
Exception 3: The site is a one-off marketing campaign
If the site will be thrown away in six months, the lock-in cost does not matter. Use whatever ships fastest.
When to use a custom theme
Exception 1: High-traffic site where every millisecond matters
A 100k+ visits-per-month site justifies the 100-hour custom theme investment. The TTFB improvement pays back.
Exception 2: Brand-driven visual identity that no theme can match
If the brand requires typography, color, and layout choices that no off-the-shelf theme supports, custom is the only path.
Exception 3: Platform-as-a-product site
If you are building a SaaS or marketplace, the site is the product. Custom is justified. For marketing sites, it is usually not.
The bottom line
Default to a clean theme and the block editor. Deviate only when one of the exceptions above applies. For 80% of small-business sites, the default is the right answer.