Webflow Development Services: What's Included and What Isn't

Webflow development services means one thing: someone builds your site in Webflow. Everything else — the design, the copy, the domain, the hosting subscription, the ongoing updates after launch — depends entirely on how the engagement is scoped. Most disputes between clients and developers trace directly back to this confusion. Both sides assumed different things were included, nobody wrote it down, and now the invoice looks wrong.

I’ve done 40+ Webflow projects. Here is exactly what a standard engagement covers, what costs extra, and what nobody will do for you unless you explicitly ask. If you already know what you need and want to skip the reading, get in touch. If you’re still deciding whether to hire a Webflow developer at all, start there first.

What the term actually means

“Webflow development services” has no formal definition. Every developer, agency, and freelancer marketplace uses it to mean something slightly different. In practice, what you’re buying is technical implementation in Webflow — translating a design into a functional, responsive, published website on Webflow’s platform.

What that doesn’t automatically include: the design itself, the words on the page, the images, the hosting bill, the ongoing maintenance, the SEO strategy, and the email marketing setup. Those are adjacent services that can absolutely be bundled into a contract — and often should be — but they don’t come standard.

The reason this matters: if you go into an engagement expecting the developer to handle design because the proposal said “we’ll build your Webflow site,” you’ll be frustrated. If the developer goes in expecting final Figma files and receives a PDF mood board and some vague direction, the project will stall at week one. Scope clarity before kickoff is the single biggest predictor of a smooth Webflow engagement.

Scope map: what’s in, what’s out

Here is how a typical senior Webflow freelancer structures a standard engagement. Agencies often bundle more; junior developers often cover less.

Area	Included	Add-on	Not included
Build from Figma files	Yes	—	—
Responsive implementation (all breakpoints)	Yes	—	—
CMS collection setup + content entry	Schema only	Full data entry	—
On-page SEO (titles, metas, alt text, H-structure)	Yes	—	SEO strategy/keyword research
Native Webflow form setup	Yes	—	—
Google Analytics / Tag Manager install	Yes	—	—
Webflow hosting configuration	Setup only	—	Pays the subscription
Design (Figma files, visual direction)	—	Yes (+$2,500–$8,000)	—
Copywriting	—	Yes (+$1,500–$5,000)	—
Custom JavaScript / advanced animations	—	Yes (hourly)	—
CRM / email marketing integration	—	Yes (+$500–$2,000)	Platform strategy
A/B testing infrastructure	—	Yes (hourly)	—
Post-launch content updates	—	Retainer	—
Domain purchase	—	—	Yes — you buy it

The “Add-on” column is where most scope surprises hide. Design and copy are the two biggest. I’ll address each of those directly below.

For a detailed breakdown of what drives the numbers in this table, the Webflow developer cost guide breaks down exactly where project budgets go.

Design handoff: what a good dev expects from you

The most important thing to understand about Webflow development services: most Webflow developers are builders, not designers. They’re skilled at translating a Figma file into a fast, responsive, technically sound website. They are not skilled at creating that Figma file from scratch — at least not at the level you’d expect from someone whose primary discipline is design.

If you arrive at kickoff without a design, you have three options:

Option 1: You hire a designer separately. The developer works from finalized Figma files once design is approved. Clean separation of roles, predictable scope. This is how the best Webflow projects run.

Option 2: You work from a Webflow template. A developer can customize a purchased template significantly — sometimes so much it’s unrecognizable. This works well for projects under $6K where the original template structure is a reasonable starting point.

Option 3: You hire a dev who also does design. A small percentage of Webflow specialists do both well. Expect to pay more ($90–$150/hr) and to have fewer samples of each discipline to evaluate. The upside is tighter Figma-to-Webflow parity; the downside is that “does both” often means “is mediocre at one.”

For a complete list of what a developer needs from you before a single element is placed in Webflow, read the Figma to Webflow handoff guide. The short version: final approved Figma with Auto Layout, named frames for every page and state, exported assets at the right formats, and a written brief confirming breakpoints and interactions.

