How to choose a Webflow agency: costs, timelines and the brief

If you're about to hire a Webflow development company, you probably have a site that's hard to change, a launch date, and three quotes that don't look like they're for the same job. This guide covers what a Webflow agency actually does, when Webflow is the wrong tool, what a build costs and how long it takes, how to write a brief that gets you comparable quotes, what to check before you sign, and how to move an old site without losing the traffic it earns.

We're Usarion, a design and build studio, and Webflow is one of the tools we build marketing sites in. So we have a stake in this. We've kept the advice to things you can check yourself, linked every figure that isn't ours, and we don't recommend or rank other agencies.

What a Webflow development company does

A Webflow agency designs and builds websites in Webflow, a visual platform that puts the page builder, the content management system (the CMS) and the hosting in one place. The job usually covers five things:

• The build: pages, components, layouts for every screen size, and any motion.
• The CMS: collections for the content that repeats, like blog posts, case studies, job ads or a changelog, so your team adds one by filling in a form.
• Search basics: page titles, headings, clean URLs, structured data and image handling, set up while the site is built.
• The move: if you have a site already, its pages, content and URLs come across, with redirects for every old address.
• The handover: a session with your team, written notes, and the site moved into your own Webflow account.

Some agencies also design the site. Others build from a design you hand them, usually a Figma file. Neither is wrong, but know which one you're paying for. When design and build sit with two different teams, the gap between them is where interactions get dropped and pages get simplified because they were awkward to build.

The thing you're really buying is a site your team can change without asking anyone. A Webflow site that only its builder can safely edit has lost most of the reason for picking Webflow.

Is Webflow the right choice, or do you need custom code?

Ask this before you compare agencies, because it changes who you should be talking to.

Webflow is a good fit when the site is mostly pages people read: a homepage, product and feature pages, pricing, a blog, case studies, careers. Your marketing team can publish without a developer, it launches faster than a site built from scratch, and hosting comes with it.

It's the wrong fit when the thing you're describing is really an application. If people log in, if they see their own data, if there are roles and permissions, or if the logic lives on a server, you need a developer and a code base. A Webflow agency that takes that job will spend your budget on workarounds.

If you sell software, you probably need both, and they're two separate builds. When we designed Reputable, a reputation platform for Web3 developers, there were two jobs from the start: the web app, where developers sign in with GitHub, and the website that sends them to it. The website's "Open App" button is the line between the two. A website like that suits Webflow. The app never would.

Orkap is the other side of that line. It's a partnership CRM we designed: a mailbox for each product, deals beside the emails, contacts imported from a CSV file, automated follow-ups. That's more than 110 screens of application. If someone quotes that as a Webflow site, get a second opinion.

And sometimes the honest answer for a marketing site is code too. Most of the marketing sites we build for founders are in Webflow or Framer, but we built our own website in code, on Next.js with Payload as the CMS, because we wanted AI to build and ship every part of it and the site to run on our own server. If you don't have a reason like that, Webflow will usually get you live sooner.

Framer is the other platform you'll hear about. In our experience it suits smaller, more visual sites, and Webflow suits sites with real content behind them, like a resource library or a changelog. If a studio builds in both, ask which one it would pick for your site and why.

Agency, freelancer or in-house?

There are three ways to get a Webflow site built, and the right one depends on how big the job is and how often the site will change after launch.

You can use two of these: an agency for the build and the migration, then someone in-house or a freelancer for the weekly changes. If you go that way, make sure the agency builds for the person who comes after it. Class names they can read, a CMS that matches what you publish, and written notes make that work.

A fourth option sits between agency and in-house: a design team on a monthly plan. Our own plans start at $2,000 a month for 40 hours of one senior designer, and the hours cover design and build, so a Webflow change counts the same as a design change (pricing). It suits teams with a steady flow of new pages more than a one-off build.

What a Webflow site costs

There are two bills: the build, paid once, and Webflow itself, paid every month or year: a site plan for each site, and seats for the people who edit it.

The build. Agencies' own guides give wide ranges, and they're worth reading as rough signals, not price lists:

The three guides are Exponetly's, Flowzai's and Flowout's, read on 31 October 2026. They're agencies writing about their own market, so read their numbers the way you'd read ours.

