Turn the content inventory into plan requirements
Count static pages and structured content records separately. A collection of case studies or articles has different editing needs from a few fixed pages. Record the number of editors, expected files and any search, form or localization requirements as well.
Webflow's pricing and plan structure can change. Use its current comparison to verify each requirement; do not build a budget around an old screenshot or assume every paid feature is included in the lowest plan. Check the billing interval, taxes and renewal commitment for your account.
Request two connected estimates
The project estimate should describe design, CMS structure, interactions, content entry and testing. The service estimate should identify paid plans, optional add-ons and any third-party tools. Keep the subscriptions in the business's name where practical and agree how the site is handed over.
| Requirement | Question before approval |
|---|---|
| Editorial content | Which collections and item volumes are needed? |
| Forms | Where do submissions go, and who sees failures? |
| Languages | Which pages and interface elements will be localized? |
| Team access | Who edits, reviews and publishes? |
| Hosting and usage | Which limits apply to the expected traffic and assets? |
| Exit | What can be exported, and what must be rebuilt elsewhere? |
Exportability needs a concrete check of your chosen setup. Being able to export files does not necessarily reproduce every hosted workflow, database or third-party connection.
Compare a launch budget with a two-year budget
Use actual quotes in this formula: project work + content work + two years of recurring services + separately approved changes. A fictional example uses $4,500 implementation, $900 content and $80 per month for all selected services. That gives $7,320 over 24 months before taxes, support labor and future features. The $80 is an illustrative combined allowance, not a Webflow tariff.
Now add the expected editing and maintenance workload. If an internal editor can perform routine changes after training, record those hours separately from outsourced costs. That makes a platform comparison more useful than looking at the monthly subscription alone.
Ask for an editable handover
Have a team member edit a real page, publish a test change and correct a mistake before accepting the handover. Confirm that the agreed design remains usable with longer titles and new content. Original animations can be attractive, but quote their design and testing explicitly if they matter to your project.
Use the business website calculator to describe the implementation scope, then replace generic platform allowances with verified Webflow inputs. SiteCost does not select the correct Webflow plan automatically.