I'm a Webflow Developer. Here's Why I Stopped Recommending Webflow to Small Businesses.

I Still Build in Webflow Every Week

Let me start with where I stand, because it matters for everything else in this post. I am a Webflow developer. I build Webflow sites for agency clients at Jaryah Studios, I learned Client-First the hard way, and I have written more than one post about why I chose Webflow in the first place.

So this is not a post from someone who tried Webflow once and left. It is a post from someone who uses it every week and has quietly changed what he tells small business owners.

When a small business whose website mostly needs content updates asks me for a new site today, I no longer recommend Webflow by default. I usually recommend custom code with a headless CMS. That does not make Webflow a bad platform. It means the thing Webflow charges for is often not the thing these businesses need. Here is why.

The Monthly Fee Never Ends

Webflow, like every site builder, charges a site plan for as long as your site is live. If you need a CMS for a blog or services, you pay for a higher plan. That is fine when the platform gives you something you use every week. For many small businesses, it does not.

A typical small business site changes a few times a month: a new photo, an updated price, a blog post. The design often stays the same for years. Paying for a visual design platform every month for that is paying for flexibility you rarely use.

A custom-code site has no site-builder subscription, but it is not free to run. It needs hosting, a CMS, a way to handle forms, and someone to keep it updated. Here is an illustrative comparison of platform costs only, using list prices as of October 2026:

• Webflow: the Premium site plan, which includes the CMS, is $25 a month billed yearly. Over three years that is about $900, before taxes, bandwidth add-ons or extra editor seats.
• Custom code: a static site can be hosted for free on platforms such as Cloudflare, or for $20 a month on Vercel Pro (Vercel’s free plan is for non-commercial use only). That is $0 to about $720 over three years. Sanity’s free plan covers up to 20 users and 10,000 documents, which is enough for most small business sites. A form service may add a small fee if you outgrow free tiers.

So the subscription saving is real, but it is not always large. What decides the real cost is everything around it: the build price, how often the site needs a developer, who fixes it when something breaks, and how much a future change costs on each setup. A Webflow site that an owner can maintain alone may well be cheaper over three years than a custom site that needs a developer for every small change.

AI Changed the Cost of Custom Code

Two years ago, my honest answer was different. Custom code took me longer to build, so it cost more up front. Webflow was the faster, cheaper way to get a good-looking site live.

That has changed for the work I do. I now build custom-code sites with AI-assisted tools like Claude Code and OpenCode. They speed up the slow parts: scaffolding, routine components, debugging and repetitive edits. I still make the requirements and design decisions, plan the structure and CMS integration, review every change, test every breakpoint and check accessibility and performance. Deployment, security updates and maintenance after launch are still real work too. AI does not remove any of that.

The result, for the small content sites I build, is that a custom-code site in Astro or Next.js now takes me about as long as a Webflow build, and I can price it similarly. That is my experience, not a rule. A framework is not automatically cheaper or faster than Webflow, and a different developer or a more complex project can land somewhere else entirely. The difference I see is after launch: no site-builder fee, more control over performance, and fewer limits on what we can add later.

”But I Need to Edit My Own Site”

This is the first thing every owner asks, and it is the right question. My answer is usually a headless CMS.

With a CMS like Sanity, your content lives in an editor separate from the design. You log in, change text, swap images, publish a blog post, and the site updates. For routine edits, it can feel a lot like editing in a site builder.

The difference is that the layout is not in the editor, so you are much less likely to break it by accident. For most owners, that is a feature, not a limitation. But it only works if the CMS is set up properly. Someone has to model the content around what you actually change, connect it to the site, set up previews and publishing, and maintain that integration. A headless CMS is not automatically simpler or cheaper than Webflow’s editor. It is simpler only when it is built well for the way you work, and a new page layout still needs a developer.

What You Get With Custom Code

• No site-builder subscription. You still pay for hosting and any services above their free tiers, but not for a visual design platform you do not use.
• Control over speed. You decide exactly what goes on the page, which makes a fast mobile site easier to achieve. It is not automatic. Real speed depends on images, fonts, JavaScript, third-party scripts, hosting and caching, and a badly built custom site can be slower than a good Webflow one.
• More control over ownership. The source code is yours, and you can usually move hosts or developers without rebuilding the site. It still depends on services like your host, CMS and form provider, so moving is easier but not effortless. With Webflow, code export gives you static HTML and CSS, but CMS-driven pages are not included.
• Room to grow. Booking forms, client portals, AI features or integrations are not limited by what a plan allows, though each one still has to be built and maintained.

When Webflow Still Makes Sense

I want to be fair here, because Webflow is still a great tool in the right hands.

• Agencies already working in Webflow. If your agency builds and manages client sites in Webflow, keep doing it. I still build Webflow sites for agencies, inside their files and class systems.
• Marketing teams who design pages themselves. If someone on your team wants to build new landing pages visually every week, without a developer, Webflow’s designer is worth the fee.
• Sites that already work. If your Webflow site is fast, easy to update and bringing in enquiries, there is no reason to rebuild it just to save a subscription.
• Owners who want independence from a developer. If you want to change layouts yourself, not just content, Webflow gives you that. A custom site with a CMS gives you content editing, but not design freedom.

The rule I use is simple. If the business will use the visual designer, Webflow earns its fee. If the business only needs to edit content, custom code with a CMS is often the better deal.

Two cautions so this is not misread. A simple site does not automatically need a custom framework, and a content-heavy site does not automatically need a headless CMS. Webflow’s CMS handles plenty of blogs well. Custom code earns its place when you need specific functionality, a particular integration, a tailored content structure or more technical control, and when you have a developer you trust to maintain it.

The Question to Ask Before You Choose

Do not ask which platform is best. Ask four things:

1. Who will change this site? A marketing team, an owner, or a developer?
2. How often? Every week, or a few times a month?
3. Who will maintain it? Is there a developer available for fixes and updates, and what does that cost?
4. What will it cost in three years? Build price, every monthly bill, and the developer time you expect until then. The cheapest build is not always the cheapest site.

For most small businesses I talk to, the answers point to custom code with a headless CMS. For most agencies, they point to Webflow. That is why I now offer both, to different people, for different reasons.

I could be wrong about where this goes next. Webflow keeps shipping, and AI keeps changing how sites get built. But today, this is the honest advice I give, even though it means recommending against the platform I use every week.