How to choose a Webflow developer

A portfolio shows how a site looks. Two sites can look identical and be completely different to live with: one your marketing team can update, one that needs a developer for every change. These questions get at the work behind the screenshots.

Ask how they organize the build

Ask to be shown how they organize classes, components and CMS content in a recent project. They should be able to explain the system, how the reusable pieces work, and how another developer would pick it up.

A named convention like client-first helps, and the implementation matters more than the label. What you are listening for is whether there is a system at all, because a site built without one accumulates near-duplicate styles and gets slow to change.

The same question, two answers

Answer to follow up on

• "We keep it clean" with nothing behind it
• Cannot show the system in a real project
• No view on how styles get reviewed
• Talks about the design, not the structure

Answer to trust

• Shows the system in a project they built
• Explains how unused styles get reviewed and documented
• Distinguishes a component from a page
• Asks what you will need to change yourself

Ask who edits it afterwards

Get concrete. Name a change you will realistically want (a new case study, a section reordered on a landing page, a stat updated in three places) and ask exactly who does it and how long it takes.

The revealing part is the third one. If the answer involves editing three separate pages, that value was typed rather than structured. Structured content lives in a collection, and shared values can live in a reusable component or a site-wide setting instead. What you want to establish is which changes your team can make, where the shared content is managed, and what still needs a developer.

Ask what happens to your existing URLs

If anything is being migrated, ask how they will inventory the existing addresses, which paths they will preserve, how the changed ones get redirected and what gets checked after launch. Redirects are one part of protecting search visibility: the content, the internal links, the metadata and whether pages can be indexed all matter too.

A developer who has done this will ask to see your current URL structure before quoting. One who has not will say “we’ll handle SEO”.

Ask what fits Webflow and what does not

Ask which of your requirements fit Webflow’s native features, which need an integration or application code, and which might be a reason to use something else. A useful answer works through the tradeoffs for your project rather than reaching for a rule.

The honest version of my own answer is on the migration pages, which say what does not carry across, and on the integration pages, which say what needs a decision before the build.

Someone who says Webflow does everything has either not hit its limits or will discover them mid-project, on your schedule.

On price

A quote you cannot compare is a quote you cannot evaluate, which is why I publish mine. Compare the exclusions, the assumptions and the ongoing costs alongside the number: how to read a gap between two quotes goes through that separately.

A quote that has not accounted for the integrations or the migration is an opening position rather than a price.

Take this with you

10 questions to ask a Webflow developer

In the order I would ask them. None of them needs you to know Webflow. What you are listening for is whether the answer is specific, and whether it comes with something they can show you.

1. What naming convention do you use for classes, and why that one?

   A system decided once is what keeps the site editable in two years. What matters more than the name of the convention is whether they can show it working in a project.

   Worry if you hear They cannot show or explain their system.

2. After launch, who changes the copy on the homepage?

   The whole reason to be on Webflow. If the answer is always them, you have bought a developer dependency with a page builder attached.

   Worry if you hear They have not worked out what your team can update.

3. Name something you would refuse to build in Webflow.

   Anyone who works in the tool seriously has a boundary. What you want is the reasoning, applied to your requirements.

   Worry if you hear They recommend an approach without discussing what you need.

4. How will you handle the existing URLs?

   Search visibility survives a rebuild when the addresses, the metadata and the internal links are all carried deliberately. The answer should involve mapping, before launch rather than after.

   Worry if you hear URL mapping and post-launch checks are not in the scope.

5. What happens when a form submits but the CRM never receives it?

   A costly defect that can go unnoticed, because nothing about it looks broken. The answer should say how anybody would find out.

   Worry if you hear Nobody owns the monitoring, the alert or the recovery.

6. How many collections and items do you expect this site to need?

   Collections and items are capped per plan, and the caps change. Someone who has not asked about your content has not thought about year two.

   Worry if you hear The estimate ignores the content structure and how it will grow.

7. Which parts of this will need custom code?

   Not a trick question, and some is fine. You want each piece named up front, along with what it does and who maintains it.

   Worry if you hear They cannot explain what it is for or who keeps it working.

8. What does the handover look like?

   A documented component system, a scoped Editor and the access transferred, or a login and good luck. Ask what documentation and training come with it.

   Worry if you hear The training, the documentation, the access and the ownership are undefined.

9. Who does the work, and who will I be talking to?

   At an agency these are often different people. Not disqualifying, and you should know before rather than after.

   Worry if you hear The responsibilities and the routes for a question are unclear.

10. What would make you tell me not to hire you?

    Everyone who has done this a while has a project shape they are wrong for.

    Worry if you hear They cannot describe what they need in order to deliver well.

Print it, paste it into the doc you are already keeping, or read it off the screen. The questions matter more than the order.

Considering me for your project?

Send your site, your goals and your requirements. I will explain how I would approach the work, what your team could maintain afterwards, and where I would point you somewhere else.

Discuss your project