TL;DR
Judge agencies on live sites, not portfolios. Ask how they handle messaging, CMS structure and redirects - vague answers there mean vague builds. Compare quotes by scope, never by number. And read the contract for ownership: the Webflow workspace, design files and content should all end up yours. The full checklist is below, in the order we would run it.
Why B2B SaaS teams get this wrong
Most agency selection comes down to two things: a nice portfolio and a price. That is how teams end up with a beautiful site that does not book demos, or a cheap build that quietly leaks rankings when it replaces an old site. The parts that decide whether a Webflow project succeeds - positioning, CMS structure, SEO at build time, ownership - are invisible in a portfolio and only surface if you ask.
So this is a list of what to ask, and what good answers sound like. We build these sites ourselves, so we are also telling you what we would be asked - use it on us too.
1. Check live sites, not mockups
- Open the actual URLs in their portfolio on your phone, not screenshots.
- Test the sites on 3G-speed throttling if you can - a slow site means weak builds.
- Check one site in Google with site:agencyclient.com - is it indexed and does it have clean titles?
- Ask what happened to the sites that are not in the portfolio anymore.
2. Interrogate the process, not the pitch
- Ask how they handle discovery - agencies that start with design skip positioning.
- Ask who writes the copy. 'You provide the copy' is where most projects stall.
- Ask for a week-by-week plan before signing, with named checkpoints for your feedback.
- Ask what their revision policy is - unlimited rounds usually means the rounds are shallow.
3. Test their SEO depth with three questions
- How do you set up metadata and OG images across a CMS collection? (They should describe template-level fields.)
- How do you handle redirects when replacing an old site? (The answer should include a 301 map.)
- How do you structure headings and internal links? (One H1 per page, intentional linking - not 'we install an SEO plugin'.)
4. Pressure-test the pricing
- Ask what is explicitly NOT included - integrations, migration, content, stock imagery, extra pages.
- Ask how they price change requests after the quote.
- Compare quotes by scope, not number: a $4k quote with no SEO or CMS structure is more expensive than an $8k one that ships complete.
- Ask about post-launch support: is there a retainer, and what does it cover?
5. Read the contract for four things
- Ownership: Webflow workspace, design files and content transfer to you at handover.
- Handover: documented CMS so your team can edit without the agency.
- Timeline with a defined scope - and what happens if either side slips.
- Exit terms: what happens if you stop working together, including hosting transfer.
Red flags that end the conversation
Any one of these and we would keep looking:
- No live client sites you can actually visit.
- Guaranteed rankings or 'we do SEO' with no structural answer.
- The project stays in their Webflow workspace, not yours.
- Timeline promises under two weeks for a custom site.
- Quotes that exclude responsive QA, redirects or forms.
- They cannot explain Webflow CMS in plain English.
What good looks like: an example
On the Fenderr project, the client came to us with a technical product and a feature-first site. The turning point was not the build - it was step one: repositioning the site around the threat the product removes, giving the page one action, and shipping with technical SEO at 100/100 on Lighthouse. Conversions moved 40% after relaunch. That is the shape of a good engagement: the agency changed the thinking, not just the pixels.
The same applies to our Vizio AI work- messaging first, then design and build, and the SEO score left at 100/100 with conversions up 33%.
A note on our own answers
If you run this checklist on us: our live work is on the portfolio page, our process and inclusions are on the Webflow service page, and you own the Webflow workspace, the Figma files and every word of content at handover. We quote fixed prices with a week-by-week plan, and we will tell you when a freelancer or a template would serve you better.
Vet a Webflow agency: FAQs
How many Webflow projects should an agency's portfolio show?+
Look for at least 5-8 live sites, not mockups, and check that at least two are B2B or SaaS. Consumer sites and internal tools need different conversion logic. If the portfolio is mostly Dribbble-style concept shots with no live URLs, treat the agency as unproven.
What should a Webflow agency quote include?+
A fixed price or a clear hourly estimate, page and CMS collection counts, responsive breakpoints covered, SEO setup (metadata, redirects, sitemap), analytics and form setup, testing rounds, and post-launch support terms. A quote that is just a number with 'Webflow website' next to it will grow.
Should the agency handle SEO too?+
Technical SEO at build time, yes - it is part of building a site correctly. Ongoing content SEO is a separate engagement. Be wary of agencies that promise rankings; ask instead how they handle site structure, metadata, redirects and CMS SEO fields, and check whether their own site ranks.
Who owns the Webflow project after launch?+
You should own the Webflow account and workspace, the design source files, and all content. Some agencies keep projects in their own workspace - which means you cannot leave without rebuilding. Agree on ownership and transfer in writing before signing.
What is a reasonable Webflow agency timeline?+
For a 5-8 page SaaS marketing site, 3-6 weeks including discovery, design, build and QA is realistic. Under two weeks means a template with your logo on it; over three months for a marketing site usually means poor process, not more value.
Vetting us? Start with a free audit.
We review your current site - structure, SEO, conversion path - and send a prioritised fix list. It is useful whether or not you ever hire us.