All posts
WebflowCustom codeProcess

When is Webflow the wrong tool for the job?

It's a fair question to ask someone who works mostly in one platform. I think Webflow is the right call for most marketing and B2B sites, especially when the content changes, and that's why I spend most of my time in it. But there are specific cases where I don't use it, and they're concrete enough that you can check them yourself before you commission anything.

The cases where I don't use Webflow

There are four, and I think they're narrower than what you'll read online. Even with most of my work on the platform, I still talk people out of it several times a year when one of these applies.

  • The interface is the product. If people log in and use what you're building, instead of reading it, you need an application framework. Webflow can run the marketing site in front of that product very well, but I wouldn't build the product in it.
  • The feel is the product, and the site is small. When how a page moves and how fast it responds are the main sales argument, a platform limits how far you can tune them. On a large site I'd accept that limit for everything else Webflow gives you. On a small one you'd be paying for a CMS you won't use and getting a limit on the one thing that matters.
  • Nobody will log in to edit it. The CMS and the Designer are most of what the monthly fee pays for. If the content changes twice a year, you're paying for features you don't use.
  • The output has to live somewhere else. If the pages have to be embedded in an existing application, served from infrastructure you control, or handed to a team that works in a repository, you'll spend the project exporting your way out of the platform.

Why Home Organizers isn't built in Webflow

Home Organizers Long Island is a small service business. I took that project end to end (design, copy, SEO and code), and I chose to build it by hand: no Webflow, no framework, no build step. I did it on purpose because I wanted every detail of the feel and the performance to be mine to tune.

It's the second case on the list. A home organizing business sells a transformation, so the centerpiece of the site is a before and after slider, written from scratch with no library, where you drag to see the room change. How that drag feels, how quickly it responds and whether it stutters on a phone is the sales argument itself, not decoration. GSAP and ScrollTrigger handle the rest of the motion, but I wrote the slider by hand because it was the part that had to feel right.

The rest of the site pointed the same way. It's a handful of pages that change rarely, with LocalBusiness structured data so search engines read the business correctly. There's no editorial team and no collection to maintain, so a CMS wouldn't have made anything easier, and the client doesn't pay a monthly platform fee.

What a custom build costs you

This isn't a free choice, and I'd be selling you something if I said it was. A hand-built site has no Designer behind it. Changing a paragraph means changing code, which means it goes through whoever writes code, and usually that's me. If you later want a marketing team to run it, that's a rebuild, not a migration.

The person who maintains it also has to be a developer. That narrows the field a lot compared with a Webflow project, which any competent Webflow freelancer can pick up after me.

So you save the platform fee and get full control over the details, and in exchange you give up easy editing. I think that trade works on a small site that doesn't change much. On almost anything else I wouldn't make it.

Two questions that usually settle it

Most of the time, these two are enough to tell which side your project is on:

  • Who edits this in eighteen months, and are they a developer? If it's a marketing person or the owner, I'd build it in Webflow.
  • Is there one thing this site has to do that the platform doesn't do? One thing, not three.

One missing feature is rarely a reason to leave

If the answer to the second question is three things, the project is working against the platform almost everywhere, and Webflow is probably the wrong choice. If it's one thing and everything else is ordinary, I'd almost never suggest a rewrite. I'd build it in Webflow and add custom code for that one piece.

Most sites that feel like they need to leave Webflow need someone to write the one part the builder can't do, and to leave the rest as it is. That's a much smaller project than a rebuild, and you keep the reasons you chose Webflow in the first place.

Why it's still Webflow most of the time

I don't want this post to read as an argument against the platform, because it isn't one.

If your site has content that changes, a team that has to change it, more than a handful of pages, or a plan to grow into more languages and markets, I think Webflow is the right tool and it isn't close. The CMS, the localization, and the fact that any competent Webflow developer can pick the project up after me are worth the monthly fee several times over.

The four cases above are exceptions. Almost everything that reaches me is a Webflow project. I write about the exceptions because I'd rather tell you up front when your project is one of them.

start a project

Ready to build.

A few quick details so I can scope it before we even talk, or just email me directly.

hello@lucasmujica.dev
Buenos Aires · Remote worldwide

Hi Lucas, I'm from . I'm building a with a budget around . Reach me at .

The details that decide the price
Replies within a day