How to Choose the Right Webflow Agency for Your Business

Functionality is where portfolios actually differ. A brochure site and a site carrying complex interactions are different projects, and heavy animation is the one most likely to be beyond a team that has only shipped the former.

Be sceptical of CMS claims. Every agency says it builds CMS-driven sites, and from the outside it is close to unverifiable: you cannot see how the collections are structured, or whether your marketing team could publish from them without a developer. Ask to be walked through a live one instead of taking the claim.

Ecommerce and memberships are rare enough in Webflow that most agencies, us included, will have little to show. If your build turns on either, look for a specialist. Ours are collected in our case studies, if you want a sense of what to ask for.

In practice this is the first filter most companies apply, ahead of anything technical. A company that has just raised a Series C looks for a vendor who has built at that stage, because the problems are stage-specific: a bigger story to carry, more stakeholders to satisfy, and a sales team that did not exist a year ago.

Work for a direct competitor is the strongest signal available. It means the agency already understands your buyer, and you are not paying for that education.

Webflow development on its own is close to table stakes now. AI has compressed the build, so the moat sits upstream: the strategy that decides what the site says, and the taste that decides how it looks. The useful question is not "did you build this" but "did you decide what it should be".

Portfolios mix built, designed, inherited and redesigned work without labelling any of it, so ask outright.

The narrower arrangement is legitimate too. Plenty of projects are a migration where an internal design team owns the look and the agency is hired for the build alone. If that is your setup, say so early: you are buying a narrower thing and should not be paying for the wider one.

Clients leave for ordinary reasons. Ask about it before you read anything into it: a portfolio where nothing survived is the version worth understanding.

Ours is a case in point. Bland AI moved off Webflow onto an agentic stack so their own team could own inbound and ship faster, which was the right call for them. Being asked about it is fair. An agency that cannot answer the question straight is the actual signal.

Client work always carries compromises the agency did not choose: a budget that ran out, a deadline that moved, a stakeholder who insisted on the video header. Their own website has none of that. Whatever you find there is the standard they hold themselves to.

Aim for LCP under 2.5 seconds and CLS under 0.1. Check mobile and desktop separately: the two often differ a lot, and mobile is usually the worse of the pair.

Based on guidance from

Philip Walton

Engineer @ Google

Read the source

Designers pick a few screen sizes to work at: a phone, a tablet, a laptop. Sites usually look right at exactly those sizes and come apart in between, or at the very narrow end. Dragging the window slowly is how you find that in about thirty seconds.

How much it matters depends on your traffic. If most of your buyers arrive on a phone, treat it as close to critical. If you sell to enterprise teams working on desktops, it matters less.

Further reading

Ahmad Shadeed

Design Engineer

Read the source

This is a common Webflow build error. Usually one element sits a little wider than the screen and drags the whole page with it.

Finding it does not automatically mean the agency was careless. If the client has been editing the site since launch, the overflow may well be theirs. Ask who has been maintaining the site before you count it against anyone.

Firefox’s developer tools flag the element causing it, which turns a guessing game into a ten-second check.

Based on guidance from

Ahmad Shadeed

Design Engineer

Read the source

Press F12 (fn + F12 on a Mac), open the Network tab, filter to images and reload. Five images across five pages is enough to see the pattern.

Images are usually the heaviest thing on a page, so the format is a large part of whether a site feels fast.

Based on guidance from

Jeremy Wagner

Technical Writer @ Google

Read the source

Anyone navigating by keyboard, people with motor disabilities, screen reader users, or anyone whose mouse has just died, tracks their position on the page by that outline. When it slides under a pinned navigation bar, they lose their place with no way to tell where they are.

WCAG names this directly: when something takes focus, it must not be hidden by other content on the page.

Webflow’s sticky navigation causes exactly this unless someone deliberately fixes it, so it reads well on whether the team finishes the parts nobody asks about.

Based on guidance from

Sara Soueidan

Accessibility Consultant

Read the source

Almost nobody zooms a page to 200%. What people who need bigger text change is the default font size in their browser settings, once, and it applies to every site they visit.

Text sized in rems respects that setting. Text sized in fixed pixels ignores it completely.

Browser zoom scales everything, pixels included, so zooming hides the problem. Change the font size setting instead, then reload one of their sites.

Based on guidance from

Josh W. Comeau

Software Engineer and Educator

Read the source

Automated scanners cover only part of what can go wrong. A score of 100 means the obvious problems are gone, not that the site works for everyone.

A team doing this properly will name most of these: an automated pass with Lighthouse or axe DevTools; tabbing the whole page with the keyboard; switching the stylesheet off to check the reading order still makes sense; validating the HTML; checking the heading outline; and viewing the page in grayscale to catch anything that relies on colour alone.

How much this matters depends on who you sell to. Government, education, healthcare and large enterprises usually treat accessibility as a procurement requirement, and failing it loses deals outright. Selling to small startups, it rarely comes up.

Based on guidance from

Manuel Matuzović

Frontend Developer and Accessibility Auditor

Read the source

