How to Choose a Webflow Agency for a B2B Website

Key takeaways

A Webflow site is owned by the Workspace it sits in, not by whoever paid for it. Paying the hosting bill gives you no ownership rights.
Webflow will not accept a contract as proof of ownership in a dispute. It asks for photo ID, a card invoice or a business license. Your contract protects you against your agency, not against your agency disappearing.
Build in your own Workspace and invite the agency as a guest. It is free, it needs no transfer, and you remove them when the project ends.
If your company sits on a Webflow Enterprise Workspace, an agency cannot transfer a live site to you directly. The site has to be downgraded to Starter first, which takes it offline until the new owner republishes. Plan this before launch week, not during it.
Ask which role you get by name. Editor access changes text and images. Designer access changes everything. The two are often described with the same words.

Eight questions before you sign. A table of what a client ends up owning after a Webflow project: the site project, CMS content and billing are decided by the Workspace, the custom domain is yours, and design files and custom code are decided by the contract.

1. Who owns the site when the build is done?

Ask this first, and ask it before the proposal, not after. Webflow's own documentation is unusually blunt about the answer: sites are owned by the Workspace they sit in. If the site is built in an agency's Workspace, that Workspace owns it, and in Webflow's words the client "won't automatically have rights to transfer or duplicate the site unless it's explicitly agreed on." Paying the hosting bill does not change this. Webflow states plainly that a client may be allowed to manage billing, and that this "doesn't give them additional rights over site ownership."

Most agencies will tell you that you own the website, and most of them mean it. The problem is that the sentence describes your contract, not your Webflow account, and those are two different things that only look the same until something goes wrong.

The detail that most buyer guides get wrong

The standard advice is to put ownership in the contract. That advice is incomplete in a way that matters. In a disputed ownership request, Webflow may ask for a government-issued photo ID, a credit card invoice, or a business license, and its documentation says explicitly that it cannot accept "emergency contact details or contracts as proof of ownership."

So a contract clause protects you against your agency. It does not protect you against the situation where your agency is simply gone. Webflow is clear about that case too: if the agency becomes unreachable, Webflow cannot transfer their account or export your site to you. The most it can do is let you take over the billing to keep the site alive. If the payment details lapse, the site is removed.

A contract is still worth having. It is just not the thing that makes the site yours.

2. Whose Workspace will the site live in?

This is the question the first one collapses into, and it has a clean answer that costs nothing. You create the Workspace on your company account, and you invite the agency in as a guest.

Webflow built the guest role for exactly this. Guests join free, they do not need your password, and they get access to the sites you choose without reaching your confidential Workspace settings. You decide which sites they can touch, whether they can publish, and whether they can bring additional people in from their side without your approval. When the project ends, you remove the guest. Nothing moves, nothing transfers, nothing needs anyone's goodwill.

If an agency tells you this arrangement is not workable, ask them to explain why, because the only honest reasons are about their internal tooling, not about your site. Those reasons may be real. They are still your risk to accept, not theirs to decide.

3. If it is built in your Workspace, can it actually be transferred to us?

Here is where enterprise buyers get caught, and it is the single most useful thing on this page if you are running a large B2B site.

Webflow's transfer feature has requirements that are easy to miss. Only Freelancer and Agency Workspace plans can transfer a site that has an active paid Site plan. And the destination Workspace must not be an Enterprise Workspace.

Read that twice if you are an enterprise company. If your organization sits on a Webflow Enterprise Workspace, which is exactly where a company with several brands, markets or procurement requirements tends to sit, then an agency cannot hand you a live site directly. The site has to be downgraded to the Starter Site plan first, then transferred, then brought back up. The same applies in reverse when the agency's own Workspace is on Starter, Core, Growth or Enterprise rather than Freelancer or Agency.

And the downgrade is not cosmetic. Webflow's documentation states that it "will result in site downtime if it's been published," and that afterwards the new owner has to upgrade to a paid Site plan, reconnect the custom domains and publish again before the site is live. If the destination is an Enterprise Workspace there is one more step: the new owner has to work with their Webflow Enterprise account team to provision the plan first. On a B2B site that is a procurement dependency sitting in the middle of your launch week.

None of this is a disaster. It is a sequence of steps that someone has to plan, on a live site, with a domain attached. It becomes a disaster only when nobody checked, and the handover week turns into an improvisation.

So the question to ask is not "will you transfer the site to us." It is "what Workspace plan are you on, what Workspace plan are we on, and walk me through what has to happen to the live site on the day."

