Webflow's November 16 Pricing Change: What Should Client Sites Do Now?

What changes for client sites on November 16, 2026?

Webflow's updated Site plan pricing reaches existing sites in Freelancer or Agency Workspaces, and sites on legacy pricing, at their next renewal or billable change on or after November 16, 2026. Owners who switch to yearly billing before then can lock in their current Site plan for another year.

This is the second wave of a change Webflow announced earlier this year. For most existing sites, the new pricing already applied from June 29, 2026. Sites managed inside a freelancer's or agency's Workspace got a later date. Webflow's own announcement says it gave this group more time because freelancers and agencies often manage sites on behalf of clients and need room for those conversations.

That extra time is now almost gone. If you build or host Webflow sites for clients, or if your site lives in someone else's Workspace, the next eleven days are the window to decide. Doing nothing is also a decision. It just happens to be the one where the renewal date makes the choice for you.

Why does this deadline matter more than the June one?

It matters more because the people affected are often not the people who pay. A client site in an agency Workspace may be billed to the agency, the client, or a card nobody remembers. When the price changes at renewal, the surprise lands on whoever owns the invoice, and the trust cost lands on the builder.

In June, most site owners got the change on their own account, with their own card on file. They saw the email and made their own call. The November group is different. These are sites where a freelancer set things up, a client uses the site every day, and the billing relationship sits somewhere in between.

I think of this as a go-to-market problem as much as a billing one. If you sell Webflow builds or retainers, your pricing to clients probably assumed a certain hosting cost. A change to that cost, even a small one, flows through to your margin or to an awkward conversation. Better to have that conversation now than at renewal.

What exactly is Webflow changing in the Site plans?

Webflow is combining the CMS and Business Site plans into one Premium Site plan, priced at $25 per month billed yearly or $39 per month billed monthly. Premium includes 20,000 CMS items and 40 CMS Collections, and Webflow says it removes the need for CMS item add-ons. Existing CMS and Business sites move to Premium automatically.

Those figures come from Webflow's own plans and pricing announcement in 2026. The same post says the Basic Site plan's yearly price rises to $15 per month and its monthly price to $25 per month, while the static page limit doubles from 150 to 300. Webflow also states that some customers will see a price increase, some a decrease, and some no change.

One detail is easy to miss. For existing Business plan customers, Webflow says included bandwidth drops from 100GB to 50GB, with bandwidth add-ons still available. If you run a client site with heavy traffic, video, or large downloads on the Business plan, check its bandwidth usage before the change rather than after an overage.

Webflow also introduced a Team plan for groups that have outgrown self-serve but are not ready for Enterprise. Per the announcement, it includes 100 CMS Collections, 10 seats, Localize, AEO agents, page branching, and single-page publishing, on an annual contract. Most small client sites will not need it, but a fast-growing client might.

Which client sites should you check first?

Check sites billed monthly first, because those are the ones Webflow says can still lock in current pricing by switching to yearly billing before the change applies. Then check Business plan sites with high bandwidth, and any site still on legacy pricing, since those carry the biggest chance of a surprise.

I would sort every site in the Workspace into three groups. The first is sites likely to pay more after the change. The second is sites likely to pay less or the same. The third is sites where you are not sure. Webflow published a pricing change calculator for exactly this, so run each uncertain site through it rather than guessing.

Then look at renewal dates. The change applies at the next renewal or billable change on or after November 16. A monthly site renews soon. A yearly site that renewed in the spring may not feel the change for months. That timing tells you which conversations are urgent and which can wait for a normal check-in.

Should clients switch to yearly billing before the deadline?

Switching to yearly billing makes sense when the site is stable, the client plans to keep it for at least a year, and the new price would be higher. It locks the current Site plan for another year. It makes less sense for a site that might be rebuilt, merged, or shut down soon.

This is a decision for the person paying, not for the builder. My job is to lay out the numbers and the trade-off clearly. Yearly billing means a larger payment now and less flexibility. Monthly billing means paying the new price sooner but keeping the option to change plans or leave.

For a client who is happy with the site and has no redesign planned, I would usually point toward yearly billing if the calculator shows an increase. For a client in the middle of a rebrand or a platform review, I would not push it. Locking in a plan for a site that will not exist in six months is not savings.

Who should own the Webflow billing for a client site?

In most cases the client should own the site's billing and the site itself. Shared billing hides cost changes like this one from the person who needs to see them. When the client owns the plan, a price change is a normal vendor update, not a surprise passed through by their builder.

I have made this argument before in my piece on why clients should own every account behind their site, and this deadline is a good test of it. If a client's site sits in your Workspace and you pay for it, ask whether that setup still serves them. Often it only exists because it was easiest on launch day.

Moving billing or ownership takes some care, so check Webflow's help documentation for the current transfer steps before you promise a client a timeline. The point is the direction. Over time, client sites should belong to clients, and your value should come from the work you do on them, not from holding the keys.

How should you tell a client about the price change?

Tell them plainly, early, and with numbers. Send one short message that says what Webflow is changing, when it reaches their site, what the calculator shows for their plan, and the one decision they need to make. Offer a recommendation, but make clear the choice and the invoice are theirs.

I would avoid forwarding Webflow's announcement without context. Most clients do not know what a Site plan is versus a Workspace plan, and they should not need to. Translate it into their terms: here is your site, here is what it costs today, here is what it may cost after renewal, and here is how to keep today's price for a year.

Keep a record of what you sent and what they decided. If you run a handover document for each client, this belongs in it. I wrote about that habit in why I write the handover doc before the build. A pricing decision made in November should still be easy to find next November.

What does this change mean for how freelancers price their work?

It is a reminder to separate platform costs from your own fees. If your retainer or build price quietly includes hosting, every vendor price change becomes your problem. Quoting your work and the client's platform costs as separate lines keeps your pricing honest and makes changes like this one easy to explain.

I price projects on a fixed fee, mostly between $1,000 and $10,000, and I keep the client's software bills out of that number. The client pays Webflow, HubSpot, Airtable, or Zapier directly. My fee covers the build and the systems behind it. When a vendor changes its pricing, my quote does not need to change.

The other lesson is about how platforms grow up. As Webflow adds AI credits to every Workspace, a Team plan, and features like AEO agents, its pricing will keep moving. Treat platform pricing as a line item you review every year, the same way you review the CRM bill. For the full background on the original announcement, see my breakdown of what the Webflow plans and pricing update changes.

What should you do next?

This week, list every client site in your Workspace, note its plan and billing cycle, and run the uncertain ones through Webflow's pricing change calculator. Contact the owners of monthly sites first. Give each one a clear recommendation and a deadline before November 16, then record what they chose.

After the deadline passes, use the moment to clean up ownership. Any site that still sits in your Workspace only because it was convenient at launch is worth a conversation about moving it to the client. That protects them from the next pricing surprise and protects you from being the messenger.

If you want a second pair of eyes on your client site list, or help planning the conversation with clients who will see a higher bill, reach out. Let's chat about it before the renewal dates arrive.