Webflow developers build and maintain marketing sites, CMS-driven blogs, and landing pages for startups, agencies, and small businesses. Invoices usually cover design-to-Webflow builds, CMS setup, custom interactions and code, migrations from other platforms, and ongoing site support. Many work solo or as subcontractors to design agencies, so invoices often need to line up with a scope document or milestone schedule.
Create an invoice for payment collection
Upload logo
PDF will be generated with filename:
Invoice_1001_Client_2026-10-14.pdf
Most Webflow developers price new builds as a flat project fee, often split into milestones (deposit, design approval, build complete, launch). Fixed pricing is usually based on page count, number of CMS collections, and complexity of interactions. Hourly billing is common for small changes, audits, and work with unclear scope, and agencies subcontracting developers often pay hourly or per-page. Ongoing work is commonly sold as a monthly retainer with a set number of hours, or as a care plan covering edits, backups checks, and minor updates. Extras such as custom code, third-party integrations, copywriting entry, and migrations are normally itemized separately. Client-side costs like Webflow site plans, workspace seats, and paid apps are usually either billed directly to the client's account or passed through at cost, so say which one on every invoice.
| 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.
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Webflow build of 8-page marketing site from approved Figma design (milestone 2 of 3, 40%) | 1 milestone | $2,800.00 | $2,800.00 |
| CMS setup: Blog and Case Studies collections with templates and filtering | 2 collection | $800.00 | $1,600.00 |
| Custom scroll interactions on home page | 5 hours | $95.00 | $475.00 |
| Custom code: HubSpot form embed and tracking scripts | 3 hours | $95.00 | $285.00 |
| Webflow Business site plan, 12 months (pass-through at cost) | 1 plan | $276.00 | $276.00 |
| Total | $5,436.00 | ||
Notes: Payment due within 14 days of invoice date. Remaining 30% is due at launch. Revisions beyond two rounds per page are billed at $95/hour. Site plan cost is passed through at cost with no markup; billing transfers to the client's Webflow account after launch.
Ties the invoice to the agreed scope so the client's accounts team can match it to the contract or proposal.
Shows what was built and prevents disputes over whether something was included in the flat fee.
Change requests and extra revisions need dates and hour counts to be defensible.
Listing these at cost separately keeps them distinct from your labor and shows you aren't marking them up unless agreed.
Helps when a client or agency asks which approved scope the invoice falls under.
Agencies and larger clients often will not process payment without it.
Clarifies who owns the project, who pays Webflow hosting, and when final payment releases the transfer.
A 30-50% deposit before work starts is standard for fixed-price builds, with the balance split across milestones or due at launch. Many developers hold the workspace transfer, DNS changes, or publishing to the live domain until the final invoice is paid. Net 14 is common for direct clients, while agencies often pay net 30 or net 45, so confirm before you start. Late fees of 1-1.5% per month are common if stated in the contract in advance. Payments usually come by ACH, card, or wire; card payments often carry processing fees, which some developers pass on. Retainers are normally billed at the start of the month.
Invoice on design handoff, staging review, and launch rather than calendar dates. Client feedback delays then do not stall your cash flow.
Limit rounds per page or per milestone, and bill extra rounds hourly. Most Webflow scope creep is small copy and layout tweaks that add up.
Have clients create their own workspace or add a card for site plans. It avoids fronting costs and removes confusion about renewals after launch.
Tracking time shows when a project is running over and gives you evidence when pricing the next change request or retainer.
Offer a short free bug-fix window, such as 14-30 days, then move edits to hourly or a retainer. State the window on the final invoice.
Flat fees work well when the design is finished and the page and CMS counts are known. Hourly suits unclear scope, ongoing edits, and cleanup of someone else's build. Many developers use a flat fee for the build and hourly for changes after approval.
Either approach works if it is written down. The cleanest option is for the client to pay Webflow directly from their own account. If you pay first, list the plan as a pass-through at cost and note the renewal date.
Invoice the party who signed your agreement, which is often the agency. Include their project code or PO, and use the rate or per-page price you agreed on. Agencies often want hours broken out by task.
Many developers do, as long as the contract says final payment is due before transfer or launch. Put that term in the proposal up front rather than raising it at the end.
It depends on the state. Some states tax digital services or custom software, and others do not. Check your state's rules or ask an accountant, and show any tax collected as a separate line.
Send a Webflow Developer estimate for approval, then turn it into an invoice when the work is done.
Webflow Developer estimate template