4. What access do we get, and what can we do without you?

There are two very different things an agency can hand you, and they are often described with the same words.

What you are given	What you can change	What you still need the agency for
Editor access	Text and images inside existing pages and CMS items	New page types, layout, navigation, components, anything structural
Designer access in your own Workspace	Everything, including new templates and the design system	Nothing, by permission. In practice, whatever your team has not been trained on

Both are legitimate. An in-house team that only publishes blog posts may genuinely never want Designer access. The failure is not choosing one, it is discovering in month four that you were given the narrower one while believing you had the wider one.

Ask the agency to name the role. Not "full access," not "you'll have control." The role.

5. Who holds the domain?

Keep the domain in a registrar account your company owns, with a recovery address that belongs to your company rather than to one employee or to the agency. Give the agency what it needs to point DNS records at Webflow, or make the records yourself from their instructions.

The reason is the same as everywhere else on this page. In an ownership dispute, the domain is one of the few things Webflow will act on independently: its documentation notes that in some cases it may release the domain to the client if the client can prove they own it. The domain is the lever that still works when the rest has stopped working.

6. What exactly arrives at handover?

"We'll hand it over" is not a deliverable. Ask for the list, in the proposal, before you sign.

A handover that leaves a team genuinely independent tends to contain four things: the live site in a Workspace you own, recorded training for the people who will actually publish, written documentation of the components and the naming system used to build them, and a named period afterwards when questions are still answered.

For comparison, ours is video training plus a live walkthrough of the Webflow CMS editor, component documentation, and 30 days of support after handover. We are a Webflow Premium Enterprise Partner, and the test we hold ourselves to is whether the client's team publishes without us. On the meteoblue project that meant a team publishing in five languages without a developer, using the video library built during handover.

Whoever you hire, the question to ask is the same one: after you leave, who on our side can publish a new page, and what did you give them to make that possible?

7. What happens to our rankings when the site changes?

Any agency rebuilding a B2B site is changing the things search engines and AI answer engines use to work out what your pages are about: URLs, headings, internal links, page templates. Rankings are lost by changing structure, not by changing platform, which is why a redesign that stays on the same platform can be riskier than a migration that moves platforms and keeps everything else intact.

Ask for the specifics. Who inventories the pages that currently earn traffic, before anything is designed? What is the redirect plan, and who checks it after launch rather than before? What is measured in the weeks after go-live, and what is the agreed response if it moves the wrong way?

Our own answer is a written zero SEO loss guarantee on migrations. The evidence behind it is the kind of thing worth asking any agency to produce: on a migration of 823 pages for Testlio we kept the roughly 200,000 monthly visits the site was already earning, and on RAM Tracking a crawl of more than 700 pages five weeks after launch found zero internal 404s across three locales.

If an agency cannot show you a crawl from after a launch, they are describing an intention rather than a method. We set the process out page by page in Website Migration Without Losing Rankings, and the question of whether your project is a migration or a redesign is worth settling early, because it changes what has to be protected.

8. How will we know it worked, and when?

A B2B website has a long feedback loop. Pipeline attributed to a redesign arrives months after launch, which gives everyone involved plenty of room to claim success.

Agree the leading indicators before the build starts, and agree when they should move. Indexation of the new URLs happens in days or weeks. Crawl errors should be at zero within the first month. Core Web Vitals field data, which is what Google actually uses, takes about 28 days to reflect a change. Conversion rate on the pages that were redesigned can be read once the traffic is comparable. Anything framed as "traffic will go up" without a date and a mechanism is not a plan.

How do you compare two agencies that both look good?

By the time you have a shortlist, every agency on it has a portfolio you like and a case study with a number in it. Portfolios stop being useful at this point, because they are selected by the agency rather than by you.

Three things separate shortlisted agencies in practice.

Ask each one the same awkward question and compare the shapes of the answers. The Workspace question from section 2 works well for this, because it has a correct answer that costs the agency something. An agency that volunteers the guest-role arrangement before you raise it has made the trade before.

Ask for the project that went wrong. Not the hardest project, the one that went wrong. Agencies that have run large B2B builds have all had one. The useful signal is whether the answer contains a specific mechanism and a specific fix, or whether it stays at the level of "the client changed the scope."

Ask who is actually assigned. On larger B2B projects the people in the pitch are often not the people who build. Ask for the names, the roles, and what else those people are working on during your build window.

