14 Nov 20267 min readBy Shaish Guni
How to price a Webflow website project
A Webflow quote goes wrong in two places: pricing pages instead of templates, and forgetting the costs that aren’t yours. Here’s a method that holds up, with a worked example.
The short answer
- Count page templates, CMS collections and integrations, not pages.
- Estimate hours per phase and multiply by your effective hourly rate.
- Add a buffer for revisions and unknowns, then quote a fixed price for that scope.
- List the Webflow site plan, fonts and other tools as client-paid costs.
Price templates, not pages
In Webflow, the work is in unique layouts and the CMS, not the number of URLs. A blog with forty posts is one collection and one template page. A site with eight hand-built landing pages is eight layouts. Before any number, list:
- Static page templates: home, about, services, contact, pricing.
- CMS collections: blog, case studies, team, jobs, each with its template page.
- Interactions: scroll animations and Lottie take real time; plain fades don’t.
- Integrations: forms to a CRM, booking, memberships, localisation.
- Content: who writes it, who loads it, and how much there is.
Estimate each phase
Break the project into phases and estimate hours for each. Here is a worked example for a four-template marketing site with a blog and case studies. Every number is hypothetical, so swap in your own rate and hours.
| Phase | What’s in it | Hours |
|---|---|---|
| Discovery and sitemap | Goals, audience, page list, content plan | 8 |
| Design | Style guide, 4 page templates, 2 rounds of changes | 28 |
| Build | 4 templates, responsive, interactions | 30 |
| CMS | 2 collections (blog, case studies), template pages | 10 |
| Content load and SEO | Supplied copy, meta titles, 301s from the old site | 8 |
| QA, launch and handover | Browsers, forms, domain, client training | 8 |
| Total | 92 |
Hypothetical: 92 hours at a $90/hr effective rate is $8,280. With a 15% buffer, the quote rounds to $9,500.
Your effective rate is what you need to earn per working hour once sales, admin and unpaid time are covered. It’s higher than the rate you’d charge for an hour of advice. The freelance rate calculator works it out from the income you need.
Add a buffer, then quote a fixed price
Estimates run short: feedback takes longer, content arrives late, one interaction fights back. A 10–20% buffer covers that. Then quote the total as one fixed price for the scope you wrote down, with a set number of revision rounds and an hourly rate for anything outside it. The client approves one number; you keep the upside of working efficiently.
Bill what isn’t yours separately
Some costs belong to the client, not your fee. List them in the proposal as client-paid, with a link rather than a price, so the document stays accurate:
- The Webflow site plan, paid to Webflow from the client’s own account.
- Paid fonts, stock photography and icon licences.
- Third-party tools: forms, booking, memberships, translation.
Fixed price, phased, or a retainer after launch
For most builds, one fixed price paid in stages works best. For larger or uncertain projects, price a paid discovery phase first and quote the build once the sitemap is agreed. Offer care and updates as a separate monthly retainer that starts after launch, never folded into the build price. How to split the payments is covered in payment schedules for website projects.
Ready to write it up? The Webflow proposal template has the scope, client-paid costs and milestone payments already laid out.
Webflow pricing questions
- How do I price a Webflow website?
- Count the page templates, CMS collections and integrations, estimate hours for each phase (discovery, design, build, CMS, content, launch), multiply by your effective hourly rate and add a buffer for revisions and unknowns. Quote that as a fixed price for the agreed scope, and bill the Webflow site plan and other third-party costs separately.
- Should I price a Webflow site per page?
- Price per template, not per page. Ten blog posts built from one CMS template cost far less to build than ten one-off pages. Count unique layouts, CMS collections and interactions; that is where the hours go.
- Who pays for Webflow hosting?
- Usually the client, directly to Webflow, on a site plan in their own account. List it in the proposal as a client-paid cost with a link to Webflow's pricing page rather than a figure, so the proposal stays accurate when Webflow changes prices.
- Fixed price or hourly for a Webflow project?
- A fixed price for the agreed scope is easier for the client to approve and rewards you for working efficiently. Protect it with a written scope, a set number of revision rounds and an hourly rate for anything outside it.
- Should maintenance be part of the website price?
- No. Quote the build as a one-time project and offer care or maintenance as a separate monthly retainer that starts after launch, with what's included each month written down.
Send the quote as one link
ApeiroCraft turns the scope into a proposal your client opens and signs on the page, and drafts the deposit invoice the moment they do. Free plan, then $19/month for up to 3 people.
Start free