let's talk

Beyond Webflow

We build in Webflow. This is the post about when not to buy it.

Most sites never reach these ceilings. The ones that do tend to reach them hard, and late.

Four of them, the hybrid that usually works instead, and three questions that settle it in week one.

Four ceilings

Real user accounts. Webflow has memberships, and they are fine for gating a page or a download. Anything with roles, permissions, a dashboard, or a user who sees a different site from the next user outgrows it quickly and awkwardly.

Data that belongs to a person. Saved items, order history, a quote that has to still be there next Tuesday. Once something must persist per user and be edited by them, you are describing an application with a website attached, not a website.

Search and filtering at scale. A few dozen collection items filter beautifully. A few thousand, across several facets, with sensible sorting, does not, and the failure is gradual, so it usually gets discovered after the content is already in.

A second system that has to answer in real time. One integration is routine. Being the front end of a live booking engine, an ERP or a pricing service is a different job, and the platform will fight you for it.

The i4B homepage: an electric car seen from above with a dotted circuit outline traced around it.

The middle path

Most companies that hit a ceiling do not need to abandon Webflow. They need a line drawn: Webflow for the marketing site, custom for the part that holds state, one domain across both, one shared design system so the seam is invisible.

The benefit is organisational as much as technical. Marketing keeps the keys to the pages that change weekly and stops queueing behind a deploy; engineering owns the part where correctness matters and stops being asked to move a button.

i4B sits firmly on the marketing side of that line. It is a software company for electric-vehicle manufacturers, the software is the product, and the site's job is to explain it and recruit the people who build it. Those are pages, not an application.

How to tell before you commit

Three questions. Does anyone log in? Does anything need to be true for one person and not another? Does a second system have to answer while the visitor waits?

One yes usually still means Webflow, with an integration doing the work. Two or three means plan the split now, while it is a design decision rather than a migration with content already loaded into it.

Asking these in week one costs an hour. Discovering them in month nine costs the timeline, and generally someone's credibility with their own board.

Get a free
audit of your
website

Speed

SEO

Animation

Design

Conversion

get my free audit
Get my website
View: CasesCases

You

Click

Drag