How to Choose a Webflow Agency: 12 Questions to Ask

TL;DR

Pick the agency that gives you a structured CMS, a clean handoff, and answers about ownership in plain English — not the one with the flashiest reel. Process and post-launch terms matter more than visual taste; almost every shortlisted agency can design a decent site, but only some leave you a system your team can actually run.

Why this guide exists

Most "top Webflow agency" lists are paid placements, sponsored badges, or affiliate-driven roundups dressed as editorial. Those have their place, but they answer the wrong question — they tell you who paid to be visible, not who builds well. This guide is the buyer-side counterpart: once a shortlist exists, these are the twelve questions that separate agencies who ship a site from agencies who ship a system.

The 12 questions

What does a typical Webflow project actually deliver — design, dev, CMS, or all three?

A good answer breaks the scope into named deliverables, not a single "website" line item. Expect them to list design (wireframes, visual design, component library), development (Webflow build, interactions, responsive QA), CMS architecture (collections, references, dynamic pages), and content operations (population, migration, editor training). Some agencies only do dev and expect designs from you; others only do design and partner out the build. Neither is wrong, but the agency should be specific about which side of the line they sit on and who owns the gaps.

Red flag: Vague proposals that bundle "website" as one line item with one number.

Who owns the Webflow project and CMS after you hand it off?

You should — fully, with admin seats, not as a guest collaborator. The agency should transfer the Workspace or Site to your account on launch, hand over editor credentials, and document the CMS schema. Some agencies host the project under their own Workspace and bill you indefinitely for "hosting management" — that's a soft lock-in, because moving the site later means a billing transfer they control. Ownership should be contractual: written into the SOW, with a defined transfer date and no dependency on continued retainer payments.

Red flag: "We host it on our account, you don't need to worry about it."

How do you scope a Webflow build — fixed price, time and materials, or sprint?

Each model has a real use case, and a competent agency picks based on the project shape. Fixed price works when scope is genuinely fixed — a templated rebuild with a known page count. Time and materials fits exploratory work where the design language isn't set yet. Sprint or phased models (often two- to four-week cycles) suit larger marketing sites where requirements shift mid-project. Ask which they default to and why. The answer should be reasoned, not reflexive.

Red flag: Fixed-price quotes given before discovery, or T&M with no ceiling.

What's a realistic timeline for a marketing-site rebuild?

For a 15–30 page marketing site with custom design and a real CMS, six to ten weeks is typical end-to-end; rebuilds with content migration or stakeholder-heavy approval cycles run 12–16 weeks. Anything quoted under four weeks is either a template job or an agency promising what they can't deliver. The timeline should be broken into phases — discovery, design, build, QA, launch — with named gates between each. Ask what slows their projects down most often. Honest answers usually involve client-side feedback delays or copy not being ready.

Red flag: "Two weeks, fully custom" — almost always a template skin.

How do you handle migrations from WordPress, Framer, or hand-coded React?

Migrations are where Webflow projects quietly burn budget, and a good agency will tell you that upfront. Ask how they audit the existing site (URL inventory, redirect mapping, content export), how they handle WordPress's deeply nested taxonomies, and what they do with custom post types that don't map cleanly to Webflow CMS collections. For hand-coded React or Next.js sites, the question is what gets rebuilt versus what gets embedded. They should also have a redirect strategy — 301s mapped one-to-one, not a wildcard redirect to the homepage that obliterates SEO.

Red flag: No mention of redirects or URL preservation in the migration plan.

Who actually writes the copy?

Most agencies don't write copy, and the ones who say they do often mean a junior staffer reformatting your existing site. Clarify this early. A good answer is one of three: (1) you provide copy, on a schedule tied to design milestones; (2) they have an in-house or contracted writer with rates listed separately; (3) they refer you to a copywriter they've worked with. Any of these works. What doesn't work is "we'll handle it" without specifics, because copy is the most common reason Webflow projects slip past launch dates.

Red flag: Copy listed as "included" with no writer named and no process described.

How do you set up CMS collections so the marketing team can ship without you?

The CMS is the difference between a site you own and a site you rent back from the agency. A good build uses logically named collections (Blog Posts, Case Studies, Team, Job Openings) with reference fields connecting related items, multi-reference fields for tags and categories, and Editor-friendly field labels with helper text. Pages should be built so non-technical staff can publish a new case study without touching the Designer. Ask for a walkthrough of a CMS they've built. If they can't show one, or if every content change requires their involvement, the architecture is wrong.

Red flag: "Just send us updates and we'll publish them for you."

What about SEO — technical, on-page, content?

Webflow handles technical SEO reasonably well out of the box, but the agency still needs to do work. Technical: clean URL structures, proper heading hierarchy, sitemap configuration, schema markup where relevant, redirect handling on launch, Core Web Vitals testing. On-page: meta titles and descriptions written or templated per page, OG images, alt text discipline, internal linking patterns. Content SEO is usually out of scope and should be — that's a different practice. A good agency will tell you what they do, what they don't, and which SEO consultants they've worked alongside.

