TL;DR

  • Webflow is still growing fast in absolute revenue, from roughly 66 million dollars in 2020 to about 213 million dollars in 2024 in compiled stats from TapTwice's Webflow numbers. AI is not showing up as a collapse in the top line.
  • At the same time, AI website builders already account for about 23.6 percent of global website builder spend according to Custom Market Insights' AI website builder report. Webflow is only a small part of that AI pool.
  • AI first site builders like Durable and Hostinger AI, plus AI assisted code stacks with GitHub Copilot and ChatGPT, now capture millions of new sites and projects every year. Webflow gets hundreds of thousands. The real effect is share and growth compression, not immediate decline.
  • For designers, AI forward Framer has tripled its user base and now powers about 0.3 percent of all CMS sites according to W3Techs' Framer stats. That is a non trivial share of new visual builder projects that used to be Webflow's near monopoly.
  • Looking out to 2030, our modeled scenarios suggest the no code plus AI web creation market roughly quadruples in size, in line with forecasts that AI website builder revenue grows from 2.87 billion dollars in 2025 to about 14.78 billion dollars by 2035 in Custom Market Insights' forecast and similar growth from DataIntelo's AI builder study. Whether Webflow wins or just rides along depends on how AI native it becomes.

At Sushidata we care about what the numbers actually say, not the hot takes. So let us walk through what is happening to Webflow under real world AI pressure.

Webflow Is Growing. That Is The Starting Point.

If you only looked at Webflow's revenue, you might wonder why anyone is worried.

Compiled data from TapTwice shows Webflow around 66 million dollars of revenue in 2020, 100 million in 2022, then roughly 213 million in 2024 in their Webflow stats table. Webflow itself said it had reached a 100 million dollar ARR business serving 200,000 customers in its 2022 Series C announcement in the Webflow press release.

On the usage side, W3Techs reports Webflow now powers about 0.9 percent of all websites and 1.2 percent of all sites that use a known CMS in their Webflow usage overview, up from around 0.4 percent a few years ago in Tooltester and Enricher coverage of Webflow's market share.

So Webflow is bigger, and its share of the web is higher. Where is the problem?

The problem is that while Webflow has been growing, the AI driven part of the market that it lives in is growing faster.

AI Builders Went From Sideshow To A Quarter Of The Market

A few years ago, AI website builders were mostly demos. That is no longer the case.

Custom Market Insights estimates that AI powered website builders rose from about 11 percent of the website builder market in 2022 to 23.6 percent in 2024 in their AI powered website builder report. Market.us and DataIntelo both put the AI builder market in the low billions of dollars already, with Market.us calling out 3.17 billion dollars in 2023 in its AI website builder market report.

Meanwhile, individual AI native tools are producing volume on a scale that Webflow simply does not match in the SMB segment.

Compare that with Webflow. BuiltWith based analyses cited by Popupsmart suggest Webflow sites increased from about 544,000 to 822,000 sites over roughly two years in their Webflow statistics article, which works out to around 140,000 net new Webflow sites per year.

On a pure site count basis, it is not a fair fight. AI native builders are creating millions of new sites each year. Webflow is creating hundreds of thousands.

The important bit is that the AI builders mostly attack the cheapest, fastest jobs to be done. Local plumbers. First time solopreneurs. People who just want a presence that looks good enough and are happy to sacrifice control.

SMBs Are Already Comfortable With AI Web Creation

SEO Sandwitch compiles several SMB surveys and finds that by 2024, 68 percent of small businesses globally say they use AI assisted tools for web creation and 25 percent of first time website creators used an AI powered tool in 2023, as reported in their AI builder statistics.

When those same small business owners compare pricing, the pattern is even clearer:

  • Webflow's Basic site plan is 14 dollars per month on annual billing and CMS is 23 dollars per month on the Webflow pricing page.
  • Durable is around 15 dollars per month, sometimes less on annual plans, as summarized in TechCrunch and Neo's Durable product review.
  • 10Web's AI Builder sits at roughly 10 to 15 dollars per month including hosting, according to the 10Web pricing table.

In emerging markets, the gap gets wider. Hostinger's AI Website Builder in India is 149 to 249 rupees per month on the Hostinger India AI builder page, which is roughly one quarter to one eighth of Webflow's entry price. Neo offers an AI website builder with a custom domain for free to small businesses on its Neo AI website builder page.

