Webflow Agency Plan vs Growth Plan: Which Workspace Tier Is Right for Your Studio

Choosing the wrong Webflow workspace tier costs studios real money — either through unnecessary Enterprise pricing or through operational friction that compounds across every client project. This guide breaks down the Growth plan versus the Agency (Enterprise) tier across the dimensions that matter most: seat access, client permissions, site limits, billing separation, and ROI.

---

Agency Plan vs Growth Plan: The Direct Answer

Growth plan is the right choice for most studios.[5] It supports up to 3 workspace seats[5][UNVERIFIED], unlimited unhosted sites[5], and client Editor access — covering the majority of agency workflows without Enterprise pricing.

The Agency tier in Webflow is not a standalone plan[3][5]. It sits within the Enterprise tier[5], which adds SSO, audit logs, advanced role customization, and dedicated support with an SLA[5]. Those features matter when clients have compliance requirements. They do not matter for a 4-person studio managing 15 branding sites[UNVERIFIED].

Here is the practical split:

• Growth ($49/seat/month):[5] Unlimited unhosted sites[5], named seats[5], client Editor invitations[5], site transfer to client workspaces[7], concurrent publishing across projects[5]
• Enterprise/Agency (custom pricing):[5] Everything in Growth plus SSO, audit logs, custom permission structures, dedicated support, and SLA guarantees[5]
• The deciding factor: If your clients require SOC 2 documentation or custom role structures, you need Enterprise[5]. If they need a content editor login and clean billing separation, Growth handles it[5][7].

For studios managing 10 or more client sites with rotating contractors and editors, Growth is the minimum viable tier[5]. Enterprise is warranted when client isolation and audit controls become contractually non-negotiable[5].

---

How Webflow Workspace Plans Are Structured

Webflow separates billing into two distinct layers, and conflating them is the most common source of pricing confusion. Site Plans cover per-site hosting costs[5][7]. Workspace Plans cover per-team collaboration costs[5][7]. Studios must evaluate both before comparing tiers.

Workspace tiers run from free to custom: Starter (free, 2 unhosted sites)[5], Core ($19/seat/month, up to 10 unhosted sites)[5], Growth ($49/seat/month, unlimited unhosted sites)[5], Agency ($35/seat/month)[5], and Enterprise (custom pricing)[5]. Each tier unlocks progressively more seats, sites, and collaboration controls[5].

The Starter and Core tiers are designed for freelancers and small teams running a handful of projects[5]. Growth is the first tier built for multi-client studio operations — it removes the site cap, enables client Editor invitations, and supports the contractor rotation workflows that agencies use[5]. The jump from Core to Growth is $30/seat/month[5]. At 3 seats, that is $90/month[UNVERIFIED]. Whether that delta is justified depends on your site count and team size[5].

---

Workspace Plan Comparison Table: Core vs Growth vs Enterprise

Feature	Core	Growth	Enterprise
Price	$19/seat/mo[5]	$49/seat/mo[5]	Custom[5]
Workspace seats	Up to 3[5][UNVERIFIED]	Up to 3[5][UNVERIFIED]	Unlimited[5][UNVERIFIED]
Unhosted sites	10 (hard cap)[5]	Unlimited[5]	Unlimited[5]
Client Editor invitations	Yes[5]	Yes[5]	Yes[5]
Site transfer to client	Yes[7]	Yes[7]	Yes[7]
SSO (single sign-on)	No[5]	No[5]	Yes[5][UNVERIFIED]
Audit logs	No[5]	No[5]	Yes[5][UNVERIFIED]
Advanced role customization	No[5]	No[5]	Yes[5]
Dedicated support + SLA	No[5]	No[5]	Yes[5]
Custom permission structures	No[5]	No[5]	Yes[5]

The Core plan’s 10-site cap is a hard limit that breaks multi-client workflows[5]. A studio managing 11 active projects on Core must either upgrade or fragment work across a second workspace account — both options carry real costs[5]. Growth removes that ceiling entirely[5]. Enterprise removes seat caps and adds the compliance and governance layer that Growth does not offer[5][UNVERIFIED]. Audit logs and SSO are not available on Growth; if those features appear in a client contract, Enterprise is the only viable path[5].

---

Seat-Based Access: How Growth Plan Eliminates Login Sharing

