WebAIM's 2026 scan of the top one million home pages found detectable WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page. Most of those sites were designed and built by someone who was paid to do it. Accessibility is rarely in the quote, so it is rarely in the build, and it is only one of nine items that Webflow design and development services leave out more often than they include.
This guide lists what a full Webflow scope should contain, line by line, then the nine items that go missing and what to write for each. Platform facts come from Webflow's own pricing and developer pages, read on 2026-10-28; search and performance rules come from Google.
What a full Webflow design and development scope contains
"Design and development" covers two jobs that are often quoted as one. Design is the Figma work: page layouts, components, states and the responsive behaviour at each breakpoint. Development is the Webflow build: classes, components, CMS collections, interactions and integrations. A scope that names both, with their own deliverables, is easier to price and easier to defend when the client asks for more.
| Line | What it should state | Typical unit |
|---|---|---|
| Discovery and page map | Pages, templates and the content each one holds | Number of pages and templates |
| Design system | Colours, type scale, spacing, components with states | Component count |
| Page design | Desktop and mobile layouts for each unique page | Unique layouts, review rounds |
| Static page build | Pages that are not generated from the CMS | Static pages |
| CMS model and templates | Collections, fields, reference fields, template pages | Collections, templates |
| Interactions | Which elements animate and on which breakpoints | Named interactions |
| Integrations | Forms, CRM, analytics, scheduling, chat | Named tools |
| QA | Browsers, widths and devices tested | Test matrix |
| Launch | Domain, SSL, publishing, sitemap, search console | Checklist |
| Handover | Documentation, training, Workspace transfer | Deliverables listed |
If you are on the buying side, our guide on how to brief a Webflow agency turns this table into a one-page brief. The lines above are the floor. The nine below are where quotes drift.
The nine items agencies forget to quote
Each of these is real work, often a day or more, and each one is invisible in a design review. That is why they slip: nobody asks about them until the site is close to launch.
| Missed item | Why it gets missed | What the scope should say |
|---|---|---|
| 1. Content migration and CMS entry | Assumed to be the client's job | Item count per collection, who enters it, by CSV, API or hand |
| 2. Redirect map | Treated as a launch-day task | Every old URL mapped, file delivered, redirects kept a year or more |
| 3. Accessibility testing | Assumed to come with good design | Target standard, tools used, manual checks, fixes included |
| 4. Consent and tracking | Belongs to "marketing", not the build | Consent banner, consent mode, tag manager, events listed |
| 5. Form routing and CRM | Forms look finished once they submit | Destinations, fields mapped, spam protection, notification addresses |
| 6. Localisation | Raised after the main build | Locales, translation source, hreflang, localised slugs |
| 7. Performance budget | No one owns a number | Core Web Vitals targets, image and font rules, script limits |
| 8. Editor training and documentation | Seen as a goodwill extra | Recorded walkthrough, CMS guide, number of training sessions |
| 9. Post-launch fix window | Assumed to be free forever | Length of window, what counts as a fix, rate after it ends |
Source: Octo Agency scope review; standards from Google Search Central, WebAIM and web.dev as cited below.
1. Content migration and CMS entry. Moving 40 blog posts by hand is an afternoon. Moving 1,200 items with references between collections is a small project, and it is the size of the largest CMS we have built for a white-label partner. Webflow's Data API allows 60 requests per minute on Starter and Basic plans and 120 on CMS, eCommerce and Business plans, per Webflow's developer documentation, so a large scripted import still needs planning. Write the item count per collection into the scope, say who cleans the source content, and say how it gets in.
2. The redirect map. Google's site move guidance is direct: map the old site's URLs to the new ones, use server-side permanent redirects, and keep them for as long as possible, generally at least a year. It also says a small to medium site can take a few weeks for most pages to move in search. A redesign without a redirect file is a traffic risk the client did not agree to take. Scope it as a deliverable: a spreadsheet of every old URL, its new URL, and a check after launch.
3. Accessibility testing. The WebAIM Million 2026 lists the most common failures: low-contrast text on 83.9% of home pages, missing image alt text on 53.1%, missing form labels on 51% and empty links on 46.3%. All four are cheap to prevent during design and build and tedious to fix afterwards. For clients selling in the EU, the European Commission lists e-commerce and banking services among those covered by the European Accessibility Act. The scope should name the standard (usually WCAG 2.2 AA), the automated tools, the manual checks such as keyboard navigation and screen reader passes, and whether fixes are included.
4. Consent and tracking. A Webflow site with Google Analytics and ad pixels needs a consent banner and, for EU visitors, consent mode. Google's tag platform documentation notes that consent mode was updated in November 2023 with two additional parameters, ad_user_data and ad_personalization, and that Google is strengthening enforcement of its EU user consent policy. Setting this up properly means a consent tool, a tag manager container, named events and a test in each consent state. It is a line item, not a snippet.
5. Form routing and CRM. A form that submits is not a form that works. The scope should say where each form sends its data (Webflow, HubSpot, Salesforce or a webhook), which fields map to which CRM properties, who receives notifications, and what spam protection is used. Notification addresses are also a handover risk: on white-label projects the partner's address is the most common leak we see, a point we cover in our client handover kit for Webflow.
6. Localisation. Webflow sells Localize as an add-on, with the Essential tier listed from $9 a month and Advanced from $29 a month, both priced by number of locales, on its pricing page as of October 2026. The add-on is the cheap part. The work is translated content, localised slugs, language switchers, and hreflang that Google can use: its documentation says each version must list itself and every other version, and that if two pages do not point to each other, the tags will be ignored. Quote each locale separately.
7. A performance budget. Google's Core Web Vitals thresholds for a good experience are Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads (web.dev). A scope that names these targets also has to name the rules that hit them: image formats and sizes, the number of font files, whether background video is allowed, and which third-party scripts load and when. Without a budget, every new script is someone else's problem.
8. Editor training and documentation. A Webflow site is sold partly on the promise that marketing can edit it without a developer. That promise depends on a CMS guide, a page-building guide and a recorded walkthrough. If the scope does not list them, they arrive as a rushed call on launch day. Our post on a website that a marketing team can edit covers what the client team needs to be able to do on day one.
9. A post-launch fix window. Something always surfaces in the first weeks: a form on a browser nobody tested, a CMS item that breaks a layout, a redirect that was missed. The scope should state how long the fix window lasts, what counts as a fix rather than a change, and what rate applies afterwards. We would set this at a fixed number of weeks per project, and we would write the definition of a fix into the contract.
The platform costs that sit outside the agency's fee
Even a complete design and development quote rarely includes the running costs of the platform. The client pays them, or the agency resells them, and the contract should say which.
| Plan or add-on | Listed price | What it decides |
|---|---|---|
| Starter | Free | Webflow.io domain, 2 static pages, 50 form submissions |
| Basic | $15 a month, billed yearly | Custom domain, 300 static pages, no CMS |
| Premium | $25 a month, billed yearly | Adds the CMS, site search and form file upload |
| Localize Essential | From $9 a month, by locale | Up to 3 locales, 10,000 words a month |
| Localize Advanced | From $29 a month, by locale | Up to 10 locales, 50,000 words a month |
| Team | From $2,500 a month, annual contract | Publishing workflows, activity log, governance |
Source: Webflow, Plans and pricing, read 2026-10-28.
Webflow's pricing page also lists CMS limits of up to 20,000 items and 40 collections on the CMS-capable site plans. A content model that will grow past those numbers needs a different plan or a different architecture, and that decision belongs in the scope, not in month eight. Fonts, scheduling tools, consent tools and form apps add their own subscriptions on top. For a fuller look at how agencies price the build itself, our comparison of 33 published Webflow agency rate cards shows what the headline prices leave out.
How to write the scope so the quote holds
Count in units, not adjectives. "Up to 12 static pages, 3 CMS templates, 4 collections, 150 migrated items" can be priced. "A modern, fully responsive site" cannot.
Name the review rounds. We would default to two rounds of design feedback per page group, and say in writing what happens on the third.
Assign every input. Copy, images, the old site's URL list, CRM access and analytics accounts each have an owner and a date. A missing input delays the build, and the scope should say that the timeline moves with it.
Write a change-request rate. Every scope leaves something out. The clause that prices the missing piece is what keeps a fixed fee fixed.
Mark what is excluded. A short "not included" list (copywriting, photography, paid ad landing pages, ongoing SEO) removes more arguments than any other paragraph in the document.
How a white-label partner should handle the same list
When an agency resells Webflow design and development services, the nine items still have to be done by someone. A partner that quotes only the build leaves the agency holding migration, redirects, accessibility and tracking, which is usually where the margin goes.
We build Webflow sites as the white-label partner behind Web Tonic: 20 or more sites in twelve months, two to three weeks each, the largest with a CMS of over 1,200 items. A two-to-three-week build only works when the inputs and these nine lines are settled before the first class is written. For a new partner agency, we would go through the nine items in the scoping call, mark each as included, excluded or quoted separately, and send that list back with the quote. We build marketing sites in Webflow and applications in Next.js, so a scope that turns into an application shows up at this stage rather than in week three.
What this means for agencies quoting Webflow work
Treat the nine items as a checklist that every quote passes through, whether you build in-house or through a partner. For each one, write one of three words: included, excluded or separate. A client who sees "excluded: redirect map" before signing can decide to add it. A client who discovers it after launch, when search traffic drops, will remember who built the site. If you would rather have a partner carry the build and the nine lines with it, our white-label service page explains how we scope it.
