What we stopped building by hand

The interesting part of bringing AI into a Webflow workflow is not what it lets you produce faster. It is what it quietly takes off a designer's desk, and what it leaves sitting there. The work that left was the easy part. The work that stayed is harder than it was before.

The workflow we used to have

For years the shape of a project was predictable. A designer worked the layout in Figma, then rebuilt every section by hand in the Webflow Designer. Naming classes, setting up the grid, fixing breakpoints one by one, populating placeholder content, wiring the CMS, building the interactions, then a long pass of QA. The decisions were made early, in Figma. Everything after that was translation.

Most of the hours went into that translation. A skilled designer was visible mostly in how clean, consistent, and maintainable the production was. The craft was real, but a large share of it was repetition of patterns we had already solved many times before.

What actually left the desk

The first thing to go was scaffolding. Building the repetitive skeleton of a layout, the standard sections, the component patterns that recur on almost every project. A well-formed prompt against the Webflow Claude connector now produces a structured starting point in minutes instead of an afternoon.

Manual variation went next. Exploring an idea used to mean rebuilding it three or four ways to see which one held up. Producing those variations is now close to free, so the exploration happens faster and earlier in the process.

Then the production busywork. First-draft copy, content population, repetitive class management across breakpoints, asset preparation. The kind of work that used to fill a junior's day and that nobody enjoyed doing.

And finally a lot of recurring code. The custom interactions and snippets for behavior we have written a hundred times no longer need to be written by hand.

Put together, the production layer collapsed. The ninety percent of a build that was execution now takes a fraction of the time it used to.

The part nobody warns you about

Here is the trap. When production gets cheap, the default output does not get better. It gets worse.

Generated layouts are competent and generic. Sections follow each other without a reading hierarchy. Headlines describe the product instead of selling an outcome. Everything is technically correct and completely forgettable. A designer who simply accepts what the tools produce now ships an acceptable, anonymous site faster than ever before. The level drops precisely because the work got easier.

This is the thing that changed most in the job. Keeping the level high used to be a byproduct of doing the work slowly and carefully. Now it is an active fight against output that is always trying to settle on the average.

What the designer does better now

The first shift is from generating to editing. The valuable skill is no longer making the thing, it is looking at a generated version and knowing what to cut, what reads wrong, what is off by a degree the model cannot feel. Most of a site that works is now subtraction, and subtraction is a judgment, not a task.

The second is designing the system instead of the page. We spend far more time now on the rules the tools operate inside: the design tokens, the spacing scale, the component architecture across Figma and Webflow. Define that system well and the AI produces output that is already on brand. Define it badly and it produces fast noise at scale. The leverage moved upstream, into the foundations.

The third is that taste became the bottleneck. When everyone can generate, the differentiator is the eye that rejects most of what gets generated. That used to be one input among many in a project. It is now close to the whole job.

The fourth is translating intent into hierarchy. Taking a brand thesis, often one the client has not fully articulated, and turning it into a reading order, a visual hierarchy, a flow that sells. This is the work a model has nothing to generalize from, and it is exactly where the hours that left production have gone.

The new skill on the bench

Directing the tools is itself a craft now. Writing a prompt that returns a usable Webflow structure, knowing what context to hand it, recognizing the moment it is about to go wrong and stopping it before it does. From the outside this looks like less work. It is a different kind of attention. Less hand, more direction.

It also widened the gap between people. A senior designer with real taste and a well-built system now does work that used to require a small team. A junior with the same tools just ships mediocrity faster. The tools did not flatten the difference in skill. They amplified it.

Where this leaves the work

The hand-built phase is mostly gone, and that is fine, because it was never where the value lived. What remains is the part that was always the hard part: deciding what to build, holding the bar against easy output, removing the ninety percent that does not belong, and making something that reads like a decision rather than a generation.

AI did not lower the level of design work. It moved the level entirely into the choices, and made the production that used to hide a weak idea almost free. For a designer who can actually decide, this is the best version of the job there has been.

See how we work with our clients.