01 / The choice
Both build a website. They leave you in very different places.
A page builder (Elementor, Divi, WPBakery and the rest) gives you a visual editor. You drag things onto a canvas and they appear. A custom theme is built for your site specifically, in code, with the editing controls decided deliberately.
The sales pitch for builders is that you can change anything yourself. The sales pitch for custom is that it is faster and cleaner. Both are half true, and the real difference only shows up months later.
02 / Where builders win
Genuine advantages, not consolation prizes
You can change the layout, not just the words. Add a section, move a testimonial, launch a campaign page on a Friday afternoon without asking anyone. For a business that markets actively, this is worth a great deal.
Getting started is cheap. A competent person with a builder produces something presentable quickly.
You are not tied to us. Thousands of people can maintain an Elementor site. That is a real answer to a real fear, and anyone who dismisses it is arguing for their own lock-in.
We build with Elementor on client sites, deliberately, when those things matter more than what follows.
03 / What it costs later
The bill arrives in month six
Weight. A builder ships a general-purpose engine that has to be ready for anything you might drag onto the page. That is CSS and JavaScript you load whether you use it or not. It can be tuned. It cannot be removed.
Drift. Every page is independently editable, which means every page eventually differs. Three shades of blue, four button sizes, headings at sizes nobody chose. Not because anyone was careless, but because the tool makes each page its own decision.
Lock-in that is not about people. Your content lives inside the builder’s own format. Deactivate it and you get shortcode soup, not clean HTML. Moving away later is a migration, not a switch.
Version risk. Your site’s appearance now depends on a plugin’s release schedule.
04 / What custom costs
The honest downsides, since they are rarely stated
You can only change what was built to be changeable. A good custom theme gives you fields for everything that should vary. It will not let you invent a new layout on a Friday. If that matters to how you work, take the builder.
It costs more to start. Somebody is designing and coding rather than assembling.
The pool of people who can maintain it is smaller. Mitigated by writing standard code and documenting it, but not eliminated.
05 / How to choose
It follows from how often you change things
Take a page builder if you run campaigns, publish landing pages, and want to restructure without a developer. The overhead is the price of that freedom, and it is a fair price.
Take a custom theme if the site is mostly stable, speed matters commercially, you have a brand worth holding consistent, or the site is going to grow into something that does more than present pages.
A middle path exists and is what we most often recommend: a custom foundation (the type scale, the colours, the components, the templates that carry most of your pages) with a builder available for the pages that genuinely need to be freeform. You get a fast, consistent core and an escape hatch for campaigns.
06 / Whichever you choose
Two questions to settle before work starts
What can I edit without calling anyone? Get a specific answer. “Everything” is not one.
What happens if we part ways? Who has the hosting, the domain, the files. If the answer is vague now, it will be worse when it matters.
Neither choice is wrong. Choosing without knowing what you are trading is.
Tell us how your site actually gets updated, and we will tell you which of the three approaches fits, including when the one you already have is fine.