15 Questions to Ask Before Hiring a Webflow Developer

TL;DR: Ask a Webflow developer about ownership, build structure, and post-launch support before anything else. If you only have time for four questions, ask these:

• Whose Webflow Workspace will the site live in?
• If we part ways, how does the site get transferred to us?
• What Core Web Vitals will the site hit on mobile?
• What is explicitly out of scope?

Clear, specific answers to those four usually predict the other 11. Vague answers are the strongest early warning you will get.

I work as a Webflow lead developer for agencies and end clients, so I have been on the answering side of this conversation many times. Good developers answer ownership, handoff, and performance questions immediately and without hedging.

Ownership and access: 4 questions people forget to ask

Ownership questions carry the most risk and get asked the least. Almost nobody raises them until the relationship is already ending, which is the worst possible moment.

1. Whose Webflow Workspace will the site live in?

The safe answer is yours. A site built inside the developer's Workspace can only move later with their cooperation, which turns a routine offboarding into a negotiation.

2. If we part ways, how does the site get transferred to us?

Webflow supports a real site transfer that moves the paid Site plan and custom domain with no downtime. Only Workspaces on a Freelancer or Agency plan can transfer a site carrying a paid Site plan to a client, and the receiving Workspace cannot be an Enterprise Workspace (Webflow Help Center). A developer who has done it will describe the steps in one breath.

3. Who pays Webflow directly?

The client should hold the billing relationship. On the projects I lead I set Site plans up on the client's own card, so nobody can be locked out of their own website over an invoice dispute.

4. How will you keep access after handoff?

Through Webflow's Agency or Freelancer guest role, not a shared login. A client Workspace can invite up to 2 guest teams free, or up to 10 on an Enterprise Workspace plan, and each guest team can bring up to 5 members (Webflow Help Center).

How they build: 5 questions that shape your next two years

Build-structure answers decide how much you pay a developer after launch. A site assembled without conventions costs more every time you touch it, and that cost compounds silently.

5. What class naming system do you use?

Client-first, a documented in-house system, or Webflow variables plus a consistent convention are all acceptable answers. "I name things as I go" is not, because it means nobody else can maintain the site.

6. Which parts will be editable in the CMS, and which are hardcoded?

Ask for this as a written list before the build starts. In my experience most change requests after launch are really the sentence "this should have been a CMS field", discovered too late.

7. How are components and variables set up?

Reusable components and site-wide variables are the difference between a rebrand taking 2 hours and taking 2 weeks. Ask to see a style guide page from a previous build.

8. What will the CMS structure look like?

You want collections mirroring how your business thinks about content, not one "Pages" collection with 40 fields. I cover the tradeoffs in my guide to Webflow CMS structure.

9. What custom code will the site depend on, and who maintains it?

Some custom code is unavoidable and healthy. What matters is that it is documented, minimal, and not a black box that only one person understands.

Performance and AEO: 3 questions with objective answers

Performance is measurable, which means it can be committed to in writing. A developer who refuses to name a target has usually never measured one on a live site.

10. What Core Web Vitals will the site hit on mobile?

Google's "good" thresholds are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less, measured at the 75th percentile of real visits (web.dev).

11. How do you handle redirects from the old site?

The answer must include a URL-by-URL mapping of existing pages, produced before launch rather than after. Without it, expect a traffic drop in the first weeks.

12. What is your approach to structured data?

Webflow has a native Schema markup field in Page Settings for static and Collection pages, with one-click AI generation, on any paid Site or Workspace plan (Webflow Help Center). Anyone claiming Webflow needs custom code for basic schema is working from outdated information.

Scope and money: 3 questions to settle before signing

Commercial questions are where proposals quietly differ. Two quotes at the same price can describe completely different amounts of work once you read what each excludes.

13. What is explicitly out of scope?

The out-of-scope list tells you more about a proposal than the in-scope list does. Ask for it in writing, and treat a missing one as an unpriced risk you will absorb later.

14. What does a change request cost and how fast is it done?

Get a rate and a response time in writing before you sign. Post-launch friction is what kills otherwise good projects, usually around month three.

15. What do the first 30 days after launch look like?

You want a warranty window for bugs, a recorded walkthrough for your editors, and a named person to contact. If none of that is offered, add all three to the contract.

The Webflow numbers worth knowing before the call

Knowing what Webflow itself costs lets you separate platform cost from developer cost when you read a quote. These figures come from Webflow's own documentation:

• Basic Site plan: $15 per month billed yearly, $25 billed monthly, 300 static pages (Webflow)
• Premium Site plan: $25 per month billed yearly, $39 billed monthly, 20,000 CMS items and 40 CMS Collections
• Team plan: annual contract, 100 CMS Collections, 10 seats, and CMS API rate limits 5 times higher than self-serve
• Pricing effective dates: new purchases from 13 May 2026, most existing sites from 29 June 2026, Freelancer and Agency Workspaces from 16 November 2026
• Dynamic content limits: 40 Collection lists per page, 10 nested lists per page, 100 items per list without pagination (Webflow Help Center)

If a quote bundles hosting into a large monthly retainer, ask what portion is the Site plan. If someone promises an unpaginated directory of 5,000 items on one page, they have not read the limits.

Which questions to ask a Webflow developer first

You do not need all 15 in one call. Start with questions 1, 2, 10 and 13, covering ownership, exit, performance and scope. If those four come back clear and specific, the rest usually will too.

If you want a second opinion on a proposal you have already received, or a Webflow lead developer who will answer all 15 of these in writing, get in touch and I will take a look. Related reading: how to hire a Webflow developer and freelance developer vs agency.