Titles are among the cheapest work in a build, and SEO belongs in every build. So when titles are missing or duplicated on a site that has already shipped, what you are seeing is the level of detail the team worked at. Details were getting dropped somewhere.

Length matters more than most people think. In a study of 80,959 titles, Google rewrote about 61% of them, and titles over 70 characters were rewritten almost every time. Titles that matched the page’s H1 were rewritten far less.

Based on guidance from

Cyrus Shepard

Founder @ Zyppy SEO

Read the source

Heading levels describe how a page is put together: what is a section, and what sits inside it. That is a semantic decision, made by the content.

The common mistake is picking a heading level for how big the text looks. We see it in Webflow builds from large agencies. If a heading needs to be smaller, that is a CSS change: the level stays where the content puts it.

Checking it takes a minute: SEO Meta in 1 Click lists a page’s full heading outline. Three H1s, or an H2 jumping straight to an H4, is the tell.

Headings are how people scan a page and how machines read its structure, so a broken outline costs you on both sides.

Based on guidance from

Manuel Matuzović

Frontend Developer and Accessibility Auditor

Read the source

You cannot audit a migration someone else did. You will not know whether a site was ever replatformed, and third-party tools do not hold reliable before-and-after ranking data for a domain you do not own. What you are judging here is the answer itself.

Change the URLs, rebuild the templates, rebrand on top of it, and some ranking loss usually follows even when the redirect mapping, the baseline and the launch checks are all done properly. The work is to keep the dip small and short, and to know when it should recover.

Plenty of agencies will tell you otherwise. An agency promising no loss at all is either inexperienced or selling you something, and both cost you more than the honest version. Take the team that tells you roughly what the dip will look like and how they intend to shorten it.

A team that has done this before will also have a list of what they check the moment the new site goes live: robots.txt, canonicals, meta robots, redirect chains on the top landing pages, tracking, the XML sitemap.

Based on guidance from

Glenn Gabe

President @ G-Squared Interactive

Read the source

Ask to see the actual document. What you want named is the stages, what gets produced in each one, who signs it off, and what they need from you before the next stage can start: usually content, access, or a decision.

A written process survives pressure. When a deadline moves or someone leaves, the team still knows what happens next and so do you. A process that only lives in conversation quietly changes shape, and you find out at the point where you had assumed something was already done.

It also shows you where you are the bottleneck. Most projects that slip are waiting on the client for content or approvals, and a written workflow makes that visible early enough to do something about it.

A team that has launched sites has a list and will read it to you. Vagueness here is the clearest warning you get before signing.

Ours is public if you want something to compare against: 61 checks across pre- and post-launch.

Based on guidance from

Evgenii Tilipman

Founder and Tech Lead @ Khod

Read the source

Projects drift. Someone waits on an answer, a task slips a few days, and nobody raises it because nothing has technically gone wrong yet.

A fixed weekly slot catches that while it is still days instead of weeks. Overcommunicating costs an hour. Finding out in week six that week three went sideways costs the timeline.

Ask who the person is by name, and what happens when they are away.

Revisions are part of every project. The arguments start after the work is done, when it turns out nobody agreed what was included.

Get three things in writing: how notes are collected, how many rounds the quote covers, and the price of one more. Feedback consolidated in one place also saves you a round on its own: notes arriving by email, Slack and phone call over four days get half-applied.

Quotes on an agency’s own site are chosen by the agency. A rating on a third-party platform carries a count and a date, which is what lets an outsider weigh it.

A 5.0 from three reviews two years ago and a 4.7 from sixty in the past year are very different signals, and the second one is the stronger of the two.

One reference is a friend. Two is a pattern.

Something goes wrong on every project. What you are listening for is what happened next: who raised it, how quickly, and whether the fix came out of the client’s budget.

Then ask whether they would hire the agency again for the same work. That one is harder to answer politely than “were they good”, which is what makes it useful.

We were asked for exactly this recently. We put forward two people from Chili Piper: one who has since moved on, and one still there. The person who has left is usually the more useful call, because they have no reason to be diplomatic. Any agency that is comfortable with its work will hand over both without flinching, and hesitation here is itself an answer.

Plenty of companies want a build and nothing more, and that is a perfectly good answer from either side. Ask anyway, so you know before the build rather than after.

If you do want ongoing work, ask what else that team is currently running. An agency that builds well and is already at capacity is the wrong fit for the second job.

Scope changes on nearly every project. The dispute only happens when the price of a change was never agreed.

Six separate things, and agencies routinely hold some of them: the Webflow project itself, transferred to your workspace rather than living in theirs; the Webflow site plan, billed to your card; the domain, registered in your name at your registrar; the design files; any custom code written for you; and your analytics, with GA4 and Search Console owned by your Google account.

Each one is free to agree now. Each one is leverage if you ever want to leave. If any answer is not "you own it", find out exactly why before you sign.

Platform security is Webflow's job and they do it well. What still needs an owner is your cookie banner and consent setup, where form submissions are stored and who can read them, and any third-party scripts added to the site.