The person on the agency call who pitches your Webflow migration or site build is rarely the person who builds it, and most buyers don't find that out until the contract is signed and the work has already started. 

Marina Filiuhina has seen this pattern from both sides of the table. Before she was managing director at Edgar Allan, she reviewed agency pitches from the client side at Intercontinental Hotels Group (IHG), where senior talent consistently ran the pitch, then handed the build to a team the client had never met.

The pattern she saw was consistent enough to remember years later: agencies would send what she calls "shiny front doors," experienced, polished, senior people to do the talking (and selling); experienced folks who’d then disappear as the project started, leaving the work in the hands of junior associates who didn’t understand the business. It’s as if the pitch and the delivery were two different products, sold as one.

That gap is the single biggest reason enterprise Webflow migrations go sideways after contract signing. And it's fixable, but only if you know to test for it before you sign.

The pitch team is built to win the deal, not preview the delivery team

Every agency pitch is an optimization exercise, and the thing being optimized is winning the deal. That means agencies put their most experienced, most persuasive people in the room, regardless of whether they'll touch the project afterward. Seniority on a pitch call tells you the agency can sell, not who will write the code, manage the CMS architecture, or handle redirect mapping during your migration.

It isn't dishonesty, exactly. It's an incentive structure. But if you don't account for it, you're evaluating the wrong team.

Junior staff without context, not junior staff without skill, is what breaks these projects

Marina's description of what showed up after the ink dried is precise: teams that were "very junior, very new to the business, and didn't really understand the customers." That points to a context problem rather than a competence one. A junior developer often knows Webflow well enough to do the job. What's much harder to backfill mid-project is an understanding of a client’s customers, CMS requirements, and the specific reasons your last site failed.

On a straightforward marketing site, that gap might cost you a few rounds of revisions. On an enterprise Webflow build, however, where architecture decisions made in week two determine whether your AI search visibility holds up 18 months later, it can cost you the project's outcome.

A bait-and-switch pitch happens whenever the makeup of the group that sells you the project is structurally different from the team who build it, a gap that stays invisible until the contract is signed and the work begins.

Asking for the team list already tells you the industry expects this problem

Here's the part that should reassure buyers: you're not being paranoid. Marina points out that clients have requested "the list of team members who will be working on this project" during pitches for a long time, specifically because this mismatch is common enough that experienced buyers have learned to ask. If the request itself has become standard practice, that's evidence the failure it protects against is real and recurring, not a one-off horror story. So you aren’t alone here if you’ve experienced this yourself.

The problem is that a list of names on a slide is easy to produce and easy to game. A name and a title don't tell you whether that person will still be assigned to your account in month three, or whether they've ever worked with a company your size.

Talking to the developer (or UX person, or strategist), not about them, is the only real test

The mechanism that works is procedural, not contractual: ask to speak directly with the person who will build, write, or concept your site, without the account lead steering the conversation. At Edgar Allan, this is standard practice. As Marina puts it, "While you may need a few people that talk to you during the pitch process, very quickly we start bringing the team members to the conversations."

That's the filter. If an agency is comfortable putting a developer or lead in a room with you unsupervised, the relationship between what you saw in the pitch and what you'll get in delivery is real. If every conversation with a technical resource is chaperoned, or the agency stalls when you ask, that's information too.

When you do get that conversation, don't spend it asking about years of experience. Ask what they know about your industry, your customers, or the specific problem you're trying to solve. Tenure tells you they've been doing this a while, not that they understand you. The three questions we'd ask before hiring any WordPress-to-Webflow migration partner start from the same premise: process claims are cheap; direct access to the people doing the work is not.

What this looks like in practice

Before you sign anything, ask for the specific names and roles of who will work on your project, then ask for 15 minutes with the most senior technical person on that list, without your account lead in the room. Come with one question ready: what do you already know about our business or our customers? A strong answer means the agency has done its homework before the contract exists. A vague one is your answer too.

If you want a sense of who's already doing this well, our data-backed rankings of Webflow agencies and our look at the SOC 2-compliant agencies in the Webflow ecosystem are both built around the same idea: the agencies worth shortlisting are the ones whose delivery holds up to the same scrutiny as their pitch.

_{This article grew out of a conversation between Edgar Allan founder Mason Poe and Marina Filiuhina, managing director at Edgar Allan, for the ongoing series, Building the Next Web. It's the same series that's brought us conversations with ourCMO's Josh Webb, Code & Wander's Alessia Sannazzaro, Edgar Allan's own Witt Langstaff, Webflow's Nathan Huening, and more.}