Those ranges are so wide because the quotes aren't for the same thing. What actually moves the price:

• Templates, not pages. A site with 40 blog posts and five page designs is a five-template site. Our own site has six service pages that share one template, so a seventh service is words, not a new build. Ask an agency to quote by template, and count yours before you ask.
• The CMS. Each collection, and each link between collections (a case study tagged with an industry, say), is work to set up and work to get right.
• Whether the design exists. A build from a finished Figma file is a different job from design and build together.
• The move. Pages, posts, images and redirects from an old site add time in proportion to how much there is.
• Who does the work. A senior builder costs more an hour and usually needs fewer of them.

Agencies price in three ways: a fixed price for a written scope, an hourly rate, or a monthly retainer or plan. A fixed price suits a clear brief; hourly and monthly suit work that keeps changing.

When you compare quotes, line them up against the same list: templates, collections, design rounds, integrations, the migration, search set-up, testing, training, and what happens when you ask for something new. A quote that leaves several of those out may cost more by the end, once the missing pieces are priced.

Webflow itself. On 31 October 2026, Webflow's pricing page listed these plans:

Check the page before you budget: Webflow changes its plans, extra seats for designers and editors are billed separately, and usage beyond a plan's allowance is billed on top. Ask the agency which plan and how many seats your team will need after handover.

How long a Webflow build takes

The answer that matters isn't the total. It's which part depends on you.

Here's how our own Webflow builds run once the design is settled, as published on our service page:

If the site needs designing first, add that. Our SaaS website projects, design and build together, take four to eight weeks for most sites. Flowout's guide puts a focused 10 to 15 page marketing site at three to four weeks from kickoff and larger sites with a complex CMS at six to ten.

The delays we see most often aren't in the build. They're in the copy that isn't written, the logo files nobody can find, and the approval that needs one more person. If your launch date is fixed, ask the agency what it needs from you and by when, and put those dates in the plan next to theirs.

How to write a Webflow brief

A brief turns three quotes for three different jobs into three quotes you can compare. It doesn't need to be long. One page is enough if it answers these:

1. What the site is for. One goal comes first: demo bookings, sign-ups, applications, sales. Everything else follows from it.
2. The templates. List each page design, not each page: homepage, product page, pricing, blog post, blog index, case study, careers, contact. Next to each, how many pages will use it at launch.
3. What the CMS has to hold. Every kind of content your team will add after launch, and who adds it. If a case study needs an industry and a service attached, say so.
4. What exists already. A design file or not. Copy written or not. Brand files. The current site's address.
5. What has to connect. The CRM forms post to, analytics, a booking tool, a newsletter.
6. The move. How many pages the old site has, and which ones bring in traffic. Your analytics or Search Console will tell you.
7. Dates and budget. The launch date and why it matters, and a budget range. Agencies scope to a budget; without one, they guess.
8. Who decides. One person who signs off design and copy, and anyone else who has to see it.

The template list is the part we'd never skip. It's what a fixed price should be written against, and it's the fastest way to see whether two quotes are for the same site.

What to check before you sign

A portfolio shows taste. It doesn't show whether a site is pleasant to run a year later. These checks do:

Open the live sites, not the screenshots. Load two or three on your phone. Fill in a form. Click into a blog post and back out. A good-looking site that's slow or broken on a phone is telling you something. Then run two of them through Google's free PageSpeed Insights. It's one rough reading, not a verdict, but a portfolio of sites that all score poorly on mobile tells you how the team builds.

Ask to see inside a build. Ask the agency to open a finished site in Webflow's Designer on a call, one whose client is happy for you to see it. Look at the class names: "hero-heading" and "pricing-card" are readable; "div-block-47" means the next person starts again. Look at whether the same card is one component or ten copies.

That's the same discipline as a design system. For Zaic Education, a tutor's workspace we designed, the screens sit on one typeface, colour scales, 29 icons and a set of components made for the product. A Webflow build should work the same way: a small set of named styles and components, used everywhere.

Ask how they'd structure your CMS. Give them two kinds of content from your brief and ask which collections and fields they'd make. A clear answer in five minutes is a good sign. "We'll figure it out in the build" isn't.

Ask for the editor test. Before the project is called finished, someone on your team should change something real without help: publish a post, swap a picture, add a page from a template. Put that test in the plan, with a date.

