How to Understand Webflow Workspace Plans

Navigating Webflow’s pricing ecosystem can be notoriously complex, often causing confusion regarding the distinction between Workspace plans and Site plans. This video alleviates that friction by translating technical billing structures into an accessible narrative, utilizing a "Lego Store" metaphor where the Workspace is a building room and Site Plans are tickets required to publish creations. The content breaks down the entry-level "Starter Workspace," explaining how users can begin building for free with limited storage capacity ("shelves") for unhosted sites before needing to upgrade.

The analysis provides a granular look at team management, detailing the specific hierarchy of "Seats" available for collaboration. It distinguishes between free roles, such as Reviewers and Agency Guests—who must hold their own paid workspace—and paid roles like Designers that offer full administrative control. Furthermore, it clarifies the critical relationship between "shelving" projects and purchasing Site Plans; buying a Site Plan not only allows a project to go live ("take it home") but also frees up a slot in the workspace for new unhosted projects.

Ultimately, viewers will achieve a comprehensive understanding of how to scale their Webflow operations efficiently. By grasping the differences between Freelancer, Core, and Agency workspaces, users will learn how to unlock higher limits for unhosted sites and leverage specialized "Client Seats" for controlled external collaboration. This resource empowers freelancers and agencies to confidently select the correct billing architecture for their business model, moving beyond confusion to strategic implementation.

• The "Lego Store" Distinction: Webflow’s ecosystem functions like a Lego store where entry is free (the Workspace), but taking a creation home to show the world requires purchasing a specific ticket (the Site Plan).
• Workspace Capacity and "Shelves": The free Starter Workspace acts as a small room with a "shelf" that holds only two unhosted projects (staging domains); to build more without publishing, one must upgrade to plans with more shelves, such as the Core/Freelancer (10 slots) or Agency (unlimited slots) workspaces.
• Protocol for Agency Guests: You can invite up to two "Agency or Freelancer Guests" into your workspace for free to collaborate, but there is a strict prerequisite: these guests must already possess their own paid workspace to be eligible for entry.
• Tiered Seat Permissions: Collaboration is managed through specific "invitations" or seats: "Reviewers" can view and comment for free, "Content Editors" have limited modification rights, and paid "Designers/Admins" hold full power to build and manage the workspace.
• Client Access Logic: For users on Freelancer or Agency workspace plans, purchasing a Site Plan generates a special "Client Seat," allowing an external stakeholder (like a client) to edit that specific site within restricted parameters defined by the designer.

• 02:49 - Naming the Workspace Establishing the initial "small room" (Starter Workspace) where unhosted projects are stored.
• 03:15 - Managing Staging Limits Identifying the capacity limit of the Starter Workspace, which restricts the user to two unhosted "shelf" spots (staging domains).
• 03:27 - Configuring Guest Access Inviting "Agency or Freelancer Guests" to the workspace, which requires verifying that the guest already possesses their own paid workspace.
• 03:51 - Provisioning Workspace Seats Purchasing and assigning specific "invitations" (Seats) to team members to expand collaboration capabilities beyond the default limits.
• 04:58 - Defining Site Permissions Setting granular rules to determine exactly which users can modify specific elements (e.g., allowing a user to build a "car" but not a "castle").
• 05:20 - Activating a Site Plan Purchasing a "ticket" (Site Plan) to publish a specific project ("take it home") and enable custom hosting.
• 05:33 - Releasing Workspace Slots The action of adding a Site Plan to a project, which automatically frees up a "shelf" spot for a new unhosted creation.
• 05:54 - Upgrading Workspace Capacity Switching to Core/Freelancer plans to unlock 10 unhosted slots, or Growth/Agency plans for unlimited slots.
• 06:22 - Deploying Client Seats Utilizing the "Client Seat" feature available on Freelancer/Agency plans to grant restricted editing access to external stakeholders.

Webflow Workspace & Billing Configuration Guide

This technical tutorial explains how to navigate Webflow’s billing ecosystem, moving from the initial setup of a Workspace to managing complex team permissions and client access.

1. Initialize the Starter Workspace

Timestamp Reference: 02:42 – 02:57

