Translucent glass pavilion glowing at sunset, illustrating how to choose a Webflow agency

How to Choose a Webflow Agency: 10 Things to Check Before You Sign

November 12, 2026

A practical checklist for choosing a Webflow agency: custom design, custom development, SEO, CMS, process and support, plus 12 questions to ask on the first call.

To choose a Webflow agency, look at how they build, not only at what their sites look like. Open their live websites on your phone, ask to see inside one of their Webflow projects, and ask who will handle SEO, the CMS and support after launch. An agency that answers those three things clearly is usually a safe choice.

Most agency websites look good. That is the problem. A polished homepage tells you the agency can design, but it tells you nothing about what happens when your marketing manager tries to add a case study in six months, or when Google re-crawls your site after the redesign.

We build on Webflow every week at Made Tight, and we also inherit Webflow sites built by others. Some are a pleasure to work on. Others have to be rebuilt because nobody can safely change a heading without breaking three other pages. From the outside, both kinds looked equally good on launch day.

It also matters what you are actually buying. A custom designed and custom developed website is a different product from a template with your logo on it, yet both are sold as "a Webflow website".

This guide shows you how to tell them apart before you sign. It covers 10 things to check, the questions to ask on the first call, the red flags that should make you walk away, and whether a local or a remote agency makes more sense for you.

Quick answer: what a good Webflow agency looks like

If you only have five minutes, check these points first.

  • Custom design: designed for your brand, content and audience in Figma, not a template with new colors
  • Custom development: built from a blank Webflow project to match that design, with a consistent class system and reusable components
  • Real Webflow work: live client websites built in Webflow, in a similar size and complexity to yours
  • A CMS your team can use without training for a week
  • SEO handled at launch: redirects, meta data, structured data and analytics are part of the project, not an extra
  • Fast pages: their own site and their client sites score well in PageSpeed Insights on mobile
  • A clear process: written scope, a timeline with milestones, and one person you talk to
  • You own everything: the site sits in your Webflow workspace, on your domain, with your logins
  • Support after launch: a defined way to get new pages, fixes and updates

The rest of this article explains how to verify each point, even if you have never opened Webflow yourself.

Custom design and custom development, or a template?

Before you compare agencies, decide which of these two products you want. Two agencies can both offer "a Webflow website" and mean very different things.

A template site starts from a ready-made layout. The agency changes colors, fonts, images and text. It is fast and affordable, and it can be a fair choice for a first website. The limits show up later: the layout was not made for your content, other companies use the same template, and you inherit a structure nobody on the project designed.

Custom design means the website is designed for your brand, your audience and your content. It starts from strategy, a sitemap and wireframes, and every layout, type choice, illustration and interaction is made for you in Figma. Nothing is picked from a theme library.

Custom development means the site is built from a blank Webflow project to match that design exactly. The agency creates its own class system, components and CMS structure, and adds only the code the site needs. The result loads faster, is easier to maintain and can grow with new pages and features without a rebuild.

Here is how to tell which one an agency is selling:

  • Ask to see the Figma file for a finished project. Custom work has one, with wireframes and design iterations.
  • Ask whether the build started from a blank project or from a template or cloneable.
  • Compare their portfolio sites with each other. If several share the same layout with different colors, you are looking at templates.
  • Read the proposal. It should name custom design and custom development as separate phases, each with its own deliverables.

If your website is a main sales channel, custom design and custom development are what you should be paying an agency for. It is not the only way we work at Made Tight, but it is the one we prefer, because custom work is what makes a client's website unique. It is also the standard the rest of this checklist assumes.

10 things to check before you hire a Webflow agency

1. Live Webflow websites, not only mockups

Start with the portfolio, but look past the cover images. A case study made of Figma screens proves the agency can design. It does not prove they can build.

Open three or four of their live client websites and do this:

  • Open them on your phone. Most of your visitors will. Check the menu, the forms and the long pages.
  • Click around like a customer. Do pages load fast? Do animations help, or do they get in the way?
  • Look for projects like yours. A five-page startup site and a 300-page site with a blog, a resource library and three languages are different jobs.
  • Check that the site is still live and looked after. A site that broke a year after launch tells you something about handover and support.

You can confirm a site runs on Webflow by viewing the page source and searching for "webflow". Agencies that build on several platforms are fine, as long as Webflow is something they do often, not once a year.

2. Build quality inside the project

