Webflow bills the Workspace and the site separately, and transferring billing to a client is a manual step agencies routinely miss. Here's what actually goes wrong.
Key takeaways
- A Webflow site is billed on two layers – its own site plan, and the Workspace plan that holds it – so an agency running several client sites pays for both.
- Transferring a site's billing to the client is a manual process, not a toggle; skipping it during offboarding leaves the agency paying for a site it no longer manages.
- Splitting code, hosting and CMS into separate layers (rather than one Webflow subscription) makes every client handoff easier to control.
Webflow's client-billing model looks simple until an agency actually has to hand a site over, add a second editor, or explain to a client why the invoice changed shape halfway through a project. None of it is hidden exactly – it is just spread across workspace plans, site plans and paid seats in a way that only becomes clear once you are the one paying for it.
Two separate bills, not one
A Webflow site needs a site plan (hosting, CMS limits, forms) and, if it is built inside an agency's Workspace, the Workspace itself carries its own plan with a cap on how many "full" seats it includes before extra members cost more. An agency managing a dozen client sites is paying twice: once per site, once for the Workspace that holds them all.
Transferring billing to the client
Webflow does support moving a site's billing to the client's own account, but it is a manual transfer, not a toggle – both sides need Webflow accounts, and until it happens the agency's card keeps getting charged for a site it no longer actively bills for. Miss that step during an offboarding and it is easy to end up quietly funding a former client's hosting.
The lost-access problem
The horror stories agencies actually tell are about access, not price: a client who cancels their own subscription without warning and takes the live site down with it; a single Workspace owner who leaves the agency and takes ownership of every client site along with them; a billing transfer that never happened, discovered only when a card expires. None of this is unique to Webflow, but a page-builder platform where the site, the CMS and the hosting are one inseparable subscription makes every one of these scenarios harder to untangle than it would be with a codebase and a separate host.
What separating the layers actually buys you
A static export or an Astro + CMS rebuild splits those concerns back apart: the code is a deliverable the client owns outright, hosting is a line item you control or hand off cleanly, and there is no Workspace seat sitting between the two. It will not fix a client relationship that is already going badly, but it removes the platform-shaped ways that a bad handoff turns into a lost site.
See the four ways to move a client site off Webflow, or talk to us about an agency handoff specifically.