It used to be that designers depended on devs to make it real. Now they don’t. They just need the right prompt.

Senior Product Designer, Fintech Startup

Gino Ferrand, writing today from Santa Fe, New Mexico 🌞

Webflow was always a tool for designers who didn’t want to wait on developers. But their latest pivot pushes the boundary further. Now, they’re not just skipping devs. They’re skipping design itself.

The company just announced a suite of generative AI features: layout generation, component composition, and automated UI suggestions based on plain-text prompts. Describe the “vibe” of a landing page, and Webflow will make it. Iterate with natural language, not Figma wires.

It’s not alone. Tools like Framer, Relume, and Modulz are building similar flows. What used to be a battle between React-based builders and design systems is becoming something else entirely: a race to compress intent into interface, skipping the middle layers.

And that’s what makes this moment so telling for engineering leaders.

Low-Code 2.0 is Here and It Doesn't Care About You

Let’s be honest. Most low-code platforms never really lived up to the hype. They still required dev resources, still broke in edge cases, still needed handoffs. Webflow’s first version helped avoid front-end devs for marketing pages, but that was it.

This is different.

AI changes the shape of the stack. It compresses layers. Instead of going from PM to designer to dev, you go from idea to product in one prompt loop. And the interfaces being built? They’re not always for users. Increasingly, they’re internal, ephemeral, or AI-facing. Think dashboards for agents. Admin panels for prompts. Output viewers for workflows that won’t last the month.

The new low-code isn't about abstracting code. It’s about the abstract process.

And Webflow’s AI pivot puts a spotlight on this shift: the stack is disappearing in favor of intent.

What This Means for Engineering Orgs

If you lead a front-end team, you’ve probably already felt this pressure. Marketing teams are shipping live pages without you. Product managers are asking if LLMs can scaffold interfaces for MVPs. And now, design tooling is leaning into AI-generated UI components that “feel right” without passing through human designers or developers at all.

This isn’t about better tooling. It’s about a collapsing value chain.

And when that happens, engineering becomes one of two things: either a bottleneck, or a systems integrator.

The smart teams are already adapting. Some are using tools like Webflow AI for prototyping, then exporting the structure into real component libraries. Others are embedding AI agents into their dev workflow to pair with these builders, creating hybrid flows that can be audited and version-controlled.

But make no mistake: the role of “front-end dev” is shifting. The job is no longer to craft every button. It’s to ensure coherence, security, and performance across interfaces that might be generated on the fly.

Need engineers who can design, integrate, and ship with AI in the loop? That’s a hiring challenge, not a tooling one.
Smart teams aren’t just buying AI tools. They’re hiring engineers who already know how to collaborate with them. At TECLA, we help U.S. tech orgs hire senior-level, English-proficient engineers across Latin America; people who understand how to scaffold with LLMs, orchestrate components, and move fast in this hybrid-build reality.

Same time zones. No language gaps. See what a real AI-native team looks like.

Why “Vibe Coding” Is More Than a Meme

Developers used to scoff at the idea that you could build real software by describing the vibe. And yet here we are.

Framer raised millions doing exactly that. Prompt-to-landing-page tools are everywhere. Some startups are skipping Figma entirely, prototyping right in the AI-augmented builder. Others are training custom LLMs on their design system to skip the ideation phase completely.

A Reddit thread last week joked that “half of design is now convincing AI not to use gradients.” Funny. But also, not wrong.

We’ve entered the prompt jockey era. It’s not about syntax anymore. It’s about guiding the machine toward something useful, usable, and on-brand. Which raises the uncomfortable question:

Are your teams ready to lead when they’re no longer the ones typing?

More to come…

Gino Ferrand, Founder @ Tecla

Keep Reading

No posts found