This is the check most buyers skip, and it is the one that decides how much your site will cost you over the next three years.

Two Webflow sites can look identical in the browser and be completely different inside. One has a clear class naming system, reusable components and a logical page structure. The other has hundreds of classes called "Div Block 47" and styles copied from page to page. The first one takes ten minutes to update. The second one takes a day and a lot of courage.

Ask the agency to share their screen and walk you through a finished project in the Webflow Designer. You do not need to be technical to judge what you see. Ask:

  • How do you name classes? A good agency follows a system, such as Client-First or its own documented convention, and can explain it in two sentences.
  • What is a component here? Navigation, footer, cards and call-to-action blocks should be built once and reused.
  • How would I change the brand color? The right answer is "in one place, with a variable". The wrong answer is "we would go through the pages".
  • Do you deliver a style guide page? A page that shows every heading, button and form style is a sign of an organized build.

If an agency is reluctant to show the inside of any project, treat that as an answer.

3. Custom design and custom development in one team

Many website problems start in the gap between the designer and the developer. The designer hands over a file, the developer interprets it, and details get lost: spacing, hover states, how a section behaves on a tablet.

Ask who designs and who builds. The safest setups are:

  • One team that does both, where designers and Webflow developers work on the same project from the first week
  • A developer who is involved before design is final, so nothing is designed that will be slow or fragile to build

At Made Tight our custom sites are designed in Figma and developed in Webflow by the same team, so the person who builds can ask the person who designed. If you already have a design from another team, ask the agency how they handle a build from an existing Figma file and what they need from you. We describe our own setup on the website design and development page.

4. A CMS your team can use

You are probably choosing Webflow because your team wants to update the website without a developer. That only works if the CMS is planned properly.

Ask the agency how they would structure your content. A good answer mentions collections for the things you publish often, such as blog posts, case studies, team members, job openings or locations, and explains which fields each one needs.

Then ask for a short demo of the editing experience on a real project:

  • Adding a new blog post or case study from start to publish
  • Changing a headline and an image on a static page
  • What an editor cannot break. Good builds limit editors to content, so layout and styles stay safe.

Also ask what you get at handover. A recorded walkthrough of your own site, in your own CMS, is worth more than a generic help article.

5. SEO handled as part of the build

A redesign is the most common moment for a company to lose search traffic. Pages change URL, old links break, titles get rewritten, and nobody notices until leads drop two months later.

A Webflow agency does not have to be an SEO agency, but it must handle the technical basics as part of every launch:

  • A redirect map from every old URL to its new one
  • Unique titles and meta descriptions, with templates for CMS pages
  • Correct heading structure and descriptive image alt text
  • Structured data where it fits, such as organization, article and FAQ markup
  • A clean sitemap and correct indexing settings, so test and utility pages stay out of Google
  • Analytics and Search Console connected and checked on launch day

Ask what happened to organic traffic on the last site they migrated. If you are moving from another platform, read our 10-step checklist for migrating to Webflow without losing SEO and ask the agency how their process compares.

6. Page speed and Core Web Vitals

Webflow hosting is fast by default, but a site can still be slow. Heavy images, too many scripts, autoplay video and animation on every element add up quickly.

You can test this yourself in two minutes. Take the agency's own website and two client sites from their portfolio, and run each through PageSpeed Insights. Look at the mobile result, because it is the stricter one.

  • Largest Contentful Paint shows how long the main content takes to appear
  • Cumulative Layout Shift shows whether the page jumps around while it loads
  • Interaction to Next Paint shows how quickly the page reacts to a tap or click

No site is perfect, and a rich, animated site will score lower than a plain one. What matters is that the agency knows its numbers and can tell you what it does about them: modern image formats, lazy loading, loading scripts late, and using animation with a purpose.

7. A clear process, scope and timeline

A good Webflow project follows a predictable path. The names differ from agency to agency, but the steps are usually these:

  1. Discovery: goals, audience, competitors and what the current site does well or badly
  2. Sitemap and structure: which pages exist, what each one is for, and what goes into the CMS
  3. Wireframes and design: layout first, then the visual design in Figma, with your feedback at set points
  4. Build in Webflow: pages, components, CMS, interactions and responsive behavior
  5. Content, SEO and QA: real content in, redirects prepared, testing on real devices and browsers
  6. Launch and handover: go-live, checks in Search Console, CMS training