Red flag: Promises of rankings, or no mention of redirect strategy at launch.

What's your retainer model after launch?

A reasonable retainer is optional, scoped to defined work, and cancellable with 30 days' notice. Common shapes: a monthly hour bank (e.g., 10–20 hours for design and dev tweaks), a project-based engagement for new campaigns, or a quarterly review with ad-hoc work in between. The agency should be willing to launch you with no retainer at all if you have in-house capacity. Watch for retainers that bundle hosting, "platform fees," or "maintenance" as required line items — Webflow hosting is paid directly to Webflow, not the agency.

Red flag: Mandatory 12-month retainer as a condition of project handoff.

Do you build with components, or page-by-page?

Component-based builds are the difference between a site that scales and a site that decays. Webflow's components and variables (introduced in 2023–2024) let an agency build a header once, use it across 30 pages, and update it everywhere from one place. Page-by-page builds — where every page has its own copy of the navigation — look identical at launch but become unmaintainable within months. Ask them to show the component library from a recent project. A mature agency will have naming conventions, a documented design system, and global style variables for color and typography.

Red flag: "We build each page custom for maximum flexibility."

How do you track conversion, and who instruments it?

Webflow doesn't track conversions on its own — someone has to instrument GA4, GTM, or a product analytics tool, and define what counts as a conversion. A good agency will ask what your funnel looks like, install the tracking layer, set up event triggers for form submits and key clicks, and verify data flowing into your destination. Some go further with heatmaps or session recording (Hotjar, Microsoft Clarity). The instrumentation should be documented so your team can add events later without re-engaging them.

Red flag: "We'll add Google Analytics" with no mention of events or goals.

What does success look like 6 months in — and what happens if we miss?

A serious agency will push you to define success metrics before kickoff — organic traffic, demo requests, signup conversion, time-on-page for key content — and write them into the SOW. The honest version of this answer acknowledges that a website rebuild alone rarely moves a metric; it's the combination of structure, content, and traffic strategy. Ask what their last three clients' six-month outcomes were, and whether they've had projects that underperformed. Agencies that have only success stories either haven't been around long or aren't telling you the full picture.

Red flag: Guaranteed metric improvements, or no interest in defining success at all.

When you should walk away

Some signals are worth treating as disqualifying. Pay-to-play directory placements aren't a problem on their own, but agencies that lead with badges instead of work usually have thin portfolios. Locked-in maintenance contracts — particularly ones that hold hosting, the Workspace, or the source files hostage — are a contract risk, not a partnership. If the SOW excludes CMS admin access or makes you a guest in your own site, walk. Watch the language: agencies that talk about "passion," "craft," and "partnership" without describing process usually don't have one. And if their portfolio shows only pre-seed startups when you're a Series B, or only enterprise when you're a five-person team, the working relationship will be off from week one.

Frequently asked

What should the contract or MSA actually cover?

A workable MSA defines IP ownership (you own the deliverables on full payment), confidentiality, payment terms, change-order process, and termination rights. The SOW underneath it covers scope, timeline, milestones, and acceptance criteria. NDAs are standard before discovery if you're sharing roadmap or financial information. What's often missing and shouldn't be: a defined transfer process for the Webflow Workspace, source files, and any third-party accounts created during the project. Add it if it's not there.

How do I source agencies in the first place?

Referrals from operators in similar-stage companies are the strongest signal — people who've actually shipped with the agency and can describe what went wrong. Directories help with breadth, conference talks and Webflow's own showcase help with surface area, and case studies tell you what kind of work they actually do. Cross-reference any list against LinkedIn to see who's still on the team — agency quality follows senior staff, and a 40-person shop that lost its design lead last quarter is not the same agency it was.

Should I ask for references, and what do I ask them?

Yes, and ask for references from projects that finished 6–12 months ago, not last week. Recent clients are still in the honeymoon; older ones know whether the CMS held up, whether the agency answered emails post-launch, and whether the site needed a rebuild within a year. Useful questions: what slipped, how did they handle scope changes, what did the handoff look like, would you hire them again for a different project. Vague endorsements ("they were great!") usually mean the reference doesn't want to talk.

Can we split work between an agency and our in-house team?

Yes, and many of the better engagements work this way — the agency handles design and initial build, the in-house team owns CMS publishing, copy updates, and ongoing iteration. The split needs to be defined before kickoff: who has Designer access versus Editor access, who owns which collections, what triggers an agency hour versus an internal task. Without this, the boundary erodes within a month and you're paying agency rates for work your team could do.

Closing

Use the directory's filters to narrow by service mix, project size, region, and industry focus, then run the twelve questions above against the shortlist. The agencies that answer specifically — with named processes, real examples, and honest tradeoffs — are the ones worth a second call. The methodology page describes how listings are evaluated and what the filters mean. A Webflow build is a six- to twelve-week commitment with multi-year consequences for how your marketing team operates; the diligence is worth the week it takes.