WordPress, Webflow, Wix or custom: how to actually choose

Start with the question nobody asks

Before comparing feature lists, answer this: after launch, who is going to change things? If the answer is a marketing person who updates copy weekly, that points somewhere very different than if the answer is nobody, or if it is a developer. I have watched businesses pay for a beautifully custom site and then never touch it for two years because every edit needed a developer they had not budgeted for. The platform was not wrong on the day it launched. It was wrong for the eighteen months that followed.

WordPress

WordPress earns its place on content-heavy sites and on e-commerce through WooCommerce. If you publish often, need editorial workflows, or want a large ecosystem of plugins for things like bookings, memberships or multilingual content, it is hard to beat. The tradeoff is maintenance: plugins update, sometimes conflict, and occasionally break things. Someone has to own that. If nobody owns it, a WordPress site quietly degrades. I have inherited plenty of sites where the real problem was not the build but two years of unattended updates.

Webflow and Wix

These suit smaller marketing sites where the owner wants to make edits without calling anyone. Webflow gives a designer far more control over layout and interaction than Wix does, and its CMS handles structured content well. Wix is the more forgiving of the two for a non-technical owner who mostly wants to swap text and images. Both start to fight you when the project needs unusual functionality or heavy integrations. The moment you find yourself working around the platform rather than with it, you have outgrown it, and pushing further usually costs more than moving would have.

Custom

A custom build in something like Next.js makes sense when you need real performance, genuinely unusual interaction, or product-like functionality that a page builder resists. It also makes sense when the site is closer to an application than a brochure. The honest cost is that it needs a developer to extend it. I build custom when the project earns it, and I say so plainly when it does not. Most marketing sites do not.

The pattern I keep seeing

The regret is almost never about visual design. It is about a mismatch between the platform and the person left holding it. A clinic that needed to add practitioners monthly and could not. A retailer on a custom stack who wanted to run a promotion this afternoon. In both cases the build was competent. The fit was wrong, and the fit is a decision made in the first conversation, long before anything is designed.

How I decide

I ask what changes after launch, how often, and who does it. I ask what has to integrate with what. I ask whether anyone will own updates. Then I recommend, and I explain the tradeoff in plain terms rather than presenting the choice as obvious. Because I design and build the site myself, I have no incentive to steer you toward whichever platform is easiest for me to hand off. The only thing I have to live with is whether you are still happy with it a year later.