No wonder third party guides now say Webflow is great for designers and agencies, while steering small businesses toward Durable, Hostinger AI, or other AI first tools.

Playcode's roundup calls Webflow powerful but complex, and says Durable is best for local businesses that want a basic site in seconds in their best AI website builders overview. NxCode similarly positions Webflow as a professional and enterprise tool, and Hostinger AI or 10Web as better fits for small firms in their AI website builder comparison.

For Webflow, this is a classic share compression story. The company still grows, but it captures a smaller slice of the fastest growing low end.

Developers Have Copilot Now, And That Changes Their Math

The other end of the spectrum is developers. Historically, Webflow's pitch to a developer or technical founder was simple: use a visual canvas to build marketing sites faster than writing front end code by hand.

AI has narrowed that advantage.

The 2023 Stack Overflow survey reports that about 70 percent of developers use or plan to use AI tools in their workflow as shown in their section on AI tools in the development process. Among AI tool users, 54.8 percent regularly use GitHub Copilot according to their breakdown of AI developer tool usage.

On top of that, GitHub's own research found that 92 percent of developers at large US companies are using AI coding tools in some way in their developer experience survey.

If you are shipping marketing sites or documentation in React or Next.js, the combo of Copilot, ChatGPT or Claude, and frameworks like Next.js hosted on Vercel or Netlify is now a very efficient path.

  • Stack Overflow shows 17.3 percent of professional developers report using Next.js in the past year in its web frameworks section.
  • 10.3 percent use Vercel and 8.5 percent use Netlify as cloud platforms in the same survey's cloud platforms table.
  • Vercel's v0 generates React UI from text prompts in seconds via the v0 app.
  • Netlify markets AI Gateway and AI Functions as first class features for AI powered apps in its developer docs.

Taken together, these tools make it quite realistic to say to a developer: "Just build the site in code using AI as your pair programmer." That is exactly what at least some advanced Webflow users are now doing.

Kyle Frost wrote a piece titled "I Moved My Websites Off of Webflow (thanks to Claude)" where he explains how Claude and modern web stacks like Astro and Next.js tipped the cost benefit balance away from Webflow for his three sites in his blog post. Field Office, a digital studio, published "Why We Moved from Webflow to Next.js and Builder.io", citing the desire for full AI capabilities and more control as key reasons in their migration write up.

If enough small teams make that jump, Webflow loses a chunk of its more advanced and higher spending user base, even while the broader market keeps growing.

Designers Are No Longer A Captive Audience Either

For years Webflow basically had a monopoly on serious designer friendly visual web builders. Figma for design. Webflow for production. That was the pattern.

Framer changed that, and it did so while leading with AI features.

W3Techs reports that Framer is now used by 0.3 percent of all CMS sites and 0.2 percent of all websites, and explicitly notes that its user base more than tripled in the last year in their Framer technology stats.

BuiltWith shows more than 250,000 live Framer Sites and over 350,000 including historical usage in their Framer Sites profile.

Those numbers are still smaller than Webflow's installed base, but the growth rate matters. W3Techs and Enricher have Webflow moving from about 0.9 percent to 1.2 percent of CMS sites over several years in their combined Webflow market share writeups. Framer added roughly 0.2 percentage points in a much shorter window.

On a regional view, BuiltWith estimates around 163,936 Webflow sites in Europe in its Webflow Europe list and about 30,103 Framer sites in Europe in its Framer Sites Europe list. That means Framer has already reached roughly 18 percent of Webflow's European installed base, despite being newer and more narrowly focused.

This shows up in the agency ecosystem too. Agencies that built their whole brand on Webflow are now "Webflow and Framer" shops.

Content from designers backs this up. Joshua Mosquera wrote "From Webflow to Framer: Why I Made the Switch" and highlights Framer's tighter Figma like workflow and speed in his Medium post. Bryn Taylor notes that his feed is full of people explaining why they moved from Webflow to Framer in his Framer thoughts article.

Framer has not killed Webflow. What it has done is claim a very real chunk of net new visual builder projects that used to belong to Webflow almost by default. That is another form of share compression.

Everyone's First Draft Now Starts In Chat

There is one more subtle shift that is easy to miss if you only look at platform revenue and market share charts.

