By Mehdi HassanWhat questions should you ask a Webflow developer before hiring?
The questions to ask a Webflow developer, or a Framer developer, focus on what makes builder sites succeed or fail after launch: CMS structure, editability and performance. Visual builders make it easy to produce a site that looks finished and is painful to update. These questions find out which kind you'll get.
Use them alongside the general questions to ask a web design agency, which cover scope, copy, contracts and ownership. The questions below are platform-specific and assume you've already checked the basics. For the hiring process itself, see how to hire a Webflow developer or agency.
Which questions test how they structure the CMS?
CMS questions reveal whether the developer designs content models or just pages. A good CMS structure lets your team publish new posts, case studies or landing pages from the editor. A bad one forces a developer into every change.
Question | Good answer | Bad answer |
|---|---|---|
Which collections would you create for our site, and why? | Named collections and fields tied to your content | We'll set up a blog |
How do you handle references between collections? | Explains reference fields and filtered lists with an example | We'll hard-code the related items |
How do you avoid hitting CMS item or field limits? | Knows current plan limits and plans around them | Hasn't considered it |
Can you show the CMS of a live site you built? | Opens the editor and walks through it | Only shows the front end |
How would we add a new landing page ourselves? | Page templates or sections we can reuse | Send us a request |
Plan limits change, so ask the developer to confirm against Webflow's or Framer's current plan page rather than relying on memory. If you're comparing platforms for content-heavy sites, our Webflow vs Framer for agency websites guide sets out the differences.
Which questions test whether your team can edit the site?
Editability questions decide how much the site costs you after launch. If your marketers can't change a headline, swap an image or launch a page without breaking the layout, every small update becomes a paid request.
- Which parts of each page can we edit in the editor? A good developer separates editable content from fixed layout and tells you which is which.
- How do you build reusable sections? In Webflow, components; in Framer, components and variants. Reusable sections mean changes in one place.
- What naming system do you use for classes and styles? A consistent system, such as a documented utility or component naming, keeps the site maintainable by someone else.
- Do you use variables for color, type and spacing? Variables let you adjust the brand across the site without editing every page.
- Will you train our team and leave documentation? A short recorded walkthrough and a written guide are reasonable to expect.
- What can't we change without you? An honest answer names a few things, such as complex interactions, and explains why.
Which questions test performance and SEO?
Performance questions check whether the developer treats speed as part of the build or an afterthought. Builder platforms handle hosting well, but heavy images, too many fonts, large animations and third-party scripts can still make a site slow.
Question | Good answer | Bad answer |
|---|---|---|
How do you keep pages fast on mobile? | Image sizing and formats, font limits, script audits | The platform handles it |
Can you show speed results for a live site? | Shares real Core Web Vitals or a test result | It's fast, trust us |
How do you handle animations and interactions? | Uses them where they help, tests on low-end phones | We animate everything |
How do you set up SEO basics? | Titles, descriptions, Open Graph, sitemap, alt text, clean URLs | SEO is extra |
If we're replacing a site, how do you handle redirects? | A URL map and redirects for every changed URL | Google will figure it out |
Google's guidance on Core Web Vitals explains the metrics worth asking about. If you're moving platforms as well, the Webflow or Framer migration agency guide covers the extra checks a migration needs.
Which questions cover ownership, plans and cost?
Ownership questions protect you from the most common builder-platform problem: a site that lives in someone else's workspace. Cost questions make sure the quote and the ongoing bills are clear.
- Whose workspace will the site be built in? It should be yours, or transferred to you at a defined point.
- Which plan will we need, and who pays for it? Hosting and workspace or seat plans can be billed separately; check the platform's current pricing page.
- Which paid apps, fonts or integrations will we depend on? Each one is a renewal you'll own.
- What is your rate for changes after launch? Compare with Framer expert hourly rates and Webflow website cost.
- If we outgrow the platform, how hard is it to move? An honest developer explains what transfers and what doesn't; see Framer to Next.js migration cost.
Hypothetical example: the same question, two answers
For example, suppose you ask two Framer developers how you'd add a new customer story. The first says: open the CMS, click new item, fill in the title, logo, quote and body, publish. The second says: send me the content and I'll add a new page.
Both sites might look the same at launch. The first is built for your team to run; the second makes you dependent on the developer for every update. This is an illustration of how to read answers, not a real hiring case.
Which non-platform questions still matter?
Platform skill doesn't replace the basics. A Webflow or Framer expert still needs a copy plan, a design source and a clear scope. Ask who writes the words, whether they design or only build from your Figma, and who owns brand decisions.
If the developer only builds, you'll need a designer and a writer, and someone to own the handoff between them. If you also need brand work, use branding questions to ask before hiring a designer and check logo design cost for that budget. For subscription-based design partners, use questions to ask a design subscription.
How do you compare the answers?
Compare developers on evidence, not confidence. The best signal is a live site where they open the CMS and the builder and walk you through it. Rank candidates on three questions: can your team edit what they built, is it fast on mobile, and do you own the workspace.
