How to Hire a Webflow Developer (Without Getting Burned)

I've been hired to fix enough Webflow sites to have a decent view of what goes wrong when the wrong person builds them. Almost none of those projects failed because the developer couldn't make things look right — the screenshots were usually fine. They failed on the parts you can't see in a portfolio: a CMS nobody could edit, a class structure nobody could extend, a site that quietly tanked in Google after launch. So here's what I'd actually check.

Look past the screenshots

A portfolio proves someone can produce a nice-looking page. It doesn't prove the site works. So open the live sites, not the case study images, and poke at them: resize the browser to an awkward in-between width, tab through the page with your keyboard, run one through PageSpeed Insights on mobile. A developer who cares about the invisible parts will hold up under thirty seconds of that. One who doesn't, won't.

The questions that actually separate people

Skills lists all look the same on a profile. These questions don't have a memorised answer, which is exactly why they're useful:

• How do you structure CMS collections — and how would you handle content that needs to relate to other content?
• What's your class naming approach, and could another developer pick this up after you?
• Will my team be able to add a new landing page without calling you?
• How do you handle URL structure and redirects if we're replacing an existing site?
• What happens after launch — what's included, and what's billed?

The CMS question is the one I'd weight heaviest. It's the single most common thing I get called in to unpick, and the answer tells you instantly whether someone builds for launch day or for two years from now.

Red flags I'd take seriously

• A portfolio of template reskins presented as custom work — check if the layouts all feel suspiciously similar
• No questions about your content, your goals, or who edits the site afterwards
• A quote given instantly, with no scope conversation — that number will move
• Vagueness about who owns the Webflow project after launch
• "SEO included" with no detail on what that actually means

Freelancer or agency?

Both work; they solve different problems. A freelancer is usually the better value for a focused marketing site, a landing page, or a redesign — you talk to the person doing the work, decisions happen in a message rather than a meeting, and you're not paying for account management. An agency earns its premium when scope is large, timelines are tight enough to need several people in parallel, or you need guaranteed cover when someone's on holiday. Rates reflect that: freelancers commonly sit around $50–100/hour, agencies roughly double that.

The honest version, since I'm a freelancer and you should discount accordingly: if your project genuinely needs five people, hire an agency. If it needs one good one, hiring five is just overhead.

Ask to see something after launch

The most revealing request you can make: ask to see a site they built a year or more ago, and ask what the client has changed since without their help. A developer who builds properly will have an easy answer — the client has been publishing away in the CMS. A developer who doesn't will change the subject. That one question tells you more than the entire portfolio.

What you should expect to pay

See how I build — real projects, live sites