Ask the agency to walk you through its version and to tell you what it needs from you at each step. Late content and slow feedback delay more projects than anything on the agency's side, and an honest agency will say so on the first call.

You should also get a written scope before you sign. It should list the pages and templates, the number of feedback rounds, what is included in SEO and integrations, and what counts as extra work. Whether the agency prices by fixed project or by monthly retainer matters less than whether the scope is written down.

8. Ownership and access

This one is simple, and it saves a lot of trouble later. When the project ends, you should own:

  • The Webflow site, in a workspace that belongs to your company
  • The domain and DNS, registered in your name
  • The design files, usually a Figma file you can open and share
  • Every connected account: analytics, Search Console, tag manager, forms, CRM and any paid plugins

Some agencies keep client sites in their own Webflow workspace and bill hosting through it. That can be convenient, but agree up front how a transfer works if you ever want to leave. Webflow lets a site be transferred between workspaces, so there is no technical reason for you to be locked in.

Also ask about custom code. A few small scripts are normal. A site that depends on thousands of lines of custom code is harder for the next person to maintain, including your own team.

9. Support after launch

A website is finished on launch day in the same way a shop is finished on opening day. You will need new landing pages, new sections, fixes, integrations and the occasional redesign of a page that is not converting.

Ask how the agency works with clients after launch:

  • Is there a support or maintenance plan, and what does it cover?
  • How fast do they respond to a small request and to something urgent?
  • Who does the work? Ideally the same people who built the site.
  • Can you buy a block of hours or a monthly retainer for ongoing design and development?

An agency that already knows your brand and your build will do this work faster and more consistently than a new freelancer each time. If the agency only does launches and nothing after, you need a plan for who will look after the site.

10. Reviews and references

Finally, check what other clients say. Independent review platforms such as Clutch are useful because the reviews are verified and usually describe the project, the budget range and what went well or badly.

Go one step further and ask for a reference call with a past client. Ask that client three things: was the project on time, how did the agency handle a problem, and would they hire them again.

12 questions to ask a Webflow agency on the first call

You can take this list into any intro call. Good agencies answer most of these without being asked.

  1. Which of your live sites is closest to what we need, and what was your role in it?
  2. Who will design and who will build our site? Will we meet them?
  3. Can you show us inside one of your Webflow projects?
  4. What class naming system do you use, and do you deliver a style guide?
  5. How will you structure our CMS, and what will our team be able to edit?
  6. What is included for SEO at launch? Who prepares the redirects?
  7. How do you test performance and on which devices?
  8. What do you need from us, and when? Content, feedback, access.
  9. What does the timeline look like, and what usually causes delays?
  10. Whose Webflow workspace will the site live in, and how does a transfer work?
  11. What happens after launch? Support, response time, ongoing work.
  12. Can we speak with a client from a similar project?

Listen to how the answers are given as much as to what is said. Specific answers with examples are a good sign. Vague answers and a quick move to the contract are not.

How to compare proposals side by side

Once you have two or three proposals, compare them on the same criteria, not on the total price alone. A simple scoring exercise helps:

  • Understanding: does the proposal show that they understood your goals and audience?
  • Relevant experience: have they built similar websites, in Webflow, for similar companies?
  • Custom or template: does it say clearly whether you get custom design and custom development, or an adapted template?
  • Process: is every phase described, with deliverables and approvals?
  • Scope clarity: is it clear what is included and what is not?
  • SEO and content: is search visibility part of the plan?
  • Support: is there a plan for after launch?
  • Team fit: did the calls feel easy, clear and honest?

The proposal that scores best across these points is usually the one that delivers the best website, even when it is not the cheapest.

What affects the cost of a Webflow website

Every agency prices differently, but the same factors drive the effort on every project. Understanding them helps you read proposals and decide where to invest:

  • Custom design or template. A custom design made for your brand takes more time than adapting a template, and it is the part that makes the site yours.
  • Number of unique templates. Ten pages built from three templates take less work than ten completely different layouts.
  • Design complexity. Custom illustrations, 3D, complex animations and scroll interactions add design and development time.
  • CMS depth. Each collection needs fields, templates, filters and testing with real content.
  • Content. Writing copy, sourcing photography and migrating large amounts of existing content are often the biggest hidden efforts.
  • Languages. Each additional language needs translated content, localized SEO and testing.
  • Integrations. CRM connections, marketing automation, gated content and custom forms add setup and testing.
  • Migration and SEO. Protecting existing rankings requires auditing, redirect mapping and post-launch monitoring.
  • Brand readiness. If the brand identity is not defined yet, it is usually better to start with branding before designing the website.