Growth plan assigns each team member a named seat with individual login credentials.[5] Each designer, contractor, or editor authenticates independently — no shared passwords, no ambiguous activity trails[5].

Named seats enable activity tracking: you can see who published what and when[5]. Access revocation is instant and complete[5]. When a contractor engagement ends, removing their seat cuts access across every site in the workspace simultaneously[5]. There is no manual site-by-site cleanup[5].

Studios on Core with 2 or more designers face a structural problem[5]. The 10-site cap and limited collaboration controls push teams toward login sharing in practice[5]. Shared credentials eliminate the ability to track changes, prevent selective access revocation, and create publishing conflicts when two people attempt simultaneous sessions[5]. Growth eliminates all three problems[5].

Key operational benefits of seat-based access on Growth:

• Individual authentication: Each team member logs in with their own credentials across all client projects[5]
• Instant revocation: Removing a seat cuts access to all workspace sites in a single action[5]
• Activity attribution: Publishing history and CMS edits are tied to named users, not a shared account[5]
• Concurrent sessions: Multiple designers work on different client sites simultaneously without session conflicts[5]

---

Managing Contractor Access Without Compromising Client Sites

Contractor access on Growth works through temporary seat assignment scoped to specific projects[5]. The workspace admin adds the contractor as a seat, assigns them to relevant sites, and removes the seat when the engagement ends[5].

The exact workflow:

1. Add the contractor as a workspace seat — they receive an email invitation and set up their own login credentials[5]
2. Assign them to specific sites — contractors only see the projects you explicitly grant access to, not your full client roster[5]
3. Set their role — Designer access for build work, Editor access for content-only contractors[5]
4. Remove the seat at engagement end — access revokes immediately across all assigned sites, no manual cleanup required[5]

Growth plan workspace admins can assign contractors as Editors on individual sites without granting workspace-level access to all client projects[5]. A contractor editing content for Client A never sees Client B’s site in their dashboard[5]. The isolation is enforced at the seat and role level, not through manual permission management[5].

---

Client Permissions: What Each Role Can and Cannot Do

Webflow offers three primary roles within a workspace: Admin, Designer, and Editor.[5] Each has distinct access boundaries that map directly to agency workflow needs[5].

The Editor role is built for clients[5]. It surfaces a simplified CMS interface — the Webflow Editor — that allows content updates, CMS item publishing, and form management[5]. Editors cannot access the Designer, cannot modify CSS or layout, and cannot touch site settings or billing[5]. This is the correct role for any client who needs to update blog posts, swap images, or manage a team directory without the risk of breaking the design[5].

Designers can build, publish, and modify all design elements[5]. They cannot access billing, cannot transfer site ownership, and cannot manage workspace members[5]. This is the correct role for contractors doing build work[5].

Admins control everything: billing, site transfer, workspace member management, and all design and publishing functions[5]. Limit Admin seats to principals and senior team leads[5].

Role	Design Access	CMS Publishing	Billing Access	Site Transfer	Workspace Management
Admin	Full[5]	Yes[5]	Yes[5]	Yes[5]	Yes[5]
Designer	Full[5]	Yes[5]	No[5]	No[5]	No[5]
Editor	None[5]	CMS only[5]	No[5]	No[5]	No[5]

---

Giving Clients Editor Access: Step-by-Step

Client Editor access is granted at the site level, not the workspace level[5]. Clients never see other client projects in your workspace — their view is scoped entirely to the site they have been invited to[5].

1. Navigate to the site’s Settings — open the specific client site from your workspace dashboard[5]
2. Go to the Editors tab — this is separate from workspace member management[5]
3. Enter the client’s email address — they receive an invitation link and create their own Webflow login[5]
4. Client accesses the Webflow Editor — a simplified interface showing only CMS collections, forms, and content fields; the Designer is not accessible[5]

Editor seats on client sites are billed separately from workspace seats[5]. Studios can pass this cost to clients as a line item or absorb it into their retainer pricing[5].

---

Client Handoff Mechanics: Transferring Sites and Separating Billing

Webflow supports full site transfer from an agency workspace to a client’s own Webflow workspace.[7] The client takes ownership of hosting billing[7]. The agency retains optional collaborator access[7]. The live site, domain, CMS content, and hosting plan transfer intact[7].

