How to scope and budget a Webflow website

A website budget has two parts: the platform you pay for each month, and the project work to design, build and launch the site. The platform is the small, predictable part. The project depends on scope: how many page templates you need, how much content moves across, what the site connects to, how many languages it covers and how ready your content is.

We don’t publish prices, because every quote depends on the site. What we can share is how we scope one, so you can do the same thinking before you ask for quotes.

The cost areas in a website project

Most website projects are made of the same nine parts. Not every project needs all of them, but every quote should say which it covers.

1. Platform subscriptions. The site plan and any add-ons, paid to Webflow or your host.
2. Design. Every page template, designed for phone and desktop.
3. Development. Components, the CMS, forms, and testing on every device.
4. Content and copy. The words and images on every page. We don’t write copy in-house: it usually comes from your team or a copywriter we can recommend, so budget for it separately.
5. Migration. Moving content from your current site, and redirecting every old address.
6. Integrations. Your CRM, booking system, payments or analytics.
7. Localisation. Versions for other countries or languages, and the translations to fill them.
8. Training and handover. Sessions and recorded walkthroughs, so your team can publish on its own.
9. Ongoing support. Studio time after launch for fixes, landing pages and improvements.

A scoping worksheet

Fill this in before your first call with any studio. Rough answers are fine.

Cost area	Questions to answer	Your answer
Platform	Do you need a CMS for a blog, case studies or resources? Will you sell online? More than one language?
Design	How many different page layouts (templates) does the site need? Is the brand settled, or does it need work too?
Development	Which features go beyond standard pages, such as calculators, filters or gated content? Should your team be able to build new pages from components?
Content and copy	Who writes the words? Is the copy finished, in draft or not started? Who supplies the photos?
Migration	How many pages and posts are on the current site? What moves, what merges and what retires?
Integrations	Which CRM, booking, payment or analytics tools must the site connect to? Who has access?
Localisation	Which countries or languages, now and in the next year? Who translates?
Training and handover	Who will edit the site each week, and how comfortable are they in a visual editor?
Ongoing support	After launch, how much will you want changed each month, and who will do it?

What the platform costs

Platform fees are paid to the platform, not to us, and they’re the smallest line in the budget. As of 9 October 2026, a Webflow site plan with the CMS is US$25 a month billed yearly, plus tax, and languages are an add-on (Webflow’s pricing has the rest). The tools the site connects to, such as your CRM or booking system, have subscriptions of their own.

Hosting is your own plan, billed to you, so the site stays in your hands. A custom-coded site swaps the site plan for hosting alone; Webflow vs WordPress compares the routes.

What changes the scope

Six things move a quote more than anything else.

1. Page templates. A template is a layout, so ten case studies on one template are far less work than ten different pages. Count templates, not pages. Design usually takes two to four weeks, depending on how many the site needs.
2. Migration size. Rebuilding a handful of pages is a different job from moving hundreds of posts and redirecting every old address. Our migration plan shows what’s involved.
3. Integrations. Each connection to a CRM, booking or payment tool needs mapping, testing and access. Linking out to a system you already use is simpler than building it in.
4. Languages. Each one adds pages to build, content to translate and check, and a platform add-on.
5. Content readiness. This is what stretches timelines most: when a project runs past the two and a half to three months we plan for, it’s usually waiting on copy. Finished copy lets design start from the real words; unfinished copy means design waits, or gets redone.
6. Review rounds. Feedback is built into every stage, and the proposal says how many rounds are included. Changes after sign-off are quoted before we make them.

Nine projects, side by side

Scope is easier to judge against real projects. These are the nine in our case studies; a dash means it didn’t apply, or the figure isn’t ours to publish.

Project	Move	Pages	Markets	Time	Redirects
Smokeball	Webflow → Webflow, 3 sites	1,600+	AU, US, UK	~4 months	645
Fresh Clinics	HubSpot → Webflow	340+	AU, US	Nov–Feb	324
Altus	WordPress → Webflow	220+	EN, DE	18 weeks	A handful
Skip	Webflow → Webflow, new domain	78	AU	Feb–Apr	Page for page
Smileyscope	Wix → Webflow	33	AU, US	4.5 months	–
Doctor Canna	WordPress → Webflow	–	AU	Mar–Aug	–
Endeavour Lotteries	New → Webflow	–	AU	6 weeks	–
Econohealth	New → Webflow	7	AU	9 days*	–
Generate	Webflow → custom code	–	AU, NZ	Aug–Oct	–

Pages include CMS items. Smokeball’s redirects are 399 for Australia and 246 for the UK. *From approved designs to launch.

What stands out:

• We plan builds for two and a half to three months. When a project runs longer, as several here did, it’s usually because the build is waiting on copy, not on design or development. Finished content is the biggest thing you control in a timeline.
• Most moves aren’t from WordPress. Two of the nine came from WordPress; the rest came from Wix, HubSpot, an earlier Webflow build, or nothing at all.
• Several markets usually means one site. Of the four projects with country or language versions, only Smokeball runs separate sites, because each country has its own pages, pricing and content (one site or regional sites).
• Redirects follow the old site. Altus needed a handful because its addresses barely changed; Fresh Clinics and Smokeball needed hundreds.

Ways to phase a build

If the budget or deadline is tight, cut scope by phase rather than by quality.

• Priority pages first. We design the pages that matter most first, so building can start sooner. A site can launch with those and add the rest later.
• A lean first version. For a new offer, one or two strong landing pages can prove the idea first.

What a proposal should tell you

Whoever you choose, a good proposal answers these before work starts:

• which pages and templates are included, and which aren’t
• how many rounds of feedback each stage has
• what the studio needs from you, and when: content, brand files, access to your domain and tools, and someone to sign off each stage
• the milestones and the launch date
• what happens after launch, and whether ongoing support is included
• who owns the finished site

With us, you own the finished site. Ongoing support is optional: reserved studio hours each month, which you can pause or end with 30 days’ notice (ongoing optimisation).

“It’s rare to find an agency that not only delivers on time and within budget, but also approaches the project with the care and attention…”

Adam Trouncer, Google review

Questions we get asked

How much does a Webflow website cost?

It depends on scope: the number of page templates, any migration, integrations and languages. The Webflow site plan itself is US$15 a month billed yearly without the CMS, or US$25 with it, as of 9 October 2026. The project work is the larger cost, and we quote it after a first call.

What makes a website quote go up?

More page templates, a larger migration, more integrations, more languages, and content that isn’t ready. Each adds design, build or testing time. Changes after sign-off add to it too, so the proposal sets out the rounds of feedback included.

Is hosting included in the project price?

No. Hosting is your own plan with Webflow or your host, billed to you directly, so the site stays in your hands. The project covers the work set out in your proposal, such as design, build, migration, integrations, launch and training.

Can we build the website in phases?

Yes. Launching the priority pages first spreads the work and gets the important pages live sooner. Languages and custom features can follow launch too, as German did for Altus.

If you’ve filled in the worksheet, or want help with it, tell us about your project. We’ll come back with a proposal that sets out exactly what’s included. Our design and development pages show what each stage covers.

Sources

• Webflow, Plans & pricing, read 9 October 2026