Webflow developers send estimates after a discovery call, a review of designs or an existing site, and a look at required integrations. Clients often compare several quotes, so the estimate needs to show clearly what is included and how many pages, collections, and revisions the price covers.
When to use estimates: Use estimates to provide project quotes and get client approval before starting work. Once approved, convert your estimate to an invoice with one click to collect payment.
Create an invoice for payment collection
Upload logo
PDF will be generated with filename:
Invoice_1001_Client_2026-10-14.pdf
Static pages and CMS templates take different amounts of time, and listing them prevents arguments over whether a new page is extra.
Collection structure drives build time. Naming the collections and rough item counts sets the boundary for migration and data entry.
State whether you are building from approved Figma files, a template, or designing as well. Unfinished designs are the largest source of overruns.
Complex scroll effects and scripts can double build time, so list which ones are included.
Forms, CRMs, analytics, e-commerce, memberships, and payment tools each add setup and testing time.
Clarify who writes copy, supplies images, and enters CMS content, and how many items you will migrate.
Set the number of feedback rounds, review turnaround times, and what post-launch support is included.
| Service | Priced | Typical range |
|---|---|---|
| Hourly development and edits | per hour | $65-150 |
| Marketing website build (5-10 pages, from approved design) | flat fee | $3,000-10,000 |
| Single landing page build | per page | $500-1,800 |
| CMS collection setup with templates | per collection | $400-1,500 |
| Site migration from WordPress or other platform | flat fee | $2,000-8,000 |
| Custom interactions and animations | per hour | $75-150 |
| Monthly maintenance retainer | per month | $250-1,500 |
| Site audit and SEO/performance cleanup | flat fee | $500-2,000 |
Typical US ranges. Rates vary by region, experience, and job size.
Build the quote from pages, collections, integrations, and interactions, then check the total against your hourly rate. This makes it easy to adjust if the client trims scope.
Presenting a basic build, a standard build with CMS, and a full build with integrations helps clients pick a budget without pushing you to discount.
Responsive checks, cross-browser testing, and client feedback cycles take more time than the build itself on some projects. Include 15-25% for them.
Webflow plan prices and your availability change. A 14-30 day validity period keeps old quotes from coming back at outdated prices.
Detailed enough to list pages, CMS collections, integrations, and revision rounds, with a price per phase. One or two pages is usually enough. A single total with no breakdown invites scope disputes.
A short call is typically free. For large builds or migrations that need a site audit or technical review, many developers charge a paid discovery phase, often $500-2,000, and credit it toward the project.
Say in the estimate that the price assumes the approved design. Design changes after build starts are billed as change orders at your hourly rate or a new fixed price, agreed before work continues.
Yes, when scope is uncertain, such as with a migration or a site you have not seen. Give a range with a stated cap, and say what would move the price to the top or bottom of it.
Use the Webflow Developer invoice template to bill the client, or convert this estimate once it's approved.
Webflow Developer invoice template