Webflow Conf 2026 made a lot of logical moves around AI, marketers and enterprise, but the bigger vision feels less clear than it used to. The core product is still strong, the question is what Webflow wants to become next and how Source fits into that future.
Vimalan Vijayasekaran
Webflow Conf 2026 introduced Source, expanded AI capabilities, new tools for marketers, AEO features and a bigger vision for enterprise marketing teams. But the mixed reaction online points to a deeper question: what does Webflow actually want to become?
There’s been a lot of scepticism and mixed feelings online following the Webflow Conf 2026 announcements.
AI. Marketers. Enterprise. Designers. Developers.
If I had to summarise my own reaction, I think a lot of the uncertainty comes down to contradictions.
Almost every individual decision Webflow is making makes sense.
I’m just less sure what the bigger idea tying all of them together is.
The headline announcement was Source by Webflow, a new platform designed for marketing teams and AI agents to build and optimise digital experiences together.
Unlike the traditional Webflow Designer, Source is built around code as the underlying foundation and can connect with an existing codebase, CMS, hosting setup and wider marketing technology stack.
Webflow described it as a shared operating environment where marketers, designers, developers and AI agents can work together. Source is currently in a limited research preview.
Webflow also announced or expanded:
The message from Webflow is relatively clear: the definition of a website builder is expanding beyond designers and developers to marketers and AI agents.
And strategically, I understand it.
AI changed the software market very quickly.
I don’t think Webflow was uniquely unprepared for it. Almost every software company has spent the last few years working out where AI fits into its product, while simultaneously trying to keep up with the expectations created by tools like Cursor, Claude and the growing number of AI website builders.
At the same time, enterprise is where the larger customers and budgets are.
That naturally means selling further into marketing organisations rather than exclusively serving the designers and developers actually building the websites.
Webflow's own messaging around Source describes a product specifically for "modern marketing teams and their AI agents".
Again, that makes complete sense.
The question is what happens when all of these individually logical decisions start pulling the product in different directions.
When I started using Webflow around six years ago, the value proposition felt incredibly easy to understand.
It gave designers and developers the ability to build high-quality websites visually, while retaining much of the flexibility and control traditionally associated with writing code.
You could build increasingly sophisticated websites without the traditional development workflow.
That was exciting.
Designers gained technical power.
Developers could work much faster.
And each year, it felt like the ceiling of what you could realistically build in Webflow was getting higher.
There was a clear relationship between the product, the people using it and where it appeared to be heading.
Webflow became very good at delivering against that vision.
I would argue it still is.
This is where things get interesting.
The core Webflow product is already really solid for the vision it was originally created around.
Website design, CMS, visual development, reusable components, hosting and content management all work together extremely well.
For many marketing websites, I still think Webflow is one of the strongest platforms available.
But what happens when the company's ambition starts expanding beyond the problem its core product was designed to solve?
Does an incredibly successful existing product eventually create baggage?
Webflow now needs to accommodate AI agents, enterprise governance, marketers, designers, developers, campaigns, optimisation, AEO and potentially completely different development workflows.
You can start to see why Source exists as a separate product rather than simply adding everything into the Designer.
But it creates another question.
Source genuinely looks interesting.
It also looks like a credible response to the growing category of AI-first and "vibe coding" tools.
Webflow says Source will use code as its foundation and allow agents to make larger changes without being constrained by an abstraction layer. It can also work alongside existing Webflow websites rather than requiring companies to rebuild their entire stack.
That sounds sensible.
But it naturally makes me wonder:
What does the traditional Webflow product become if Source succeeds?
Is the Designer still at the centre of Webflow's long-term vision?
Is Source simply another layer around it?
Do the two eventually merge?
Or does the visual Designer increasingly become the traditional way designers and developers use Webflow while Source becomes the growth product aimed at enterprise marketing teams?
I don't think Webflow has clearly answered that yet.
And perhaps it can't. Source is still only in research preview.
But that ambiguity matters.
There is another contradiction underneath all of this.
The people who originally championed Webflow were largely designers, developers, agencies and technically minded people.
They didn't just use Webflow.
They often genuinely cared about the product.
They taught other people how to use it, built businesses around it, created templates, produced tutorials and convinced their companies and clients to adopt it.
But Webflow increasingly wants to sell to enterprise marketers.
And marketers generally shouldn't care deeply about which tool powers their website.
They care about outcomes.
If another platform solves those problems materially better three years from now, most marketing teams will switch.
I don't blame them. That is exactly how a business should evaluate software.
But it creates an unusual dynamic.
The people most emotionally invested in your product aren't necessarily the buyers who can fund your next stage of growth.
That tension probably explains some of the reaction to Webflow Conf.
I don't think that's a fair conclusion.
Webflow dedicated part of this year's conference specifically to improvements for designers, developers and content creators using the existing platform.
And I don't think every new Webflow product needs to directly benefit agencies or developers.
Companies evolve.
Their markets evolve.
The way websites get built is clearly changing.
I also run an agency today, rather than looking at Webflow purely as an enthusiastic developer like I might have years ago. My own perspective has changed.
So I'm not arguing that Webflow should simply go backwards.
The issue is more subtle.
It used to be easy to explain what Webflow was trying to achieve.
Today, I'm less sure.
This is another interesting consequence of where Webflow and the wider market are heading.
I don't necessarily think AI makes good agencies less valuable.
It might actually make the difference between agencies much more obvious.
Execution is getting cheaper.
First drafts, landing pages, code, content production, research and design exploration can all happen dramatically faster than they could a few years ago.
Webflow itself described this shift at Conf, with one session explicitly arguing that execution is becoming cheaper while expertise, intuition and judgement remain differentiators.
There is a major difference between an agency that uses AI to improve its thinking and an agency that outsources its thinking to AI.
As technical execution becomes commoditised, the differentiators become things like:
AI will probably consume parts of the lower end of the website market.
But that isn't entirely new.
Wix, Squarespace, templates, freelancers and no-code platforms have been lowering the cost of building websites for years.
AI simply accelerates it.
If someone can successfully build the website they need themselves, they probably should.
I wouldn't go that far.
I don't know what targets Webflow is working towards internally.
I don't know the pressures its leadership team faces, its long-term commercial strategy or what the full Source roadmap looks like.
And many of the things announced at Webflow Conf 2026 make strategic sense.
But as someone who has used Webflow for around six years and built a business around the ecosystem, something does feel different.
A few years ago, I think most active Webflow users could have explained what Webflow was building towards.
Today, the answer feels less obvious.
Maybe that is inevitable as companies mature.
Maybe Webflow is simply between two eras.
Maybe Source eventually becomes the thing that ties the whole strategy together.
Or maybe this is just the AI hype cycle that almost every software company is currently navigating.
I genuinely don't know.
But I suspect a lot of the scepticism around Webflow Conf 2026 isn't really about individual features.
It's about people trying to understand what Webflow wants to become next.
And right now, that vision feels less clear than it once did.
Yes, particularly for marketing-led websites that need strong CMS capabilities, fast publishing workflows, design flexibility and less dependency on engineering teams.
For enterprise teams, the bigger considerations are usually governance, integrations, localisation, permissions, scalability and how the website fits into the wider marketing stack.
Webflow has been investing heavily in those areas, which is one reason it is increasingly being considered for larger and more complex websites.
It depends on what the team is trying to achieve.
Webflow is still a strong option for marketing websites where teams want visual control, CMS flexibility and the ability to move quickly without relying heavily on developers.
Source appears to be aimed at a broader workflow where marketers, developers and AI agents can work across an existing codebase and marketing stack.
A custom-coded website can still make sense when the website behaves more like a software product, requires highly bespoke functionality or has technical requirements that sit outside a typical marketing website.
For most growing B2B companies, the decision should be based on the operating model of the marketing team rather than simply which platform has the most features.
Almost certainly.
AI should make repetitive tasks, content production, page creation and certain website changes much easier for non-technical teams.
But that does not remove the need for good website architecture.
The easier it becomes to create pages and content, the more important it becomes to have strong components, CMS structures, design systems and governance in place.
Otherwise, teams simply create inconsistency faster.
For a simple brochure website, an internal team may be able to build and manage Webflow themselves.
An agency becomes more valuable when the project involves:
At that point, the value is less about knowing how to use Webflow and more about knowing how to structure, design and deliver the website properly.
In my view, yes.
The important distinction is between Webflow as a company and Webflow as a product.
The product itself remains very strong for marketing websites, particularly for B2B companies that want their marketing team to move quickly without sacrificing design quality or technical flexibility.
The uncertainty around Webflow's longer-term direction does not suddenly make the existing platform less capable.
If anything, its increasing focus on enterprise, marketers and AI suggests Webflow intends to become more deeply embedded in how larger marketing teams operate.
The question is less whether Webflow is still viable, and more how its existing platform and new products like Source eventually fit together.
Learn why Webflow’s built-in security, speed and design freedom can take your marketing site to the next level and what to watch out for so you don’t get stuck with a complex, hard-to-manage setup. This post gives you the real pros and cons, plus practical steps to make your migration a success.
.webp)