- To hire a Webflow developer, write a short brief, shortlist three to five people with live Webflow work, check those sites on a phone, ask how they structure classes and the CMS, then run a small paid test.
- A good Webflow developer builds for your editors, not just for the launch screenshot. Ask to see a read-only link to a real project.
- Look for clean class naming, a planned CMS, real responsive work and basic SEO set up before launch.
- Make sure the site lives in your own Webflow workspace and that you own every file, font licence and login.
- Expect about $500 for a landing page and from $2,500 for a 5 page site at Kookies. Freelance rates vary a lot by experience.
How to hire a Webflow developer: the short answer
To hire a Webflow developer, start with a one page brief, find three to five developers who can show live Webflow sites, test those sites on your phone, ask how they plan classes and CMS collections, and pay for a small test before you sign the full project. That is the whole process. The rest of this guide shows you how to do each step well.
We hire for our own team and we get hired by founders and marketing leads every week, so we see both sides. The teams that end up happy are rarely the ones who found the cheapest quote. They are the ones who knew what they needed and checked the right things before they said yes.
If you are short on time, read the sections on checking a portfolio and the questions to ask. Those two steps filter out most bad fits.
What a Webflow developer actually does
A Webflow developer turns a design into a working website inside Webflow. That sounds simple, but the job covers a lot more than dragging boxes onto a canvas.
- Structure. They build sections, containers and components so the layout holds up from a small phone to a wide monitor.
- Class system. They name and reuse classes so the site stays consistent and easy to change. Many developers use a naming system like Client-First.
- CMS. They plan collections for blog posts, case studies, jobs or team members, and connect them to template pages.
- Interactions. They add scroll and hover effects that feel smooth and do not slow the page down.
- SEO and speed. They set titles, descriptions, alt text, redirects and Open Graph images, and keep images and scripts light.
- Integrations. They connect forms, analytics and tools like HubSpot, Zapier or a booking widget.
- Handover. They show your team how to edit content without breaking the design.
Some Webflow developers also design. Some only build from a Figma file. Know which one you need before you start looking, because it changes who you shortlist and what you pay.
Write a one page brief first
A short brief saves you hours of calls and gives you quotes you can actually compare. It does not need to be fancy. Answer these questions in plain words:
- What is the site for? Leads, sign ups, hiring, fundraising, or a mix.
- Do you have a design? A finished Figma file, a rough wireframe, or nothing yet.
- How many pages? List them. Count CMS templates like "blog post" as one page.
- What content changes often? This tells the developer what belongs in the CMS.
- Are you moving from another platform? WordPress, Wix and Squarespace moves need redirects and content transfer.
- Which tools must connect? CRM, analytics, booking, email.
- When do you need it live, and what is the budget range?
Share the same brief with everyone on your shortlist. When quotes come back, you are comparing like with like, not guessing why one number is three times another.
Where to find Webflow developers
There are four common places to look. Each one has trade offs.
The Webflow partner directory
Webflow lists agencies and freelancers who are part of its partner program. Partners have shipped real Webflow projects and have a public profile with work samples. It is a good first stop if you want someone who works in Webflow every day. Kookies is a Webflow Premium Partner, for example.
Referrals
Ask founders and marketers whose sites you like who built them. A referral comes with an honest review of how the project felt, not just how it looks.
Freelance marketplaces
Big marketplaces have plenty of Webflow freelancers at every price point. Quality varies a lot, so the portfolio check below matters even more here.
Agencies
An agency gives you a team: design, build, SEO and support under one roof. It usually costs more per hour than a solo freelancer, but you get cover for holidays and sick days. We wrote a full guide on choosing a Webflow agency or a freelance Webflow developer if you are torn.
How to check a Webflow portfolio
Screenshots tell you very little. A Webflow developer can make any site look good in a mockup. Open the live sites instead and spend ten minutes on each one.
- Open it on your phone. Most visitors are on mobile. Look for text that overflows, buttons that are too small and sections that feel squashed.
- Resize your browser slowly. Drag the window from wide to narrow. Good builds reflow smoothly. Weak ones jump or break between breakpoints.
- Run a speed test. Paste the URL into PageSpeed Insights. A score in the red on mobile is a warning sign, especially on a simple marketing page.
- Check the blog or case studies. If they are CMS driven, the layout should look the same on every post, with no odd gaps.
- View the page title and description. Search the site on Google. Missing or duplicated titles mean SEO was an afterthought.
- Confirm it is really Webflow. Some portfolios mix in sites built on other tools.
Then ask for a read-only link to one project. Webflow lets owners share a read-only view of the Designer. Inside, you can see how classes are named, whether components are used and how the CMS is set up. A tidy project is the best sign that your own site will be easy to live with.
Questions to ask in the first call
A 20 minute call is enough to learn how someone works. These questions get past the sales talk:
- How do you name classes, and why? (Listen for a system, not "it depends".)
- How would you plan the CMS for our blog and case studies?
- What do you check before launch? (You want to hear speed, SEO, forms, redirects and mobile.)
- How will my team edit the site after handover?
- Who builds it, you or someone else? Who covers you if you are away?
- How do you handle changes after we sign off a page?
- Will the site sit in our own Webflow workspace from day one?
- What happens after launch if something breaks?
Good developers answer quickly and give you examples. If someone needs to "get back to you" on how they name classes, they probably do not have a system.
Red flags to watch for
- A price before any questions. A real quote needs your page count, CMS needs and integrations.
- No live links. Only Dribbble shots or mockups.
- The site lives in their account. You should own the Webflow site and the hosting plan, or at least be able to transfer it any time.
- Heavy custom code for simple things. Webflow handles most layouts and interactions natively. Lots of pasted scripts make the site harder to edit and slower.
- SEO "later". Titles, descriptions, alt text and redirects take minutes during the build and days to fix after.
- No written scope. If what is included is not written down, you will argue about it later.
The cheapest Webflow build is often the most expensive one you pay for, because the next developer has to rebuild it.
Run a small paid test
If you are choosing between two good options, pay each of them to build one section. A hero, a pricing table or a blog post template is enough. Keep it small: a few hours of work.
Then look at three things. Does it match the design at every screen size? Is the class naming clear when you open the Designer? Did they ask good questions while they worked? You learn more from one real section than from three calls.
We offer a free test section on Figma to Webflow projects for this reason. You can read how that works on our Figma to Webflow page.
Contracts, ownership and handover
A simple agreement protects both sides. Make sure it covers:
- Scope. Pages, CMS collections, integrations and the number of review rounds.
- Ownership. You own the site, the design files and the content once the invoice is paid.
- Accounts. The Webflow site sits in your workspace, and you pay for hosting directly or through a clear client billing setup.
- Licences. Fonts, icons and stock images are licensed in your name or under a licence that covers you.
- Handover. A walkthrough video, a style guide page and notes on how the CMS works.
- Support. How long the developer fixes bugs for free after launch, and what ongoing help costs.
Hiring mistakes we see again and again
We often get called in after a first build did not work out. The reasons are almost always the same.
- Hiring on looks alone. The portfolio was beautiful, but nobody opened the Designer. The site looked fine at launch and became hard to edit a month later.
- No mobile check. The team reviewed the staging link on a laptop and signed it off. Most of their visitors were on phones.
- Content last. Copy arrived the week before launch, so the layout had to bend around text it was never designed for.
- Nobody owned SEO. The developer thought the marketer would do it. The marketer thought the developer had. The old URLs never got redirects.
- No plan for after launch. The developer moved on to the next client and small fixes sat in a queue for weeks.
Each of these is easy to avoid if you ask about it before you sign. That is really the whole point of this guide.
What it costs and how long it takes
Webflow developer prices vary widely. Freelance hourly rates depend on country, experience and demand. Agencies usually quote a fixed price per project. Our own prices are public so you can use them as a reference point:
| Project | Kookies price | Typical time |
|---|---|---|
| Hourly work | $35 an hour | As needed |
| Landing page | $500 | About 1 week |
| Website, up to 5 pages | From $2,500 | 3 to 5 weeks |
| Large site, 6+ pages | From $3,000 | 6+ weeks |
| Care plan | $3,000 to $4,000 a month | Ongoing |
The Webflow site plan is billed by Webflow on top of the build. For a deeper breakdown, read how much a Webflow developer costs or see our pricing page.
How we approach a new Webflow project
Since you are reading this on our site, here is how we run things, so you can compare. Every project starts with a 20 minute call and a written scope with a fixed price. We build in your Webflow workspace from day one. We set up a style guide page, components and the CMS before pages, then add SEO, speed checks and redirects before launch. You get a training video and 30 days of support after go live.
If you want ongoing help after that, our Webflow care plan covers unlimited requests, one at a time. If you want to see a finished project first, the ClanX case study is a good place to start, or read about our full Webflow development service.
Terms used: Webflow, Core Web Vitals



