Webflow agencies charge $3,000 to $50,000. Here's what actually drives the number, the 12 questions to ask before you sign, and when not to hire one.
A website build takes six to twelve weeks and, for most B2B marketing sites, costs between $8,000 and $25,000. Most buyers decide who gets that money after three portfolio screenshots and one call that felt friendly.
Knowing how to hire a Webflow agency means knowing what a portfolio cannot show you: a build nobody documented, a CMS your team cannot update without a developer, a launch that quietly drops rankings you already had, a contract that never said who owns the workspace. All of it is knowable before you sign.
This guide covers what the work costs and why the same scope gets quoted at $8,000 and at $30,000, how to read a portfolio in five minutes, the twelve questions to ask on a discovery call, the red flags that should end it, and when not to hire an agency at all.
We are a Webflow agency, so we have an obvious stake in this. The guide is written as the questions we would expect a buyer to put to us.
First, though: if you have not settled on a platform, that decision changes which agencies are worth calling. Our comparison of Webflow and WordPress covers what each costs to run over three years and which suits your team.
A Webflow agency designs, builds and maintains websites on the Webflow platform. In practice that means design, Webflow development with reusable components and clean class structure, CMS architecture for anything your team publishes repeatedly, CRM and analytics integrations, technical SEO setup, migration from another platform, and maintenance after launch. Most Webflow web development agency work is the second of those. Some agencies do only part of this list. Others run the whole project.
Nobody sells all of it at every price point. Which parts fall inside your quote is the question most buyers do not think to ask, and it explains a large share of why two quotes for the same site look nothing alike. We cover it properly in the pricing section below.
The short answer: a design agency decides what the site should look like and say, and a Webflow development agency builds it. Plenty of firms do both, which is why the labels get used loosely.
There are three models you will meet, and the right one depends on what you already have.
Design only gives you strategy, messaging and finished Figma files, and you find someone else to build it. Development only means you bring approved designs and they build them, which is cheaper and faster but only works if those designs were drawn by someone who understands how Webflow builds pages. End to end is one team from strategy to launch, which costs more and is usually the practical choice if you have no in-house designer.
Most teams without a designer on staff should start by looking at end-to-end agencies, and treat design-only or build-only firms as the cheaper route available once you know exactly what you want. If you are still weighing that against hiring a freelancer or building an in-house team, we have compared all three on cost, speed and risk in our breakdown of agency, freelancer and in-house Webflow teams.
Three groups, with different reasons.
Founders and early-stage teams who need a site that explains the product and captures leads, and who do not want to spend the next two months managing a build. The site usually needs to ship before a launch, a raise or a conference.
Marketing teams without a developer. This is the most common case. A Webflow agency for marketing teams is really buying autonomy: componentised pages and a CMS the team can publish to without help. If your marketing team cannot launch a landing page in an afternoon, that is the problem you are hiring to fix.
Design and marketing agencies that need a white-label Webflow partner. They have won the client and the design work, and they need someone reliable to build it under their brand. What matters here is different: NDA terms, whether the partner will speak to your client directly, and whether the handoff is documented well enough that you can support the site afterwards.
An agency is not automatically the right answer, and for a meaningful share of buyers it is the expensive one. The question is not which option is best, it is which one matches the site you need and how often you will change it.
Two honest conclusions from that table.
In-house only makes sense with a continuous pipeline. A single mid-level hire costs more in year one than almost any agency project, and that maths only works if you are shipping landing pages every week. If the site goes live and then sits still, you have converted a one-off cost into a permanent one.
An agency earns its premium on complexity and accountability. Multiple page types, a CMS your team will actually publish to, CRM and analytics integrations, a migration with rankings at stake, or a deadline that cannot move. Those are project management problems as much as build problems, and they are what you are paying an agency to absorb.
If you want the fuller version of this comparison, including what each option looks like over three years rather than one, we have broken it down in our piece on agency versus freelancer versus in-house Webflow teams.
Most of the time an agency is the wrong purchase, it is not because the agency is bad. It is because the project does not need one yet. Three situations where you should spend the money elsewhere.
Your budget is under $3,000. At that level you are not buying an agency project, you are buying a fraction of one, and what arrives will show it. Customise a good template, or hire a freelancer for a focused build. Both will serve you better than the cheapest quote an agency is willing to write, which is usually the quote they least want to deliver.
You need fewer than five pages and no CMS. A homepage, an about page, a services page and a contact form is a freelancer's week. An agency will run a discovery workshop, a design phase and a QA cycle for it, and you will pay for all three. The process is not padding, but it is built for projects with more moving parts than yours has.
Your real problem is positioning, not the website. The most expensive mistake in this list. If you cannot say who the site speaks to or what you want a visitor to do, a redesign produces a better-looking version of the same confusion. If the message is wrong, a new site makes the wrong message load faster. A strategist is cheaper than an agency for that piece of work, and once it is settled the build gets faster and cheaper too. We wrote about this pattern in agencies themselves, where the symptoms are easiest to see, in our piece on why most marketing agencies cannot sell themselves.
One test that cuts through all three: if you cannot write a paragraph explaining what the new site should do that the old one does not, you are not ready to brief an agency. That paragraph is the brief, and without it you are buying opinions.
Most buyers find Webflow agencies in three places: Webflow's own Certified Partner directory, B2B listing sites like Clutch and DesignRush, and referrals from other founders who have recently been through a build. Gather ten to twelve names from those sources, then cut to three before you book a single call.
Where to look
Three filters, applied in order, before you speak to anyone.
Three is the right number. Each call is an hour, plus a brief, a proposal and a follow-up, so five agencies adds two or three weeks to a decision that will not improve for having more options in it. If none of the three convinces you, go back to the list of twelve knowing much more than you did.
Most Webflow agency projects fall between $3,000 and $50,000. The majority of B2B and SaaS marketing sites land between $8,000 and $25,000. Single landing pages start around $2,000, and enterprise builds with multiple regions or complex integrations run from $50,000 upwards.
After launch, ongoing retainers typically run $2,000 to $15,000 a month. Hourly rates at established US agencies sit between $100 and $200, while mid-level developers working globally charge $40 to $80.
Those are wide bands, and the width is the real story. The rest of this section explains what moves a project from one end to the other.
ranges are compiled from public 2026 pricing data published by Webflow agencies and specialist directories, including rate bands agencies self-report on their Clutch, DesignRush and Webflow Certified Partner profiles. Platform costs come directly from Webflow's own pricing page. Salary figures for the in-house comparison come from published Webflow developer salary guides, adjusted for total cost of employment.
Migration pricing scales with the number of URLs rather than the number of designs, which surprises most people. A 200-page WordPress site can cost more to move than a 20-page site costs to build from scratch, because the risk sits in the redirect map rather than the visuals. If you are moving an existing site, our website migration service page covers what that work involves.
As a worked example of what published pricing looks like, our own tiers run $3,000 to $5,000 for a lean launch site, $5,000 to $9,000 for a componentised site with landing funnels, and $10,000 to $20,000 for larger builds with a design system and complex integrations. Full scope for each is on our Webflow agency page. We publish them because a buyer should be able to rule us in or out before booking a call, and because an agency that will not name a range before a 45-minute discovery call is usually managing you rather than informing you.
This is the question underneath every cost search, and almost nobody selling agency work answers it. Six things account for most of the spread.
Agency fees are not the whole budget. Six things routinely land after the invoice.
Most Webflow projects take six to twelve weeks from kickoff to launch. Those numbers assume the client side keeps pace, which is the part most timelines quietly depend on.
Two things cause almost every overrun, and neither is the build.
Late content. Copy and images arrive halfway through the build, or arrive as placeholders that get replaced twice. Every design decision made around Lorem Ipsum gets revisited once real words appear, and long headlines break layouts that were drawn for short ones. If content is not ready at kickoff, say so and let the agency plan around it, because a timeline built on the assumption that it is ready will not survive week four.
Revision rounds nobody capped. If the contract does not say how many rounds of design feedback are included and how long each one may take, the design phase has no end. Two rounds with a five-day feedback window is a normal arrangement. Ask what happens on round three, because the answer tells you whether the timeline is a plan or a hope.
One useful test before you sign: ask the agency for a week-by-week schedule with client deadlines marked on it, not just their own. An agency that can produce that has run the process before. An agency that gives you a single end date has given you a guess.
Do not judge a portfolio on screenshots. Open the live sites, test them on your phone, run one through PageSpeed Insights, and ask to see inside the Webflow Designer on a real project. How a site is built tells you far more about what you are buying than how it looks in a case study image.
Screenshots are the agency's best moment, cropped. Live sites are what your site will actually be.
Ask for three live URLs. If an agency cannot give you three, that is your answer. Then spend five minutes on each.
This is the strongest single test in this guide, and almost nobody does it. Ask the agency to share their screen and walk you through the Webflow Designer on a real client project. You do not need to know Webflow to read what you are shown. Four things to watch for.
Ten SaaS builds beat fifty mixed ones if you are SaaS. An agency that has shipped repeatedly in your category already knows the pattern: what a pricing page has to do, how a trial funnel is structured, where documentation sits, what a security page needs on it for an enterprise buyer. You will not be paying them to learn it on your project.
Two ways to check quickly. Ask which three industries they work in most, and see whether the answer is specific or a list of everything. Then look for depth rather than logos: two or three detailed case studies in your category beat twenty client badges. If you want a sense of what a strong build in one category looks like before you start comparing, our breakdown of the best SaaS website designs covers what the good ones get right and why.
Agencies advertise Webflow partner badges constantly and almost never explain what they mean. The programme has three tiers, plus a separate distinction badge that is often mistaken for a fourth.
Webflow publishes the full requirements for each tier and the site grading rubric that portfolios are judged against, and both are worth checking at source rather than taking an agency's word for it.
A tier proves that someone outside the agency has looked at their actual builds and found them competent, and that they ship consistently. Given most agency credibility signals are self-awarded, that is useful. It does not prove the agency is right for your project. A Premium Partner with fifty ecommerce builds is the wrong hire for a SaaS marketing site. And it says nothing about communication, scoping discipline or whether deadlines hold, which is what the discovery call and the twelve questions are for.
Treat a partner tier the way you would treat a professional qualification in any field. It is a reason to take someone seriously and a poor reason to skip the interview.
One other thing worth knowing: Webflow's individual certifications are separate from the partner programme. Webflow Practitioner and similar exams cost $100 each and certify a person, not a company. An agency listing individual certifications is telling you about a staff member. A partner tier is telling you about the business.
Ask all twelve on the discovery call. How they answer matters as much as what they say: an agency that has run projects properly answers specifically and quickly, while one that has not speaks in generalities and promises detail in the proposal.
If you are comparing three agencies, ask all twelve of each and write the answers down. By the third call they blur together, and the proposals will not tell you what was said out loud.
Three proposals for the same website will not be comparable as written. Each agency has scoped differently, included different things, and made different assumptions about what you are supplying. Comparing the headline numbers tells you almost nothing.
Before you compare anything, send all three the same one-page scope: page count, whether design exists, integrations needed, who writes the copy, and your launch date. Ask each to restate its quote against that scope. Some will come back with a different number than the one they first gave you, and the size of that change is itself useful information.
Then pull the same eight things out of each proposal.
A blank is an answer. If you cannot find one of the eight in a proposal, go back and ask, then note how long it took to get a straight reply. That response time is the cheapest preview you will get of what working with them is like.
One last thing: resist scoring this out of ten. The list is for making three proposals legible, not for producing a winner arithmetically. Once you have the eight for each, the right choice is usually obvious, and where it is not, the deciding factor is which team you would rather have on a call in week six when something has gone wrong.
Not all of these are dealbreakers on their own. Two or three together usually are.
The pattern behind all of them: each one moves risk from the agency to you while looking like speed, generosity or value.
You should own the site, the workspace it lives in, the domain and the design files. In practice, ownership is decided by how the handoff is set up rather than by what the contract says, and most buyers find that out only when they try to leave.
The mechanics matter, because one detail changes whether your site goes offline during the handover.
You should own the site, the workspace it lives in, the domain and the design files. In practice, ownership is decided by how the handoff is set up rather than by what the contract says, and most buyers find that out only when they try to leave.
The mechanics matter, because one detail changes whether your site goes offline during the handover.
Webflow sites move between workspaces through a transfer, not a login handover. The agency initiates it, the recipient must already have a Webflow account and workspace, and the transfer only completes when the recipient accepts it from an email or a banner in their dashboard. Once accepted, the site leaves the agency's workspace and appears in yours. Designer content, CMS collections and form submissions all travel with it.
What does not automatically travel is the part to get right.
If your agency is on a Freelancer or Agency workspace plan, it can transfer a site with its paid Site plan and connected custom domains directly to your workspace. There is no downtime and no loss of unused plan time, and the agency gets credit back for whatever it has already paid. This is the clean version.
If your agency is not on one of those plans, the Site plan does not move. You have to buy your own plan and reconnect the domain after accepting, which means the live site can go down in the gap. Your workspace also cannot be an Enterprise workspace for a plan transfer to work.
So the question to ask is not "will you transfer the site" but "which workspace plan are you on". It is a one-word answer that decides whether your handover is seamless or an outage.
One exception worth knowing. Ecommerce sites do not transfer their plans, so a new owner needs to add an Ecommerce plan and re-enable checkout, with payment providers disconnected first.
There is also a middle option some agencies use. Through client payments, the site stays in the agency workspace while your card pays Webflow directly. That solves billing, but it does not give you ownership, and it is sometimes presented as though it does. If the site is still in their workspace, you are paying for something you do not hold.
Webflow documents all of this publicly. The transfer a site lesson covers the process, and the help centre article on transferring a site or plan sets out the workspace plan rules. Both are worth reading before you sign, and worth sending to any agency that is vague about it.
Six clauses. None is unusual, and a reasonable agency will agree to all of them without friction.
If you already have a site that gets traffic, this is the part of the project with the most money at risk. Rankings are rarely lost because of the platform. They are lost through unmapped redirects, content that quietly did not make it across, and URL structures that changed for design reasons nobody connected to search.
The pattern is always the same. A site with 180 pages gets rebuilt as 40 "cleaner" ones, the 140 that were dropped included the ones ranking for long-tail queries, and nobody notices until organic traffic has fallen for two months.
Four things to require before a single page is built.
None of this is optional work, and an agency that treats it as an add-on is telling you it has not done a migration with real traffic at stake. If you are moving an existing site, the audit is where the whole project succeeds or fails, and we have set out what it should cover in our guide to what to audit before migrating a large website to Webflow, alongside our walkthrough of moving from WordPress to Webflow.
You will spend the call assessing them. The stronger signal runs the other way: what they ask you.
A good agency spends most of a first call asking questions. Who are you selling to, and what makes them hesitate? How do deals actually close, and where does the website sit in that? Who are you losing to, and why? What is failing on the current site, and how do you know? Who will maintain this after launch, and what can they do without help?
Those questions are not politeness. They are the inputs for a scope. An agency that does not ask them cannot price your project, so the proposal that follows is a guess with a number on it, and the gap between the guess and reality surfaces later as change requests.
Agencies quote what they can see. Send the same seven things to everyone you approach and you will get proposals that are comparable, faster, and closer to what the project actually costs.
On that last one: naming a range gets you a better proposal, not a worse one. Agencies use it to decide what to include, not to charge you the maximum. Without a number they build to a guess, which is usually either too thin to achieve your goal or too expensive to be taken seriously. And if your range is below their floor, you find out in a day rather than after two calls and a proposal.
Different job. You are not buying a website, you are buying delivery capacity that has to operate under your name without your client noticing a seam. Five things to check before you commit a client project to a Webflow partner.
We take on agency partnerships on this basis, and the scope of what that covers is on our Webflow agency page.
The right decision rarely comes down to which agency looked best. It comes down to whether you can explain, in a sentence, what this website has to achieve that the current one does not. Get that clear and everything downstream gets easier: you will know which agencies to rule out, what to insist on in the scope, and whether a proposal is answering your problem or describing a generic website. Get it wrong and you will buy something that looks like an upgrade and changes nothing. When you are choosing between two agencies that both seem capable, pick the one that asked better questions, not the one that gave better answers. Capability is common. Genuine curiosity about your business is rare, and it is the thing that shows up in the work.
If you want to put your project in front of us, we are That Webflow Agency, a Webflow Certified Partner that builds on Webflow and nothing else, for SaaS companies, startups and marketing teams. Our pricing sits on our Webflow agency page rather than being held back for a call, so you can rule us in or out before spending an hour with us. Book a call with That Webflow Agency and bring the twelve questions. We would rather answer them than talk you through a deck.
Most Webflow agency projects cost $3,000 to $50,000, with typical B2B marketing sites landing between $8,000 and $25,000. Single landing pages start around $2,000. Ongoing retainers run $2,000 to $15,000 a month, and hourly rates at established US agencies sit between $100 and $200.
Most Webflow projects take six to twelve weeks from kickoff to launch. A landing page takes one to two weeks, a five to fifteen page site three to six weeks, and a larger B2B site six to twelve weeks. Late content and uncapped revision rounds cause most delays.
A freelancer is usually the better choice for a brochure site under five pages with no CMS, and costs a fraction as much. An agency earns its premium on complexity: multiple page types, a CMS your team will publish to, integrations, migrations, and deadlines that cannot move.
A Webflow Certified Partner is an agency or freelancer that has passed a pre-qualification assessment, built at least three client sites in Webflow, and had a portfolio approved against Webflow's published site grading rubric. Certified Partners appear in Webflow's public directory. Premium Partner is the tier above, re-earned annually on points.
You should, but it depends on the contract and the handoff. Webflow sites move between workspaces through a transfer that you have to accept. Agree in writing that the Webflow project, design files, domain and DNS are yours, and that the workspace transfers at launch rather than on request.
Yes, if the site was built for it. A properly structured build gives your team an editor for text, images and CMS entries without touching the design. Ask to see the editor view before you sign. If changing a headline needs a developer, the build was done badly.
Avoid fixed quotes given within 48 hours with no discovery, guaranteed rankings, unlimited revisions, portfolios with no live URLs, and proposals silent on who owns the site. A quote far below every other is not a bargain, it is a different scope with something removed, usually QA or support.
.png)
.png)
.png)