If you want to see how we and other agencies describe ourselves on these criteria, we keep a comparison of the Webflow SEO agencies working with B2B teams, including the ones we lose to.

What we would walk away from

The first three of these rest on Webflow's own documentation and the fourth on Google's. The rest are our judgement after running these projects, offered as that rather than as fact.

The site will be built in their Workspace and they are vague about the transfer. Vagueness here is the single highest-cost ambiguity in the whole project.
They offer to buy the domain for you. It can be transferred later, but it puts the one asset that still works in a dispute into someone else's account, and buys you nothing you cannot get another way.
Ownership is described only as "you own your website," with no mention of a Workspace.
They guarantee rankings, traffic, or AI citations. Google's own guidance on hiring an SEO is blunt about this: no one can guarantee a number one ranking, and if an agency promises one, find someone else.
Custom code is described as proprietary, or the component naming system is theirs rather than a public convention.
Training is listed as a line item but nobody can say who is trained, on what, or for how long.
They cannot show a single post-launch crawl from a previous migration.

What a good answer sounds like

You are not looking for agencies who claim none of this applies to them. You are looking for the ones who answer in specifics without being pushed.

A good answer to the ownership question names the Workspace and the role. A good answer to the transfer question mentions the plan requirements before you do. A good answer to the rankings question starts with an inventory rather than a promise. A good answer to the handover question tells you which person on your team will be trained, and what they will be able to do when the training is over.

The pattern underneath all four is the same: an agency that has done this often enough has already hit the edge cases, and talks about them unprompted. One that has not will tell you it will be fine.

Sources

Webflow Help Center, Site ownership. Workspace ownership, disputed ownership, and what happens when an agency is unreachable. Retrieved 6 November 2026.
Webflow Help Center, How do I transfer a site or plan to another workspace?. Workspace plan requirements and the Enterprise destination restriction. Retrieved 6 November 2026.
Webflow Help Center, Guide for clients of agencies and freelancers. The guest role, permissions, and publishing controls. Retrieved 6 November 2026.
Google Search Central, Do you need an SEO?. "No one can guarantee a #1 ranking on Google." Retrieved 6 November 2026.
Chrome for Developers, CrUX API. "The data in the Chrome UX Report is a 28-day rolling average of aggregated metrics." Retrieved 6 November 2026.

Frequently asked questions

Who owns the Webflow site after an agency builds it?

The Workspace the site sits in owns it. If the agency built it in their Workspace, they own it, and Webflow states that the client does not automatically have the right to transfer or duplicate the site unless it was explicitly agreed. Paying for the hosting does not create ownership rights. The reliable arrangement is to create the Workspace on your own company account and invite the agency in as a guest, so nothing has to be handed back at the end.

Is a contract enough to prove we own our Webflow site?

No. A contract governs your relationship with the agency, and it is worth having for that. But in a disputed ownership request Webflow asks for evidence such as a government-issued photo ID, a credit card invoice or a business license, and its documentation says it cannot accept contracts as proof of ownership. If the agency becomes unreachable, Webflow cannot transfer their account or export your site to you at all.

Can an agency transfer a Webflow site to an Enterprise Workspace?

Not directly, if the site has an active paid Site plan. Webflow allows site transfers with an active plan only from Freelancer and Agency Workspace plans, and the destination Workspace must not be an Enterprise Workspace. An enterprise company receiving a site has to have it downgraded to the Starter Site plan first, then transferred, then brought back up. Agree the sequence before launch week.

What should a B2B company look for in a Webflow agency?

Beyond the portfolio, look for specific answers on four things: which Workspace the site will live in, which access role your team receives, what arrives at handover in writing, and how existing rankings are protected when URLs and page structure change. An agency that has run large B2B builds will raise the awkward parts of these before you do.

Will our marketing team be able to publish without a developer?

That depends on the access role and on the training, not on the platform. Editor access lets a team change text and images inside pages and CMS items. Designer access in a Workspace you own lets them build new templates and change the design system. Ask which one you are getting by name, and ask who on your team will be trained and what they will be able to do when the training ends.

How do I compare two Webflow agencies that both look good?

Ask all of them the same awkward question and compare the shape of the answers rather than the polish. Ask for the project that went wrong and listen for a specific mechanism and a specific fix. Ask which named people are assigned to your build and what else they are working on during your window. Portfolios stop being useful once everyone on the shortlist has a good one.