Webflow’s Source Pivot: What Agencies Should Do With Client Sites

Webflow announced Source by Webflow at its first Builder Keynote, described in the company’s own keynote post as “a new platform for marketing teams and their agents to launch, optimize, and scale the web.” If you run client sites on Webflow, the question isn’t whether Webflow Source is interesting. It’s whether anything you bill for changes.

Short answer: not yet, and probably not for most of your builds. Here’s the longer one.

What Source actually is, and what it isn’t

Source is aimed at marketing teams and the AI agents working alongside them. The framing in Webflow’s Builder Keynote post is about launching, optimizing and scaling — the ongoing work after a site exists, not the construction of it.

That’s a different buyer from the one your agency serves. You’re hired to design and build. Source is pitched at the team that then runs the thing.

The Designer canvas isn’t going anywhere in this announcement. The keynote spends most of its length on quality-of-life work inside the existing product, not on a replacement for it.

The 151 improvements matter more than the headline

Webflow says it has shipped 151 individual improvements since Webflow Conf 2025, and that almost all came from user feedback. That number is the part worth reading closely, because it’s where your day-to-day build time actually moves.

The keynote calls out on-canvas spacing, a dedicated canvas for components, and pan and zoom. Component visibility controls and slot restrictions are also on the list.

None of that is glamorous. All of it is the kind of thing that quietly removes an hour from a build.

AI code components now get a visual edit pass

The more consequential change: AI code components can now be edited visually. Previously, if the Assistant generated a code component, the only way to change it was through prompts.

Now you can click into the component, select an element, and adjust it in the Style panel. You can edit text directly on the canvas. Or you can drop the piece you want changed into the Assistant as context so its next pass is scoped to that one thing.

Webflow’s example is an interactive ROI calculator for a product comparison page — the sort of thing that used to become a dev ticket. Visual editing for AI code components is available to all customers as of the announcement.

For an agency, that’s the real story here. It changes who on the team can ship a custom component, and it changes whether that work needs a developer at all.

Components inside the CMS

Webflow is also rolling out components in the CMS. CTA buttons, testimonial cards and pricing tables can now be dropped into rich text, on the canvas or in a CMS item, and configured per item through props.

Before this, that needed custom code or a third-party workaround. The keynote explicitly frames the benefit around client handoffs — which is your problem, not the marketing team’s.

What the pricing page tells you about cost

Webflow’s pricing page lists plans per site, in USD, plus applicable taxes at checkout, with yearly billing saving up to 40%. The free tier covers 2 static pages, 1 GB of bandwidth and 50 form submissions. The paid site plans step up through 300 static pages and 10 GB of bandwidth at the entry paid level.

Two details on that page are worth flagging to a client before you scope anything:

• Bandwidth overages trigger an automatic plan upgrade after two consecutive months over the limit.
• Several AI features require a paid Workspace plan even on a Starter site — including the SEO/AEO audit tool and the AI text generation.

That second point is the one that catches people. A client on a Starter site who wants the AI content tools is buying a Workspace plan, not a site plan.

Source vs the Designer workflow

If you’re weighing Webflow against other build options for a client, the same logic applies as with any Webflow project: the platform choice is downstream of who maintains the site after launch.

What an agency should actually do this month

Don’t migrate a client site because of a keynote. Nothing in the announcement says existing sites need to move, and the improvements described land inside the product you already use.

Do three things instead:

• Audit which clients are on Starter. If any of them have asked for AI content or SEO tooling, they need a Workspace plan, and that’s a conversation to have before the next invoice.
• Re-scope one custom component build. Pick a project where a dev ticket was raised for something like a calculator or an interactive table, and test whether the visual editing path gets you there faster.
• Check bandwidth headroom on your heaviest client site. Two consecutive overage months means an automatic upgrade, and that’s a cost the client didn’t approve.

The honest caveat

Source is new, and the keynote is a launch document, not a case study. There’s no published evidence yet about how Source performs on a real client site, what it costs at scale, or how it interacts with an agency’s existing handoff process.

Treat the platform as something to watch, not something to sell. The 151 improvements and the visual editing for AI code components are the parts you can use today. Source is the part you read about.

For a freelancer or a small studio, that split is actually good news. The work that changes your week is already shipped. The work that might change your business model hasn’t been proven yet.

Sources

• Webflow Builder Keynote 2026 — Source announcement, 151 improvements, AI code component visual editing, components in CMS.
• Webflow Pricing — plan structure, bandwidth limits, Workspace gating for AI features.
• CMSWire: Webflow Launches Source Agentic Workspace for Marketers — independent coverage of the Source launch.