How to Price Webflow Projects as an Agency (Margin Math)

TL;DR: Agency Webflow pricing holds up when the quote is built backwards from delivery cost and a target gross margin, not forward from an hourly rate. Scope the build in pages and components, cost every internal hour including project management and QA, keep Webflow subscription fees as a separate client line, and refuse work that cannot clear your margin floor.

• Quote a fixed price for a fixed scope, so working faster raises margin instead of cutting revenue.
• Count internal PM, QA and client-call hours in the cost base, because unbilled coordination is where agency margin quietly disappears.
• Webflow Basic is $15/mo billed yearly and Premium is $25/mo billed yearly, so hosting belongs on the client invoice, not inside your build fee.
• Webflow pays partners 10% commission at Foundations and 20% at Certified on Site plans and add-ons for the first 12 months of each subscription.
• Set a margin floor before you quote, then cut scope rather than price when a project cannot reach it.

What should an agency charge for a Webflow project?

An agency should charge a fixed project price derived from its own delivery cost and a target gross margin, not from a published hourly rate. Agency Webflow pricing that starts with an hourly figure hands the client a lever to shrink the invoice by questioning hours. In the agency builds I lead as a white label Webflow developer, the quote is assembled from a scoped page and component count, costed at the agency's true internal hourly cost, then divided by the margin target to produce the number the client sees. If the resulting price is one the client will not accept, cut the scope and requote rather than discounting the margin.

• Count unique page templates, not total pages, because a CMS template covers hundreds of items at the cost of one build.
• Count reusable components separately, since a component built once and reused twelve times is the cheapest hour in the project.
• Count CMS collections and the reference fields between them, because collection architecture is decided once and expensive to unwind.
• Count interaction complexity, because a scroll-linked animation sequence can cost more hours than the page it sits on.
• Count review rounds explicitly, and state in writing how many are included.

Why does hourly pricing destroy agency margin on Webflow work?

Hourly pricing destroys agency margin on Webflow work because Webflow rewards speed, and an hourly rate converts speed directly into lost revenue. A developer who has built the same navigation component thirty times finishes it in a fraction of the time a first-timer needs, and under hourly billing that expertise reduces the invoice. What I see agencies get wrong here is treating the hourly rate as a safety net when it is actually a penalty on the exact capability they hired for. If your team is genuinely fast, price the outcome and keep the efficiency gain.

Hourly billing also caps upside. A fixed-price project that comes in under the estimated hours simply earns a higher effective rate, while an hourly project that comes in under estimate earns less money for identical work.

How do you calculate the real margin on a Webflow project?

Real margin on a Webflow project equals the fixed price minus every hour spent on it, including the internal hours nobody logs. Agencies routinely cost the build hours correctly and then omit project management, QA passes, client calls, feedback consolidation and launch-day support, which together can easily add a third again on top of the build hours, as the worked example below shows. The rule I apply on client projects is that any hour a human at the agency spends because this project exists is a delivery cost, whether or not it is billable. If your calculated margin drops below your floor once those hours are added, the quote was wrong, not the project.

The worked example above shows why the internal hours matter so much. Drop the 30 management hours out of the calculation and the same project appears to earn a 66% margin, which is the illusion that leads agencies to underquote the next one.

What does Webflow itself cost, and who should pay for it?

Webflow's own subscription costs should be billed to the client as a pass-through line, never absorbed into the agency's build fee. Webflow's published Site plan pricing lists Basic at $15/mo billed yearly with 300 static pages and 10 GB bandwidth, and Premium at $25/mo billed yearly with the CMS included and bandwidth starting at 50 GB. Webflow's Team plan is listed at $2,500/mo with an annual contract required. When I quote a build for an agency, the Site plan sits on its own line in the proposal so that a plan upgrade later is a client conversation rather than a margin event.

Webflow Site plan	Published price	What it covers
Starter	Free	Webflow.io domain, 2 static pages, 1 GB bandwidth
Basic	$15/mo billed yearly	Custom domain, 300 static pages, 10 GB bandwidth, no CMS
Premium	$25/mo billed yearly	Webflow CMS, bandwidth from 50 GB, site search, code components
Team	$2,500/mo, annual contract	Localize, AEO agents, publishing workflows, single-page publishing

Source for the table above: Webflow plans and pricing, checked August 2026.

Where does recurring revenue come from on Webflow projects?

Recurring revenue on Webflow projects comes from three places: the Webflow partner commission, a maintenance retainer, and paid iteration after launch. Webflow's Partner Program pays 10% commission at the Foundations tier and 20% at the Certified and Premium tiers on Site plans and add-ons, for the first 12 months of each subscription, and 10% on Enterprise annual contract value at every tier. On the projects I lead, commission is treated as a margin cushion rather than a business model, because it expires after 12 months while a retainer does not. If your agency ships more than a handful of client sites a year, reaching Certified doubles that commission line for the same delivery work.

• Partner commission requires an active Freelancer or Agency Workspace plan before you can even apply for the Certified tier.
• Certified also requires passing a pre-qualification assessment and building at least three new client sites as a Foundations member.
• The Certified application requires a portfolio of three client sites built from scratch that meet Webflow's published grading rubric.
• Maintenance retainers price the response time, not the task list, which is what makes them defensible.
• Post-launch iteration should be quoted as small fixed scopes, so the retainer does not silently absorb new build work.

Which pricing model should an agency use for Webflow builds?

Most agencies should default to fixed-scope pricing for Webflow builds and reserve other models for specific situations. Fixed scope suits a defined marketing site with a known page count. Value-based pricing suits a project where the client can name the commercial outcome, which is rare outside performance-driven redesigns. Retainers suit ongoing delivery for a client who ships continuously. When an agency asks me which model to use, the deciding question is whether the scope can be written down in one page: if it can, price it fixed.

Model	Use it when	Main risk
Fixed scope	The page and component count is known before signature	Scope creep, unless review rounds are capped in writing
Hourly	Discovery, audits, or rescue work with unknown depth	Speed reduces revenue, so expertise is penalised
Value based	The client can state the commercial outcome in numbers	Attribution disputes after launch
Monthly retainer	The client ships continuously and needs guaranteed capacity	Unlimited-request drift into unpaid build work

What margin floor should an agency defend?

An agency should set a written margin floor before quoting and treat it as a go or no-go test rather than a negotiating position. The floor exists so that the decision to decline is made in advance, when it is a policy, instead of during a sales call, when it feels like losing a client. What I see agencies get wrong here is discounting to win a first project on the theory that later work will be more profitable, which almost never happens because the first price anchors everything after it. If a prospect will not clear your floor, reduce the scope to something that does and let them choose.

Two exceptions are worth naming. A short, well-scoped project for a client who reliably sends referrals can justify a thinner margin, and so can a build that produces a genuinely reusable component library you will charge for many times. Neither exception should apply to more than a small share of the pipeline.

Working with a white label developer on fixed-price work

A white label Webflow developer changes the margin math by converting an unpredictable internal cost into a known external one. For agencies quoting fixed-price Webflow builds, a fixed subcontractor cost per project makes the margin calculation deterministic before the proposal goes out. I work as the delivery layer for agencies on exactly this basis, quoting the build so the agency can quote the client with confidence. If you are pricing a Webflow project now and want a fixed build number to put into your own margin calculation, get in touch for a quote, or read the related breakdowns of white label agency economics and what a Webflow developer costs.