The word “final” matters. I’ve had clients send “almost final” files that changed three times during build. Every design revision mid-build costs 2–4 hours of rework at minimum. Lock design before build starts, or agree explicitly on a change-order rate for revisions.

CMS setup: the piece most people underestimate

CMS setup is listed as “included” in most Webflow development proposals. What’s actually included varies enormously, and what isn’t can derail a project weeks in.

What “CMS setup” typically covers: defining collection schemas (field names, field types, required fields), building the CMS-powered templates, wiring dynamic lists and filters, and configuring the content editor so your team can add posts without touching the Designer.

What it often doesn’t cover: migrating existing content from WordPress or another CMS, populating hundreds of existing blog posts or case studies, building custom import workflows, or designing the editorial workflow for ongoing content creation.

The decisions that matter most: collection depth (reference fields vs. multi-reference, nested collections vs. flat), field limits (Webflow caps collections at 20 custom fields before you have to restructure or split), and how the Editor experience works for non-technical content managers. A CMS that’s technically correct but unusable for your marketing team is a failed CMS.

On real projects, I budget 8–15 hours for CMS architecture on a mid-size site — scoping the schema, reviewing it with the client, building it, and then testing content entry before handing over to the team. Proposals that include “CMS setup” in two hours are not building a real CMS structure; they’re dropping a collection in and hoping for the best.

Integrations: forms, analytics, email, payments

Webflow has a native integration ecosystem — Logic for form routing, Memberstack for auth, Webflow Commerce for simple e-commerce, Finsweet’s Filter for client-side filtering, Outseta for membership and billing. And then there’s everything outside that ecosystem that requires custom embeds, Zapier, or a Make workflow.

Here’s how to think about what’s in scope:

Always included in a standard engagement:

• Webflow’s native contact form with email notifications
• Google Analytics 4 (GA4) tag installation via code embed or Tag Manager
• Google Tag Manager container setup
• Webflow site search (if the plan supports it)

Commonly add-on (quoted separately, typically $500–$2,000 per integration):

• HubSpot form-to-CRM sync
• Mailchimp / ConvertKit list sign-up forms with automation triggers
• Calendly or Cal.com embed (this is straightforward; rates at the low end)
• Intercom or Crisp live chat installation
• Stripe payment links (distinct from full e-commerce)
• Airtable or Notion sync via Zapier/Make

Not in scope unless explicitly contracted:

• Full e-commerce with inventory, variants, discount logic, and checkout customization
• Membership gating and login-protected pages (requires Memberstack or Outseta; the integration scope is significant)
• A/B testing with tools like VWO or Optimizely
• Custom webhook endpoints or serverless function builds
• Any integration that requires backend code

Payment integrations are particularly worth discussing upfront. “We’ll add Stripe” can mean anything from a payment link button ($500 scope) to a fully custom checkout with product variants, discount codes, and subscription billing ($8,000+ scope). Define “payments” in writing before signing.

SEO + launch checklist

On-page SEO is standard in a Webflow engagement. Technical SEO infrastructure beyond the basics is not. Here’s the line I draw:

What a developer handles as part of a standard build:

• Page titles and meta descriptions on every page (you provide the copy; they implement it)
• Open Graph tags for social sharing
• Alt text on all images (you provide the text; they add it)
• Heading hierarchy (H1 → H2 → H3 in logical order)
• Canonical tags
• Clean URL structure (no trailing parameters, no duplicate pages)
• 301 redirects from old URLs to new ones (if migrating)
• robots.txt and sitemap.xml via Webflow’s built-in generator
• Schema markup on key pages (this varies — some developers do it, some don’t; ask)

What’s not included without an explicit line item:

• Keyword research and content strategy
• Competitor gap analysis
• Backlink acquisition or outreach
• Content optimization beyond on-page structure
• Core Web Vitals remediation beyond standard Webflow optimization practices
• Google Search Console setup and monitoring after launch

