--- title: "12 Questions to Ask a Webflow Agency Before You Hire" description: "12 questions to ask before hiring a Webflow agency—outsourcing, scope creep, and the ownership question every other list skips, plus red flags to avoid." author: "Ognjen Martinovic" datePublished: 2026-08-24 dateModified: 2026-09-04 readTime: "6 min" canonical: https://www.flowhivedigital.com/insights/questions-to-ask-webflow-agency --- # 12 Questions to Ask a Webflow Agency Before You Hire Key takeaways - The questions that protect you when hiring a Webflow agency aren't about design taste — they're about outsourcing, scope creep, and who owns the Workspace your site lives in. - Ask directly who owns the Webflow Workspace and account, not just the site: per Webflow's own Help Center, an agency's Workspace cannot be unilaterally transferred or exported to you if the agency disappears. - Five red flags should end a vetting call outright: a 48-hour fixed quote with no discovery call, no live sites to visit, the seller vanishing after signing, a dodged ownership question, and unwritten post-launch support terms. If you're vetting Webflow agencies, the questions that actually protect you aren't about design taste — they're about outsourcing, scope creep, and who owns the Workspace your site lives in. Ask these 12 before you sign anything, and the answers (or the dodges) will tell you more than any portfolio call. A bad agency pick doesn't just waste the project fee. It costs a second rebuild plus every week of pipeline you lose while the first site limped along or got stuck mid-handoff. These questions are ordered the way a real vetting call should go: capability first, then process, then the two questions almost nobody asks that decide what happens when the relationship ends. ## The 12 questions to ask a Webflow agency 1. **Can you show me live SaaS sites with real results, not just a screenshot?** Ask for URLs you can visit today, not a case-study PDF. Open them, check they still run on Webflow (view page source and look for Webflow's own class-naming conventions), and ask what changed after launch — traffic, demo requests, load time. A good answer names a specific number with a caveat attached. A bad answer stays qualitative: "clients loved it." 2. **What do the first two weeks actually look like?** Vague answers here ("we'll kick off with discovery") predict a vague project. A team that's done this before can tell you, day by day, what they need from you and what you'll see back — content audit, sitemap, first Figma pass, whatever their actual sequence is. 3. **Who exactly works on our project, and is any of it outsourced?** Industry vetting guides for Webflow hiring flag this as one of the most common complaints: a senior person runs the sales call, then execution quietly moves to a subcontractor the client never meets. Outsourcing itself isn't a red flag — plenty of good work gets built that way — but not disclosing it is. Ask directly who touches the build. 4. **How do you protect our SEO during a rebuild or migration?** This should produce a specific list without prompting: redirect mapping for every existing URL, metadata carried over (not regenerated from scratch), a pre-launch crawl, and a monitoring window after the domain switches. If they haven't done a migration before, that's fine to hire for — but they should say so rather than improvise it live on your domain. 5. **How do we edit the CMS ourselves after launch?** You should get a real answer about which fields are editable without touching layout, and ideally a short walkthrough or Loom before final payment — not "it's all in Webflow, you'll figure it out." 6. **What integrations have you actually shipped?** HubSpot, Salesforce, a booking tool, analytics and consent tooling — ask for one they've done, not one they're confident they could do. Integration work is where estimates go wrong most often, so past experience with your specific stack is worth more here than anywhere else in the call. 7. **How do you scope and price, and what triggers a change order?** Scope creep — the slow expansion of a project past what was quoted — is one of the most consistently cited reasons fixed-fee Webflow projects blow past budget and deadline. A good agency can tell you, before you sign, exactly what counts as in-scope revisions versus a billable change. If the answer is fuzzy now, it will be fuzzier three weeks into the build. 8. **What's the most common reason your projects run late?** This is a trap question in a useful way. An agency that's honest says something specific and usually points partly at clients — slow content delivery, delayed approvals, scope changes mid-build. An agency that blames only external factors, or claims they're never late, is telling you how they'll handle it when your project runs long. 9. **What does post-launch support cost, and what does it cover?** Get this in writing, including the boring parts: is a broken third-party embed covered, or only Webflow-native bugs? What happens after a Webflow platform update if a custom code block breaks — sites with heavy custom code have a real, non-trivial chance of something shifting after any given platform release. Separately, ask what your own ongoing Webflow bill looks like: hosting plan, any ecommerce transaction fees, and what happens if traffic outgrows your bandwidth tier. These numbers should come from the agency unprompted, not surface for the first time on an invoice after launch. 10. **How will we know the rebuild actually worked?** Listen for a plan to track specific numbers — conversion rate, page speed, organic impressions — against a pre-launch baseline. "You'll just see the difference" is not a measurement plan. 11. **Do we own the Webflow Workspace and account — not just the site?** This is the question every other "questions to ask" list skips, and it's the one that matters most if the relationship ever ends badly. Per Webflow's own Help Center: if your site is built inside the agency's or freelancer's Workspace, that Workspace owns the site, and you don't automatically get the right to transfer or duplicate it unless that's explicitly agreed in advance. Webflow states plainly that if the agency becomes unreachable, it cannot transfer their account or export the site to you on its own. That's not a hypothetical — it's the documented mechanism. Ask, specifically: which Workspace will this be built in, what's the transfer procedure at project end, and who holds the site plan's billing? We wrote a full breakdown of the ownership mechanics — Workspaces, seats, and the transfer procedure itself — in our [agency vs. freelancer vs. in-house comparison](https://www.flowhivedigital.com/insights/webflow-agency-vs-freelancer), since it applies whichever route you choose. 12. **Why do clients leave you?** Every agency has lost a client. The ones worth hiring can say why without spin — a mismatch in scope, a client who needed faster turnaround than the agency's model supports, a fair disagreement on process. If the honest answer is "we've never lost one," that's not a strength; it's an agency that hasn't been asked hard enough. ## Red flags that should end the call **Table 1:** Red flags that should end the call Red flag Why it matters A fixed quote within 48 hours with no discovery call Accurate pricing needs to know your CMS structure, integrations, and content volume first No live sites they'll let you visit Portfolio screenshots can be staged; a live URL can't The senior person on the sales call disappears after signing Ask by name who's actually building, not just who's selling No clear answer on Workspace or account ownership If this gets deflected or waved off as "standard," treat it as the answer Vague or missing post-launch support terms If it's not written down before you sign, assume it doesn't exist after you pay ## A quick scorecard for comparing quotes Score each agency 1–5 on these five criteria after the call, before you look at price. It keeps a strong sales pitch from outweighing a weak process: 1. Specificity of the first-two-weeks answer 2. Clarity on who does the actual build work 3. Concreteness of the SEO/migration plan 4. Whether ownership and transfer terms were volunteered, not just answered when pressed 5. Whether post-launch cost and scope were quantified in writing ## Bring these questions to us too We answer all 12 of these on every discovery call, including the ownership one — because we'd rather lose a prospect over an honest answer than win one on a vague one. See recent builds on [our work](https://www.flowhivedigital.com/work), check our own numbers on [pricing](https://www.flowhivedigital.com/pricing), or [tell us about your project](https://www.flowhivedigital.com/contact) and ask us the hard version of every question above. Want to ask us the hard version of these questions? We answer all 12 on every discovery call, including the ownership one. [Tell us about your project](https://www.flowhivedigital.com/contact)[Check our pricing](https://www.flowhivedigital.com/pricing) ## FAQ What happens if my Webflow agency goes out of business or disappears? If the site and account sit in their Workspace, Webflow's own documentation says it cannot transfer the account or export the site to you unilaterally — you're dependent on the agency staying reachable and cooperative. The fix is structural, not contractual: insist the build happens in a Workspace you own, with the agency added as a collaborator, from day one. Should these questions be a conversation, or written into the contract? The load-bearing ones — ownership and transfer, pricing and change-order triggers, post-launch support scope — belong in the statement of work, not just the sales call. A verbal answer is easy to forget once the project is underway. How many agencies should I actually interview? Two or three is usually enough to compare answers meaningfully without dragging out the decision. Use the scorecard above on each one and compare notes side by side rather than trusting your memory of the first call by the time you reach the third. Is a freelancer safer than an agency on the ownership question? Not automatically — the same Workspace mechanics apply to either. It comes down to whose Workspace the site is built in, not whether the vendor is a solo freelancer or a team. Our [agency vs. freelancer comparison](https://www.flowhivedigital.com/insights/webflow-agency-vs-freelancer) goes through when each option actually makes sense. How much should I expect to pay, and how do I compare quotes fairly? Pricing varies enough by scope that we've written a separate guide with real ranges and a quote-comparison checklist: [how much a Webflow agency costs](https://www.flowhivedigital.com/insights/webflow-agency-cost). Use it alongside the scorecard above — price only means something once you know what you're actually comparing.