Hiring a Webflow Developer? 9 Questions to Ask Before You Pay
Webflow makes building look easy, which is exactly why the quality of Webflow developers varies so much. Two builds can look identical on launch day and be completely different to live with a month later: one your team edits happily, the other a maze of classes nobody dares touch.
These nine questions separate the two before you sign anything.
About the build
1. "What class naming system do you use?"
Listen for a named convention such as Client-First, or a clear system of their own. "I just name things as I go" is a warning sign, because the next person to touch the site will have to guess what every class does.
2. "How will you handle mobile if my file only has desktop?"
A good answer: they adapt using your own spacing and type rules and show you before launch. A bad answer: "it will be responsive automatically".
3. "What will be in the CMS?"
Blog posts, case studies, team members and anything else that changes often should be CMS collections, so your team can add them without design skills.
4. "How do you check it matches the design?"
You want side-by-side checks against Figma at each breakpoint, on real devices. See what pixel-perfect really means.
About performance and SEO
5. "What SEO setup is included?"
Titles, meta descriptions, alt text, Open Graph images, a sitemap, redirects for old URLs and Search Console. If it is not mentioned, assume it is not included.
6. "How do you keep it fast?"
Compressed and properly sized images, lazy loading, restrained custom code and interactions that stay smooth on phones.
About the working relationship
7. "What exactly is the timeline, and what can delay it?"
Honest developers tell you what they need from you and when. Vague timelines tend to stretch.
8. "Who owns the site and the Webflow account?"
You should. The site should live in your Webflow workspace, or be transferred to it at launch.
9. "What happens if something is wrong after launch?"
Look for a clear fix period in writing, not "just message me".
Good answers and warning signs at a glance
Keep this open during the call. You do not need to be technical to hear the difference.
| Topic | Good sign | Warning sign |
|---|---|---|
| Class naming | A named system, explained in a sentence | "I name things as I go" |
| Mobile | Adapted from your design rules and shown to you before launch | "Webflow makes it responsive automatically" |
| CMS | A list of collections and the fields in each | Every page built by hand, even the blog |
| SEO | A specific list of settings and redirects | "Webflow does SEO for you" |
| Timeline | A date, plus what they need from you to hit it | "A few weeks, depending" |
| Ownership | Built in, or transferred to, your workspace | Hosted in their account with no transfer plan |
| After launch | A fix period in writing | "Just message me if anything comes up" |
Check their work yourself
A portfolio shows what a site looks like. These checks show what it is like to live with:
- Ask for a read-only link to a past Webflow project. Webflow can share a project in read-only mode, so you can look inside without touching anything.
- Open the Navigator panel. Elements should have readable names and a tidy structure, not dozens of "Div Block 47" layers.
- Click a few elements and look at the class names. Can you guess what each one is for?
- Look at the CMS collections. Are blog posts and case studies there, with sensible fields?
- Open a live site they built on your phone, on mobile data. Does it load quickly and read well?
- Run the live site through PageSpeed Insights. You are not chasing a perfect score, just checking nothing is badly wrong.
Questions a good developer will ask you
The interview runs both ways. A developer who cares about the result will want to know:
- Who are your customers, and what should they do on the site?
- Which pages bring in the most inquiries or sales today?
- Who on your team will update the site, and how often?
- Is the copy final, or still changing?
- Do you have an existing site whose URLs need redirecting?
If they ask none of these and jump straight to price, they are probably planning to build exactly what is in the file and nothing more, including the gaps.
Red flags to watch for
- No live examples, only screenshots or Dribbble shots.
- A price far below everyone else with no clear scope. Something will be missing.
- They want to host the site in their own account with no plan to transfer it.
- No questions about your business, only about colours and pages.
- Vague answers about SEO, such as "Webflow does SEO automatically".
Freelancer, agency or specialist team?
Freelancers can be excellent and affordable, but capacity is limited, and holidays or illness stop the project. Full-service agencies handle strategy, design and build, at a higher price and slower pace. Specialist build teams sit in between: they take a finished design and turn it into a site quickly and consistently, which is ideal when the design is already done.
No design yet, or an old site that needs rethinking first? Start with a website redesign so the developer has something solid to build from.
Moving an existing WordPress site?
Many people hiring a Webflow developer are not starting fresh. They have a WordPress site with years of blog posts and rankings behind it. In that case, add three questions to the nine above: how will my posts be imported into the CMS, how will every old URL be redirected, and how will you check nothing was lost? Our WordPress to Webflow migration guide covers the whole process, and our WordPress to Webflow migration service handles it for you.
How to brief a Webflow developer well
- Share the Figma file with view and Dev Mode access.
- List the pages in scope and what goes in the CMS.
- Name the one person who approves revisions.
- Share your launch date and any fixed deadlines (campaigns, events).
- Provide domain and hosting access, or say who will set them up.
Our Figma handoff checklist covers the file itself.
Our answers, up front
Client-First classes, mobile adapted from your own design system and approved before launch, CMS for anything that changes, side-by-side QA, full SEO setup, your workspace, a 24-hour build from an approved brief, and 30 days of care after launch. You own everything. That is our Figma to Webflow in 24 hours service. Send your Figma link for a fixed quote within the hour.
Frequently asked questions
How much does it cost to hire a Webflow developer?
It depends on the number of pages, the CMS collections, the interactions and whether copy and SEO are included. Ask for a fixed quote that lists all of those, so you can compare offers fairly. Our guide to what a website costs in the Philippines explains the main price drivers.
How long does a Webflow build take?
Most of the time goes into waiting for content and approvals, not the build itself. With a finished Figma file, final copy and one approver, a small site can go live in 24 hours. Larger sites with many CMS collections or custom interactions take longer.
Do I pay for Webflow separately from the developer?
Usually, yes. Webflow charges a site plan to host your site on your own domain, and it should be billed to your workspace, not the developer's. That keeps you in control if you ever change developers.
Can my team edit the site without a developer?
Yes, if it was built well. Your team can change text, images and CMS items in Webflow's editing mode without touching the design. That only works smoothly when the CMS and class naming were set up properly, which is why questions 1 and 3 matter so much.
What is Client-First?
Client-First is a free class naming convention for Webflow from Finsweet. It names classes by what they do, so anyone opening the project can understand how it is built. It is not the only good system, but it is widely known, which makes handovers easier.