A word on Webflow’s Lighthouse scores: Webflow’s default export is not automatically fast. A developer who knows what they’re doing — stripping unused fonts, lazy-loading below-the-fold images, removing heavy Lottie files, optimizing video embeds — can hit 88–94 on mobile consistently. A developer who just publishes whatever Webflow generates might hand you a 62. Ask specifically about mobile Lighthouse scores in their recent work.

For the full pre-launch and handoff checklist, the Webflow handoff checklist covers every step from final QA through DNS cutover and post-launch monitoring. Print it out and walk through it with your developer before you sign off on delivery.

Post-launch: what an ongoing relationship covers

Launch is not the end of a Webflow project. It’s the end of the build phase. What happens after depends on how the ongoing relationship is structured.

The most common post-launch arrangements:

Ad hoc / hourly. You reach out when something needs changing. The developer invoices at their hourly rate. Works for infrequent updates — a new landing page every quarter, the occasional content fix. Breaks down when you need fast turnaround or someone to proactively notice issues.

Monthly retainer. A fixed number of hours reserved each month — typically 10–40 hours at $1,500–$5,000/month. Covers new pages, CMS updates, SEO work, A/B test setup, and bug fixes. The developer is effectively your part-time Webflow team. For B2B SaaS companies shipping new landing pages every month, this is the right model.

Support-only retainer. A lighter arrangement — a few hours per month for bug fixes and small updates, not new feature development. Typically $500–$1,000/month. Useful as a bridge while your team learns to manage the CMS themselves.

What’s rarely covered in any retainer without explicit discussion: major redesigns, building new sections that require significant design direction, custom integrations that weren’t part of the original build, and CMS restructuring (see the CMS section above — this is a significant rebuild, not a maintenance task).

The decision between a project-based relationship and a retainer isn’t about preference — it’s about how often your site needs to change. The retainer vs project model breakdown walks through the calculation for five common business types. If you’re shipping marketing pages once a month or more, the retainer math almost always wins.

My own project work shows what a well-scoped, fully documented build looks like before it’s handed off — whether the client takes it from there or continues with an ongoing arrangement.

One practical note: the best time to negotiate a post-launch retainer is during the initial engagement, not after launch. At that point, the developer knows your site architecture cold, the handoff is tight, and there’s no ramp-up time. Post-launch rates negotiated pre-launch are almost always better than going back to the market after the build is done.

The rule of thumb I’d leave you with: if your site generates revenue or drives leads, budget for 10 hours per month of Webflow maintenance from day one. Something always needs updating — whether it’s a CRO test on the homepage, a new pricing tier, or fixing the one interaction that broke on iOS after a Webflow update. That 10 hours is insurance. The alternative is a site that silently decays while you’re focused on something else.

Frequently asked questions

What's typically included in Webflow development services?

Build from design files (Figma handoff), CMS setup, responsive implementation, basic on-page SEO, form/analytics integration, and launch. Design, copywriting, and advanced integrations usually cost extra.

Does Webflow development include design?

Not by default. Most Webflow developers are builders, not designers. If you need design, you either hire a designer separately, use a template, or hire a full-service agency that bundles both.

Does Webflow development include copywriting?

Almost never. Copy is your responsibility. A few devs offer content strategy or light editing as an add-on, but expect to deliver final copy before build starts — or pay $1,500–$5,000 extra for a copywriter.

What about Webflow hosting — is that part of the service?

Hosting is a separate Webflow subscription ($14–$39/mo) billed to you. Developers typically set it up for you but don't pay for it on your behalf. Some agencies resell hosting with a markup.

How long do Webflow development services take?

A landing page: 3–5 days. A 10-page marketing site: 2–4 weeks. A CMS-heavy marketing site: 4–8 weeks. Exact timelines depend on how ready your content is.

What isn't included that people assume is?

SEO strategy (as opposed to on-page implementation), ongoing content updates after launch, custom JavaScript/animations beyond Webflow's built-ins, email marketing integration beyond a single form, and A/B testing infrastructure.