Webflow development services cover five jobs: design, the build, the CMS, integrations and the handover. The platform sets hard edges on each one. The Premium site plan holds up to 20,000 CMS items in 40 collections, an inline script registered through the API is capped at 10,000 characters, and the Data API allows 60 or 120 requests a minute depending on the plan, all according to Webflow's own pricing page and developer documentation. A good service is one that knows where those edges are before it quotes.
This guide explains what each of the five parts should deliver, where native Webflow stops and custom code begins, and the acceptance test that tells you a part is finished. Platform facts come from Webflow's pricing page and developer documentation, read on 2026-11-05; performance and search rules come from Google.
The five parts of a Webflow development service
Most buyers think of Webflow development as "turning the design into a site". That is one part of five, and each part is priced in different units.
| Part | What the team does | What you receive | Priced in |
|---|---|---|---|
| Design | Page layouts, components and states in Figma, desktop and mobile | Figma file with a component library | Unique layouts, review rounds |
| Build | Classes, variables, components, responsive behaviour, interactions | Staging site you can click through | Static pages, templates, named interactions |
| CMS | Collections, fields, references, template pages, content entry | Content model document and filled collections | Collections, templates, items migrated |
| Integrations | Forms, CRM, analytics, consent, scheduling, custom code | Tracking map: every form and event, where it lands | Named tools, custom features |
| Handover | Workspace transfer, editor guide, walkthrough, fix window | Site in your Workspace, guide and recording | Deliverables listed |
Source: Octo Agency service structure; platform units from Webflow, Plans and pricing, read 2026-11-05.
A team that only builds from your Figma file is selling one of these five, which is fine as long as someone else owns the other four. Our guide on how to brief a Webflow agency shows how to describe these parts on one page.
Design: what a Webflow-ready design looks like
A design made for Webflow is made of components. Each repeated section, card and button exists once, with its states (hover, focus, empty, long text) drawn out, so the build can reuse it instead of copying it.
Breakpoints. A design that shows desktop and mobile for every unique layout, and says what happens in between, saves the build team from guessing.
Design tokens. Colours, type sizes and spacing should be named in Figma as they will be named as Webflow variables, so a brand colour change later is one edit.
Motion. If the design has animation, it should say what moves, on what trigger and on which breakpoints.
Acceptance test. Pick any section on any page and find it in the component library with its states. If it is not there, the design is a set of pictures, not a system.
Build: classes, components and the staging site
The build turns the design into classes, variables and components on a staging site, and decides how easy the site is to change for the next three years.
A class system, written down. Sites drift when every new section invents its own classes, so a build should follow a named convention. Webflow documents its own Flowkit framework, which its developer documentation now describes as legacy; other teams use Client-First or their own. Which one matters less than having one.
Components with props. Repeated sections should be Webflow components with editable fields, so a marketer can change a heading without detaching the component.
Interactions. Webflow acquired GSAP in late 2024 and made it 100% free in April 2025, according to its announcement, and its Interactions page lists ScrollTrigger, SplitText and staggers in the Designer. The cost now is performance. Every animation should be checked against Google's Core Web Vitals, which web.dev sets at 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint and 0.1 for Cumulative Layout Shift, measured at the 75th percentile of page loads.
Acceptance test. Ask the team to add a new page from existing components while you watch. If it takes more than a few minutes, or needs new classes, the component library is not finished. Then run the home page and one template through PageSpeed Insights on mobile.
CMS: collections, references and the limits that shape them
The CMS is where Webflow development services differ most between teams. A blog is an afternoon; a resource library with authors, categories and cross-references is a modelling job that is expensive to undo once content is in.
| Limit | Value | Where it bites |
|---|---|---|
| CMS items per site, Premium plan | 20,000 | Large resource libraries, location pages, programmatic SEO |
| Collections per site, Premium plan | 40 | Sites that model every content type as its own collection |
| Fields per collection, Team plan | 100 fields, 20 reference fields | Rich templates with many optional blocks |
| Static pages, Basic plan | 300 | Sites without a CMS that keep adding landing pages |
| Data API requests per minute | 60 on Starter and Basic, 120 on CMS, eCommerce and Business | Bulk imports and scripted migrations |
| Cheapest plan with the CMS | Premium, $25 a month billed yearly | Any site with a blog or resource library |
Source: Webflow, Plans and pricing, and Webflow Developers, Rate limits, both read 2026-11-05.
Our largest CMS for a white-label partner holds over 1,200 items. That is well inside the ceiling, but big enough that the import had to be scripted and paced against the API rate limit rather than pasted in by hand.
Model before you build. Each collection should exist because it has its own template page or filter; content that only appears inside another page is usually a field. Our post on the five-collection model for a B2B site covers the structure we would start from.
Content entry is a separate line, with an item count per collection and a named owner. If the site replaces an old one, Google's site move guidance says to map every old URL to a new one and keep redirects for as long as possible, generally at least a year.
Acceptance test. Ask for the content model document: every collection, every field, what it renders and whether it is required. Then create one item yourself in each collection. If you cannot do it without asking a question, the model or the document needs work.
Integrations: forms, tracking and where custom code starts
Integrations are the part the design never shows, and where most post-launch problems come from, because they depend on accounts outside Webflow.
| Need | Native in Webflow | When it needs more | What that means |
|---|---|---|---|
| Forms and notifications | Forms, notification emails, CSV export; unlimited submissions from Basic | Routing to a CRM or another system | Webhook on the form_submission trigger, an app or a CRM embed |
| Animation | Interactions built on GSAP | Bespoke scroll scenes or canvas work | Custom GSAP code in an embed or page script |
| Reusable interactive widgets | Components with props | Calculators, configurators, stateful UI | React code components, from the Premium plan |
| Site-wide scripts | Custom code in site and page settings | Scripts managed by an app through the API | Inline scripts up to 10,000 characters, or hosted scripts with an integrity hash |
| Translation | Localize add-on from $9 a month, by locale | Locales beyond the add-on tier | Advanced or Enterprise Localize |
| Logins, databases, server logic | Not part of a marketing site | Portals, dashboards, gated tools | Webflow Cloud app (Next.js, Astro, Vite) or a separate application |
Source: Webflow, Plans and pricing; Webflow Developers, Custom code, Working with webhooks, Code components and Webflow Cloud; all read 2026-11-05.
Forms. Webflow's Basic plan lists unlimited form submissions; the free Starter plan allows 50. Webflow's webhook documentation shows a form_submission trigger that can be filtered by form name, which is how a build sends one form to the CRM and another to a support inbox.
Custom code. Scripts registered through the Data API follow Webflow's rules: inline scripts are limited to 10,000 characters each, and hosted scripts need a URL and an integrity hash. Every script belongs in the tracking map with an owner.
Code components. From the Premium plan, Webflow supports React code components that designers place on the canvas with props and slots, imported through DevLink. This is the right home for a pricing calculator that used to be a fragile embed.
Where Webflow stops. Webflow Cloud now hosts Next.js, Astro, Vite and static apps alongside a Webflow site, with SQLite, key-value and object storage, according to Webflow's developer documentation. For a full product, a separate application is usually still cleaner. Our comparison of Webflow and Next.js for a marketing site sets out how we decide, and we should say the bias plainly: we build marketing sites in Webflow and applications in Next.js, so we have an interest in both answers.
Acceptance test. Ask for the tracking map, then submit every form and trigger every tracked event on staging with the analytics debug view open. Each one should land where the map says it does.
Handover: what you should own on launch day
The handover decides whether you need the development team again for small changes, and it is the part most often cut when a project runs late.
The site, in your Workspace, with its site plan and domain, or in the agency's Workspace under a written agreement. Webflow's pricing page notes that code export produces HTML and CSS but not CMS items or pages, so the site is not fully portable.
The documents. A content model document, a page-building guide, the tracking map and a QA record. Our Webflow client handover kit lists the settings and scripts we would check before the transfer.
The recording and the fix window. A short walkthrough of editing and publishing, plus a defined period after launch for bugs, with a written definition of a bug.
Acceptance test. Someone on your team who did not attend any build calls publishes a new CMS item and a new page from components, using only the guide and the recording. If they get stuck, the handover is not done.
How long each part takes
Design and build take most of the time; the CMS and integrations run alongside the build. We have built 20 or more Webflow sites in twelve months as the white-label partner behind Web Tonic, at two to three weeks per site, usually working from a finished design. When we run design as well, we work to a four-week process; our week-by-week four-week Webflow build shows where each part falls and which decisions have to be made by the end of each week.
What stretches those timings is rarely the build: it is late content, a CMS model that changes after entry starts, or an account nobody can log into. We quote per project, because a five-page site and a 1,200-item CMS migration are different jobs.
What this means for buying Webflow development services
Ask for a quote that lists all five parts separately: design, build, CMS, integrations and handover. For each one, ask what you will receive and how you will test it. A team that can name the deliverable and the acceptance test for every part has done this before; a team that can only name a total and a launch date is pricing the build and leaving the other four to luck. If you want a team that carries all five parts on a Webflow marketing site, our marketing websites service page explains how we scope it.
