Webflow
What it is
A visual site builder and CMS in one hosted tool: the designer builds in the browser and the marketer edits in the same place. Webflow hosts it.
What it’s good at
Design fidelity: what the designer builds is what ships, with no developer translating mock-ups. A CMS a non-developer runs, so a landing page goes live without a ticket. Speed from approved design to a live site, measured in days.
What it costs to own
The design system lives inside the tool as classes, so site quality is the quality of whoever built them. A disciplined build stays editable for years; a sloppy one is expensive to inherit, and untangling it takes a Webflow specialist, a scarce hire. You rent the hosting, and the export ships pages without the CMS. Leaving means a rebuild.
When it’s a poor fit
It is a poor fit when your IT policy requires infrastructure you control, since Webflow’s hosting is part of the product. The same goes when the site needs sign-ins or data flowing back; that is application work, and Webflow builds pages. And if nobody on your team has opened the editor since launch, you are paying for an editor nobody opens.
What it sits beside
It replaces WordPress for marketing sites, and the habit of emailing an agency to change a headline. It is bought alongside Tag Manager and GA4, with forms feeding the CRM. The overlap to watch: add HubSpot landing pages and the team builds in two systems with two tracking setups, until nobody knows where a page lives.
My experience
The previous bucca.dk ran on Webflow, and what I have seen decide whether it gets used is whether marketing is in the editor every week.