Your Webflow website has several costs: planning and building it, the platform, connected tools and ongoing support. Keep those separate when you compare quotes. A single headline price can hide very different scopes.
For a useful budget, separate the one-off scope from the recurring operating costs. Then ask what the business owns and what the team will be able to manage after launch. This guide explains the cost structure without inventing a universal agency price.
Start with the website's job
A small marketing site, a content-heavy B2B website and an ecommerce store have different requirements. Page count is only a rough signal. A five-page site with complex integrations can involve more work than a larger site built from a simple shared template.
Write down the audience, main action, required content and functions. Include languages, forms, CRM routes, publishing needs and migration. Use the website brief template to make those inputs concrete before requesting quotes.
Ask providers to price the same brief. Otherwise, one proposal may include strategy and copy while another assumes you'll supply both.
Separate planning, design and implementation
Planning can include page architecture, content decisions and technical scope. Design can include the visual system, responsive layouts and component behaviour. Implementation can include Webflow development, CMS collections, forms, integrations and publication.
Clarify which of those are included. “Custom Webflow website” doesn't establish who writes the copy, creates the brand assets or checks the launch. Ask what happens if the initial content or identity isn't ready.
For a redesign, include the existing URL inventory, redirects and content transfer. These are real tasks even if they are less visible in a design presentation.

Read platform costs separately
Check Webflow's current pricing for the Site and Workspace options relevant to your team. Site hosting and team-workspace needs are related but distinct. Verify billing frequency, currency, tax, capacity and any add-ons when you make the decision.
Avoid using a screenshot of an old plan table as the budget. Pricing structures and product names can change. Keep a dated note of the selected plan and the requirements it meets.
List connected costs separately: domains, localisation, analytics, forms or CRM services, automation and chat. Not every site needs all of them. A subscription should have a job and an owner rather than being included because a template supports it.
Budget for content and migration
Content work includes more than pasting text into pages. It can involve rewriting service explanations, selecting images, gathering case-study information and reviewing metadata. Name the provider and approval process for each.
A migration may require moving CMS records, downloads, image references and old links. Ask whether the quote includes redirects, live-domain checks and post-launch monitoring. See the website redesign SEO guide for the questions to put into the scope.
If the business is changing its identity at the same time, define that work explicitly. A website designer can't apply guidelines that are still being debated without affecting the schedule.

Define support after launch
Ongoing support can include content help, integration maintenance, release checks and incident handling. Platform hosting doesn't automatically include every change or problem in your website's configuration.
Ask for agreed response expectations, exclusions and a way to request work. A maintenance arrangement and a monthly growth programme serve different purposes; compare what each actually delivers.
Know who owns the domain, Webflow workspace, integrations and billing. The business should understand how another provider could take over and what documentation would be available.
Compare the first year, not only the build fee
Use this worksheet for each proposal:
- One-off planning, content, design and build.
- Migration, launch testing and training.
- Site and Workspace plans required.
- Third-party subscriptions and expected usage.
- Support scope and recurring fee.
- Optional work and likely change-request process.
- Account ownership and handover deliverables.
Separate confirmed prices from estimates and assumptions. A lower build fee can be reasonable if you supply more work, but that responsibility should be visible in the comparison.
Is a template always cheaper?
It can reduce some design or implementation work when it fits. Content, accessibility, integration and migration still need attention. Compare the complete scope rather than assuming the template price is the project price.
Why do Webflow agency quotes vary so much?
Providers may include different strategy, copy, design, technical work and support. Ask them to explain the deliverables and assumptions against the same brief before deciding that the higher quote is simply a markup.
Explore Hilvy's Webflow services, website work and maintenance, or read the wider business website cost guide.
Choose the scope, then budget the first year
To compare Webflow proposals, price the same deliverables and add four separate totals: the build, platform and connected tools, content and migration, and continuing support. Agree who supplies each item and what counts as finished before comparing the final number.
Which project are you asking someone to quote?
Use these planning scenarios to make the brief specific. They describe work to discuss with a provider; the signed proposal should identify the agreed inclusions.
- A focused marketing launch. List the unique page layouts, supplied copy and brand assets, enquiry form destination, responsive checks and handover. Confirm whether copywriting, brand work and new integrations need separate estimates.
- A website with a growing content library. Add CMS collections, reusable templates, content relationships, search or filtering requirements and editor training. Count both the layouts to build and the records to populate. Assign responsibility for writing and approving those records.
- A redesign or platform migration. Add the existing URL and content inventory, field mapping, redirects, downloads, form connections and launch checks. Agree which pages move, merge or retire and who checks the destinations after launch. Our website migration service explains the work to scope.
What the Mirador Local project helps you compare
The public Mirador Local case study credits Hilvy with designing and developing its marketing website, from Figma to Webflow. It describes custom scripting and a CMS for case studies, feature pages and resources.
For a comparable marketing brief, ask providers to identify design, reusable CMS templates, custom behaviour and editor handover separately. The case study shows a delivered scope; it does not publish a project fee or provide a budget for building the underlying business-profile management application.
A first-year budget worksheet
Copy the four rows into your proposal comparison. Record each amount, supplier, payment date and whether it is confirmed or estimated. Use one currency and a consistent tax basis throughout.
| Budget line | What to record | First-year calculation |
|---|---|---|
| Build | Planning, design, development, integrations, testing, launch and handover included in the quote. | Add the one-off fees due in year one. Identify exclusions and optional work. |
| Platform and tools | The required Webflow plan, any separately required Workspace plan, domain and agreed connected services. | Add annual invoices due in the year and monthly charges for the months used, plus any usage allowance. Count each subscription once. |
| Content and migration | Copy, images, CMS population, content transfer and redirect work. Name the owner for each task. | Add separately quoted fees. Mark work already included in the build so it is not counted twice; record internal staff time separately. |
| Continuing support | The agreed support scope, coverage period, purchased hours or programme, and separately approved changes. | Add the support purchases planned for year one. Record optional work as an allowance with its assumptions. |
First-year total = build + platform and tools + content and migration + continuing support. Keep optional allowances visible beside the confirmed total. If a service starts partway through the year, use its actual billing schedule rather than automatically multiplying by twelve.
Check the selected plan and billing terms against Webflow’s current pricing when completing the worksheet. Keep the provider quote and the platform invoice as separate lines unless the proposal explicitly includes both.
Use our website service to frame the design and build brief, then tell us about your project with the existing site, required page types, content owner and intended launch window.