Billing separation is the primary operational reason to use site transfer[7]. Once a site moves to the client’s workspace, their credit card is charged for hosting[7]. The agency exits the billing relationship entirely[7]. This eliminates the dynamic of agencies fronting hosting costs and chasing reimbursement, and it removes the agency’s liability if a client’s site incurs overage charges[7].

Site transfer does not break live URLs[7]. The domain continues resolving[7]. CMS content remains intact[7]. The client will need to confirm or upgrade their hosting plan to maintain the site’s current tier after the transfer completes[7].

---

How to Transfer a Site to a Client Workspace

The receiving client needs a Webflow account to accept a transfer[7]. A free Starter account is sufficient — they do not need a paid workspace plan to receive ownership[7].

1. Open the site in your workspace and navigate to Site Settings > General[7]
2. Scroll to the Transfer Site section — enter the client’s Webflow account email address[7]
3. Client receives an email invitation to accept ownership — they must accept within the expiration window[7]
4. After transfer, request collaborator access — the agency can be re-invited to the client’s site as a Designer or Admin, maintaining retainer access without retaining billing responsibility[7]

After transfer, the agency’s ongoing access is managed through the client’s workspace, not the agency’s[7]. This is the correct structure for retainer relationships: the client owns the asset, the agency has working access[7].

---

Multi-Client Site Management: Growth Plan Capabilities

Growth plan removes the 10-site cap, allowing studios to manage unlimited unhosted sites within a single workspace.[5] For agencies with 10 or more active client projects, this is the feature that makes Growth non-negotiable[5].

All client sites appear in a single workspace dashboard[5]. Admins switch between projects, monitor CMS publishing queues, and manage team access without logging in and out of separate accounts[5]. The operational efficiency gain compounds as site count grows — at 20 client sites, a fragmented multi-account setup on Core creates significant admin overhead that Growth eliminates[5].

Unhosted sites — sites in active development that have not been connected to a paid hosting plan — do not count against any limit on Growth[5]. Studios can maintain staging environments, development branches, and pre-launch builds for every client simultaneously without additional cost[5]. On Core, each unhosted site counts toward the 10-site cap, which means development environments compete with live client sites for the same limited slots[5].

Key Growth plan capabilities for multi-client management:

• Unlimited unhosted sites: Development and staging environments for every client, no cap[5]
• Single workspace dashboard: All client projects visible and accessible from one login[5]
• Concurrent team access: Multiple designers working on different client sites simultaneously[5]
• Centralized member management: Add, remove, and reassign team members across all projects from one admin panel[5]
• Client Editor invitations: Invite clients to their specific site without exposing other workspace projects[5]

---

Publishing Workflow Speed: How Seat Access Reduces Bottlenecks

On Core with shared logins, only one person can publish at a time[5]. Simultaneous publishing attempts create session conflicts and overwrite risk — a real problem when two designers are working against the same client deadline[5].

Growth plan with named seats allows multiple designers to work on different client sites concurrently without conflicts[5]. Each session is authenticated independently, so Designer A publishing Client X’s site has no interaction with Designer B working on Client Y’s project[5].

Client editors on Growth can publish CMS content independently without waiting for a designer to log in[5]. For retainer clients who update blog posts or event listings regularly, this reduces content update turnaround from hours to minutes[5]. The client logs into the Webflow Editor, makes their changes, and publishes — no agency involvement required unless design changes are needed[5].

---

ROI Calculation: When Upgrading to Growth Pays for Itself

Growth plan costs $49/seat/month.[5] A 3-person studio pays $147/month versus $57/month on Core — a $90/month delta.[5][UNVERIFIED] That gap must be justified by workflow gains, client capacity, or both[5].

The site-count ceiling is the clearest forcing function[5]. A studio managing 11 active client sites on Core has hit a hard wall[5]. The options are: upgrade to Growth ($90/month more)[5][UNVERIFIED], open a second workspace account (duplicates admin overhead and fragments reporting), or drop a client site (not viable)[5]. In practice, the $90/month upgrade is the only rational choice once you are at 11 sites[5].

The break-even calculation on workflow friction: if Growth eliminates 2 hours per month of login-sharing friction per team member — session conflicts, manual access revocation, sequential publishing queues — at a $75/hour effective rate, the plan pays for itself at 3 seats with 0.6 hours saved per person per month[UNVERIFIED]. Most studios with shared logins lose more than that in a single week[UNVERIFIED].

