Webflow Development Agency
Created by @namkyu · Updated Sep 11, 2026
A Webflow development agency builds, redesigns, migrates, and maintains websites for clients using Webflow. Revenue usually comes from fixed website projects, redesigns, CMS migrations, custom development, and recurring maintenance.
Item | Practical summary |
|---|---|
Main revenue models | Website build fee, redesign fee, migration project, custom development, monthly maintenance |
Agency workspace cost | Webflow Freelancer starts at US$16/mo annually; Agency starts at US$35/mo annually |
Client site cost | Basic starts at US$15/mo annually; Premium starts at US$25/mo annually |
Common services | Marketing sites, CMS builds, migrations, redesigns, custom code, maintenance |
Partner program | Webflow Partner Program with Certified Partner pathway |
Partner commission | 10% for entry-level partners; up to 20% for Certified Partners |
Main advantage | Agencies can stage client sites before attaching a paid Site plan |
Main risk | Scope creep, client ownership disputes, third-party integrations, and maintenance can reduce margins |
The agency creates a Webflow site from scratch.
Typical deliverables include:
page design and build;
responsive layouts;
CMS structure;
forms;
animations;
SEO settings;
analytics integration;
launch support.
The quote should define the number of pages and CMS collections because these directly affect delivery time.
Existing websites can be rebuilt or redesigned in Webflow.
This may include:
visual redesign;
CMS restructuring;
component cleanup;
responsive fixes;
migration from another CMS;
redirect setup.
Migration work can include:
pages;
blog posts;
CMS items;
redirects;
metadata;
images;
structured content.
Migration should be scoped separately from visual design because large content libraries can create significant implementation work even when the page design is simple.
Recurring services can include:
landing pages;
new CMS templates;
design updates;
bug fixes;
SEO changes;
campaign pages;
analytics updates.
This provides recurring revenue after the initial project.
Webflow provides Workspace plans specifically for freelancers and agencies.
Requirement | Minimum option | Cost | Priority |
|---|---|---|---|
Webflow account | Starter Workspace | Free | Essential |
Freelancer workflow | Freelancer Workspace | US$16/mo billed annually | Recommended |
Agency workflow | Agency Workspace | US$35/mo billed annually | Upgrade |
Client production site | Paid Site plan | Paid by client | Required at launch |
The free Starter Workspace currently supports two staging sites.
The Freelancer plan supports up to 10 staging sites, while the Agency plan supports unlimited staging sites.
Workspace | Annual-billing price | Staging sites |
|---|---|---|
Starter | Free | 2 |
Freelancer | US$16/mo | 10 |
Agency | US$35/mo | Unlimited |
Freelancer adds:
client payments;
free guest access in client Workspaces;
full CMS access on staged sites;
shared libraries;
one free client seat per site.
Agency additionally provides:
three free client seats per site;
unlimited shared libraries;
site-level roles;
publishing permissions;
site password protection;
redirects.
A solo developer can therefore begin on the free tier and upgrade when client volume or collaboration requires it.
Current Webflow Site plan pricing for new purchases includes:
Plan | Annual-billing price | Typical use |
|---|---|---|
Starter | Free | Staging and experimentation |
Basic | US$15/mo | Simple site without CMS |
Premium | US$25/mo | CMS and content-heavy sites |
Webflow changed its Site plan lineup in May 2026, combining its previous CMS and Business plans into the Premium plan.
Existing Freelancer and Agency Workspace sites on older pricing may transition on a different schedule, so client quotes should use the pricing applicable to the specific account.
Webflow's client payments feature is available on Freelancer and Agency Workspace plans.
It allows the client to pay directly for:
Site plans;
bandwidth;
add-ons.
The agency can continue managing the site without paying those costs itself.
This avoids a common agency problem where the developer pays hosting or platform fees and then has to recover those costs from the client.
Webflow also supports transferring a paid site directly to the client's Workspace without downgrading the plan or creating downtime.
Webflow ownership depends on the Workspace where the site exists.
If a site is inside the agency's Workspace, the agency Workspace owns it by default.
If it is inside the client's Workspace, the client retains control while the agency works as a guest or collaborator.
Webflow explicitly recommends that clients and freelancers agree in advance on:
site ownership;
billing responsibility;
access;
transfer expectations.
This should be written into the project agreement.
Define the number of pages, CMS collections, integrations, and custom features.
Decide whether the site will initially live in the agency or client Workspace.
Build the site on a staging environment.
Configure components, CMS, forms, and responsive layouts.
Import or create the required content.
Configure SEO metadata, redirects, analytics, and integrations.
Test the site on desktop and mobile.
Obtain client approval.
Attach or transfer the paid Site plan.
Transfer ownership or retain agency management according to the agreement.
Offer maintenance separately if required.
Webflow operates a Partner Program for freelancers and agencies.
Entry-level partners can join the Foundations tier and earn 10% commission on Site plans and add-ons they sell.
Certified Partners can earn up to 20% commission and receive additional benefits including:
Certified Partner directory listing;
client matchmaking;
Partner Hub access;
priority support;
additional program resources.
Webflow currently requires applicants for Certified Partner status to:
maintain an active Freelancer or Agency Workspace plan;
pass a pre-qualification assessment;
build at least three new client sites in Webflow;
submit a portfolio containing three client sites built from scratch;
pass Webflow's portfolio review.
Certification is therefore not necessary to begin taking clients.
It becomes more relevant after the agency already has completed Webflow work.
A fixed-price Webflow project should define:
page count;
CMS collections;
CMS item migration;
custom animations;
custom code;
integrations;
copywriting;
design responsibility;
number of revision rounds;
browser testing;
post-launch support.
“Build a Webflow site” can describe anything from a five-page marketing site to a large CMS migration.
Pricing both as the same type of project creates scope risk.
Webflow's Freelancer and Agency Workspace plans support custom code.
Code export is also available on paid Workspace plans, but Webflow states that dynamic CMS content and CMS-generated pages cannot be fully exported with the static code.
This matters when a client expects the finished Webflow site to be portable to another hosting environment.
Static export should not be represented as equivalent to exporting the entire Webflow CMS implementation.
A practical agency structure is:
Agency builds → client pays Site plan → client ultimately controls site or receives agreed ownership
The client payments feature allows the client to pay Webflow directly while the site remains in the agency Workspace during ongoing management.
If the client later wants full ownership, Webflow supports transferring the active site to the client's Workspace without downtime.
Suppose an agency charges US$5,000 for a Webflow project.
Direct delivery costs are:
designer: US$1,200;
developer or contractor: US$1,000;
project management: US$600;
project-specific software: US$100.
Total direct delivery cost:
US$2,900
Gross project contribution before general overhead:
US$5,000 − US$2,900 = US$2,100
This is a calculated illustration, not an observed Webflow agency benchmark.
Project profitability depends more on delivery time and scope control than on invoice size alone.
Project revenue − direct project delivery costs
Project revenue ÷ total delivery hours
This can reveal projects that look valuable by invoice size but consume too much labor.
Actual project hours − estimated project hours
Repeated overruns usually indicate weak estimates or poorly defined deliverables.
Maintenance agreements can reduce dependence on continuously winning new build projects.
Site ownership must be agreed in advance. By default, the Workspace containing the site owns it.
Scope creep can eliminate fixed-price margins. Page count, CMS work, integrations, and revisions should be defined before work begins.
Client platform costs are separate from agency revenue. Site plans and add-ons should normally be paid directly by the client.
Static code export has limits. Webflow CMS functionality does not transfer completely through a normal code export.
Certification is not a starting requirement. The Certified Partner pathway is designed for agencies that already have completed client work.
Yes.
Webflow's free Starter Workspace can be used for initial staging work.
The Freelancer plan is currently US$16/mo billed annually, and Agency is US$35/mo billed annually.
No.
On Freelancer and Agency Workspace plans, Webflow's client payments feature allows the client to pay Site plans and add-ons directly.
By default, the Workspace containing the site owns it.
If the site is built inside the agency Workspace, ownership and eventual transfer should be defined in the contract.
If it is built in the client's Workspace, the client retains control.
Current requirements include an active Freelancer or Agency Workspace, a pre-qualification assessment, at least three new Webflow client sites, and a portfolio review.
Webflow currently states that Partner Program members can earn 10–20% commission on Site plans and add-ons they sell.
Entry-level Partners begin at 10%, while Certified Partners can receive higher rates.
Linked Pages
No published pages are linked from this document.
Backlinks
No published pages link to this document yet.