A lot of people no longer start in a web builder at all. They start in ChatGPT or Claude.

Major registrars and hosts encourage this. Network Solutions has a guide titled "How To Build a Website with ChatGPT" that literally walks beginners and small business owners through prompting ChatGPT to generate a site outline, content, and HTML before they ever touch a traditional builder in their blog guide. Bluehost has a similar piece about using ChatGPT to build a WordPress site in its ChatGPT website tutorial. ThemeIsle shows how to have ChatGPT generate a full one page HTML and CSS site in their step by step tutorial.

If your first draft is written by an LLM and deployed as static HTML or into a WordPress or Next.js template, Webflow never even enters the evaluation set.

Combine that with data points that APAC and emerging markets now represent a large chunk of ChatGPT traffic and that 20 percent of European SMEs say they are fully embracing AI and innovative technologies in Webnode's survey of 8,200 European companies in their digital maturity report, and you get a picture where AI based flows quietly re route thousands of projects per month away from classic builders.

So What Does All Of This Actually Mean For Webflow?

If we zoom out, a few patterns emerge.

  1. The top line is still going up. Webflow moves from about 66 million dollars of revenue in 2020 to 213 million by 2024 in TapTwice's Webflow stats. There is no evidence yet that AI has caused its revenue to shrink in absolute terms.
  2. AI has made the market bigger. AI website builder revenue itself is already in the low billions of dollars annually and is forecast to grow to 14.78 billion dollars by 2035 in Custom Market Insights' market forecast, with DataIntelo describing similar growth paths in its AI builder market report. No code plus AI web creation looks more like a 10 to 12 billion dollar annual TAM by 2030 than a 3 billion dollar niche.
  3. Webflow's share of new projects is being squeezed. AI native builders dominate cheap, fast SMB sites. Framer and AI assisted code are winning a meaningful fraction of designer and developer projects. LLM first workflows capture many first drafts.
  4. Some of Webflow's best customers are churning for AI reasons. The Kyle Frost and Field Office stories are not isolated. Community threads about moving off Webflow mention AI powered code and flexibility as reasons, and Sacra's teardown notes Webflow has had high churn historically at around 60 percent in its Webflow report. Even if only a small part of that churn is now going straight into AI stacks, it matters.

At Sushidata we model this as growth plus share compression. Webflow can absolutely grow its revenue and user base through 2030, but in many plausible futures it does not keep up with the expansion of AI first web creation.

Three Futures For Webflow By 2030

Taking Webflow's historical trajectory and combining it with AI builder TAM forecasts, you can outline three broad scenarios for 2030.

These are simple scenario models, not forecasts, but they are useful for thinking.

  1. Optimistic scenario: AI native Webflow.
    Webflow succeeds in making AI a first class part of its product. The Webflow AI assistant and site builder, introduced in 2024 and covered by Envizn in a Webflow AI guide, evolve into a true copilot for designers and marketers. Webflow plugs deeply into LLMs, code exports, and headless architectures. Agencies standardize on an AI native Webflow as their front end of choice. In this world Webflow might reach roughly 600 to 650 million dollars in revenue or GMV by 2030 and capture something like 6 percent of the no code plus AI TAM, consistent with the upper line in our modeled chart that is grounded in CMI and DataIntelo's AI builder forecasts.
  2. Base scenario: Committed but not dominant.
    Webflow ships solid AI features, keeps pace with competitors, but does not fundamentally reshape the category. AI expands the market, but AI first builders bundled with hosting and AI assisted code capture much of the raw volume. Webflow grows to around 400 to 450 million dollars by 2030, and its share of the expanded no code plus AI TAM stabilizes around 4 percent, roughly in line with the middle scenario line in our chart that builds on Custom Market Insights' TAM numbers.
  3. Pessimistic scenario: Premium niche.
    Webflow lags behind AI native tools, prices itself into the upper mid market, and becomes a premium niche. It still grows, but slower than the category. Revenue creeps to around 300 million dollars by 2030 while global no code plus AI TAM races ahead to double digit billions. Webflow's effective share drifts toward 2 percent. It becomes a strong but relatively small brand inside a much larger ecosystem dominated by hoster bundles, AI first tools, and code plus AI workflows.