When you know which of these matter most for you, you can ask agencies to prioritize them and simplify the rest.

Red flags when hiring a Webflow agency

Some signs are strong enough to end the conversation early.

  • No live sites to show. Only mockups, or links that no longer work.
  • Templates sold as custom design. A template can be a fair choice for a small budget, but you should know that is what you are buying.
  • They will not show a project in the Designer. There is rarely a good reason for this.
  • SEO and redirects are "not part of the build". Then someone else has to do it, or it will not be done.
  • A price before any questions. An agency that quotes without asking about your pages, content and goals is guessing.
  • A timeline that sounds too short. A custom site with strategy, design, build and content rarely fits into two weeks.
  • The site stays in their account with no exit plan. You should be able to leave with your website.
  • No named contact. If you do not know who answers your messages, expect slow answers.
  • Slow or unclear replies before you sign. Communication does not improve after the contract.

Local agency or remote agency: does location matter?

Webflow is a browser-based tool, so the work itself can be done from anywhere. Most Webflow projects today run fully remote, with calls, shared Figma files and written feedback. Location still matters in three practical ways.

Time zone. A few hours of overlap in the working day makes feedback rounds much faster. A team in Central Europe shares most of the day with clients across Europe and still overlaps with the US East Coast in the afternoon.

Language and market. If your site needs more than one language, or you sell in a specific country, an agency that knows that market will ask better questions about content, legal pages and local search.

Value. Rates differ a lot between regions for the same level of skill. Many companies in Western Europe and the US work with agencies in Central and Eastern Europe for that reason, and judge them on the same things as any other agency: the work, the process and the references.

Made Tight is based in Belgrade, Serbia, and works with startups, SaaS and B2B companies across Europe and the US. If you are looking specifically for a Webflow agency in Belgrade, that page explains what we build, how we work and what is included.

Webflow agency, freelancer or in-house: which one do you need?

An agency is not always the right answer. The choice depends on the size of the job and on what you need after launch.

A freelancer fits a small site with a clear brief, a ready design and a limited budget. The risk is availability: one person can be sick, busy or gone when you need a change.

An agency fits when you need strategy, design, development and SEO together, when several people on your side are involved, or when the website is a main sales channel. You pay more than for a freelancer, and you get a team, a process and continuity.

An in-house hire fits when the website changes every week and you have enough ongoing work for a full-time role. Many companies combine the two: an agency builds the system, and an in-house marketer runs the CMS day to day.

If you are still deciding on the platform itself, our comparison of Webflow vs WordPress covers editing, SEO, security and maintenance side by side.

FAQ

What does a Webflow agency do? A Webflow agency designs and builds websites on Webflow. A full-service one also covers strategy, content structure, CMS setup, technical SEO, integrations, launch and ongoing support.

How long does a Webflow website take? A smaller marketing site usually takes three to six weeks from kickoff to launch. Larger sites with many templates, a migration or several languages take longer. Content and feedback speed on the client side affect the timeline as much as the build.

Can my team edit the site after launch? Yes, if the site is built for it. Ask the agency to set up CMS collections for the content you update often and to train your team on your own site before handover.

Will I own my Webflow website? You should. The site should sit in your company's Webflow workspace, on a domain registered to you, and you should receive the design files. Confirm this in writing before the project starts.

Can a Webflow agency move my site from WordPress? Yes. A migration includes moving content into the Webflow CMS, rebuilding templates, and mapping every old URL to a new one with 301 redirects so you keep your rankings.

Should I choose a Webflow agency in my own country? Only if you need in-person meetings or local market knowledge. Most Webflow projects run remotely. A few hours of time zone overlap and clear communication matter more than the address.

What should a Webflow agency deliver at the end? A live site in your workspace, a style guide page, a CMS your team can use, redirects and SEO settings in place, connected analytics, the Figma file, and a recorded walkthrough of how to edit the site.

Looking for a Webflow agency?

Made Tight does custom Webflow design and custom Webflow development for startups, SaaS and B2B companies. Custom is the work we like most, because it gives each client a website that is unique to them, and we are happy to be checked against every point in this article. See how we work as a Webflow agency, look through our work, or book a 30-minute intro call and bring the 12 questions with you.

Related: How to migrate to Webflow without losing SEO.

Similar Articles