Contractor rotation adds a fourth data point[5]. Every time a contractor engagement ends on a shared-login setup, someone manually audits which sites that contractor touched and changes passwords[5]. At 4 contractor rotations per year, that is a non-trivial time cost[UNVERIFIED]. Growth’s instant seat revocation eliminates it entirely[5].

---

Cost Scenarios for Studios at Different Scale Points

Scenario	Studio Size	Site Count	Recommended Plan	Monthly Cost
A	2 designers	8 client sites	Core	$38/mo[5][UNVERIFIED]
B	3 designers + 2 rotating contractors	12 client sites	Growth	$147/mo[5][UNVERIFIED]
C	5 designers	20+ client sites, client editors required	Growth	$245/mo[5][UNVERIFIED]
D	5+ designers	20+ sites, SSO or audit logs required	Enterprise	Custom[5]

Scenario A: Core at $38/month is sufficient[5][UNVERIFIED]. The 10-site cap is not a constraint, and 2 seats do not create login-sharing pressure[5]. Growth adds $52/month without unlocking features this studio needs[5][UNVERIFIED].

Scenario B: Growth at $147/month is the minimum viable tier[5][UNVERIFIED]. Core’s 10-site cap is a direct blocker at 12 sites[5]. Contractor rotation on named seats eliminates the access management overhead that shared logins create[5].

Scenario C: Growth at $245/month (5 seats) plus per-site Editor seat costs covers the full workflow[5][UNVERIFIED]. Enterprise is warranted only if a client contract specifically requires SSO or audit log access — most 20-site studios will not face that requirement[5].

---

When to Consider Enterprise (Agency) Tier Instead

Enterprise adds four capabilities that Growth does not offer: SSO, advanced role customization, dedicated support with SLA, and audit logs.[5] These features are not incremental improvements — they are categorically different capabilities that matter in specific client contexts[5].

The threshold is straightforward[5]. If your clients require SOC 2 documentation, custom permission structures beyond Admin/Designer/Editor, or guaranteed support response times written into a contract, Growth cannot satisfy those requirements[5]. No workaround exists on Growth for audit log access or SSO integration[5].

Enterprise pricing is custom and starts significantly above Growth[5]. Request a quote only after confirming that at least two Enterprise-exclusive features are genuinely required by your client base — not just preferable, but contractually or operationally necessary[5].

Indicators that Enterprise is warranted:

• Client compliance requirements: SOC 2, HIPAA-adjacent data handling, or audit trail documentation in the contract[5]
• SSO mandate: Client IT departments requiring identity provider integration for all vendor tools[5]
• Custom permission structures: Roles beyond Admin/Designer/Editor that do not map to Webflow’s standard three-tier model[5]
• SLA requirements: Clients requiring guaranteed support response times that Growth’s standard support cannot provide[5]
• Seat scale: Teams exceeding Growth’s seat limits who need centralized identity management[5][UNVERIFIED]

---

Decision Framework: Choosing the Right Workspace Tier

Four criteria determine the right tier: number of active client sites, number of concurrent workspace users, whether clients need Editor access, and whether billing separation is required.[5][7]

If any single one of the following conditions is true, Growth is your minimum viable tier:

1. More than 10 active client sites in your workspace[5]
2. Three or more team members needing concurrent workspace access[5][UNVERIFIED]
3. Clients requiring Editor invitations to manage their own content[5]
4. Contractor rotation requiring instant access revocation without manual cleanup[5]
5. Billing separation needed between agency hosting costs and client hosting costs[7]

The most common mistake is staying on Core past the 10-site threshold and managing overflow through a second workspace account[5]. This approach fragments your project dashboard, doubles admin overhead for member management, and — at 3 seats across two accounts — costs more than a single Growth workspace[5][UNVERIFIED]. Studios make this mistake because the Core-to-Growth price jump feels significant in isolation[5]. It rarely is when measured against the operational cost of the workaround[5].

If none of the five conditions above apply, Core is the correct choice[5]. If SSO, audit logs, or custom permissions appear in a client requirement, skip Growth and go directly to Enterprise[5]. Growth covers the vast majority of agency workflows between those two poles[5].

---

Frequently Asked Questions

Does a no-code website builder’s agency workspace tier let you manage multiple client sites with separate permissions per client?

