Turns out Webflow now requires clients to pay $39/month for a Designer seat just to give access to their freelancer - even when they have free guest slots available. This unexpected cost creates friction at the worst possible moment: right after project completion during client handoff. The absurdity? I’m already paying for a Freelancer workspace specifically designed for client work.
The Webflow pricing page has always been complex. As a platform serving both people building sites for themselves and those building for others, some complexity is unavoidable. But the recent addition of seat pricing has crossed a line from complex to contradictory - particularly for the freelancer-client relationship.
A Real-World Example of the Current Friction
Recently, I experienced firsthand how the new seat pricing impacts the client handoff process. A new client found me through the Webflow directory, having already created their free workspace and project. As per standard practice, I built their site in my Freelancer workspace, planning to transfer it to them upon completion. They knew they’d need the CMS plan for hosting, and I explained I’d transfer site ownership to their workspace - all standard procedure so far.
But here’s where things got messy. When the client tried to add me as a guest Designer (despite having 2 free guest slots), they discovered this now requires a full Designer seat at $39/month. This feels like a step backward from both the original Client Billing system and the previous guest access approach. What makes this particularly frustrating is that I’m already paying for a Freelancer workspace specifically designed for client work.
The Evolution of Client Billing
The original Client Billing was nice for freelancers - sites stayed in our workspace, billing was automated, and we could add maintenance fees. But it had one critical flaw: clients didn’t truly own their sites. If a freelancer vanished, the client was stuck. So Webflow sunset it - a completely valid decision.
In the community, many of us freelancers talk about the frustrations of clients accidentally breaking things in the Designer that we then get asked to fix. Sure, we could use Client Billing 2.0 (Client Payments) where the site stays in our workspace, but again, I don’t want this liability or to prevent true client ownership.
The Current Dilemma
The pendulum has now swung the other way. With the new pricing structure, we’re in an awkward spot where ensuring client ownership (good!) creates unnecessary friction and costs (bad!). This particularly stings given Webflow’s statement that “Freelancer and Agency guest access remains unchanged at this time.”
My client was understanding and paid for my Designer seat despite having free guest slots available. But this isn’t just about the cost - it’s about adding complexity to client relationships at exactly the wrong moment.
A Proposed Solution
Imagine if clients could “forgive” Designer access to specific freelancer/agency workspaces? Think of it like delegating access back to the professionals who built the site. The client maintains ownership while avoiding redundant seat costs, and we maintain the ability to support our clients efficiently. Just like we transfer sites from one workspace to another, we could assign roles to workspaces. This wouldn’t impact pricing plans because there would be no additional cost unless you wanted to add another Designer seat.
I understand Webflow is working on solutions - Client Payments (Client Billing 2.0), Seamless Transfers, and Project Fees were all announced at Webflow Conf 2024. Maybe we’re just in an awkward transition phase. But right now, this seat pricing structure is creating unnecessary friction in the client handoff process - the exact moment when we want things to be smoothest.
While I respect the move away from the original Client Billing to ensure client ownership, this current implementation needs refinement. The pricing page remains confusing, and the seat/roles system adds complexity exactly where we need simplicity - in the client handoff and ongoing support process.
Those of us building client sites on Webflow need a middle ground - one that preserves client ownership while maintaining the efficiency of the guest access system we’ve relied on. Until then, we’re stuck explaining to clients why they need to pay extra just to let us help them with their own site.
The Webflow ecosystem thrives because of freelancers and agencies who champion the platform. It’s time for the pricing structure to support, rather than complicate, these crucial relationships.