How to hire a Webflow developer: what to check and ask.

If you are about to hire a Webflow developer, the hard part is not finding someone who can use Webflow. Plenty of people can drag elements onto a canvas. The hard part is telling apart a developer who will hand you a site your team can run for years from one who will hand you something that looks right on launch day and becomes painful to change. This guide covers what to look for, what to ask and how to check a portfolio properly.

What does a Webflow developer actually do?

Webflow is a visual tool, so the line between design and development is blurrier than on other platforms. In practice, a Webflow developer takes a design (usually from Figma) and turns it into a working site: page structure, styles, components, CMS collections, interactions, forms, SEO settings, custom code where Webflow does not cover a need, and publishing to your domain.

The work you do not see matters most. Two sites can look identical in a browser while one is built from tidy, reusable classes and components and the other is a tangle of one-off styles. The difference shows up months later, when someone needs to add a page or change a button colour across the site.

What good Webflow development looks like

A class naming system they can explain

Webflow styles elements through classes, and without a plan those classes multiply quickly. Experienced Webflow developers usually follow a naming system. One widely used option is Client-First, a free convention published by Finsweet that combines descriptive custom classes (for example hero_content-wrapper) with a set of shared utility classes for spacing and typography. Others use their own structured approach based on similar ideas.

Which system they use matters less than whether they use one consistently and can explain it. Ask them to walk you through how they name classes and why. A clear answer suggests your site will still make sense to the next person who opens it.

CMS structure planned before pages

Webflow's CMS stores repeatable content such as blog posts, case studies, team members or locations in collections, each with its own fields. A careful developer works out the collections, fields and references before building templates, because changing them after content has been entered is slow. If your site has any repeating content, ask how they would structure it. You can see more on how we approach this in our Webflow CMS work.

Interactions with a purpose

Webflow interactions let developers animate elements on scroll, hover, click and page load without writing code. Used well, they guide attention. Used heavily, they slow pages, distract readers and can cause problems for people who are sensitive to motion. A good developer will suggest fewer, quieter animations and will think about how the page behaves when motion is reduced.

Accessibility built in

Webflow gives developers control over semantic HTML, heading levels, alt text, focus states and ARIA attributes, but it does not apply them for you. Look for someone who works towards WCAG 2.2: proper heading order, real buttons and links rather than clickable divs, visible focus styles, sufficient colour contrast, labelled form fields and menus that work with a keyboard. Our guide to website accessibility basics covers what to expect.

A site your team can edit

Most businesses choose Webflow partly so their marketing team can update content without a developer. That only works if the build allows it. Ask how editors will add a new blog post, swap an image or create a landing page, and whether the developer will show your team how to do it.

Questions to ask before you hire a Webflow expert

• "Can you share the read-only link to a past project?" Webflow lets site owners share a read-only version of a project. Seeing inside a build tells you far more than the published site.
• "Which class naming system do you use, and why?" Listen for consistency and reasoning, not a particular brand name.
• "How would you structure our content in the CMS?" Even a rough answer shows whether they think about content before layout.
• "When do you use custom code?" Good answers name specific cases, such as third-party scripts, structured data or features Webflow does not offer natively, and mention keeping that code documented.
• "How do you check accessibility and performance before launch?" Look for named checks: keyboard testing, contrast checks, Lighthouse or PageSpeed Insights, testing on real phones.
• "What will you hand over at the end?" Expect the site transferred to your workspace, any custom code documented and a short guide for editors.
• "How do you handle redirects if we are moving from another platform?" Anyone replacing an existing site should talk about mapping old URLs to new ones.

How to check a Webflow portfolio

A polished screenshot proves very little. Open the live sites and look a bit deeper.

1. 1 Open each live site on your phone and scroll through every section.
2. 2 Press the Tab key on a desktop and check you can see where the focus is as you move through links and buttons.
3. 3 Run a page through PageSpeed Insights and note whether the developer can explain the results.
4. 4 Right-click an image and check whether it has meaningful alt text in the page source.
5. 5 Open a blog post or case study and check it looks like a template built from CMS fields, with consistent layout across items.
6. 6 Ask for a read-only link and look at the class names in the Navigator and Style panel.
7. 7 Ask what the developer built themselves on each site, as opposed to the designer or the client team.

Freelancer, agency or in-house?

Each option suits a different situation. This is a neutral comparison, not a recommendation.

Whichever route you choose, matters such as contracts, who owns the work and the Webflow project, and tax on paying someone in another country depend on your situation. Check these points carefully and take professional advice where needed.

What affects the cost of Webflow development?

Quotes for Webflow projects can vary a lot, and that is usually down to scope rather than skill alone. The main factors are:

• the number of unique page layouts, as opposed to pages built from the same template
• how many CMS collections there are and how they relate to each other
• the amount and complexity of interactions
• integrations with CRMs, forms, booking tools or other systems
• whether the design is finished or still needs work
• content migration from an existing site, and redirect mapping
• localisation into other languages with Webflow Localization
• whether ongoing support is included

A clear brief narrows the gap between quotes. Our guides on writing a website brief and comparing website quotes walk through both steps.

Warning signs to watch for

• No read-only links or examples of the inside of a build.
• Vague answers about class naming, or none at all.
• Heavy page-load animations on every portfolio site.
• No mention of redirects when replacing an existing site.
• Plans to build the site in their own workspace with no clear transfer to yours.
• Promises of specific rankings or traffic. Nobody can promise these honestly.

A short hiring checklist

1. 1 Write a brief listing your pages, repeating content and integrations.
2. 2 Shortlist developers whose live sites work well on a phone.
3. 3 Ask each one for a read-only link to a past project.
4. 4 Ask how they would structure your content in the CMS.
5. 5 Ask which class naming system they use.
6. 6 Ask how they test accessibility and performance.
7. 7 Confirm what will be handed over and where the project will live.
8. 8 Agree how changes after launch will be handled.

Web Canvas builds sites on Webflow as part of our web development work, and you can read more about our Webflow development approach. If you would like to talk through your project or get a second opinion on a quote, get in touch.