• How: Upon entering Webflow (the "Lego Store"), the system automatically provisions a "Starter Workspace" (the "small room"). You can assign a custom name to this workspace via the dashboard settings.
• Why: This establishes the foundational environment where all your projects are stored. It allows you to begin building immediately without an upfront cost.

2. Manage Staging Domain Limits

Timestamp Reference: 03:07 – 03:17

• How: Monitor your unhosted project count. In the Starter Workspace, you are limited to two "shelf spots" (staging domains) at any given time.
• Why: Understanding this cap is crucial for workflow management. Once both spots are filled with unhosted sites, you cannot create a new project unless you delete an existing one, upgrade your workspace, or add a Site Plan to publish one.

3. Configure Agency and Freelancer Guest Access

Timestamp Reference: 03:27 – 03:42

• How: Navigate to the Members/Team settings and invite up to two external collaborators as "Agency or Freelancer Guests."‍
  
  • Constraint: Ensure the invitee already possesses their own paid Workspace account before sending the invite.

• Why: This allows you to scale your team temporarily for free. If the guest does not hold their own paid workspace, the system will block them from joining as a free guest, requiring you to purchase a seat instead.

4. Provision Workspace Seats

Timestamp Reference: 03:51 – 04:46

• How: If you need more than two guests or guests without paid accounts, purchase specific "Seats" (invitations). Choose from three tiers:

1. Reviewers (Free): Read-only access for commenting.
2. Content Editors (Limited): Can change content/marketing elements but cannot alter structure.
3. Designers/Admins (Full): Full access to build and manage the workspace.

• Why: This grants permanent, role-based access to team members, allowing you to control who can build versus who can only view or edit text.

5. Define Granular Site Permissions

Timestamp Reference: 04:58 – 05:07

• How: Access the permission settings for individual members. Configure rules that restrict specific users to specific actions or projects (e.g., allowing a user to modify "the car" but not "the castle").
• Why: This enforces security and structural integrity, ensuring that team members or clients only modify elements they are authorized to touch.

6. Activate Site Plans (Publishing)

Timestamp Reference: 05:20 – 05:49

• How: Purchase a "Site Plan" (a "ticket") for a specific project. This action allows you to publish the site to a custom domain.
• Why: Buying a Site Plan serves two functions:

1. It enables the site to go live ("take it home").
2. It automatically frees up a "shelf spot" in your workspace, allowing you to start a new unhosted project without hitting your limit.

7. Upgrade Workspace Capacity

Timestamp Reference: 05:54 – 06:08

• How: To increase the number of unhosted projects you can store simultaneously, upgrade your Workspace plan:‍
  
  • Core/Freelancer: Increases capacity to 10 unhosted sites.‍
  • Growth/Agency: Increases capacity to unlimited unhosted sites.

• Why: This is necessary for agencies or freelancers who need to draft multiple prototypes simultaneously before they are ready to be sold or published.

8. Deploy Client Seats

Timestamp Reference: 06:22 – 06:56

• How: If you are on a Freelancer or Agency workspace plan, use the "Client Seat" feature. Assign this seat to an external stakeholder for a project that has an active Site Plan.
• Why: This grants the client restricted access to the editor (e.g., to change text or images) without giving them full designer access that could break the site layout. Note that a new Site Plan is required for every distinct project you wish to share with a client in this manner.

A Webflow Workspace functions as your building environment—a "room" where you store and manage your unhosted projects—while a Site Plan acts as a specific "ticket" required to publish a single project to a custom domain. Essentially, the Workspace dictates your team size and drafting limits, whereas the Site Plan is purchased individually for every site you want to host live.

The free Starter Workspace allows you to store a maximum of two unhosted projects (staging domains) on your digital "shelf". However, purchasing a Site Plan for a project effectively moves it off this shelf, freeing up a spot for you to begin a new unhosted build.

You can invite up to two "Agency or Freelancer Guests" to collaborate in your workspace at no additional cost, provided these guests already possess their own active, paid Webflow workspace. If the external collaborator does not hold their own paid plan, they are ineligible for this specific free guest access and requires a paid seat.

When using a Freelancer or Agency Workspace, purchasing a Site Plan unlocks a specialized "Client Seat" that allows external stakeholders to access the editor for that specific site. This role is restricted based on your configuration, ensuring clients can only modify content or elements you have explicitly permitted via site permissions.