Developers like me are quick to write off page builders like Elementor and Divi, and I've done it myself in a piece I wrote a while back about what they end up costing you. That's still true for a lot of businesses. But it's not the whole picture, and pretending a builder is always the wrong answer would be as dishonest as pretending it's always the right one. Here's the honest version.
Where a builder is genuinely the right call
If you're a sole trader with five pages, you're the only person who'll ever touch the site, your budget is genuinely tight, and you don't expect the business, or the site, to grow much in complexity over the next couple of years, a page builder is a perfectly reasonable tool. You can learn it in a weekend, make your own changes without emailing a developer every time, and get something live fast.
I built a five-page Elementor site for a sole trader in Hull last year, a mobile hairdresser who wanted to update her own price list without messaging me every few months. It was the right call. She's been maintaining it herself since, no help needed, and it does exactly what it needs to. I've told clients this to their face when it was true, even though it meant they didn't need me.
Where it starts to bite
The problems show up later, not on launch day. As the site grows past a dozen or so pages, or more than one person starts editing it, the builder's own structure gets in the way rather than helping. Speed becomes a real issue once you care about it, because the builder loads its engine on every page whether that page needs it or not, and that shows up in Google's page speed scores and, eventually, rankings. And if you ever need something the builder genuinely can't do well, a custom booking flow, a proper integration with another system, a specific layout it fights you on, you find out the hard way that you've been building inside someone else's walls.
I inherited a client site last year that had started on a builder with one person editing it. Eighteen months on, three people were adding pages, the site had six different heading styles, and the homepage took four seconds to load on a phone signal outside the office. Untangling it cost more than building it properly the first time would have.
The real question isn't which tool
Ask yourself who's going to be editing this site in two years, not who's building it this month. A single non-technical owner making occasional text changes has very different needs from a growing team publishing weekly, or a business that expects its site to do more next year than it does now. Pick the tool for where the site is headed over that time, rather than only where it sits on launch day, because rebuilding from scratch later costs more than the extra you'd have spent up front.
The middle ground most people don't know about
The choice isn't actually "builder or nothing." A lean, hand-built WordPress theme using ACF for the editable fields gives a non-technical owner a clean, simple editing experience, real named fields rather than a drag-and-drop canvas, without the weight and lock-in of a full builder. It used to cost noticeably more than a builder site because of the hours involved. AI-assisted development has closed a lot of that gap for me, which is most of what I cover in the longer piece on what page builders really cost if you want the detail.
My honest rule of thumb
If in doubt, I ask a client three questions: how many pages, who's editing it long term, and what's the growth plan for the next two years. The answers usually make the decision obvious, and more often than not it points away from a builder once a business is paying someone to build the site rather than doing it themselves. It rarely takes more than five minutes to work out, and it saves both of us from a rebuild neither of us wanted a year down the line.
If you want a straight answer for your own situation rather than a sales pitch either way, book a free 30-minute surgery and I'll tell you honestly which one fits.
Free 30-min surgery
Working on something similar?