Ask who built what. Design for Webflow and the build in it are different skills, and a portfolio can mix them. Ask which sites the team built itself. A good case study says. Ours for Finsaro, a finance website template on the Webflow Marketplace since May 2026, says we designed it and the template studio we designed it for built its eleven pages in Webflow.

Look them up. Webflow keeps a directory of Certified Partners, more than 1,200 of them, which it says it has vetted. It's a reasonable filter. A team outside it isn't ruled out, and one inside it still needs the checks above. Reviews on third-party sites and a call with a past client are worth more than either.

Questions to ask on the first call

Listen to how specific the answers are. A team that has done this before answers with examples.

• Would you build this in Webflow, or would you suggest something else?
• Who will work on our site, and who will I talk to every week?
• If a publish breaks a live page, how do we roll it back, and who does it?
• What will you need from us, and by when?
• How do you price this: per template, per page, or by time?
• What happens when we ask for something that isn't in the quote?
• How would you set up the CMS for our case studies and blog?
• How do you handle the old site's URLs and redirects?
• How do you check speed and the phone layout before launch?
• Whose Webflow account is the site built in, and when does it move to ours?
• What does support look like in the month after launch, and after that?

Red flags

• No live Webflow sites to show, only images.
• A price far below the others with no explanation of what's missing.
• No question about your old site's URLs if you have one.
• A promise of rankings. Nobody controls Google.
• No mention of training or handover.
• Pressure to sign this week.
• The site stays in the agency's account with no plan to move it.

How to move to Webflow without losing traffic

A new platform doesn't lose traffic on its own. Old addresses that stop working on launch day do. Search engines and links still point at them, and they all land on a 404.

We've lived the other side of this. When we rebuilt our own site, ten pages out of fifteen on the old site were already broken or redirected, and none of them showed up when founders searched for what we do.

The steps that protect you:

1. List every old URL before any design starts: pages, blog posts, case studies, and anything an old campaign linked to.
2. Mark the pages that earn traffic from your analytics or Search Console. Those keep their content, and ideally their address.
3. Write the redirect map: every old URL against its new one. Pages you're retiring point to the closest match, not to the homepage.
4. Set the redirects up before launch and test them on the live domain on the day.
5. Watch Search Console for a few weeks after launch for pages that drop out.

Webflow has its own rules worth knowing, from its help article on setting up redirects:

• Redirects need a paid site plan, or a Workspace with a paid Workspace plan.
• They're added in Site settings, under Publishing, and they work only after you publish.
• You can import and export them in bulk as a CSV file.
• Webflow doesn't set a hard limit today but recommends no more than 1,000 rules, and suggests wildcard rules for whole folders, written with capture groups, such as sending /blog/(.*) to /articles/%1.
• Redirects don't apply to localized versions of a page: /old-url and /es/old-url need separate rules.

That last one catches sites in more than one language. If yours is, ask the agency how they'll handle it before you sign.

After launch: who owns the site

Get this in writing: the site, its Webflow project, the design files, the pictures and the domain belong to you, and any font licences are in your name.

If the agency builds in its own Webflow Workspace, the site has to be transferred to yours at the end. Webflow's help article on transfers says only a Freelancer or Agency Workspace plan can transfer a site with a paid site plan to a client, and the client's Workspace can't be an Enterprise one. You accept the transfer from an email, add your card, and reconnect any third-party apps. After that, you can add the agency as a Workspace guest, as long as it's on a Freelancer or Agency plan.

So ask early whose account the site will live in, who pays for the site plan, and when it moves to you. It's an easy question at the start and an awkward one at the end.

Then the work after launch:

• A fix period. Bugs found in the first few weeks should be fixed without a new quote. Ask how long.
• A handover session. One session with the people who'll run the site, and written notes they can go back to.
• Help after that. Hourly, a retainer, or a monthly plan. Pick the one that matches how often the site really changes.

If you're hiring for the design of a product as well as its website, our guide to choosing a product design agency covers that hire. And if the site is a SaaS marketing site, our list of SaaS website design agencies compares ten studios on price, platform and fit.

FAQ

If you'd like to talk to a team that designs and builds in Webflow, this is what our Webflow development service covers: the build, the CMS, the move and the handover, at a fixed price against a written page list.