You can argue with the exact numbers. The important point is the shape: AI is enlarging the pie much faster than Webflow is currently growing. If Webflow's AI strategy hits, it can ride that expansion. If it merely follows, it will still grow but leave a lot of upside to others.

If You Were On Webflow's Product Team, Where Would You Over Invest?

This is the practical question for anyone building in this space, not just at Webflow.

A few product bets stand out when you look at the data through an AI lens.

1. Treat AI As The Primary Workflow, Not An Add On

Most of the AI that users touch today sits outside Webflow: ChatGPT, Claude, GitHub Copilot, v0. Yet the usage data shows AI assisted workflows will likely be the majority of new projects well before 2030, given that 70 percent of developers already use or plan to use AI tools according to the Stack Overflow 2023 survey and that AI builders already generate millions of SMB sites per year in the SEO Sandwitch stats.

Webflow should not just bolt an assistant onto its existing canvas. It should redesign the canvas around co creation with AI. Things like:

  • Prompt to layout flows that feel as fast as Framer AI's "skip the blank canvas" experience highlighted on the Framer AI page.
  • Native support for iterating on copy, imagery, and microcopy across a site in one place, not per element.
  • AI powered refactors that restructure content models or CMS collections based on plain language instructions.

2. Make Webflow A First Class Target For LLM Output

Today, when someone asks ChatGPT to "build me a website," the answer is usually raw HTML, a WordPress template, or some React code that ends up on Vercel or Netlify. You can see that pattern in guides from Network Solutions and Bluehost that walk users straight from ChatGPT to code in their ChatGPT website articles and WordPress plus ChatGPT guide.

Webflow should aim to be a target, not a bystander. That means:

  • Documented JSON or schema formats that LLMs can target to describe pages, CMS collections, and components.
  • Official plugins or actions for major LLM platforms that say "send this site to Webflow" as clean structured data.
  • Deep integrations with hosts and registrars that already teach "build with ChatGPT," so the last step is "click to open in Webflow" instead of "paste into cPanel."

3. Fix Pricing And Complexity For The AI Era

AI is compressing project time, which also compresses agency and freelancer billable hours. Agencies like Coherent say that Webflow AI and external tools already handle copy, images, and metadata for CMS collections, saving hours per project and cutting routine tasks significantly in their write up on the state of Webflow AI.

At the same time Webflow has raised prices and introduced more complex seat based models, which triggered loud community threads on the Webflow forum pricing discussions and coverage on sites like AlternativeTo's pricing change news.

If AI makes projects faster and cheaper to deliver, Webflow's pricing and packaging needs to match that reality instead of fighting it. Options include:

  • More straightforward site based plans for agencies that reflect AI compressed workloads.
  • Emerging market pricing that can compete with Hostinger AI and local builders such as Neo and Webji, which heavily undercut Webflow as shown on Hostinger's AI builder pricing and Neo's AI website builder page.
  • Clear AI usage included in plans, not hidden behind separate and confusing quotas.

4. Build A Best In Class AI Story For Agencies

Agencies and freelancers are the power users who influence tool choice for many clients. Right now they are hedging. Many "Webflow agencies" are now "Webflow and Framer agencies" or "Webflow and headless and Builder.io" studios, as their own sites plainly say on Flow Samurai and Field Office.

Webflow can win this group if it offers:

  • The most efficient AI enhanced workflow from Figma or FigJam into a live site.
  • Agency specific AI features like bulk content generation, migration helpers, and client friendly AI content editing inside the CMS.
  • Education and credentials that help agencies sell "AI powered Webflow" to clients in a credible way, similar to what Flowsultants is doing with its "Future proof your Webflow agency with AI" course described on the Flowsultants AI program page.

Closing Thought

AI is not a simple "kill or be killed" shock to Webflow. The data suggests something more nuanced. AI has expanded the no code web creation market into a multi billion dollar space and given birth to new competitors across the stack. In that environment, Webflow can keep growing in absolute terms and still lose relative share of new sites and future wallet share.

For Sushidata and for anyone building in this ecosystem, the right question is not "Will Webflow die?" It is: Which workflows will Webflow own in an AI first world, and which ones will it cede to AI native builders and AI assisted code?

The next few years of product and pricing decisions will answer that.

WebflowAINo-CodeWeb BuildersMarket AnalysisTAM