Yes[5]. Growth plan supports unlimited unhosted sites within a single workspace, with permissions managed at both the workspace level (Admin, Designer) and the site level (Editor)[5]. Clients invited as Editors on their site cannot see other client projects in your workspace[5]. Workspace-level roles apply across all sites; site-level Editor invitations are scoped to individual projects[5]. This separation is enforced by the platform, not by manual configuration[5].

Can a growth workspace plan for a no-code web design studio support multiple editors and seat-based access without sharing logins?

Yes[5]. Growth plan assigns each team member a named seat with individual login credentials[5]. Each person authenticates independently[5]. Simultaneous sessions on different client sites do not conflict[5]. When a contractor engagement ends, removing their seat revokes access across all workspace sites instantly — no password changes, no manual site-by-site cleanup[5]. Core plan technically supports multiple seats but its 10-site cap and limited collaboration controls push teams toward login sharing in practice[5].

Do agency-level workspace plans in low-code web platforms include client handoff features like transferring a site to a client workspace and keeping billing separate?

Yes[7]. Webflow supports full site transfer from an agency workspace to a client’s own Webflow account via Site Settings > General > Transfer Site[7]. The domain, CMS content, and hosting plan transfer intact[7]. After transfer, the client’s credit card is charged for hosting — the agency exits the billing relationship entirely[7]. The agency can then be re-invited as a collaborator on the client’s site, maintaining retainer access without retaining billing responsibility[7]. This workflow is available on Growth and does not require Enterprise[7].

What should a no-code web studio evaluate when choosing between a growth plan and an agency-tier plan?

Evaluate four factors: seat count (Growth supports up to 3 workspace seats; Enterprise removes the cap)[5][UNVERIFIED], compliance requirements (audit logs and SOC 2 documentation are Enterprise-only)[5], SSO needs (Growth has no SSO integration)[5], and support SLA requirements (Growth uses standard support; Enterprise includes dedicated support with response time guarantees)[5]. For studios managing up to 25 client sites with standard Admin/Designer/Editor role structures, Growth covers the full workflow[5][UNVERIFIED]. Enterprise is warranted when client contracts include compliance, SSO, or SLA clauses[5].

How do you calculate ROI for upgrading a no-code agency workspace tier when managing 10 or more client sites?

The Core-to-Growth delta is $30/seat/month — $90/month at 3 seats[5][UNVERIFIED]. The break-even calculation has two components[5]. First, the site-count forcing function: if you are managing 11 or more sites, Core’s hard cap makes the upgrade mandatory regardless of ROI[5]. Second, workflow friction: at a $75/hour effective rate, Growth pays for itself if it eliminates 1.2 hours of combined monthly friction across a 3-person team[UNVERIFIED]. Login-sharing conflicts, manual access revocation, and sequential publishing queues typically account for more than that[5].

What is the best no-code website builder workspace plan for an agency managing multiple client sites, contractors, and frequent content updates?

Growth plan is the correct tier for this profile[5]. It provides unlimited unhosted sites for active project management[5], named seats for contractor rotation without security risk[5], client Editor invitations for independent content publishing[5], and site transfer for clean billing separation at project completion[7]. The only reason to move to Enterprise is if a client contract requires SSO, audit logs, custom permission structures, or a support SLA — requirements that most studios managing up to 25 client sites will not encounter[5][UNVERIFIED].

---

Key Takeaways

• Growth is the correct tier for studios managing 10 or more client sites, 3 or more team members, or any workflow requiring client Editor access and billing separation via site transfer[5][7]
• Seat-based access on Growth eliminates login sharing, enables contractor rotation with instant revocation, and allows concurrent publishing across client sites without session conflicts[5]
• Site transfer to client workspaces is fully supported on Growth — clients take over hosting billing while agencies retain optional collaborator access through re-invitation[7]
• The ROI threshold is low: studios with 3 seats and 11 or more sites recover the $90/month Core-to-Growth delta through eliminated workflow friction within the first month[5][UNVERIFIED]
• Enterprise is warranted only when SSO, audit logs, compliance documentation, or custom permission structures appear as contractual requirements — most studios managing up to 25 client sites will not need it[5][UNVERIFIED]
• The most expensive mistake is managing overflow past Core’s 10-site cap through a second workspace account — it costs more and fragments operations compared to a single Growth workspace[5]