WordPress runs 43% of all websites on the internet. Sixty percent of every site that bothers to use a CMS. Roughly 58% of the top 10,000 sites by traffic, per W3Techs. Webflow polls in the low single digits.
That’s not because of nostalgia for WordPress. That’s a market voting, over and over, for the platform that lets a marketing team touch its own website without filing a dev ticket.
Webflow’s pitch is genuinely good: design-led, no-code, ship something gorgeous in a relative hurry. Fine for a five-page site that never changes. Not so fine when a company needs to publish constantly and can’t wait around for a developer’s calendar to open up.
The client that switched, then switched back
Early this year, a B2B AI company I work with bought the Webflow pitch, despite the reams of analysis I provided that said, “don’t pick Webflow, it’s wrong for your purposes.”
The site launched looking sharp, as promised.
Then the marketing team tried to actually use it.
New content type? Get the developer. Restructure a page? Developer! A schema update or a new landing page template meant working in the Webflow Designer, not the Editor most of the team was actually
Click here to continue reading this article.
