An estimate made at the "initial concept" stage of a project can be four times too high or four times too low, a sixteen-fold spread, according to Steve McConnell's Cone of Uncertainty as published by Construx. That is the quote you get from a Webflow agency when the brief says "we need a new website, something like Stripe". The agency is not being vague. The brief is.
This guide is the one-page brief we would want to receive: ten lines written in Webflow's own units (templates, collections, items, locales), plus the attachments that let an agency price a migration. The numbers come from Construx, PMI, Webflow, Google Search Central and WebAIM, read on 20 October 2026.
Why a vague brief produces a wide quote
An agency quoting a Webflow build is estimating hours. The hours depend on things it cannot see from your homepage: how many distinct layouts there are, how much content moves, which tools connect, and who approves the work.
The cone of uncertainty. Construx puts the error of an initial-concept estimate at 4x on the high side and 0.25x on the low side. Commitments made at the initial-concept or product-definition stage carry a 2x to 4x error, and completing requirements and interface design reduces the variability from 4x to 1.6x. The page's point is blunt: more time on the estimate does not narrow the range; only defining the project does.
Scope creep is the usual result. PMI's 2018 Pulse of the Profession, which surveyed 4,455 practitioners, 447 senior executives and 800 PMO directors, found that 52% of projects completed in the previous twelve months had scope creep or uncontrolled changes, up from 43% five years before. It names erroneous requirements gathering among the top three causes of failure. It is cross-industry and eight years old, so read it as a direction, not a rate for websites.
What agencies do with uncertainty. They quote high to cover it, quote low and recover the gap through change requests, or decline. None of those helps you compare proposals.
The one-page brief, line by line
The brief fits on one side of A4. Each line changes the hours, or the risk, in a way an agency cannot infer.
| Line | What to write | Why it changes the quote |
|---|---|---|
| 1. Business and goal | Who you sell to, what the site must make people do, how you will measure it | Sets where design time goes |
| 2. Page map | Every page, grouped into unique templates, with counts | Templates drive build hours, not page count |
| 3. CMS collections | Each collection, its fields, and today's item count | Decides the plan, content model and import effort |
| 4. Content ownership | Who writes copy, supplies images and enters content | The most common source of budget surprises |
| 5. Migration | Current platform, URL count, a content export, pages that rank or convert | Redirect mapping and import time |
| 6. Integrations | Every tool the site must talk to, written as a job | Each one is setup, testing and a failure point |
| 7. Languages and accessibility | Locales now and within a year; the WCAG level | Localisation and QA scope |
| 8. Design input | Brand system, Figma files, three reference sites and why | Whether design is a phase or a handoff |
| 9. Budget and deadline | A range, a launch date and whether it is fixed | Lets the agency propose a version that fits |
| 10. Sign-off | Who approves, how many review rounds, when you will choose | Review loops are hours too |
Source: Octo Agency recommended brief structure; line 4 follows theCSSAgency's September 2026 RFP guide, a Webflow agency's guidance.
The page map. Write templates with counts: "Home (1), Product (4), Solution by industry (6), Blog post (CMS), Legal (3)". If the page map is not settled, our post B2B Website Strategy: How to Write the Page Map Before Anyone Opens Figma covers it, and it is worth doing before you brief anyone.
The collections. Name each one, list the fields, and give today's item count and growth. "Blog, 340 posts, 6 fields, about 8 a month" can be priced. "We have a blog" cannot.
Write the scope in Webflow's units
Webflow's plan limits are the walls your site will live inside. A brief that states them stops an agency quoting for the wrong plan.
| Item | What Webflow publishes | What to put in the brief |
|---|---|---|
| Basic Site plan | $15 a month billed yearly, 300 static pages, no CMS | Whether you have any repeatable content |
| Premium Site plan | $25 a month billed yearly, 20,000 CMS items, 40 collections | Item count per collection and yearly growth |
| CMS API | 120 requests a minute on Premium, 60 on Starter and Basic | Whether content syncs from another system |
| Localize Essential | $9 a month per locale, up to 3 added locales | Languages at launch and within a year |
| Localize Advanced | $29 a month per locale, up to 10, localised URLs | Whether URLs must be translated |
| Team plan | $2,500 a month, annual contract, publishing workflows | Whether publishing needs approval steps |
| Ecommerce plans | $29, $74 and $212 a month billed yearly | Product count and checkout needs |
Source: Webflow pricing page and Webflow developer documentation on rate limits, read 2026-10-20. Vendor-published prices, before tax.
Plan cost is not build cost. These are hosting fees you pay Webflow. For what agencies charge, our post How Webflow Agencies Price Builds in 2026: 33 Published Rate Cards Compared lists the published numbers, and Webflow CMS Limits in 2026 covers the item and reference ceilings.
State the growth. A site at 1,500 items adding 3,000 a year sits on Premium for years. A plan to add 15,000 location pages in one quarter does not, and the agency needs to know before it designs the content model. Our largest Webflow CMS build for Web Tonic held over 1,200 items, a small fraction of the ceiling, which is typical of marketing sites.
Migration: the attachments that replace guesswork
If you already have a site, the migration is usually the least predictable part of the quote. Three attachments fix that.
A full URL list. Export every live URL from your sitemap, analytics and CMS, and mark the ones that bring organic traffic or leads. Google Search Central's site-move guide, updated August 2026, says to map old URLs to new ones, starting from sitemaps, server logs and analytics, and to keep redirects generally for at least one year.
A content export per collection. One spreadsheet column per field. Webflow's help centre says its CMS importer accepts CSV files up to 4 MB, that file fields cannot be imported and must be uploaded by hand, that images imported by URL get no responsive variants, and that an option field takes at most 100 values. Each becomes hours if discovered mid-project.
The redirect count. Webflow imports 301 redirects from a CSV of up to 16 MB, but a new import overwrites every existing redirect, and one invalid row fails the whole file. An agency that knows the URL count plans for that; one that does not finds out on launch day.
Integrations and the features Webflow no longer ships
Integrations are where quotes most often miss, because briefs list them as nouns ("HubSpot") instead of jobs ("form submissions create a contact and alert sales in Slack").
Write each one as a job. Say what data moves, in which direction, and what happens on failure. "Webinar sign-ups go to HubSpot with UTM fields" is a few hours. "Gated content for logged-in customers" is a different project.
Logins and automations are third-party now. Webflow announced in December 2024 that it would retire Logic on 27 June 2025 and User Accounts on 29 January 2026, recommending Zapier and Make, then Outseta and Memberstack, as replacements. If you need members, gated pages or automation, say so: the quote will include a third-party tool, its subscription and the setup.
Accessibility is a scope line. WebAIM's 2026 analysis of the top million home pages found detectable WCAG 2 failures on 95.9% of them, up from 94.8% in 2025, with an average of 56.1 errors per page and low-contrast text on 83.9%. The European Commission lists e-commerce and banking services among those covered by the European Accessibility Act. State the level you need, for example WCAG 2.2 AA, so testing is priced in rather than added later.
Budget, timeline and who decides
Give a range. theCSSAgency, a Webflow agency, argues in its September 2026 RFP guide that leaving out the budget produces quotes that cannot be compared, and leaving out content ownership produces a low quote that grows later. That is a seller's view, and we share the bias, but a range lets each agency propose what fits instead of three readings of "a website".
Say what is fixed. A launch tied to a funding round or event is fixed. A date picked because it was round is not. Tell the agency which you have, and it can propose a phased launch instead of a rushed one.
Name the decision-maker. One person who approves design and content, a number of review rounds, and the date you will choose. The same guide puts a full RFP process at four to six weeks and suggests a shortlist of three to five agencies.
Where to look. Webflow's Certified Partner directory lists over 1,200 partners and filters by services, budget and location. Send each the same brief and ask for answers in the same structure.
A filled-in example
Illustrative, not a client: a B2B SaaS company replacing a WordPress site.
| Line | Example entry |
|---|---|
| Business and goal | Finance workflow software; the site must book demos; measured as demo requests a month |
| Page map | Home (1), Product (3), Solution by role (4), Pricing, About, Contact (1 each), Legal (3), CMS templates |
| CMS collections | Blog: 220 posts, 7 fields, 6 a month. Case studies: 14. Jobs: synced from the ATS |
| Content ownership | We write copy; agency edits and enters CMS content from our CSV |
| Migration | WordPress, 410 URLs, 60 with organic traffic; CSV and URL list attached |
| Integrations | HubSpot forms with UTMs, GA4 with consent mode, Calendly on the demo page |
| Languages and accessibility | English at launch, German within a year; WCAG 2.2 AA |
| Design input | Brand guide and Figma library attached; three reference sites with notes |
| Budget and deadline | Range stated; launch before a March product announcement, fixed |
| Sign-off | Head of Marketing; two review rounds per phase; agency chosen by 15 November |
Source: Octo Agency illustrative example.
An agency can quote that within a narrow band and tell you on the first call whether the deadline is realistic.
What this means for hiring a Webflow agency
Before you hire a Webflow agency, spend an afternoon on the ten lines above. It moves your request out of the widest part of the cone, gives every agency the same job to price, and puts the expensive unknowns (migration, integrations, content) on the table before anyone signs.
We are a Webflow development agency, so read this with that bias. We have built 20 or more Webflow sites in twelve months as Web Tonic's white-label partner, at two to three weeks each, and run new marketing sites through a four-week process. We would use these ten lines as the agenda for a first call, and we quote each build per project. Our Webflow development service page explains how we scope it.
